1. E-Business Suite Integration Guide
  2. Involved Party Mapping

Involved Party Mapping

This section is applicable for the Order Compliance and Delivery Compliance flows only.

Default mapping creates involved parties on Oracle Global Trade Management transaction lines based on party types/partner types from sales order, delivery XMLs.

XML path ‘order_line/party/type’ is used for sales order Oracle E-Business Suite XML.

XML path ‘SHOW_SHIPMENT/SHIPMENT/PARTNER/PARTNRTYPE’ is used for delivery Oracle E-Business Suite XML.

Following are covered by default

  • SHIP_FROM
  • SHIP_TO
  • DELIVER_TO
  • BILL_TO
  • END_CUSTOMER
  • INTERMED_SHIP_TO
  • SOLD_TO

This flow doesn’t create the qualifier records (INVOLVED_PARTY_QUAL) on the fly. All of the above party types should be pre-existing as involved party qualifiers in Oracle Transportation Management/Oracle Global Trade Management. For convenience, the above qualifiers were already added to Oracle Transportation Management/Oracle Global Trade Management seed data.

For all of the above types, contacts as well are assumed to be pre-existing in the Oracle Global Trade Management prior to execution of this flow. This flow doesn’t create Oracle Global Trade Management contacts on the fly.

The below note and mapping table are applicable for Order Compliance flow only.

Logic to determine contact for involved parties: Check to see if the Contact Party Number is populated and make that the involved party, if not go to Party Site Number, if not go to Party Number, if not ignore that party completely. If Party Site Number is used, it is appened with “_PS”.

In general, both flows assume that qualifiers, contacts, and locations are all created before invoking the flow. These compliance flows don’t create these records on the fly.

The only exception is the SHIP_FROM party type for the Order Compliance flow. For this type of Oracle E-Business Suite party, default mapping would produce elements GTMLocation, GTMContact with IU as the transaction code. So, these extra elements would create/update contact and location if they don’t exist in Oracle Global Trade Management already.

Following is the mapping table for SHIP_FROM parties.

Mapping table for SHIP_FROM parties

Oracle Global Trade Management Element Oracle E-Business Suite Element (party/type=SHIP_FROM)
GLogXMLElement/Contact/ContactGid/Gid/Xid order_line/ship_from_org_code
GLogXMLElement/Contact/CompanyName order_line/party /name
GLogXMLElement/Contact/LocationGid/Gid/Xid order_line/ship_from_org_code
GLogXMLElement/Location/LocationGid/Gid/Xid order_line/ship_from_org_code
GLogXMLElement/Location/IsTemplate Y
GLogXMLElement/Location/Address/AddressLines

order_line/party/address1,

order_line/party/address2,

order_line/party/address3,

order_line/party/address4
GLogXMLElement/Location/Address/City order_line/party/city
GLogXMLElement/Location/Address/PostalCode order_line/party/postal_code
GLogXMLElement/Location/Address/ Province order_line/party/state_or_province
GLogXMLElement/Location/Address/ CountryCode3Gid/Gid/Xid order_line/party/country/@code