Overview of the Customer Order Sync Sterling Order Management System Software to JDA Demand and Workforce Management process flow

In the Customer Order Sync Sterling Order Management System Software to JDA Demand and Workforce Management process flow, Sterling Order Management System Software sends completed Customer Orders to the JDA Demand and Workforce Management components, which converts the Customer Orders to history records and uses the records to forecast customer demand, inventory capacity, and labor costs.

The Sterling Order Management System Software system interacts with JDA through JMS queues and functions that are supplied by the integration. Use the integration properties file at <INSTALL_DIR>/properties/customer_overrides.properties to configure the supplied queues. For more information, see Defining integration properties.

Note: To ensure that only completed orders are picked by the Close Order transaction, modify the Sterling Order Management System Software Sales Order pipeline.

The following diagram and description explain the services for the Customer Order Sync Sterling Order Management System Software to JDA Demand and Workforce Management process flow.

Figure 1. Customer Order Sync Sterling Order Management System Software to JDA Demand and Workforce Management process flow
Customer Order Sync OMS to Demand and Workforce Management flow diagram
  1. Sterling Order Management System Software sends completed Customer Order details to JDA Demand and Workforce Management. Customer Orders are considered completed in Sterling Order Management System Software after the order is shipped to or picked up by the customer.
    Order header and order line details, including seller and channel details for the following types of orders, are required by JDA and are included in the closed Customer Order message that is sent from Sterling Order Management System Software to JDA:
    • Ship to address; Capture online, in the call center, or catalog
    • Ship to address; Capture in store
    • Pick up in store; Capture online, in the call center, or catalog
    • Pick up in store; Capture in store
    • Pick up in store; Capture in another store
    When a completed Customer Order closes in Sterling Order Management System Software, the Sterling Order Management System Software event, CLOSE_ORDER.ON_SUCCESS, is invoked, which then invokes the IBMJDA_CloseOrder_OnSuccess service and the IBMJDA_CloseOrder_OnSuccess_Internal subservice.

    The service converts the closed customer order message to GS1 format and sends the message to a JMS queue that is monitored by an ESB or by 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 message.

    Within JDA, the message is sent to the Demand and Workforce Management components, which converts the customer order details to history records and uses the records to forecast customer demand.

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