Overview of Host/ERP-planned Transfer Orders between Distribution Centers and Stores process flow

In the Host-Planned Transfer Order from Distribution Center (DC) to Store process flow, an external host (or ERP) requests the movement of inventory between enterprise locations. For example, an external host might move inventory between stores or distribution centers when a sale or campaign at a store or online store increases the demand for supplies at another store or distribution center. In this process flow, Sterling Order Management System Software moves the inventory to the store by creating a transfer order and a shipment, confirming the shipment, and creating a receipt against the shipment.

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.

The following diagram and description explain the services for the Host-planned Transfer Order from Distribution Center to Store process flow.

Host-planned Transfer Order from Distrubtion Center to Store flow diagram — Figure 1. Host-planned Transfer Order from Distribution Center to Store process flow

An external host (or ERP) approves a transfer order for the movement of inventory between enterprise locations. The host (or ERP) publishes a transfer order as a GS1 Order for Execution message, which is sent to the following systems through the ESB:
- JDA TMS. The message instructs JDA TMS to create a TMS shipment.
- JDA WMS. The message instructs JDA WMS to create a WMS order.
- Sterling Order Management System Software. Sterling Order Management System Software creates a Transfer Order using the GS1Order message.
  Additionally, the host (or ERP) might cancel or modify the transfer order. In this case, a message to cancel or modify the transfer order is sent to Sterling Order Management System Software.
  Order for Execution messages contain the following DocumentActionCode values, which instruct Sterling Order Management System Software to create, cancel, or modify transfer orders:
  - ADD: This value instructs Sterling Order Management System Software to create the transfer order.
  - CANCEL: This value instructs Sterling Order Management System Software to cancel the transfer order.
  - CHANGE_BY_REFESH: This value instructs Sterling Order Management System Software to make the following modifications:
    - Change attributes in the transfer order
    - Add, remove, or change an order line in the transfer order
    - Change an item ID
  To indicate a series of actions that are required by Sterling Order Management System Software, a message can contain multiple DocumentActionCode values, as shown:
```
 <documentActionCode>ADD/CHANGE_BY_REFRESH</documentActionCode>
```
  When Sterling Order Management System Software receives multiple incoming messages, Sterling Order Management System Software checks the OrderDate element to determine the sequence for processing messages.
  The Sterling Order Management System Software integration server, IBMJDA_CreateHostTransferOrder, fetches the inbound message based on the message selector that is specified on the JMS message header, targetFunctionName=HostTOCreateCancel, and then invokes the following Sterling Order Management System Software services:
  - IBMJDA_HOST_TO_CreateCancel
  - IBMJDA_HOST_TO_CreateCancel_Internal
  The Sterling Order Management System Software and GS1 message mapping file, CreateHostTO.xsl, is in <INSTALL_DIR>/repository/xapi/template/merged/xsl/ibmjda.
JDA TMS creates and tenders a load to transport the Transfer Order shipment. JDA TMS publishes a GS1 Transportation Instruction (Load Plan) message, which is sent to the following systems through the ESB:
- JDA Shipping WMS. The message instructs JDA Shipping WMS to create a carrier move and shipment.
- JDA WMS. The message instructs JDA WMS (or receiving store) to create an expected receipt.
- The host.
- Sterling Order Management System Software. The message instructs Sterling Order Management System Software to create the shipment.
  Note: Sterling Order Management System Software creates the shipment but does not schedule or release the transfer order. To configure this scenario, modify the Transfer order pipeline in Sterling Order Management System Software so that orders move from Created status directly to Included in Shipment without moving through Scheduled and Released.
  
  If JDA TMS cancels or modifies the load, a message to cancel or change the shipment is sent to Sterling Order Management System Software.
  Transport Instruction messages contain the following DocumentActionCode values, which instruct Sterling Order Management System Software to create, cancel, or modify shipments:
  - ADD: This value instructs Sterling Order Management System Software to create the shipment.
  - DELETE: This value instructs Sterling Order Management System Software to cancel the shipment.
  - CHANGE_BY_REFRESH: This value instructs Sterling Order Management System Software to add, update, or delete shipments.
  To indicate a series of actions that are required by Sterling Order Management System Software, a message can contain multiple DocumentActionCode values, as shown:
```
 <documentActionCode>ADD/CHANGE_BY_REFRESH</documentActionCode>
```
  Sterling Order Management System Software creates, cancels, or changes the shipment based on the following Load Change operations:
  - Load re-plan: JDA TMS sends a message that contains the ADD and CHANGE_BY_REFRESH DocumentActionCode values.
  - Load replacement: JDA TMS sends a message that contains the ADD and CANCEL DocumentActionCode values.
  - Load cancel: JDA TMS sends a message that contains the CANCEL DocumentActionCode value.
  - Load merge: JDA TMS sends a message that contains the CANCEL and CHANGE_BY_REFRESH DocumentActionCode values.
  - Load split across replacements: JDA TMS sends a message that contains the CANCEL and multiple ADD DocumentActionCode values.
  - Load split across load re-plans: JDA TMS sends a message that contains the CHANGE_BY_REFRESH and ADD DocumentActionCode values.
When Sterling Order Management System Software receives multiple incoming messages, Sterling Order Management System Software checks the Shipment AdditionalDate element to determine the sequence for processing messages.
The Sterling Order Management System Software integration server, IBMJDA_TI_CreateCancel, fetches the inbound message based on the message selector that is specified on the JMS message header, targetFunctionName=HostTICreateCancel, and then invokes the following Sterling Order Management System Software services:
- IBMJDA_HOST_TI_CreateCancel
- IBMJDA_HOST_TI_CreateCancel_Internal
The Sterling Order Management System Software and GS1 message mapping file, CreateCancelHostTI.xsl, is in <INSTALL_DIR>/repository/xapi/template/merged/xsl/ibmjda.
When the shipment for the transfer order departs the store or distribution center, JDA Shipping WMS publishes shipment details as a GS1 Dispatch Advice message, which is sent to the following systems through the ESB:
- JDA WMS or the receiving store. The message instructs JDA WMS (or the receiving store) to update the expected receipt details.
- The host and JDA TMS. The message provides updated shipment details, such as information about the trailer number, to the host and to JDA TMS.
- Sterling Order Management System Software. The message instructs Sterling Order Management System Software to confirm the shipment. If there are any changes to the shipment, Sterling Order Management System Software changes the shipment and then confirms the shipment.
  The Sterling Order Management System Software integration server, IBMJDA_HOST_DispatchAdvace, fetches the inbound message based on the message selector that is specified on the JMS message header, targetFunctionName=HostTODispatchAdvice, and then invokes the following Sterling Order Management System Software services:
  - IBMJDA_HOST_DispatchAdvice
  - IBMJDA_HOST_DispatchAdvice_Internal
  The Sterling Order Management System Software and GS1 message mapping file, HostTODispatchAdvice.xsl, is in <INSTALL_DIR>/repository/xapi/template/merged/xsl/ibmjda.
When the transfer order shipment arrives at the store or distribution center, the receiving store or JDA WMS publishes the details as a GS1 Receiving Advice message, which is sent to the following systems through the ESB:
- The host. The message instructs the host to create a receipt against the Transfer Order shipment.
- JDA TMS. The message instructs JDA TMS to confirm the delivery.
- Sterling Order Management System Software. The message instructs Sterling Order Management System Software to receive and close the receipt. The message can carry information for one or more order receipts.
  The Sterling Order Management System Software integration server, IBMJDA_HOST_ReceiveOrder, fetches the inbound message based on the message selector that is specified on the JMS message header, targetFunctionName=HostTOReceiveOrder. The integration server invokes the following services:
  - IBMJDA_HOST_ReceiveOrder
  - IBMJDA_HOST_ReceiveOrder_Internal
  The IBMJDA_HOST_ReceiveOrder service passes the message to the IBMJDA_HOST_ReceiveOrder_Internal service, which translates the message by calling the receiveOrder API through the multiAPI call. The Sterling Order Management System Software and GS1 message mapping file, HostTOReceiveOrder.xsl, is in <INSTALL_DIR>/repository/xapi/template/merged/xsl/ibmjda.