4 Integrating JD Edwards EnterpriseOne Procurement with Oracle Transportation Management

This chapter contains the following topics:

Section 4.1, "Understanding Integrating JD Edwards EnterpriseOne Procurement with Oracle Transportation Management"
Section 4.2, "Procurement Freight Request"

4.1 Understanding Integrating JD Edwards EnterpriseOne Procurement with Oracle Transportation Management

The Oracle Transportation Management system delivers robust transportation planning and execution capabilities for manufacturers, retailers, distributors, and third-party logistics providers. The JD Edwards EnterpriseOne Procurement system communicates with the Oracle Transportation Management through the Procurement Freight Request integration point:

Integration Point	Description
Procurement Freight Request	You enter or update the purchase orders. When you run the JD Edwards EnterpriseOne the (R49T100) program to extract the Oracle Transportation Management eligible order lines, the system extracts the purchase order, item, and location information; and generates an XML file which is then transmitted to Oracle Transportation Management when the HTTP post program runs. The system transmits a message to Oracle Transportation Management when a purchase order is entered or any of the key fields are updated on the purchase order. The key fields include: Hold Status. The purchase order is placed on hold or released from hold status. Transactional quantity. Promised delivery date. Requested date. The purchase order is canceled, closed, or reopened. Weight, volume, or unit of measure.

Integration Point

Description

Procurement Freight Request

You enter or update the purchase orders.
When you run the JD Edwards EnterpriseOne the (R49T100) program to extract the Oracle Transportation Management eligible order lines, the system extracts the purchase order, item, and location information; and generates an XML file which is then transmitted to Oracle Transportation Management when the HTTP post program runs. The system transmits a message to Oracle Transportation Management when a purchase order is entered or any of the key fields are updated on the purchase order. The key fields include:
- Hold Status. The purchase order is placed on hold or released from hold status.
- Transactional quantity.
- Promised delivery date.
- Requested date.
- The purchase order is canceled, closed, or reopened.
- Weight, volume, or unit of measure.

4.1.1 Procurement Integration Process Flow

This diagram illustrates the procurement integration process flow:

Figure 4-1 JD Edwards EnterpriseOne Procurement Integration to Oracle Transportation Management (1 of 2

Description of ''Figure 4-1 JD Edwards EnterpriseOne Procurement Integration to Oracle Transportation Management (1 of 2''

Figure 4-2 JD Edwards EnterpriseOne Procurement Integration to Oracle Transportation Management (2 of 2)

Description of ''Figure 4-2 JD Edwards EnterpriseOne Procurement Integration to Oracle Transportation Management (2 of 2)''

4.1.2 Oracle Transportation Management Eligibility and Filter Criteria

This section discusses eligibility and filter criteria for:

Purchase order types.
Purchase order lines.
Document type and line type combinations.
Items.

4.1.2.1 Purchase Order Types

The JD Edwards EnterpriseOne purchase order types that are eligible for processing with Oracle Transportation Management include:

Purchase orders.
Credit orders.
Direct ship orders.
Transfer orders.

Note:

For direct ship orders and transfer orders, it is a good practice to include only one order type in UDC table 49/TP. For example, enter sales transfer order type or procurement direct ship order type but not both. If you include both order types you get two freight requests and two shipments for the same transportation movement of goods.

The JD Edwards EnterpriseOne purchase order types that are ineligible for processing with Oracle Transportation Management include:

Requisition orders.
Blanket orders.
eRequisition orders.
Purchase order quotes.

4.1.2.2 Purchase Order Lines

You determine JD Edwards EnterpriseOne purchase order lines as eligible for processing within Oracle Transportation Management by entering the document type and line type combination into the user-defined code UDC table 49/TP.

The purchase order lines that are eligible for processing within Oracle Transportation Management include:

New order lines on purchase orders that are not sent to Oracle Transportation Management for freight request.
Transportation critical fields modified lines that may or may not have been sent to Oracle Transportation Management.
Canceled, closed or reopened order lines that Oracle Transportation Management received before cancellation, closure, or reopened.
Orders in which the order-line requested dates fall within a specified date and time period as designated by the Procurement Freight Request processing options.
Order lines that include item number, quantity, weight, and volume.

The purchase order lines that are ineligible for processing within Oracle Transportation Management include:

Those previously processed as procurement freight request, unless they are modified again.
Service order lines without item numbers
Lump sum lines without quantity.
Bulk lines.
Text lines.
Kit children.
Lines without weight and volume.
Held order lines.

4.1.2.3 Items

Stock items, non stock items, and kit items are eligible for processing within Oracle Transportation Management. The JD Edwards EnterpriseOne system sends parent kit items to Oracle Transportation Management.

4.2 Procurement Freight Request

This section provides an overview of Procurement Freight Request and discusses:

Procurement Freight Request prerequisites.
Procurement Freight Request process flow.
Procurement Freight Request data processing.
Running the Procurement Freight Request Extract program.
Setting processing options for Procurement Freight Request Extract (R49T100).

4.2.1 Understanding Procurement Freight Request

The Procurement Freight Request process enables the JD Edwards EnterpriseOne system to extract eligible purchase order lines and place them in the Procurement OTM Freight Request Staging table (F49T100), which then enables XML request for transportation planning to Oracle Transportation Management. This occurs when purchase orders have been added or updated within the JD Edwards EnterpriseOne Procurement system.

Apart from newly entered or modified purchase order lines, the JD Edwards EnterpriseOne system also extracts purchase order detail lines that were closed or canceled through other JD Edwards EnterpriseOne applications such as Purchase Order Entry (P4310), Purchase Order Receipts (P4312), and Voucher Match (P4314).

When Oracle Transportation Management receives the freight request lines it creates order base lines for transportation planning. When Oracle Transportation Management receives the closed or canceled status updates, it sets the order base line's release control status to RELEASE CONTROL_CLOSED or RELEASE CONTROL_CANCELED respectively. No further order releasing can be done on this order base line. However, the status change does not affect existing shipments or order releases. If the line is reopened, Oracle Transportation Management receives the transmission to update the release control status on the order base line's RELEASE CONTROL ALLOW_RELEASING. Oracle Transportation Management can then create order releases and shipments because the JD Edwards EnterpriseOne purchase order is reopened.

Note:

When you use any of the JD Edwards EnterpriseOne programs to partial receive, two-way match, close, or cancel the Oracle Transportation Management eligible purchase order lines without the message from Oracle Transportation Management you must access Oracle Transportation Management to manually correct the order base. In other words, if the open quantity on purchase order and the order base differ in some exceptional cases (for example, when a partial purchase order is received without Oracle Transportation Management arranging shipments) Oracle Transportation Management's open quantities may be updated manually to match up with JD Edwards EnterpriseOne.

4.2.2 Prerequisites

These prerequisites apply for Procurement Freight Request. You must:

Set up the parent address book data for all suppliers that the JD Edwards EnterpriseOne Procurement system sends to Oracle Transportation Management.
Ensure that calendars in the JD Edwards EnterpriseOne system are set up such that they mirror the calendar setup in the Oracle Transportation Management system. This setup is based on the ship to and ship from combinations.

Note:
This is optional and only required if the Oracle Transportation Management calendaring system is preferred.
Set up the base weight and volume unit of measure conversions for all items.
Define the purchase order document type and line type combinations in UDC table 49/TP.
Enable system SY49T (Use Transportation Integration Module).

4.2.3 Procurement Freight Request Assumptions

These assumptions apply to the Freight Request integration point:

When closing or canceling a line in JD Edwards EnterpriseOne, the release status for the remaining quantity only is updated in Oracle Transportation Management. If there are open shipments or order releases, you must cancel them manually before the purchase order line is closed or canceled.
The cancel date transmitted to Oracle Transportation Management may not actually reflect the date of the closed or canceled order.
The JD Edwards EnterpriseOne system extracts to Oracle Transportation Management units that are open on the purchase order. In some cases the open quantity in JD Edwards EnterpriseOne may differ from the open quantity in Oracle Transportation Management; especially when reversing an Oracle Transportation Management-eligible purchase order. Check Oracle Transportation Management to make sure the open quantities are correct.
The JD Edwards EnterpriseOne system calculates the weight and volume of the parent kit item by accumulating the weight and volume of all shippable components.
The JD Edwards EnterpriseOne system does not extract services or non-stock line type items that do not have weight or volume associated with the transaction. Thus, the JD Edwards EnterpriseOne system bypasses the purchase order line during Freight Request and does not select it for extraction. However, if a weight and volume is associated with the transaction, the JD Edwards EnterpriseOne system extracts the non-stock or service item.
Order quantities can be expressed in fractional numbers in the JD Edwards EnterpriseOne system; whereas in the Oracle Transportation Management system, order quantities are always expressed as whole numbers. Therefore, the JD Edwards EnterpriseOne system extracts order quantities into the packaged item count as a round up whole number at the time the Freight Request Order Release XML is built.
If the JD Edwards EnterpriseOne system places a purchase order on hold or cancels it after transmitting the freight request, orders are not removed from the order base in Oracle Transportation Management but instead the status is changed to "Hold Releasing" or "Cancel Releasing."
If an order line is eligible for extraction to the Oracle Transportation Management system, the shipment details in the purchase order grid are disabled in the inquiry mode. In the Add mode, if the user enters shipment details such as carrier or mode of transport, the system blanks out those details and, after issuing a warning, disables the grid columns.
In some exceptional cases such as a partial receipt reversal upon over receipts, the quantities may differ between the Oracle Transportation Management and JD Edwards EnterpriseOne systems. Thus, whenever a receipt is reversed, it is necessary to manually check the quantities in both systems to ensure that both systems are synchronized.
The JD Edwards EnterpriseOne system does not receive message transmissions from the Oracle Transportation Management system, except voucher information.
The JD Edwards EnterpriseOne system transmits short item number along with its assigned Branch/Plant to the Oracle Transportation Management system.

You should complete procurement order entry override address changes within the Oracle Transportation Management system after the initial freight request.
There is no programmatic process which prevents the Freight Request program from selecting JD Edwards EnterpriseOne transportation orders or blanket orders. Customers must set up valid UDC values in the UDC 49/TP table to exclude these types of orders.
If a procurement order is created with foreign currency, the staged amount contains unconverted decimals. The XML builder converts the decimals.
The JD Edwards EnterpriseOne system transmits the extended price on the purchase order line to the Oracle Transportation Management system by data mapping to the Declared Value element in the Oracle Transportation Management system.

4.2.4 Procurement Freight Request Process Flow

The following diagram depicts the process flow for the JD Edwards EnterpriseOne to Oracle Transportation Management Procurement Freight Request integration point:

Figure 4-3 Procurement Freight Request Process Flow

Description of ''Figure 4-3 Procurement Freight Request Process Flow''

The process is twofold:

The system filters purchase order header and detail data. This includes purchase order document types, line types, item types, date and time, and a new integration state indicating the state of the order line within the integration process.
Data processing. This includes the retrieval of required data to be mapped to Oracle Transportation Management data, evaluation of suppliers sets to determine ship-to, override address consideration, date/time evaluation, shipping unit of measure processing, item-level shipment compatible consolidation, and credit order processing.

4.2.5 Procurement Freight Request Data Processing

This section discusses data mapping clarifications and data processing:

4.2.5.1 Data Mapping Clarifications

The JD Edwards EnterpriseOne system transmits some data to Oracle Transportation Management at the transactional level, which is freight request execution. This data is not provided as initial master data and includes:

Data	Description
Item Master Data	Oracle Transportation Management receives item descriptions.
Address Book Data	The JD Edwards EnterpriseOne system overrides address book information based upon the override order address information (F4006) or address book effective date (F0116) and sends it to Oracle Transportation Management. The system determines the ship-to address book based on customer sets and sends it to Oracle Transportation Management.
Oracle Transportation Management Calendar ID	The system extracts the Oracle Transportation Management ID for the ship-from and ship-to address book from the new workday calendar setup application.

4.2.5.2 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: Keys of the failed lines. A count of successfully processed lines. The message (0) records processed if none of the selected lines were eligible for processing. The message No Data Selected if the data selection fails.

4.2.6 Running the Procurement Freight Request Extract Program

Select Purchase Order Processing (G49T12), Freight Request.

4.2.7 Setting Processing Options for Procurement Freight Request Extract (R49T100)

Processing options enable you to specify the default processing for programs and reports.

4.2.7.1 Process

1. Transportation Planning Date Range Factor

Indicate the number of days the that system looks forward from the date of procurement freight request execution. The system uses this number to determine the latest requested date that the system exports.

2. Freight Request XML Directory Path

Indicate the path to the location where the release XML document is stored when the system executes Procurement Freight Request.

3. Generate XML files

Specify whether to generate XML documents. Values are:

Blank: Do not generate XML files.

1: Generate XML files.

4.2.7.2 Domains

1. Transportation Planning Domain

Designate the domain in which transportation planning is planned.

Note:

A domain is a unique name that typically identifies a company. The purpose of a domain is to enable you to keep company data separate and secure from other company data in a shared, web-based environment.

2. Location Domain

Designate the domain in which transportation planning locations are stored.

3. Item Domain

Designate the domain in which items are stored.