Delivery Compliance
When an Oracle E-Business Suite delivery is synchronized, a corresponding transaction is created in Oracle Global Trade Management having the same ID as the delivery. For Delivery Synchronization, Oracle Global Trade Management assumes that the related items and parties have been synched and are available in Oracle Global Trade Management. Some of the major fields get mapped to the Oracle Global Trade Management transaction as per the below mapping table:
Oracle E-Business Suite Source | Oracle E-Business Suite Element | Oracle Global Trade Management Element | Details |
---|---|---|---|
SHOW_SHIPMENT_005/CNTROLAREA/SENDER/REFERENCEID | GtmTransaction/ | ||
WSH_NEW_DELIVERIES.delivery_name; VARCHAR2(30) |
SHOW_SHIPMENT_005/ DATAAREA/ SHOW_SHIPMENT/ SHIPMENT/USERAREA/ORACLE.SHOW_SHIPMENT_005.SHIPMENT.USERAREA/ORACLE.DELIVERY_NAME | GtmTransaction/ GtmTransactionGid/Gid/Xid |
Name of the delivery, by default it is the Delivery_id but can be changed to a user defined value. Delivery_name appended with “_D” Ex : 34566_D |
WSH_ITM_SHIPMENT_V.carrier; VARCHAR2(30) | SHOW_SHIPMENT_005/ DATAAREA/ SHOW_SHIPMENT/ SHIPMENT/CARRIER | GtmTransaction/ CarrierCode | e.g. ‘Fedex’ |
WSH_ITM_SHIPMENT_V.transportation_method; VARCHAR2(30) | SHOW_SHIPMENT_005/ DATAAREA/ SHOW_SHIPMENT/ SHIPMENT/ TRANSMETHD | GtmTransaction/ ConveyanceFlag | |
Either Literal or from HZ_CUST_SITE_USES_ALL.site_use_code; VARCHAR2(30)
|
SHOW_SHIPMENT_005/ DATAAREA/ SHOW_SHIPMENT/ SHIPMENT/ PARTNER/ PARTNRTYPE | GtmTransaction/ InvolvedParty/ InvolvedPartyQualifierGid /Gid/Xid |
Partner Types could be: SHIP_FROM, SHIP_TO, BILL_TO, INTERMED_SHIP_TO |
HZ_CUST_SITE_USES_ALL.location VARCHAR2(40) | SHOW_SHIPMENT_005/ DATAAREA/ SHOW_SHIPMENT/ SHIPMENT/ PARTNER/ PARTNER_CODE | GtmTransaction/ InvolvedParty/ ContactRef / ContactGid/Gid/Xid |
Location of the partner, i.e. SHIP_FROM, SHIP_TO, BILL_TO. If SHIP_FROM then it is Warehouse Code ex. M1, CA etc. Oracle Global Trade Management will use Party Number for the contact to match against a pre-existing record |
SHOW_SHIPMENT_005/ DATAAREA/ SHOW_SHIPMENT/ SHIPMENT/USERAREA/ORACLE.SHOW_SHIPMENT_005.SHIPMENT.USERAREA/ ORACLE.SITE_NUMBER |
GtmTransaction/ InvolvedParty/ ContactRef / ContactGid/Gid/Xid
|
GTM will use this Site Number appended with “_PS” for the contact to match against a pre-existing record for Partner Types except SHIP_FROM | |
WSH_NEW_DELIVERY. initial_pickup_date; Date |
SHOW_SHIPMENT_005/ DATAAREA/ SHOW_SHIPMENT/ SHIPMENT/ DATETIME/@qualifier = 'INITIAL_PICKUP' | GtmTransaction/ ExportDate | |
WSH_DELIVERY_DETAILS.requested_qty | SHOW_SHIPMENT_005/ DATAAREA/ SHOW_SHIPMENT/ SHIPMENT/QUANTITY | GtmTransaction/ Remark/ | All the quantities are mapped as GtmTransaction remarks. Qualifier GID is taken as value of the attribute ‘qualifier’, for the QUANTITY element. |
For each ‘SHIPITEM’ inside ‘SHOW_SHIPMENT_005/ DATAAREA/ SHOW_SHIPMENT/ SHIPMENT/’ | This is mapped to the ‘GtmTransactionLine’ element inside ‘GtmTransaction’ | ||
WSH_DELIVERY_DETAILS.delivery_detail_id; Number | USERAREA/ORACLE.SHOW_SHIPMENT_005.SHIPMENT.SHIPITEM.USERAREA/ORACLE.DELIVERY_DETAIL_NUMBER | GtmTransactionLine/ GtmTransactionLineGid/Gid/Xid |
delivery_detail_number appended with “_D” Ex : 237376_D |
MTL_SYSTEM_ITEMS_B.inventory_item_id; NUMBER | DATAAREA/SHOW_SHIPMENT/SHIPITEM /ITEM_ID | GtmTransactionLine /ItemGid/ Gid/Xid |
Inventory Item Identifier mapped as Oracle Global Trade Management Trans Line Item. These items will pre-exist, none are created on the fly. This is the same Item ID used in the Order trans. |
Quantity can be from different sources determined by qualifier. WSH_DELIVERY_DETAILS.requested_qty WSH_DELIVERY_DETAILS.Backordered_Qty WSH_DELIVERY_DETAILS.Ordered_Qty WSH_DELIVERY_DETAILS.Shipped_quantity ; NUMBER WSH_DELIVERY_DETAILS.volume; NUMBER, WSH_DELIVERY_DETAILS.NET_WEIGHT |
DATAAREA/SHOW_SHIPMENT/SHIPITEM /QUANTITY qualifier="ITEM" qualifier=" BACKORDERED "
qualifier=" ORDERED " qualifier=" SHIPPED "
qualifier=" VOLUME " qualifier=" WEIGHT" |
GtmTransactionLine/Quantity |
Attribute ‘qualifier’ is mapped to the ‘QuantityTypeGid/Gid/Xid’ ,
‘VALUE’ is mapped to ‘QuantityValue’ , ‘UOM’ is mapped to ‘UOM’ element of Oracle Global Trade Management. |
SHOW_SHIPMENT_005/ DATAAREA/ SHOW_SHIPMENT/ SHIPMENT/AMOUNT | GtmTransactionLine/ Currency | The Shipment level AMOUNT field is mapped to GtmTransactionLine/ Currency element |
Logic for Transaction Line Hierarchy Implementation
Iterate through each "SHIPITEM" inside "SHIPMENT":
- Check for which "USERAREA/ORACLE.SHOW_SHIPMENT_005.SHIPMENT.SHIPITEM.USERAREA/ORACLE.SHIPITEM.ORDERED_BOM/ORACLE.PARENT_LINE_ID" is not null
- Now for each such element, get "ORACLE.PARENT_LINE_ID" as parent transaction line number & "ORACLE.LINE_ID" as child transaction line number.
- Now iterate again through each "SHIPITEM" inside "SHIPMENT"
- compare "USERAREA/ORACLE.SHOW_SHIPMENT_005.SHIPMENT.SHIPITEM.USERAREA/ORACLE.ORDER_LINE_ID" with parent transaction line number,
- "USERAREA/ORACLE.SHOW_SHIPMENT_005.SHIPMENT.SHIPITEM.USERAREA/ORACLE.DELIVERY_DETAIL_NUMBER" is the parent transaction line ID compare "USERAREA/ORACLE.SHOW_SHIPMENT_005.SHIPMENT.SHIPITEM.USERAREA/ORACLE.ORDER_LINE_ID" with child transaction line number,
- "USERAREA/ORACLE.SHOW_SHIPMENT_005.SHIPMENT.SHIPITEM.USERAREA/ORACLE.DELIVERY_DETAIL_NUMBER" is the child transaction line ID
The default mapping given in the StyleSheetContent ‘DEFAULT_SHIPMENT_COMPLIANCE_STYLESHEET’ is used by the system to generate Oracle Global Trade Management XML for inserting delivery data as Oracle Global Trade Management trade transaction unless it is overridden. The sample EBS and transformed GTM XMLs appears in the Appendix: XML Samples chapter, in the Delivery Compliance section.