Sales Order Confirmation Assumptions

These assumptions apply to the Sales Order Confirmation integration point:

1. If the Ship Confirm (P4205) program processing option is set to not relieve inventory, the system functions to execute pack confirm and the Oracle Transportation Management state flag does not update to SC (ship confirm). The status remains at TA (transportation arranged). Upon quantity change to the order line when the Ship Confirm program is executed, the JD Edwards EnterpriseOne system does not transmit the quantity difference to the Oracle Transportation Management system. Thus the quantity within JD Edwards EnterpriseOne and Oracle differs between the execution of pack confirmation and ship confirmation. The Oracle Transportation Management system is updated with the JD Edwards EnterpriseOne quantity at the time of sales order confirmation.

   If the Ship Confirm program processing option is set to relieve inventory, the JD Edwards EnterpriseOne system executes ship confirm and the Oracle Transportation Management state flag updates to reflect the sales order confirmation (SC) state at the time of sales order confirmation.

   Note: The Inventory Relief flag processing option is located on the Process tab of the Ship Confirm program.

2. The system bypasses the subsystem auto-launch of the Print Invoice program at shipment confirmation or an additional invoice is required for billable freight charges that are not determined until the next integration point transaction of Sales Transportation Confirmation.

3. The Ship Confirm processing option that overrides line types is disabled. This prevents anyone from overriding sales order lines that are set up for interface to the Oracle Transportation Management system.

4. The system holds the staging table records representing the confirmed order lines and actual shipments until all of the order lines that are associated with all pickup stops within an Oracle Transportation Management shipment have been confirmed. At this point the JD Edwards EnterpriseOne system transmits the staging table records to Oracle Transportation Management as an actual shipment message and request for transportation confirmation.

5. For transportation document reference, the JD Edwards EnterpriseOne system transmits the JD Edwards EnterpriseOne shipment number to the Oracle Transportation Management system at sales order confirmation.

6. Dual Unit of Measure:

   • For dual unit of measure items with the DPPO flag turned on and you ship confirm by a secondary quantity that is less than the primary quantity, you must cancel the remaining secondary quantity to transmit it to the Oracle Transportation Management system.

   • For dual unit of measure items with the DPPO flag turned on, the actual weight may not be equal to the weight transmitted to the Oracle Transportation Management system during shipment confirmation.

7. Kit Items:

   • The JD Edwards EnterpriseOne system transmits the kit parent information only to the Oracle Transportation Management system.

   • The only association between the kit component lines and the Oracle Transportation Management shipment is through the kit parent.

   • The Sales Order Confirmation integration point calculates the weight and volume of the kit parent by accumulating the weight and volume of all shipped components.

8. For kits a kit parent item has passed through Freight Request, Transportation Arranged, and shipped entirely at Ship Confirmation. The Sales Order Ship Confirmation integration point confirms the parent kit item and not each component line. The Oracle Transportation Management system only updates the parent item as being shipped.

9. For kits, when line splits occur due to serialized items or multiple shipping locations, the JD Edwards EnterpriseOne system does not disassociate the kit parent and its components. The system accumulates the weight and volume of the components to calculate the weight of the kit parent.

10. During sales order confirmation components may become orphan from the kit parent.