Service Layer Structure

Technology Stack

Catalog Data Sources

The item catalog is primarily maintained in the Bookmaster ERP system on AS400/IBM i and synchronized with external systems.

Key Database Tables:

• Item Master: Core product information (ISBN, title, author, publisher)
• Item Classification: Product categorization and groupings
• Item Templates: Default settings for new products
• Warehouse Item Balance: Stock levels across warehouses
• Special Price Files: Customer-specific pricing

Catalog Services

Data Synchronization

Catalog data is synchronized with external systems through various mechanisms:

Order Input Channels

Order Processing Workflow

Processing Steps:

1. Order Receipt: Orders received via various channels are queued for processing
2. Format Validation: EDI parsing and data structure validation
3. Customer Validation: Customer account verification and credit checks
4. Item Validation: ISBN/product code verification and availability
5. Pricing Calculation: Apply customer-specific pricing and discounts
6. AS400 Integration: Create order in Bookmaster ERP system

EDI Order Processing

Specialized handling for EDI order formats:

Order Interface Tables

Orders are staged in interface tables before AS400 processing:

• OrderInterfaceDetailRepository: Order line items
• OrderInterfaceHeaderSupplementRepository: Order header information
• OrderInterfaceDetailSupplementRepository: Additional line details
• OrderInterfaceBillingRepository: Billing information
• OrderInterfaceTextRepository: Order notes and comments

Acknowledgement Types

Acknowledgement Processing Flow

Processing Logic:

1. Trigger: Acknowledgement triggered when order is successfully created in AS400
2. Data Gathering: Collect order details, customer information, and delivery estimates
3. Format Selection: Determine acknowledgement format based on customer preferences
4. Template Processing: Apply appropriate templates for formatting
5. Delivery: Send via configured delivery method (EDI, email, FTP)

Acknowledgement Templates

Email acknowledgements use Freemarker templates located in src/main/resources/templates/:

Customer-Specific Configurations

Purchase Order Triggers

Purchase Order Processing Flow

Key Processing Steps:

1. PO Generation: System generates purchase orders based on triggers
2. Supplier Lookup: Identify primary and alternate suppliers
3. Format Selection: Choose appropriate format (EDI, email, fax)
4. Approval Workflow: Route for approval if required
5. Transmission: Send to supplier via configured method
6. Tracking: Monitor for acknowledgements and updates

Purchase Order Database Tables

Supplier Communication Methods

Acknowledgement Types

Acknowledgement Processing Flow

Processing Logic:

1. Receipt: Acknowledgement received via configured channel
2. Parsing: Extract structured data from various formats
3. Matching: Match acknowledgement to original purchase order
4. Status Update: Update PO status and delivery dates
5. Exception Handling: Process rejections, changes, and partial accepts
6. Notification: Alert purchasing team of status changes

Acknowledgement Status Types

Shipment Receipt Processing

The system also processes advance ship notices (ASN) and goods receipt confirmations:

• ShipmentReceiptRepository: Tracks incoming shipments
• Automated Matching: Links receipts to purchase orders
• Inventory Updates: Updates stock levels upon receipt
• Quality Control: Manages inspection and acceptance processes

Courier Integration Partners

Collection Request Flow

Automated Workflow:

1. Order Ready: System detects orders ready for shipment
2. Carrier Selection: Choose carrier based on customer, destination, and service level
3. Booking Request: Submit collection request to courier API
4. Scheduling: Receive collection slot and tracking information
5. Label Generation: Generate shipping labels and documentation
6. Dispatch: Update order status and notify customer

Courier Service Management

The CourierService manages all courier-related operations:

Collection Request Configuration

Backstamp Data Sources

Backstamp Processing Flow

Processing Workflow:

1. Status Receipt: Delivery status received from various sources
2. Tracking Match: Match tracking number to original order
3. Order Update: Update order status in AS400 system
4. Customer Notification: Send delivery confirmation to customer
5. Invoice Trigger: Trigger invoicing process if applicable
6. Analytics: Update delivery performance metrics

Delivery Status Types

Proof of Delivery (POD)

The system captures and stores proof of delivery information:

• Digital Signatures: Electronic signature capture
• Photo Evidence: Delivery photos from courier
• GPS Coordinates: Delivery location verification
• Recipient Details: Name and time of person who received
• Delivery Notes: Special instructions or exceptions

Integration with Business Processes

Types of Claims

Claims Processing Workflow

Detailed Process:

1. Claim Initiation: Customer or internal team initiates claim
2. Documentation: Collect evidence (photos, delivery proof, etc.)
3. Investigation: Research order history and determine cause
4. Resolution Decision: Approve/deny claim and determine remedy
5. Credit/Replacement: Process refund or ship replacement
6. Case Closure: Close claim and update customer record

Claims Database Structure

Claim Status Management

Resolution Types

Claims Analytics and Reporting

The system provides comprehensive claims analytics:

• Claims by Reason: Track common claim causes
• Claims by Customer: Identify problematic accounts
• Claims by Supplier: Quality issues by supplier
• Resolution Time: Average time to resolve claims
• Cost Analysis: Financial impact of claims
• Trend Analysis: Claims trends over time

Core API Endpoints

Documentation and Testing

Database Connections

Key AS400 Tables

Core business data tables in the Bookmaster ERP system:

• DSED* Tables: Sales order processing and customer data
• DSPO* Tables: Purchase order and supplier management
• XACTD00P: User management and authentication
• AXI_EVENT: System messaging and notifications

Customer-Specific Integrations

Windows Customers!!!!, Update and Build Commands

Click on axigrate service, stop the service, then exit. As administrator on terminal, cd to to the root of the project and run update.bat. Click on axigrate service again, start the service, then exit.

rem Clean and build the application
@echo off
SETLOCAL

rem Update the axigrate project (branch = master)
git pull

rem Build the axigrate project
mvn clean package spring-boot:repackage

ENDLOCAL

Build Commands

# Clean and build the application
mvn clean spring-boot:repackage

# Run the application
java -jar target/axigrate-0.0.1-SNAPSHOT.jar

# Run with specific profile
java -jar target/axigrate-0.0.1-SNAPSHOT.jar --spring.profiles.active=jbp_jbt

Docker Deployment

# Build Docker image
docker build -t ax-axigrate .

# Run with Docker Compose
docker compose up -d
docker compose logs -f

Environment Profiles

Key Configuration Properties

# Database Configuration
spring.datasource.url=jdbc:as400://hostname:port/library
spring.datasource.username=${DB_USER}
spring.datasource.password=${DB_PASSWORD}

# Scheduling Configuration
sales.inbound.scheduled=true
purchasing.outbound.scheduled=true

# Integration Settings
app.root.dir=/path/to/data/directory
email.smtp.host=mail.company.com