Data Processing
Data processing occurs in these functional areas:
Functional Area |
Comments |
|---|---|
Origin (ship from) Address Book Determination |
The origin (ship from) address book number is derived from the sales order detail business unit (MCU) value. |
Customer Sets |
Sales order customer sets are processed in such a way that the JD Edwards EnterpriseOne system sends either the ship-to or deliver-to address book number designated as the ship-to per customer setup for the sold-to ship-to combination on the sales order. |
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. Accordingly, the system does not assign a shipment number to the order line. However, consideration is required for these order lines at a sales order confirmation such that the order line is assigned a shipment number facilitating its relationship to the other lines on the order. |
Date and Time |
To qualify for processing, the JD Edwards EnterpriseOne request date on the sales order line must fall within a specified Oracle Transportation Management date and time window that is designated in the Sales Freight Request processing options. The sales 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 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 unit of measure and branch/plant to enable a package item designation in Oracle Transportation Management and sends this information to Oracle Transportation Management. |
Currency Code |
Oracle Transportation Management calculates billable freight charges based on the carrier's currency code, and JD Edwards EnterpriseOne calculates currency code conversions when necessary from the carrier currency code to the customer's transactional currency code for the billable freight returned at the Transportation Confirmation integration point. |
Order Release and Ship Units |
At the initial freight request extraction of a sales order line, the JD Edwards EnterpriseOne system creates an Oracle Transportation Management order release ID and order release line ID by concatenating the JD Edwards EnterpriseOne sales order key and sales order line key respectively. The system stores the order release ID and order release line ID in the Sales Order Detail Secondary Tag Table (F49T211). The system also assigns the order release line ID value to the Oracle Transportation Management ship unit and stores its value in the tag table. A JD Edwards EnterpriseOne sales order may contain one or more order releases and each order release has unique transportation critical field values. Also, each new order release assigned within the sales order is created with the concatenation of a next number to the sales order key. |
Credit Order |
Credit order quantities are reversed upon extraction and consolidation. |
Report Output/Error |
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. If the Oracle Transportation Management transmission report reflects that the data received from JD Edwards EnterpriseOne could not be processed, you must make corrections in the JD Edwards EnterpriseOne system and resubmit the data. The sales 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:
|