6 Integrating JD Edwards EnterpriseOne Kit Processing with Oracle Transportation Management

This chapter contains the following topics:

6.1 Understanding Integrating JD Edwards EnterpriseOne Kit Processing with Oracle Transportation Management

The JD Edwards EnterpriseOne system provides accurate kit information in the outbound messages sent in the Freight Request and Sales Order Confirmation integration points. The JD Edwards EnterpriseOne system totals the weight and volume of all kit components to reflect the weight and volume of the kit parent item.

When the system processes a component apart from the kit parent, the system processes the component as a regular sales order line. For example, if the system releases the component from back order without the kit parent, the line becomes eligible to have a freight request created. Likewise, if a component is shipped without the kit parent, the system adds the component to the current shipment and sends it outbound in the Order Release and Actual Shipment XML produced at the Sales Order Confirmation integration point.

6.1.1 Sales Freight Request Export (R49T10) Program

The Sales Freight Request Export (R49T10) program calls a function to accumulate the weight and volume of all components associated with a kit parent and updates the associated sales order detail record (F4211).

6.1.2 Sales Order Confirmation Export (R49T30) Program

The Sales Order Confirmation Export (R49T30) program calls a function to accumulate the weight and volume of all components associated with a kit parent and updates the associated cache and sales order detail records (F4211).

6.1.3 Procurement Freight Request Export (R49T100) Program

The Procurement Freight Request Export (R49T100) program calls a function to accumulate the weight and volume of all components associated with a kit parent and updates the associated purchase order detail record (F4311).

6.1.4 Back Order Release (P42117) Program

The Back Order Release (P42117) program inserts a record into the Sales Order Detail file — Secondary Tag File (F49T211) table when a component line is released from back order without the parent line or left on back order when the parent is released.

During Back order Release the release of the sales order line from back order and the hard commitment of inventory occur in separate phases of the process. This two phase approach may lead to orphaned component and kit parent lines that are both on back order. This occurs when the system releases a component from back order; causing the component to be orphaned from the kit parent. Furthermore, if inventory is insufficient the system places the released line on back order again during the hard commit process.


Note:

The JD Edwards EnterpriseOne system inserts a record into the F49T211 table only if the order type and line type combination has been updated into the 49/TP UDC table.

6.1.5 Shipment Confirmation (P4205) Program

The Shipment Confirmation (P4205) program inserts a record into the F49T211 table when the JD Edwards EnterpriseOne system:

  • Fully or partially confirms component lines without confirming the kit parent.

  • Fully or partially back order component lines without back ordering the kit parent.

  • Leaves partial component lines shippable without leaving the kit parent shippable.

  • Back orders partial component lines without back ordering the kit parent.

Based upon the insertion of the F49T211 records, the JD Edwards EnterpriseOne system functions according to the following conditions:

  • When the Shipment Confirmation program inserts F49T211 records for kit components converted to shipped lines, the JD Edwards EnterpriseOne system flags the F49T211 records with a state flag value of "SC" for subsequent creation of the corresponding Order Release and Actual Shipment messages through the Sales Order Confirmation Export program to transmit the shipped lines to the Oracle Transportation Management system.

  • When the Shipment Confirmation program inserts F49T211 records for kit components converted to packed lines, the JD Edwards EnterpriseOne system flags the F49T211 records with a state flag value of "TA" for subsequent shipment confirmation of the packed line.

  • If the Shipment Confirmation program inserts F49T211 records for back ordered lines, the JD Edwards EnterpriseOne system flags the F49T211 records with a blank state flag value indicating eligibility of the order line for Sales Freight Request program processing upon back order release. The JD Edwards EnterpriseOne system subsequently creates the corresponding Order Release message through the Sale Freight Request Export program to transmit the back order released lines to the Oracle Transportation Management system.

  • If the Shipment Confirmation program inserts F49T211 records for left shippable lines, the JD Edwards EnterpriseOne system flags the F49T211 records with a blank state flag value indicating eligibility of the order line for Sales Freight Request program processing. The JD Edwards EnterpriseOne system subsequently creates the corresponding Order Release message through the Sales Freight Request Export program to transmit these lines to the Oracle Transportation Management system.

  • If a kit parent is unshipped, unpacked, back ordered, canceled, or no longer associated with any of its components, the JD Edwards EnterpriseOne system updates the F49T211 table to enable creation of a message to the Oracle Transportation Management system to delete the kit parent through the Sale Freight Request Export program.

  • If a kit parent is changed by updating the quantity of any component or by not shipping an associated component, the JD Edwards EnterpriseOne system updates the F49T211 table to enable the Sales Order Confirmation Export program to recalculate the kit parent weight and volume.


Note:

The JD Edwards EnterpriseOne system inserts a record into the F49T211 table only if the order type and line type combination has been updated into the 49/TP UDC table.