Integrating JD Edwards EnterpriseOne with Oracle Transportation Management

This chapter provides an overview and discusses:

Activating the JD Edwards EnterpriseOne integration to Oracle Transportation Management.
Setting up transportation planning integration constants.
Setting up cross-reference data.
Setting up shipping document and line type combinations.
Executing outbound transmissions from JD Edwards EnterpriseOne to Oracle Transportation Management.
Executing inbound transmissions from Oracle Transportation Management to JD Edwards EnterpriseOne.
Extracting Master Data.
Assumptions and requirements of the integration process.

Understanding the JD Edwards EnterpriseOne to Oracle Transportation Management Integration

This diagram illustrates the process flow and technology used to successfully import and export data from JD Edwards EnterpriseOne and Oracle Transportation Management:

JD Edwards EnterpriseOne to Oracle Transportation Management Process Flow and Technology

Initially outbound to the Oracle Transportation Management system, you must run the JD Edwards EnterpriseOne programs to extract data from JD Edwards EnterpriseOne. The JD Edwards EnterpriseOne programs write outbound data to a staging table where the data is read and an XML file is generated. Run the standalone Java program to process the generated XML files to Oracle Transportation Management through a HTTP connection. As for the inbound from Oracle Transportation Management to JD Edwards EnterpriseOne, the Oracle Transportation Management system invokes an HTTP post. The application server that listens for the HTTP post validates and authorizes the inbound message and updates JD Edwards EnterpriseOne transmission F49T90 table. All the inbound batch programs parses the information from the F49T90 table into the JD Edwards EnterpriseOne tables.

Activating the JD Edwards EnterpriseOne Integration to Oracle Transportation Management

This section provides an overview of the JD Edwards EnterpriseOne integration to Oracle Transportation Management activation and discusses how to activate the integration.

Understanding the JD Edwards EnterpriseOne Integration to Oracle Transportation Management

Before you can use the features of the JD Edwards EnterpriseOne integration to Oracle Transportation Management, you must activate it within JD Edwards EnterpriseOne. When you activate the integration, the system creates the links between the JD Edwards EnterpriseOne system and the Oracle Transportation Management system. Specifically, you can now transmit information between the two systems.

Forms Used to Activate the JD Edwards EnterpriseOne Integration to Oracle Transportation Management

Form Name	FormID	Navigation	Usage
Work With EnterpriseOne System Control	W99410A	Setup (G49T41), Activate External Transportation Integration	Access forms to activate external transportation integration.
EnterpriseOne System Control - Revisions	W99410B	Select data item SY49T on the Work With EnterpriseOne System Control form, and click the Select button.	Activate the JD Edwards EnterpriseOne Transportation Integration module.

Setting Up Transportation Planning Integration Constants

This section provides an overview of transportation planning integration constants and discusses how to set up transportation planning integration constants.

Understanding Transportation Planning Integration Constants

Transportation planning integration constants are data constants that support the JD Edwards EnterpriseOne to Oracle Transportation Management integration. These constants allow communication and transference of other constant information that is needed between both systems.

Form Used to Set Up Transportation Planning Integration Constants

Form Name	FormID	Navigation	Usage
Transportation Planning Integration Constants	W49T00A	Setup (G49T41), Integration Constants	To set up transportation planning integration constants.

Setting Up Transportation Planning Integration Constants

Access the Transportation Planning Integration Constants form.

Transportation Planning User ID

Specify the user ID to login to the Transportation Planning system.

Transportation Planning Password

Specify the password to use for login to the Transportation Planning system.

Max Number of Transactions

Specify the maximum number of transactions per transmission. This is only applicable to the master data and is used for scalability purposes.

Voucher EDI Document Type

Specify the user defined code (00/DT) that identifies the origin and purpose of the transaction. The document type is the same as the default value used when creating EDI records for inbound voucher interface.

Note. J.D. Edwards reserves several prefixes for document types, such as vouchers, invoices, receipts, and time sheets.

Setting Up Cross Reference Data

This section provides an overview of cross reference data discusses how to set up cross reference data.

Understanding Cross-Reference Data

Cross-referencing static data between JD Edwards EnterpriseOne and Oracle Transportation Management minimizes manual data configuration in both systems. You use the X-Ref Application (P49T01) program to reduce the number of master data uploads. The cross-referenced static data includes:

Country codes.
Currency codes.
Units of measure.
Freight UDC.
Mode of Transport UDC.

Form Used to Set Up Cross-Reference Data

Form Name	FormID	Navigation	Usage
E1 Transportation Planning Cross Reference	W49T01	Setup (G49T41), X-Ref Application.	To set up cross-reference data.

Setting Up Cross Reference Data

Access the E1 Transportation Planning Cross Reference form.

Cross Ref Type

Enter a name for the cross-reference type.

Cross Ref Type Desc

The cross reference description is the default value found in UDC table 49/XR.

E1 Internal Value

Enter a code that exists in the JD Edwards EnterpriseOne system. This code is for cross reference purposes.

External Value

Enter a code which is native to the external system such as Oracle Transportation Management.

Setting Up Shipping Document and Line Type Combinations

This section provides an overview of shipping document and line type combinations.

Understanding Shipping Document and Line Type Combinations

In the JD Edwards EnterpriseOne system you must identify the order type and line type of the order lines that are eligible for processing in Oracle Transportation Management. When you enter a sales order or a purchase order, the system automatically creates an inbound or outbound shipment based on the combination of order type and line type that you define in the UDC table 49/TP, Shipping Document/Line Types. This code is a four-character, alphanumeric code in which the first two characters indicate the order type and the third and fourth characters indicate the line type. The system creates eligible Oracle Transportation Management shipments only for line types on an order that match a value found in the 49/TP UDC table.

Executing Outbound Transmissions from JD Edwards EnterpriseOne to Oracle Transportation Management

This section provides and overview and discusses the outbound transmissions process.

Understanding Outbound Transmissions from JD Edwards EnterpriseOne to Oracle Transportation Management

All outbound transmissions from JD Edwards EnterpriseOne to Oracle Transportation Management are done using a HTTP Post Java program. This program sends all XML files from a file system to Oracle Transportation Management via HTTP Post.

The Outbound Transmissions Process

This diagram illustrates the outbound transmission process:

JD Edwards EnterpriseOne Outbound Transmissions

These specifications apply:

The Java program sends XML formatted files to Oracle Transportation Management via HTTP Post sequentially based upon time.
There are no data validations performed against the XML file.

Examples of directory structure for outbound transmissions are listed in this table:

Structure Example	Description
c:\otm\sales\freightrequest\ready	These are the files that the system has ready to send to Oracle Transportation Management.
c:\otm\sales\freightrequest\processed	These are the files that the system processed.
c:\otm\sales\freightrequest\errors	These are the files that the system did not process.

Note. All successfully processed files have a Transmissions Acknowledgement XML file received from Oracle Transportation Management. This transmission file is stored in processed directory. This file includes the Oracle Transportation Management transmission ID for cross reference purposes.

The program expects an XML configuration file (for example, c:\otm\config.xml) location specified in the Java program. The configuration file contains:
- Connection information. This connection information includes versions, XML encoding, XML schema URL location and Oracle Transportation Management HTTP post servlet and port.
- Oracle Transportation Management userid and password. The system does not perform password encryptions.
- Log file name.
- Time-out settings.

Executing Inbound Transmissions from Oracle Transportation Management to JD Edwards EnterpriseOne

This section provides and overview and discusses the inbound transmissions process.

Understanding Inbound Transmissions from Oracle Transportation Management to JD Edwards EnterpriseOne

Oracle Transportation Management sends XML-formatted data to JD Edwards EnterpriseOne via a HTTP post. The inbound HTTP receive program deployed on an application server listens for this HTTP post, validates it, and updates the JD Edwards EnterpriseOne transmission table (F49T90).

The Inbound Transmissions Process

The following diagram illustrates the JD Edwards EnterpriseOne inbound integration process:

JD Edwards EnterpriseOne Inbound Transmissions

The inbound integration process has three stages:

Stage 1: Oracle Transportation Management to Application Server. Oracle Transportation Management uses HTTP Post to send transmissions to JD Edwards EnterpriseOne. The httpReceive servlet receives the HTTP Post and updates the Inbound Transmissions (F49T90) table and sends an acknowledgement to Oracle Transportation Management confirming transmission receipt into JD Edwards EnterpriseOne. The JD Edwards EnterpriseOne system can process only one transaction in a transmission. Therefore, when setting up external systems in Oracle Transportation Management, limit the number of transactions in a transmission to one. The transmission acknowledgement to Oracle Transportation Management (TransAck XML) document is based on GLogXML-v2001.xsd TransAck schema.
Stage 2: JD Edwards EnterpriseOne transmission table to JD Edwards EnterpriseOne staging tables. The Inbound Transmissions Master (R49T90) program reads the records in the Inbound Transmission table and processes the records in the order received. The Inbound Transmissions Master program:
1. Initializes XML DOM Parser and creates a document.
2. Parses the document, thereby locating the transaction types and calling the appropriate Parser function to process the elements.
3. Deletes the transmission records from the Inbound Transmissions table after successfully extracting records from the Inbound Transmissions table into the staging tables.
  
  Warning! If parsing a transmission fails, the system updates the error code in the Inbound Transmissions table. You can view and delete the transmissions. The JD Edwards EnterpriseOne system does not process the records again. Either these transmission must be sent again from Oracle Transportation Management if the current state has not changed in JD Edwards EnterpriseOne, or the latest transaction must be sent to JD Edwards EnterpriseOne. If transmissions fail to process into the JD Edwards EnterpriseOne staging table, the system does not communicate the failure to Oracle Transportation Management.
Stage 3: JD Edwards EnterpriseOne staging tables to JD Edwards EnterpriseOne transaction tables. After the transmissions are transferred to the staging tables for processing, UBE programs for the integration point processes the records to the JD Edwards EnterpriseOne transaction tables.

For voucher transmissions, when the Inbound Transmissions Master program successfully processes the records, it calls a version of the Inbound EDI Voucher Edit/Create (R47041). For Transportation Arranged and Transportation Confirmation transmissions, when the Inbound Transmissions Master program successfully processes the transactions it calls a version of both the Sales Transportation Arranged Batch Import (R49T20) program and the Transportation Confirmation Batch Import (R49T40) program.

Extracting Master Data

This section provides and overview and discusses

Running the Corporation Extraction program.
Setting the processing options for Corporation Extraction (R49T70).
Running the Locations Extraction program.
Setting the processing options for Locations Extraction (R49T80).

Understanding Master Data Extraction

The diagram represents an overview of the key reference data and the methods to synchronize between Oracle JD Edwards EnterpriseOne and Oracle Transportation Management:

JD Edwards EnterpriseOne Master Data Extraction

The Master Data requirements:

The order in which the Master Data synchronization occurs is as follows:
1. You run the Corporation Extraction (R49T70) program to transmit corporations or parent address book numbers to Oracle Transportation Management.
2. You run the Location Extraction (R49T80) program to transmit carrier master, customer master (ship to and sold to), facilities address book, and supplier information to Oracle Transportation Management.
  
  Note. You create different versions of the Location Extraction program based upon processing options setup. The processing options determine which data the respective version transmits to Oracle Transportation Management.
The system can load locations and carrier information as master data.
Locations are updated on a transactional basis.
Items are created at the time of transaction with the order interface.

Running the Corporation Extraction Program.

Select Periodic Processing (G49T20), Corporations Upload

Setting the Processing Options for Corporation Extraction (R49T70).

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

Domain

Transportation Planning Domain

Designate the domain in which you want to conduct transportation planning.

Generate XML Files

Specify whether to generate XML files.

Blank: Do not generate XML files.

1: Generate XML files.

XML Directory Path

Designate a directory path for XML files. A path is require if you set the Generate XML Files option to 1. The maximum length is 255 characters.

Note. Make sure the path ends with a valid slash for the environment.

Running the Locations Extraction Program.

Select Periodic Processing (G49T20), Carrier Upload

Select Periodic Processing (G49T20), Supplier Upload

Select Periodic Processing (G49T20), Customers Upload

Select Periodic Processing (G49T20), Facilities Upload

Setting the Processing Options for Locations Extraction (R49T80).

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

Process

Transportation Planning Domain	Designate the domain in which you want to conduct transportation planning.
Search Type	Specify the type of address book record to search for. Examples include: C:Customers. TC:Transportation Carriers. V:Vendors.
Generate XML Files	Specify whether to generate XML files. Blank: Do not generate XML files. 1: Generate XML files.
XML Directory Path	Designate a directory path for XML files. A path is require if you set the Generate XML Files option to 1. The maximum length is 255 characters. Note. Make sure the path ends with a valid slash for the environment.

Assumptions and Requirements of the Integration Process

This section discusses assumptions and requirements of the integration process:

Setup Requirements

These actions are required:

Set up parent address book data for address book numbers in JD Edwards EnterpriseOne.
Set up calendars in Oracle Transportation Management. The calendars can mirror JD Edwards EnterpriseOne workday calendars per the sales and purchase order calendar setup.
Set up currency code exchange rates manually in both Oracle Transportation Management and JD Edwards EnterpriseOne.

Item Preference for Options and Equipment

The JD Edwards EnterpriseOne system cannot transmit options and equipment information at the time of Freight Request. You must set up options and equipment information in the Oracle Transportation Management system and apply to applicable transaction with the Oracle Transportation Management system.

Taxes

Oracle Transportation Management calculates taxes based on source and destination. Thus, if a shipment is taxable, the Oracle Transportation Management system uses all of the costs associated with the shipment to calculate the taxes. You can use the Oracle Transportation Management system to calculate both provincial tax and VAT taxes.

Sales Integration

No purge mechanism is provided for the Sales Order Detail Oracle Transportation Management Tag Table (F49T211).

Freight Charges

Manually apply shipment level accessorial charges to shipments in the Oracle Transportation Management system prior to shipment confirmation. The Oracle Transportation Management system returns the accessorial charges to JD Edwards EnterpriseOne as an addition to the estimated freight charges. You must apply any additional charges prior to Transportation Confirmation.

This integration consolidates freight charges (base plus any accessorial and miscellaneous charges). You must access Oracle Transportation Management to view itemized charges for both billable and payable freight charges.

Packing

If the customer is using JD Edwards EnterpriseOne Warehouse Management, this integration does not support any functionality derived from the Carton Detail Information table (F4620). Such functionality includes EPC number generation, carton reorganization, standard pack, and so on.

Time Zones

Time zones are inferred in this integration. The JD Edwards EnterpriseOne system converts the date and time information received from the Oracle Transportation Management system to the equivalent JD Edwards EnterpriseOne date and time.

See Sales Transportation Arranged Assumptions

XML Transmissions

Transactions from Oracle Transportation Management to JD Edwards EnterpriseOne consist of one transaction per transmission. If a transaction within the transmission fails, the entire transmission fails, invoking exit course of actions such as roll back, log errors, and so on. You then have to send the transmission again if needed.

Oracle Transportation Management Domains

This integration handles transmissions from multiple domains by enabling you to set the domain in the extraction UBE.

Transportation Planning User ID	Specify the user ID to login to the Transportation Planning system.
Transportation Planning Password	Specify the password to use for login to the Transportation Planning system.
Max Number of Transactions	Specify the maximum number of transactions per transmission. This is only applicable to the master data and is used for scalability purposes.
Voucher EDI Document Type	Specify the user defined code (00/DT) that identifies the origin and purpose of the transaction. The document type is the same as the default value used when creating EDI records for inbound voucher interface. Note. J.D. Edwards reserves several prefixes for document types, such as vouchers, invoices, receipts, and time sheets.

Cross Ref Type	Enter a name for the cross-reference type.
Cross Ref Type Desc	The cross reference description is the default value found in UDC table 49/XR.
E1 Internal Value	Enter a code that exists in the JD Edwards EnterpriseOne system. This code is for cross reference purposes.
External Value	Enter a code which is native to the external system such as Oracle Transportation Management.