Static Data Assumptions

The sample integration assumes certain implementation specific data will reside in Transportation and Global Trade Management Cloud. This may include:

Units of Measure

The above sample flow (#u30225542__fig_q2j_r4f_mjb) assumes unit of measure codes match one-to-one between Supply Chain Cloud and Transportation and Global Trade Management Cloud. If units of measure differ (i.e. LB vs. lbs), one option is to map them as a Lookup in OIC.

Qualifiers

The FA domain in Transportation and Global Trade Management Cloud includes reference and remark qualifiers to store some of the information coming from Order Management Cloud. For example, there are Order Release Reference Qualifiers for FA.ORDER NUMBER, FA.ORDER LINE NUMBER, FA.FULFILLMENT LINE NUMBER and Remark Qualifiers for FA.PACKING INSTRUCTIONS and FA.SHIPPING INSTRUCTIONS.

Custom Status

The FA domain in Transportation and Global Trade Management Cloud includes custom statuses FA.SENT TO FA INV and FA.SHIP CONFIRM to handle change requests coming from Order Management Cloud. These statuses are used to find the state of the shipment, letting the sample workflow agents handle the change request accordingly.

Custom Events

The FA domain in Transportation and Global Trade Management Cloud includes custom events FA.OR ON SHIPMENT MODIFIED, FA.SHIPMENT ON ORDER MODIFIED, and FA.ORDER RELEASE CONSTRAINTS MODIFIED to handle change requests coming from Order Management Cloud. These custom events are used in the sample workflow to demonstrate one way of handling the change requests.

Currency

The above sample flow assumes currency codes match one-to-one between Supply Chain Cloud and Transportation and Global Trade Management Cloud. Transportation and Global Trade Management Cloud includes both 2-character and 3-character country codes and can be configured to work with either. An OIC lookup table can also be used to translate one code to another.

Locations, Contacts, Service Providers

Locations, Contacts, and Service Providers should be pre-seeded in Transportation and Global Trade Management Cloud, but Locations and Contacts will also be created and updated as part of the compliance screening.

IncoTerms

IncoTerms should be pre-seeded in GTM to sync FOB point coming from Order Management Cloud.

Internal Organization Structure

The Internal Legal Entity, Business Units and Inventory Organizations should be pre-seeded as parties in GTM to sync those coming from Order Management Cloud. Carriers need to be pre-seeded as parties in GTM too if the decision is to send them to GTM from Order Management Cloud. The FA domain includes a LEGAL ENTITY involved party qualifier.