9 Data Requirements and Prerequisites

This chapter covers data requirements, prerequisites, or both for Oracle Transportation Order Management integrations and includes the following sections:

• Section 9.1, "Customer Integration"

• Section 9.2, "Location Integration"

• Section 9.3, "Order Integration"

• Section 9.4, "Order Status Integration"

• Section 9.5, "Product Integration"

• Section 9.6, "Query Transportation Order Itinerary Integration"

9.1 Customer Integration

As a prerequisite, the customer management process integration is not dependent on other processes being run; however, the organization cross-reference must be set up first. See Chapter 10, "Working with Cross-References".

The data requirements for customer process integration are:

• The business units being used must be seeded in all applications and in cross-references.

• Address is required to create an account in Oracle E-Business Suite.

• The address must have Address Line 1, City, State, Country, and Zip Code.

9.2 Location Integration

As a prerequisite, before synchronizing a location, you must synchronize the corresponding parent account to Oracle Transportation Management (OTM).

9.3 Order Integration

The prerequisites are:

• Customer Synchronization. See: Chapter 2, "Process Integration for Customers".

• Location Synchronization. See: Chapter 3, "Process Integration for Location".

• Product Synchronization. See: Chapter 4, "Process Integration for Product".

The data requirements are:

• The customers, locations, and commodity products used in the transportation order must be synchronized before submitting the Order.

• The Verify button can be used in the Siebel transportation sales order to validate that all the data has been appropriately populated.

• Order validation processes are successfully executed before the start of the transportation order integration flow.

• The order rating must be done to determine a rating solution for the transportation order to be submitted.

9.4 Order Status Integration

The prerequisites are:

• In Oracle Transportation Management (OTM) an external system must be defined for element PlannedShipment for the OTM outbound messages to be published.

• Automation agents must be defined in OTM to listen for certain events and trigger the planned shipment out of OTM upon this event taking place, or when the dates or defined statuses are updated on the buy shipment, and to send the Sell Shipment out when its status is set to BILLED_APPROVED.

• The cross-references for the order header and lines are established through order synchronization before this flow.

The data requirements are:

• A buy shipment in OTM is necessary to provide the assigned and moving status values to Siebel.

• A sell shipment has to be invoiced in OTM to send the billed status to Siebel.

9.5 Product Integration

This integration has no specific requirements.

9.6 Query Transportation Order Itinerary Integration

The prerequisites are:

• Location synchronization. See: Chapter 3, "Process Integration for Location".

  Note:

  If the location is used as an origin and destination, then the role type is mandatory in OTM.

• Product synchronization. See: Chapter 4, "Process Integration for Product".

  For the rating query to get the appropriate data from OTM the origin and destination location, earliest pickup time, and latest delivery time for the order should be included. In addition, you must provide commodity to be shipped, number of units to be shipped, weight, and volume.