Overview of the Customer Order Ship by Parcel process flow

In the Customer Order Ship by Parcel process flow, Sterling Order Management System Software creates and sources a Customer Order for delivery to the customer's address, and JDA WMS fulfills the Shipping Order.

The two systems interact with each other through JMS queues and functions that are supplied by the integration. You can use the integration properties file at <INSTALL_DIR>/properties/customer_overrides.properties to configure the supplied JMS queues. For more information, see Defining integration properties.

The following diagram and description explain the services for the Customer Order Ship by Parcel process flow.

Figure 1. Customer Order Ship by Parcel process flow
Diagram for the Customer Order Ship via Parcel process flow
  1. An external system captures a Customer Order for delivery to the customer's address. Sterling Order Management System Software then creates and sources the Customer Order. Sterling Order Management System Software determines that the Shipping Method for the Order is Parcel and creates an Order Release. On release, the ON_RELEASE_CREATION_OR_CHANGE event is invoked, which invokes the IBMJDA_RO_OnCreationOrChange service and the IBMJDA_RO_OnCreationOrChange_Internal subservice. The Order Release is published by Sterling Order Management System Software to a JMS queue monitored by an ESB or JDA. If the JMS queue is monitored by an ESB, the ESB transports the message to a JMS queue that is monitored by JDA. JDA fetches the shipment details from the JMS queue. The WMS creates a WMS Order.

    The Sterling Order Management System Software and GS1 message mapping file, ReleaseOrderOnCreationOrChange.xsl, is in <INSTALL_DIR>/repository/xapi/template/xsl/ibmjda.

  2. After the Order is created, JDA allocates and prepares the Parcel Shipment. Within JDA, WMS publishes Parcel Shipment details to the JMS queue. The JMS queue is monitored by the Sterling Order Management System Software integration server or by the JDA ESB. If the JMS queue is monitored by an ESB, the ESB transports the message to a JMS queue that is monitored by the integration server, IBMJDA_changeShipment. The integration server fetches the inbound message based on the message selector that is specified on the JMS message header, targetFunctionName='CreateShipment' OR 'ChangeShipment'. The integration server invokes the IBMJDA_changeShipment service and the IBMJDA_changeShipment_Internal service to deliver Parcel Shipment details, such as tracking numbers or container IDs, to Sterling Order Management System Software. Sterling Order Management System Software then creates and confirms the shipment and completes the process flow.

    The Sterling Order Management System Software and GS1 message mapping file, changeShipment.xsl, is in <INSTALL_DIR>/repository/xapi/template/xsl/ibmjda.

Note: For scenarios where order lines with different Delivery Methods are sourced from the same store or distribution center, modify the Release Consolidation template to include the DeliveryMethod attribute on the Hub Organization (DEFAULT) and the order's enterprise. By including the DeliveryMethod attribute, you ensure that order lines with different Delivery Methods are included in different Order Releases. To locate the Release Consolidation template, open the Applications Manager and go to Application Platform > Process Modeling > Order Fulfillment > Details > Templates > Release Consolidation.