Data Processing
Data processing occurs in these functional areas:
Functional Area |
Comments |
---|---|
Destination (ship to) Address Book Determination |
The destination (ship to) address book number is derived from the purchase order detail business unit (MCU) value. |
Override Addresses |
If the JD Edwards EnterpriseOne system has designated an override ship-to or deliver-to address in the Order Address Information table (F4006), then the system sends the override address information to the Oracle Transportation Management system. The system also takes the valid address book information from the Address by Date table (F0116) and stages it for transport to the Oracle Transportation Management system. |
Bypassing Order Lines |
The JD Edwards EnterpriseOne system performs bypass processing of order lines with line types that are not eligible to process using the Oracle Transportation Management system or are defined as text. |
Date and Time |
To qualify for processing, the JD Edwards EnterpriseOne request date on the purchase order line must fall within a specified Oracle Transportation Management date and time window that is designated in the Procurement Freight Request processing options. The purchase order line also qualifies for processing if the request date is changed to a date and time that falls outside the parameters of the Oracle Transportation Management date and time window and the Oracle Transportation Management system state flag indicates a previously freight-request processed order line. |
Shipping Information |
The JD Edwards EnterpriseOne system assumes standard unit of measure (UOM) conversions for volume and weight on each order line. The JD Edwards EnterpriseOne system sends this information to the Oracle Transportation Management system. If extended weight and volume are missing, the system bypasses processing the record and send an error message to the work center. The JD Edwards EnterpriseOne system concatenates the item with the transaction UOM to enable a package item designation in Oracle Transportation Management and sends this information to Oracle Transportation Management. |
Currency Code |
The JD Edwards EnterpriseOne system sends the declared value (purchase order extended cost) of the goods to Oracle Transportation Management in the supplier's currency. |
Credit Order |
Credit order quantities and ship from becomes ship to and vice versa are reversed upon extraction. |
Report Output and Error Processing |
Each system, JD Edwards EnterpriseOne and Oracle Transportation Management, is the source by which to review errors generated from each system. Errors from the respective systems are not sent to or received by the other system. However, when JD Edwards EnterpriseOne receives an HTTP post from Oracle Transportation Management and the transmission fails to write to the JD Edwards EnterpriseOne Inbound Transmissions table (F49T90), JD Edwards EnterpriseOne sends the exception information back to Oracle Transportation Management. If the Oracle Transportation Management report indicates that Oracle Transportation Management did not process the data received from JD Edwards EnterpriseOne, you must make corrections in JD Edwards EnterpriseOne and submit the data again. The purchase order lines are not extracted when errors are detected during processing. The freight request process ensures that Oracle Transportation Management-required values are supplied. The system sends an error message to the work center if any values are missing. Upon failure of the freight request process, the system publishes a work center message that identifies the order line key from which the error originated along with the errors responsible for the failure. This report displays:
|