ITM Partner Cookbook

Oracle International Trade Management (ITM) Partner Integration: Specifications
Version Prepared By Control Ref Last Updated : : : : Draft Product Management, Oracle Shipping Execution intlptnrint.rtf 28-Dec-05
Disclaimer: The following is intended to outline our general product direction and is intended for information purposes. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.
Copyright 2006 Oracle Corporation All Rights Reserved
Oracle International Trade Management Partner Integration
Specifications
Contents
Overview.....................................................................................................................................................................1 ITM Process Flow ...................................................................................................................................................1 Major Features ..........................................................................................................................................................3 Interfaces with Partner Application .........................................................................................................................3 Item Synchronization...............................................................................................................................................4 Party Synchronization .............................................................................................................................................4 Export Compliance Screening .................................................................................................................................4 Transaction Documents ...........................................................................................................................................6 Messaging................................................................................................................................................................7 Service Request Grouping .....................................................................................................................................10 Print Queues ..........................................................................................................................................................10 Transaction Delivery .............................................................................................................................................10 User Interface ........................................................................................................................................................10 Message Formats ...................................................................................................................................................17 Scalability Features ...............................................................................................................................................17 Phasing ..................................................................................................................................................................18 Partner Requirements.............................................................................................................................................20 Assumptions .............................................................................................................................................................21 Process Flows ...........................................................................................................................................................22 Item Synchronization.............................................................................................................................................22 Party Synchronization ...........................................................................................................................................23 Order Compliance Screening.................................................................................................................................24 Delivery Compliance Screening ............................................................................................................................27 Appendix A - Item Synchronization Request XML..............................................................................................28 Appendix B - Party Synchronization Request XML ............................................................................................31 Appendix C Order Compliance Request XML..................................................................................................35 Appendix D Export Compliance Response XML ..............................................................................................38 Appendix E Delivery Compliance Request XML ..............................................................................................40 Appendix F Acknowledgements ...........................................................................................................................52 XML Acknowledgement .......................................................................................................................................52 HTML Acknowledgement.....................................................................................................................................52 Appendix G Oracle XML Gateway Setup..........................................................................................................54 Define Transactions...............................................................................................................................................54 Define Trading Partners.........................................................................................................................................54 Appendix H Additional Resources ......................................................................................................................56
Intlptnrint.doc
Oracle Confidential - For internal use only
ii
Specifications
Figures & Tables

Fig 1: International Trade Management Process Flow Diagram .........................................................................2 Fig 2: Oracle ITM Partner Integration - Flow Diagram .........................................................................................3 Fig 3: Integration Flow Diagram along with Overview Messaging .......................................................................6 Fig 4: Item Synchronization Overview Messaging .............................................................................................7 Fig 5: Party Synchronization Overview Messaging ............................................................................................7 Fig 6: Export Compliance for Sales Orders Overview Messaging......................................................................8 Fig 7: Export Compliance for Deliveries Overview Messaging..........................................................................9 Table 1: International Trade Service Request by DTDs.........................................................................................9 Table 2: International Trade Service Response by DTDs ......................................................................................9 Fig 8: ITM Partner Setup Form ............................................................................................................................11 Fig 9: ITM Partner Application User Setup Form................................................................................................12 Fig 10: ITM Adapter Parameter Setup Form........................................................................................................13 Fig 11: Item Synchronization Program Parameters ..............................................................................................15 Fig 12: Party Synchronization Program Parameters.............................................................................................16 Fig 13: Submit Deliveries for Screening Program Parameters .............................................................................17 Fig 14: ITM Services, Integrating Oracle Applications........................................................................................18 Table 3: Summary of ITM Services and Integrating Oracle Applications ...........................................................19 Fig 15: Item Synchronization Integration Flow Diagram.....................................................................................23 Fig 16: Party Synchronization Integration Flow Diagram....................................................................................24 Fig 17: Order Export Compliance - Integration Flow Diagram ...........................................................................26 Fig 18: Export Compliance for Deliveries Integration Flow Diagram ..............................................................28 Fig 19: Item Synchronization Request Message Structure ...................................................................................28 Table 4: Element Description of Item Synchronization Request Message..........................................................29 Table 5: Element description of Control Area Elements of Item Synchronization Request................................30 Fig 20: Party Synchronization Request Message Structure..................................................................................32 Table 6: Element description of Party Synchronization Request Message...........................................................34 Table 7: Element description of Control Area Elements of Party Synchronization request.................................34 Fig 21: Order Compliance Request Message Structure........................................................................................36 Table 8: Element description of Order Compliance Request Message.................................................................37 Table 9: Element description of Control Area Elements of Order Request XML................................................37 Fig 22: Export Compliance Response Message Structure....................................................................................38 Table 10: Element description of Export Compliance Response Message...........................................................39 Table 11: Element description of Delivery Compliance Request Message..........................................................51 Fig 23: Acknowledgement Message Structure (Confirm_BOD_004)..................................................................52
Intlptnrint.doc
iii
Specifications
Overview
International trade requires dealing with the rules, regulation and duties applicable for the products between the countries of trade. The international trade management solutions provide latest information on the country specific rules and regulations along with several other value added tools to manage the international trade effectively. Oracle International Trade Management (ITM) adapter is an open interface, which enables international trade management functionality in Oracle Applications. It is the interfaces gateway to third party ITM applications. It acts as a unified transaction channel for all of the international trade compliance requests originating from Oracle Applications and response originating from the ITM Application. This document is intended to provide an overall understanding of the ITM Partner Integration for the purpose of integrating with the partner ITM application. For any detailed information on setting up the integration in Oracle Applications, please refer to the Oracle Shipping Execution product documentation on metalink (metalink.oracle.com).
ITM Process Flow

The international trade compliance process varies depending upon the exporting and importing countries regulation, the type of goods being traded, the intended end use of the goods, and the quantity and value of the goods. An international trade management solution helps you answers the following questions: Is it legal to sell to/buy from this entity? Is a license required for exporting/importing this product? Are there any special government documents needed for the export/import? How can the customs delays be prevented? What is the total cost for buying/selling the products? The international trade management processes include classifying products and screening orders, determining and applying for required licenses with appropriate Government or regulatory bodies, generating and submitting extensive documentation, managing and minimizing country-specific tariffs and duties, and tracking and tracing shipments across the entire global trading community. Business processes for international trade can be divided into two major categories: 1. 2. Export related Import related
It is important to point out that an international trade involves both of these

Intlptnrint.doc Oracle Confidential - For internal use only 1
Specifications
classifications, i.e. an export from a sellers country is an import to the buyers country and compliance to both is mandatory for a successful business transaction. An effective trade compliance system need to provide a flexible way of performing the compliance functions at several points in the buy and sell process. On the sell side, Sales Orders, Picking and Shipping processes need to have most of the export compliance functions accessible. In case of a compliance issue, the quotes, the orders and the shipments are to be re-evaluated by the compliance users and appropriate decisions to be made in accordance with the compliance policy of the organization. Similarly on the buy side, several different compliance checks are required to be performed at several different points in the process.
International Trade Management: Process Flow

Embargo Country Screening Restricted Party Screening Embargo Country Screening Landed Cost Restricted Party Screening Export License Landed Cost Estimation Document Generation Embargo Country Screening Restricted Party Screening Landed Cost Export License Document Generation
Order Quote
Sales Order
Pick
Pack
Ship
Freight Forwarder/ Consolidator
Customs Clearance
Enter/Edit Item
Enter/Edit Customer
Exports Flow: Sell Side
Item Classification
Embargo Country Screening Restricted Party Screening
Delivery/ Receipt
Requisition/ Requirement
RFQ
Source Selection
Purchase Order
Notification of Shipment
Customs Clearance
Enter/Edit Item
Enter/Edit Supplier Embargo Country Screening Restricted Party Screening Embargo Country Screening Restricted Party Screening Landed Cost Import License Embargo Country Screening Restricted Party Screening Landed Cost Import License Document Generation
Item Embargo Country Screening Classification Restricted Party Screening
Imports Flow: Buy Side
Fig 1: International Trade Management Process Flow Diagram
Intlptnrint.doc
Specifications
Major Features
Oracle International Trade Management adapter is an open interface, which enables international trade management (ITM) functionality in Oracle Applications. It is the interfaces gateway to third party ITM solutions and acts as a unified transaction channel for all of the international trade compliance requests originating from Oracle Applications and response from the ITM Application. The international trade management adapter not only provides a standard mechanism to access trade application but also performs several other value added functions in the process. The ITM adapter is deployable over LAN, WAN or Internet and hence presents a uniform architecture for integration with the partner ITM applications.
Interfaces with Partner Application

Oracle International Trade Management adapter is the interface gateway to partner ITM application from Oracle Applications. A trade management service request may initiate from several functional modules within the Oracle Applications i.e. Oracle Order Management, Oracle Purchasing etc., but all of the module would access the international trade compliance functionality through the adapter. The response from the partner application is communicated back to the functional application. Internet/LAN/WAN
Oracle TCA
Oracle BOM
ITM Application
Oracle Quoting and other Apps
Oracle Order Management Oracle Shipping Execution
Oracle ITM Partner Integration
Oracle Purchasing/iProcurement Oracle Payables
ITM Application
Fig 2: Oracle ITM Partner Integration - Flow Diagram
Intlptnrint.doc
Specifications
Item Synchronization
`Items are classified in the partner ITM application. Oracle ITM Adapter provides the classification service request XML for facilitating the item definition in the partner application. The Item Synchronization request XML contains all the necessary data elements required for classifying items. The partner ITM application provides country specific rules and regulations to help you assign the right classification (e.g. HS code, ECCN for exports from US) for your items. Integrated with Item Master Oracle ITM adapter leverages the item definition in Oracle Bill of Materials for communicating to partner ITM application. The ITM adapter also provides a flexible mechanism for indicating the filtering criteria for items. This allows you to easily specify which items need to be transmitted to the partner ITM application for export classification. The adapter enables the integration with the item master by providing a concurrent program with several user-friendly parameters.
Party Synchronization
Oracle ITM Adapter supports a XML service request to communicate the international trade entities to the partner ITM application. The Party Synchronization XML Request contains all the necessary data elements required for performing export screenings like Restricted Party Screening, Embargo Country Screening etc. The parties may also be stored in the partner ITM application so that they can be rescreened as and when there are updates to these lists. The audit trail of the screenings is maintained in the partner ITM application. Integrated with Customer Master Oracle ITM Adapter leverages the party definition in Oracle Trading Community Architecture for screening the parties for exports. The ITM adapter also provides a flexible mechanism for indicating the filtering criteria for parties. This allows you to easily specify which parties need to be transmitted to the partner ITM application for export screening. The adapter enables the integration with the customer master by providing a concurrent program with several user friendly parameters.
Export Compliance Screening

The ITM adapter supports one combined request i.e. Order Compliance Request XML for all the export related compliance checks for the sales order. These include Restricted Party Screening, Embargo Country Screening, License Determination, Document Generation and other partner supported screening like EPCI etc. The combined request XML contains all the necessary data elements required for all of the export compliance services. The partner ITM application evaluates the transaction (sales order or delivery) for export compliance and responds to Oracle Applications with the overall compliance pass or fail status for each of the order line. The audit trail of the compliance checks is maintained in the partner ITM application.
Intlptnrint.doc
Specifications
Integrated with Oracle Order Management Oracle Order Management (OM) features export compliance check at any point after scheduling in the order line flow. A workflow activity enables flexible integration with the ITM adapter. The ITM Adapters Order Compliance Request XML is utilized to communicate key order line attributes to the ITM application. The ITM application responds with overall compliance Pass or Fail result in the Export Compliance Response XML asynchronously. The ITM adapter and OM integration also highlights automated action based on the overall compliance status. A sales order line is placed on hold if it is identified as noncompliant by the partner application. Integrated with Oracle Shipping Oracle Shipping Execution (WSH) features export compliance screening for deliveries. The ITM Adapters Delivery Compliance Request XML is utilized to communicate key delivery attributes to the ITM application. The ITM application responds with overall compliance Pass or Fail result in the Export Compliance Response XML asynchronously. The ITM adapter and WSH integration also highlights automated action based on the overall compliance status. When compliance is requested for a delivery through the ITM adapter, an exception preventing ship confirmation is logged automatically. A compliance pass response removes the exception and enables the delivery for ship confirmation. Deliveries can be submitted for export compliance screening once prior to ship confirmation and again at ship confirm. The shipping integration also provides flexibility for users to designate the severity on the seeded exception.
Intlptnrint.doc
Specifications
Transaction Documents
Oracles adapter supports communication with partner applications via XML. The following diagram reflects the service requests (and direction) the Oracle adapter is designed to support in this phase:
Legend 1 - Item Synchronization Request XML 2 - Party Synchornization Request XML 3 - Order Compliance Request XML 5 - Delivery Compliance Request XML 4,6 - Export Compliance Response XML A1 - Acknowledgment from ITM Application A2 - Acknowledgement from Oracle Applications
Item Master
Customer Master
Sales Order
Delivery
Oracle Applications
(Oracle BOM)
(Oracle TCA)
(Oracle Order Mgt.)

Oracle ITM Adapter
(Oracle Shipping Execution)
Oracle XML Gateway

1
A1
2
A1
3
A1
A2
A1
A2
LAN/WAN/Internet
ITM Application XML Adapter
Partner ITM Application
Create / Update Product

Product Classification
Create / Update Partner

Trade Party Screening
Export Compliance Determination
Send XML Response

Compliance=Pass/Fail
Export Compliance Determination
Send XML Response

Compliance=Pass/Fail
No
Compliant?
Yes
No
Yes
Compliant?
Yes
Yes
Generate Documents?
Compliance User Review
Compliant?
No
Compliance User Review
Compliant?
No
Fig 3: Integration Flow Diagram along with Overview Messaging
Each service request maps to an XML message that the Oracle Adapter supports. For example, a request for export screening for sales orders is supported by the Order Compliance Request message. The XML response to the Order Compliance Service Request is termed as Export Compliance Response message. A separate DTD is provided for the response message.
Intlptnrint.doc
Specifications
Messaging
The ITM adapter supports XML based synchronous and asynchronous communication capabilities with the partner ITM application. The partners trade management application must be able to provide a web-based listener that accepts an XML request message from the adapter and provides synchronous acknowledgement. Item Synchronization The purpose of the Item Synchronization service request is to communicate key transaction and setup entities required for Item Synchronization in the partner ITM application. A synchronous XML acknowledgement in the specified format is expected from the partner application. The request DTD, its structure and element description is provided in Appendix A. The acknowledgment XML details are provided in Appendix F. Internet/LAN/WAN
Item Synchronization Request XML
Oracle Bill of Material
Oracle ITM Adapter
Synchronous Acknowledgement
Fig 4: Item Synchronization Overview Messaging Party Synchronization The purpose party synchronization service request is to communicate key transaction and setup entities required for party based screenings in the partner ITM application. OAGs 007_sync_customer_005.dtd (Revision 7.2.1) DTD is used for the request XML. A synchronous XML acknowledgement in the specified format is also expected from the partner application. The request DTD, its structure and element description is provided in Appendix B. The acknowledgment XML details are provided in Appendix F. Internet/LAN/WAN
Party Synchronization Request XML
Oracle TCA
Oracle ITM Adapter
Fig 5: Party Synchronization Overview Messaging
Intlptnrint.doc
Specifications
Order Compliance Screening The purpose of order compliance request is to communicate key transaction and setup entities required for export compliance screenings in the partner ITM application for sales orders. The request is designed to support all the relevant attributes to perform all the export compliance checks. The request DTD, its structure and element description is provided in Appendix C. A synchronous acknowledgement is expected for the request XML. The acknowledgment XML details are provided in Appendix F. The partner ITM application responds with an overall export compliance status for the order line via Export Compliance Response XML asynchronously. A synchronous HTML acknowledgment is provided by the Oracle XML gateway on receiving the response XML. Additionally, Oracle XML Gateway can be setup to provide an XML based asynchronous acknowledgement. The response DTD, its structure and element description is provided in Appendix D. Internet/LAN/WAN
Order Compliance Request XML Generic Export Compliance
Oracle Order Management
Oracle ITM Adapter

Asynchronous Exp. Comp. Response XML
Oracle XML Gateway
Synchronous HTML Acknowledgement Optional Asynchronous XML Acknowledgement
Fig 6: Export Compliance for Sales Orders Overview Messaging
Delivery Compliance Screening The purpose of delivery compliance request is to communicate key transaction and setup entities required for export compliance screenings in the partner ITM application for delivery. The request is designed to support all the relevant attributes to perform all the export compliance checks. The request DTD, its structure and element description is provided in Appendix E. A synchronous acknowledgement is expected for the request XML. The acknowledgment XML details are provided in Appendix F. The partner ITM application responds with an overall export compliance status for the order line via Export Compliance Response XML asynchronously. A synchronous HTML acknowledgment is provided by the Oracle XML gateway on receiving the response XML. Additionally Oracle XML Gateway can be setup to provide an XML based asynchronous acknowledgement. The response DTD, its structure and element description is provided in Appendix D.
Intlptnrint.doc
Specifications
Internet/LAN/WAN
Delivery Compliance Request XML Generic Export Compliance
Oracle Shipping Execution
Oracle ITM Adapter

Asynchronous Exp. Comp. Response XML
Oracle XML Gateway
Synchronous HTML Acknowledgement
Optional Asynchronous XML Acknowledgement
Fig 7: Export Compliance for Deliveries Overview Messaging
Table 1 and Table 2 below summarizes each the ITM service request and its corresponding request and response XML messages:
Request DTDs Supported International Trade Service Request Item Synchronization Party Synchronization Order Export Compliance Delivery Export Compliance DTD Item Synchronization Request XML Party Synchronization Request XML Order Compliance Request XML Delivery Compliance Request XML DTD Details Appendix A Appendix B Appendix C Appendix D
Table 1: International Trade Service Request by DTDs
Response DTDs Supported International Trade Service Response Export Compliance Response DTD Export Compliance Response XML DTD Details Appendix E
Table 2: International Trade Service Response by DTDs
Intlptnrint.doc
Specifications
Service Request Grouping

The ITM partner integration provides a user configurable parameter for bundling a group of request together in a single XML message. In the case of sales order integration, a response is expected for each of the order line. For shipments, a response is expected for each delivery. The partner ITM application may also group several individual responses in a single XML message with individual responses for each transaction reference.
Print Queues
The trade documents are generated, printed and delivered in the partner ITM application. All the printing related tasks including printer/format determination are managed by the partner application. The document audit trail is also maintained in the partner application.
Transaction Delivery
Both secured and unsecured transaction delivery methods are supported. Oracles Adapter supports standard http as well as secure (SSL) connections over https to the partners trade management server.
User Interface
Oracles Adapter can be configured for the outbound messages forwarded to the partner application. The ITM Adapter provides user interface for defining the necessary and optional attributes. The attributes can be defined at several levels including ITM Application, Service etc. A service request XML includes the relevant attributes for the ITM service. The following forms are provided: ITM Partner Setup Form The form provides for setting up the preferences for the partner ITM application and supported services. The ITM application level setup include: ITM Application Vendor/Service Provider Name Contact Name Contact Email Vendor URL Name-Value pairs of parameters (Each ITM application may have multiple parameters e.g. Request Version, Request Language)
Intlptnrint.doc
10
Specifications
The following fields are provided for a service in the ITM application: Service Type URL Port Protocol (HTTP/HTTPS) Certificate (for Secure HTTS) Certificate Store Certificate Password Service Priority Name-Value pair of parameters (Each service will have multiple parameters e.g. Service Handler, Service Version, Threshold)
Fig 8: ITM Partner Setup Form Partner ITM Application User Preferences A set up form is provided for users of Oracle Applications to store their trade management application login information. Oracle Applications customers or Oracle Exchange operators will be able to store their third party trade application user ID and
Specifications
password using this form. An Oracle Application User/Organization may have a User ID/password for the entire company/operation, at a organization level or at a application user level.
Fig 9: ITM Partner Application User Setup Form ITM Adapter Middle Tier Parameters Each partner application that communicates with Oracles Adapter must pass the appropriate content to the adapter. The following list includes all of the mandatory and optional parameters:
Intlptnrint.doc
Output Directory Log file Directory Set Proxy Proxy Host Proxy Port Polling Frequency Task Size Maximum DB Connections Minimum DB Connections DB Connection Timeout DB Connection Idle Time Minimum Threads
Oracle Confidential - For internal use only 12
Specifications
Maximum Threads Maximum Resubmits on Error Thread Maximum Idle Time Queue Polling Interval
Fig 10: ITM Adapter Parameter Setup Form ITM Error Classification Form The adapter provides the Oracle Application users to classify the error responses from the partner application. The feature provides the ability for user configurable actions when the errors are encountered. The errors may be classified into system error, data error and successful. The following fields are provided in the ITM Error Classification form: ITM Application/Service Provider Name Error Type Error Code Classification
Adapter Administration User Interface

The adapter administration functions are implemented as a standard concurrent request in
Specifications
Oracle Applications. This enables all the administration tasks for the adapter to be completed from within the Oracle Applications. The following adapter administrative tasks are implemented:
Adapter Startup The processing engine in the adapter need to be active before any trade service request can be fulfilled. The program ensures that proper environment variables are set and processes have been started. Adapter Status Report This program verifies the status of the adapters processing engine and also provides other valuable information about the pending requests, errors encountered etc. Skip/Resubmit Service Request The program allows skipping of service requests in the adapter request queue. These service requests may be submitted by the calling applications and are either waiting in the queue, or might have encountered errors in getting a response from the trade application. The program can be submitted with several parameters including Error Type, Error Code, Customer, Ship From, Ship-To etc. Adapter Shut Down
Similar to Adapter Startup, the program is used to shut down the adapter engine.
Batch Programs The following batch programs are provided to support the partner integration: Items Synchronization Item Synchronization program lets you select and send inventory item definitions to partner ITM application for export classification. Additionally the filtering criteria can be defined in a custom PL/SQL package.
Intlptnrint.doc
14
Specifications
Fig 11: Item Synchronization Program Parameters
Party Synchronization Party Synchronization lets you select and send party definitions to partner ITM application. Additionally the filtering criteria can be defined in a custom PL/SQL package.
Intlptnrint.doc
15
Specifications
Fig 12: Party Synchronization Program Parameters
Submit Delivery for Export Screening Submit deliveries for export screening lets you submit deliveries for compliance screening to partner ITM application. The program offers a range of parameters to select the appropriate deliveries for screening. Additionally, a filter criterion can also be defined in a custom PL/SQL package.
Intlptnrint.doc
16
Specifications
Fig 13: Submit Deliveries for Screening Program Parameters
Message Formats
Oracles Adapter supports XML-based communication with the partners trade management application. Oracle XSU and XSLT are used for XML request generation and maintenance.
Scalability Features
Oracles Adapter leverages a multi-threaded Java based middle-tier. It supports interface scanning, polling request batch mechanism, task queuing and a thread pool with configurable worker threads. All the components of the middle-tier are configurable to suit the throughput requirements and hardware constraints of the installation site. The adapter also features Database Connection Pool for efficient management of database resources.
Intlptnrint.doc
17
Specifications
Middle-tier Configuration Screen.
Phasing
Supporting the international trade services in key business flows involve developing the generic integration capabilities for individual ITM services as well as embedding the ITM services in the core transaction application. The ITM adapter plans to support access to several international trade services individually as well as combined together in a single request. These services can be embedded seamlessly into multiple Oracle Applications. Oracle Applications development has taken a phased approach in providing these capabilities and export requirements are targeted for the current phase. The figure 3 below represents some of the key applications targeted for the initial phase along with the services planned to be supported from the respective application: Internet/LAN/WAN
Oracle TCA
Oracle BOM
Party Synchronization Item Synchronization
Sales/Quotes/Contracts and other Applications Oracle Order Management
ITM Application
Oracle ITM Partner Integration
Oracle Shipping Execution Oracle Purchasing/ iProcurement
Import Compliance Screening
ITM Application
Import Compliance Screening
Oracle Payables
Phase I Phase II
Fig 14: ITM Services, Integrating Oracle Applications
Oracle Applications development has taken a phased approach in supporting ITM

Specifications
integration with specific Applications. Exports controls are targeted for the current phase. The following ITM services are planned for this phase: Item Synchronization Party Synchronization Export Compliance Screening The table below lists down the integrating Oracle Applications for each of the above ITM services and the business processes they are:
ITM Service/Integrating Oracle Applications Business Processes
Item Synchronization Oracle Bill of Material (BOM) Party Synchronization Oracle Trading Community Architecture (TCA) Export Compliance Screening Oracle Order Management (OM) Oracle Shipping (WSH)
Entry/Update of Items using batch process Entry/Update of Parties using batch process Sales Orders Booking Pick and Ship Processes
Table 3: Summary of ITM Services and Integrating Oracle Applications
Intlptnrint.doc
19
Specifications
Partner Requirements
The following are some of the key requirements for the partner ITM application to be able to integrate with Oracle ITM adapter. Web based Listener Asynchronous/Synchronous XML Response Ability to process inbound request XML in Oracles published DTD Ability to produce a valid response XML in Oracles published DTD
Intlptnrint.doc
20
Specifications
Assumptions
The proposed generic integration with the ITM application is based on the following assumptions: The ITM application supports XML based integration. Oracle ITM Adapter manages all the communication with the partners ITM application. Though the adapter provides an extensible data element support for a specific ITM service, any alterations to the element data size have to be resolved by the partner ITM application. The time to respond to an XML request depends on the performance of the ITM application/service provider. The ITM application would adhere to performance standards thereby facilitating the overall response time for the integration.
Intlptnrint.doc
21
Specifications
Process Flows
Item Synchronization
The ITM adapter generates and transmits the Item Synchronization Service Request XML to the partner application. A synchronous handshake is expected from the ITM application for the sake of acknowledgement. The Item Synchronization request XML contains all the necessary data elements required for export classification. There is no response back from the ITM application after the items are classified. The diagram below represents the Item Synchronization process flow between Oracle Applications and partner ITM application:
Intlptnrint.doc
22
Specifications
Submit Items for Export Classification Program
Any more items in the range

Yes
No
Export Item? (based on filter criteria)

Yes
No
Interface Tables Populated (Oracle ITM Adapter)
XML Generation (Oracle ITM Adapter)
XML Transmission to ITM Application and Receive Acknowledgement (Oracle ITM Adapter)
Receive XML Message and Acknowledge
No
Ack. Received?
Item created/ updated in ITM Application
HS and ECCN needed?
Yes
Notify Compliance User
Yes
No
Oracle Applications
Fig 15: Item Synchronization Integration Flow Diagram
Party Synchronization
The ITM adapter generates and transmits the party synchronization request XML to the partner application. A synchronous acknowledgement is expected from the ITM application. The party synchronization request XML contains all the necessary data elements required for all party based export screenings. There is no response back from the ITM application. If any of the party is determined to be a restricted party in the ITM application, it needs to be handled manually in Oracle Application. All the existing transactions i.e. orders and shipments may need to be canceled manually along with customer de-activation. The diagram below represents party synchronization process flow between Oracle Applications and partner ITM application:
Specifications
Submit Parties for Party Synchronization Program
Any more party in the range
No
Yes
Export Party?(based on filter criteria)
No
Yes
Export Screening in ITM Application
No
Ack. Received?
Restricted Party?
Yes
Party created/ updated in ITM Application
No
Export
Compliance
Yes
User Review
Flag Party as NOT a restricted Party
No
Restricted Party ?
Yes
Manually Inactivate the Party in Oracle
Flag Party as a restricted Party
Oracle Applications
Fig 16: Party Synchronization Integration Flow Diagram
Order Compliance Screening

Booking of a new export order submits an export compliance request to the ITM adapter. The ITM adapter generates and transmits the export compliance service request XML to the partner application. A synchronous acknowledgement is expected from the ITM application. The export compliance request XML contains all the necessary data elements required for all export related compliance checks. The partner ITM application evaluates the sales order lines for export compliance and responds to Oracle Applications with the overall compliance pass or fail status for each of the order line. The export compliance is evaluated individually for each order line. If an order line is found to be compliant by the partner application, it responds
Intlptnrint.doc
24
Specifications
back to Oracle Application with compliant (compliance=Pass) status for the order line. The asynchronous response is received by Oracle XML gateway and a synchronous HTML acknowledgement is provided to the partner application. Oracle XML Gateway can also be setup to provide an asynchronous XML acknowledgement. The XML gateway passes the response information to the ITM adapter, which in turn removes the order line block. If any of the order line is determined to be non compliant (compliance=Fail), the ITM adapter places the sales order line on hold. Users will need to manually cancel these order lines depending upon their business processes. In case, the ITM application is unable to evaluate the compliance of the order line programmatically, the ITM application notifies the compliance users for a manual compliance review. A response is not communicated back to Oracle Application until a final compliance determination is made by the compliance user.
The diagram below represents the export compliance process flow between Oracle Applications and partner ITM application:
Intlptnrint.doc
25
Specifications
Sales Order Line Scheduled (Oracle Order Mgt.)
Oracle Applications
Export Compliance Activity (Oracle Order Mgt.)
Block Order Line Workflow Activity
Run all export rules for the order line
Export Compliance Pass?
No
Export
Compliance
User Review
No
Ack. Received?
Yes
Yes
No
No
Export Compliance Fail?
Remove the Order Line Workflow block
Receive XML Message and Acknowledge (XML Gateway)
Async. XML Response to Oracle (Compliance=Pass) and Receive Acknowledgement
Ack. Received?
Yes
Yes
No
Place the Order Line on Hold
Async. XML Response to Oracle (Compliance=Fail) and Receive Acknowledgement
Ack. Received?
Yes
Fig 17: Order Export Compliance - Integration Flow Diagram
Intlptnrint.doc
26
Specifications
Custom API Callout for Order Screening The following custom APIs are supported for order screening: Pre-processing Custom API A pre-process custom API is provided for order export screening. This API can be used by for any pre-processing and massaging of data in ITMs interface tables. The pre-processing API can also be used to populate additional attributes i.e. the Name and Value pairs provided in the USERAREA of the message. These could be any other attributes, which you may need for export screening and are not provided in the seeded message. API Name: WSH_ITM_CUSTOM_PROCESS.PRE_PROCESS_ONT_REQUEST Post-Processing Custom API A post-process custom API is provided for Order export screening. This API can be used by for any post-processing and massaging of data once its interfaced in ITMs interface tables. This call out is made in WSH_ITM_CUSTOM_PROCESS package. WSH_ITM_CUSTOM_PROCESS.POST_PROCESS_ONT_REQUEST
Delivery Compliance Screening

Export compliance screening may be performed at delivery creation and at Ship Confirmation. When the export compliance is requested for a delivery, an export compliance request is submitted to the ITM adapters interface tables. The ITM adapter generates and transmits the export compliance service request XML to the partner application. A synchronous acknowledgement is expected from the ITM application. The export compliance request XML contains all the necessary data elements required for all export related compliance checks for the delivery. The partner ITM application evaluates the delivery for export compliance and responds to Oracle Applications with the overall compliance pass or fail status for the delivery. The export compliance is evaluated for delivery as a whole. If a delivery is found to be compliant by the partner application, it responds back to Oracle Application with compliant (compliance=Pass) status. The asynchronous response is received by Oracle XML gateway and a synchronous HTML acknowledgement is provided to the partner application. Oracle XML Gateway can also be setup to provide an asynchronous XML acknowledgement. The XML gateway passes the response information to the ITM adapter, which in turn handles the exception, originally logged against the delivery to prevent ship confirmation. If a delivery is determined to be non compliant (compliance=Fail), the ITM adapter logs compliance failure exception against the delivery. Users will need to manually cancel these deliveries depending upon their business processes. In case, the ITM application is unable to evaluate the compliance of a delivery programmatically, the ITM application notifies the compliance users for a manual compliance review. A response is not communicated back to Oracle Application until a final compliance determination is made by the compliance user. The diagram below represents the export compliance process flow between Oracle Applications and partner ITM application:
Specifications
User Submits SRS program Submit Deliveries for Export Screening All the deliveries with Require Export Screening exception selected
Oracle Applications
Any more deliveries? Yes Log Submitted for Export Screening Exception for the delivery
No
XML Generation
XML Transmission to ITM Application and Receive Acknowledgement
Run all export rules for delivery
Export Compliance Pass?
No
Handle Require Export Screening exception
No
Ack. Received?
Yes Yes Ship Hold Release No No
Export Compliance User Review
Interface Tables Populated Handle Submitted for Export Screening Exception for the delivery
Export Compliance Fail?
Async. XML Response to Oracle (Compliance=Pass) and Receive Acknowledgement
Ack. Received?
Yes Generate Documents? No Yes
Yes
Handle Submitted for Export Screening Exception for the delivery
No Log Not Compliant for Export Exception for the delivery Receive XML Message and Acknowledge (XML Gateway) Async. XML Response to Oracle (Compliance=Fail) and Receive Acknowledgement Ack. Received? Yes
Fig 18: Export Compliance for Deliveries Integration Flow Diagram

Specifications
Custom API Callout for Delivery Screening The following custom APIs are supported for order screening: Pre-processing Custom API A pre-process custom API is provided for Delivery Export compliance. This API can be used by for any pre-processing and massaging of data in ITMs interface tables. The pre-processing API can also be used to populate additional attributes i.e. the Name and Value pairs provided in the USERAREA of the message. These could be any other attributes, which you may need for export screening and are not provided in the seeded message. API Name: WSH_ITM_CUSTOM_PROCESS.PRE_PROCESS_WSH_REQUEST
Post-Processing Custom API A post-process custom API is provided for Delivery Export compliance. This API can be used by for any post-processing and massaging of data once its interfaced in ITMs interface tables. This call out is made in WSH_ITM_CUSTOM_PROCESS package. API Name: WSH_ITM_CUSTOM_PROCESS.POST_PROCESS_WSH_REQUEST
Intlptnrint.doc
27
Specifications
Appendix A - Item Synchronization Request XML
The structure of the Item Synchronization request message is illustrated in the following diagram: This diagram illustrates the following attributes of the request message: Hierarchy of Elements Each element is shown as a box in the diagram. Top-to-bottom; left-toright. "Parent" elements are shown with "child" elements below them. Required/Optional elements. A required element is depicted via solid boxes. An optional element is depicted via a dashed line. When an element has attributes or children, it is possible for the (parent) element to be optional, while the child or attribute is required. This indicates that when that (parent) element is present, its required attributes and/or children must also be present Repetition of elements. Two types of relationships are illustrated in this diagram: one-to-one and one-to-many. One-to-one relationships are represented by a single box. One-to-many relationships are represented by multiple boxes.
ITEM_SYNC
CNTROLAREA DATAAREA
Request
Request
ITEM_ID
ITEM
USERAREA
Fig 19: Item Synchronization Request Message Structure
Intlptnrint.doc
28
Specifications
Element/Attribute 1 1.1 1.2 1.3 1.4 ITEM ITEM_ID ITEM_CODE DESCRIPTION HAZARD_CLASS
Description
Oracle Applications Table.Column_name
Unique Identifier of an Item (Inventory_item_id) Product Code. Concatenated segments of the Item Flexfield. Description of the item Hazard Class Classification
MTL_SYSTEM_ITEMS_B.inventory_item_id MTL_SYSTEM_ITEMS_B.segment1..segment15 MTL_SYSTEM_ITEMS_TL.Description PO_HAZARD_CLASSES_TL. (For PO_HAZARD_CLASSES_TL.hazard_class_id = MTL_SYSTEM_ITEMS_B.hazard_class_id) MTL_SYSTEM_ITEMS_B.Organization_id MTL_SYSTEM_ITEMS_B.src_organization_id FND_COMMON_LOOKUPS.meaning (for Lookup_type =ITEM_TYPE and FND_COMMON_LOOKUPS.lookup_code = MTL_SYSTEM_ITEMS_B.item_type MTL_SYSTEM_ITEMS_B.PRIMARY_UOM_C ODE MTL_SYSTEM_ITEMS_B.LIST_PRICE_PER_ UNIT HR_LOCATIONS_ALL.Country (Select hl.country from hr_all_organization_units hu, hr_locations hl where hulocation_id = hl.location_id and hu.organization_id = MTL_SYSTEM_ITEM_B.Organization_id) MTL_SYSTEM_ITEMS_TL.Long_Description ORG_ORGANIZATION_DEFINITIONS.Operati ng Unit
1.5 1.6 1.7
ORGANIZATION_ID SRC_ORGANIZATION _ID ITEM_TYPE
Organization to which this item is assigned. Master Organization of the item. User Defined Item Type
1.8 1.9 1.10 1.11
UNIT_OF_MEASURE ITEM_VALUE CURRENCY COUNTRY
Unit of Measure Value of the Item Currency Country of the organization to which the item is assigned in Oracle Application.
1.12 1.12.1 1.12.2 1.12.3
USERAREA Long Description of the item LONG_DESCRIPTION OPERATING_UNIT PARAMETERS Operating Unit of the Organization to which the Item is attached. This element bounds any additional parameters to be sent. This element has a attribute named TYPE which can have any of the following values VENDOR or SERVICE or DATA. VENDOR ---- Vendor Parameters SERVICE ---- Service Parameters DATA ---- Additional Data Information / Flexfield All the 15 Descriptive Flexfield attributes(attribute1..atrribute15) of the Item can be passed as Parameters of Type Data. Every Parameter has three attributes Index , Name and Value
PARAMETER
Parameters of type VENDOR WSH_ITM_VENDOR_PARAMETERS.Parmeter _name, WSH_ITM_VENDOR_PARAMETERS.Parmeter _value Parameters of type SERVICE WSH_ITM_SERVICE_PARAMETERS.Prameter _name, WSH_ITM_SERVICE_PARAMETERS.Prameter _value Parameters of type DATA MTL_SYSTEM_ITEMS_B.attribute1..attribute15
Table 4: Element Description of Item Synchronization Request Message
Intlptnrint.doc
29
Specifications
Element/Attribute
Description
CONTRLAREA BSR VERB NOUN REVISION SENDER LOGICALID COMPONENT TASK REFERENCEID CONFIRMATION LANGUAGE CODEPAGE AUTHID
The Verb is the actual service to be performed. (SYNC) The Noun indicates the object the service is to be performed on(ITEM)
logical location of the server and application from which the message originated. (ORACLE) business application that issued the message (ITM Application)) Event that initiated this message (Item Synchronization) Reference Identifier (Message Id) Whether Confirmation is required or not Language code. The entire message is sent in this language. Basically the base language of the installation. Character set User Name-Password
Table 5: Element description of Control Area Elements of Item Synchronization Request
Intlptnrint.doc
30
Specifications
Appendix B - Party Synchronization Request XML

OAGs 007_sync_customer_005.dtd (Revision 7.2.1) DTD is leveraged for the party synchronization request. Userarea has been extended to include the additional elements. For a description of these elements refer to the table 5. oracle_sync_customer_005.dtd contains the userarea extensions. The structure of the party synchronization request message is illustrated in the following diagram: This diagram illustrates the following attributes of the request message: Hierarchy of Elements Each element is shown as a box in the diagram. Top-to-bottom; left-toright. "Parent" elements are shown with "child" elements below them. Required/Optional elements. A required element is depicted via solid boxes. An optional element is depicted via a dashed line. When an element has attributes or children, it is possible for the (parent) element to be optional, while the child or attribute is required. This indicates that when that (parent) element is present, its required attributes and/or children must also be present Repetition of elements. Two types of relationships are illustrated in this diagram: one-to-one and one-to-many. One-to-one relationships are represented by a single box. One-to-many relationships are represented by multiple boxes.
SYNC_CUSTOMER_005
CNTROLAREA
DATAAREA
SYNC_CUSTOMER PARTNER
ADDRESS
USERAREA CONTACT
USERAREA ATTCHREF
USERAREA
Note: Required = Solid boxes Optional = Dashed boxes 31
Intlptnrint.doc
Specifications
Fig 20: Party Synchronization Request Message Structure (The element ATTCHREF in the above figure is not sent.) The following table describes all the elements which would be sent under the PARTNER element of the party synchronization request
Element/Attribute Description Oracle Applications Table.Column_name HZ_PARTIES.party_name HZ_CUST_SITE_USES_ALL.Site_use_ id FND_LOOKUPS.meaning (For FND_LOOKUPS.code = HZ_CUST_SITE_USES.Site_Use_Code = fnd_lookups.lookup_code)
1.1 1.2 1.3
NAME PARTNRID PARTNRTYPE
Name of the partner PARTNRID is the identifier of the partner that the PARTNRTYPE defines. (Site Use Id in Oracle Applications) PARTNRTYPE indicates the type of partner entity or the site use code. Valid values are: Bill To - The customer location where the invoice goes to. Ship To - Location of the customer where goods are sent. Sold To - The customer who is responsible for ordering the goods or services. Drawee - A customer drawee is a customer account site responsible for paying bills. Dunning The location where the customers dunning letters are sent. Invoices Legal : This address acts as the customer accounts legal site. A legal site is responsible for all government reporting requirements. Marketing - Marketing collateral is sent to this address. Self Service User Statements The Customer location where the customers statements are sent. Bills of Lading Credit Memos Credit Contact Deliver To Acknowledgments
1.4 1.5
NAME PARTNRIDX
Account Name and Alternate Name PARTNRIDX is the identifier of the partner that the receiving application may use to identify the PARTNER. Synonyms Customer Number Supplier Number Customer ID Supplier ID The Customer Number will be sent here. TAXID is the tax identifier of the business partner. Synonyms VAT ID Federal Tax ID State Tax ID PARTNER LEVEL Site Number Operating Unit This element bounds any additional parameters to be sent. This element has an attribute named TYPE which can have
HZ_CUST_ACCOUNTS.Account_name , HZ_CUST_ACCOUNTS.Account_Num ber
1.6
TAXID
Hz_parties.tax_reference
1.7 1.7.1 1.7.2 1.7.3
USERAREA SITE_NUMBER OPERATING_UNI T PARAMETERS
HZ_PARTY_SITES.Party_Site_Number HZ_Cust_Acct_sites_all.OrgID
Intlptnrint.doc
32
Specifications
Element/Attribute
Description
Oracle Applications Table.Column_name
1.7.3.1
PARAMETER
any of the following values VENDOR or SERVICE or DATA. VENDOR ---- Vendor Parameters SERVICE ---- Service Parameters DATA ---- Additional Data Information / Descriptive Flexfield Information All the Descriptive Flexfield attributes(attribute1..attribute15) of the Customer, Contact (Open Issue 29)can be passed as Parameters of Type Data. Every Parameter has attributes Index, Name and Value
Parameters of type VENDOR WSH_ITM_VENDOR_PARAMETERS. Parmeter_name, WSH_ITM_VENDOR_PARAMETERS. Parmeter_value Parameters of type SERVICE WSH_ITM_SERVICE_PARAMETERS. Prameter_name, WSH_ITM_SERVICE_PARAMETERS. Prameter_value Parameters of type DATA HZ_CUST_ACCOUNTS.Attribute1..15
1.8 1.8.1 1.8.2 1.8.3 1.8.4
ADDRESS ADDRLINE ADDRTYPE CITY COUNTRY
1.8.5
POSTALCODE
The Data Type ADDRESS represents the data concerning the location of the business partner. ADDRLINE represents the lines needed to describe street address or post office box information. ADDRTYPE represents a qualification of the address of the business partner CITY is the city or town of the business partner. COUNTRY represents the country within an address. The list of valid codes can be found in ISO Standard number 3166. POSTALCODE is the postal code within a mailing address. Synonyms Zip code STATEPROVN is the state or province within the mailing address. ADDRESS LEVEL This element bounds any additional parameters to be sent. This element has an attribute named TYPE which has value DATA ---- Additional Data Information / Descriptive Flexfield Information All the Descriptive Flexfield attributes(attribute1..attribute15) of the Customer Site Level can be passed in this region. Every Parameter has attributes Index, Name and Value The Data Type CONTACT represents people associated with the PARTNER and various ways to contact them, such as telephone or fax. First Name and the Last Name
HZ_LOCATIONS.ADDRESS1..ADDRE SS4 HZ_CUST_SITE_USES_ALL.Primary_ Flag HZ_LOCATIONS.CITY HZ_LOCATIONS.COUNTRY
HZ_LOCATIONS.POSTAL_CODE
1.8.6 1.8.7 1.8.7.1
STATEPROVN USERAREA PARAMETERS
HZ_LOCATIONS.STATE
1.8.7.1. 1 1.9
PARAMETER CONTACT
HZ_CUST_ACCT_SITES_ALL.attribute 1..15
1.9.1
NAME
HZ_PARTIES.Party_name (Having a record in HZ_PARTY_RELATIONSHIPS with relationship_type = CONTACT_OF
1.9.2 CONTCTTYPE
1.9.3 1.9.4
EMAIL FAX
CONTCTTYPE describes the contact persons responsibilities. Synonyms Job Title EMAIL is the electronic mail address for the CONTACT. FAX is the facsimile telephone number.
1.9.5
TELEPHONE
HZ_CONTACT_POINTS.Email HZ_CONTACT_POINTS.PHONE_NU MBER (With Phone_Line_Type = FAX) HZ_CONTACT_POINTS.PHONE_NU MBER
Intlptnrint.doc
33
Specifications
Element/Attribute
Description
Oracle Applications Table.Column_name (With Phone_Line_Type = PHONE)
1.9.6 1.9.6.1
USERAREA PARAMETERS
1.9.6.1. 1
PARAMETER
CONTACT LEVEL This element bounds any additional parameters to be sent. This element has an attribute named TYPE which has value DATA ---- Additional Data Information / Descriptive Flexfield Information All the Descriptive Flexfield attributes(attribute1..attribute15) of the Customer Contact or Site Contact can be passed in this region. Every Parameter has attributes Index, Name and Value
HZ_PARTIES.attribute1..15 (Having a record in HZ_PARTY_RELATIONSHIPS with relationship_type = CONTACT_OF
Table 6: Element description of Party Synchronization Request Message
Element/Attribute
Description
The Verb is the actual service to be performed. (SYNC) The Noun indicates the object the service is to be performed on(CUSTOMER)
logical location of the server and application from which the message originated. (ORACLE) business application that issued the message (ITM Application)) Event that initiated this message (Party Synchronization) Reference Identifier (Message Id) Whether Confirmation is required or not Language code. The entire message is sent in this language. Basically the base language of the installation. Character set User Name-Password
Table 7: Element description of Control Area Elements of Party Synchronization request
Intlptnrint.doc
34
Specifications
Appendix C Order Compliance Request XML
The following message is leveraged for order compliance request XML. This diagram illustrates the following attributes of the request message: Hierarchy of Elements Each element is shown as a box in the diagram. Top-to-bottom; left-toright. "Parent" elements are shown with "child" elements below them. Required/Optional elements. A required element is depicted via solid boxes. An optional element is depicted via a dashed line. When an element has attributes or children, it is possible for the (parent) element to be optional, while the child or attribute is required. This indicates that when that (parent) element is present, its required attributes and/or children must also be present Repetition of elements. Two types of relationships are illustrated in this diagram: one-to-one and one-to-many. One-to-one relationships are represented by a single box. One-to-many relationships are represented by multiple boxes.
REQUEST CONTROL AREA
DATA AREA
MESSAGE_ID ADMIN PARAMETERS ADDL_INFO ORDER_LINE TRANSACTION_KEY
ORDER_NUMBER
ORDER_LINE ITEM_ID PARTY
Intlptnrint.doc
35
Specifications
Fig 21: Order Compliance Request Message Structure

XML Fields
Order
Tables
Represents the Order line information. Every Order line would map to one Order Tag and multiple Order Tags would be present in a message for same Order Number. OE_ORDER_HEADERS_ALL.ORDER_NUMBER OE_ORDER_HEADERS_ALL.ORDER_TYPE OE_ORDER_HEADERS_ALL.ORG_ID OE_ORDER_HEADERS_ALL.CUST_PO_NUM OE_ORDER_HEADERS_ALL.TRANSACTIONAL_CURR_ CODE OE_ORDER_HEADERS_ALL.CONVERSION_TYPE_COD E OE_ORDER_HEADERS_ALL.CONVERSION_RATE OE_ORDER_HEADERS_ALL.ORDERED_DATE From OE_ORDER_LINES_ALL concatenation of (LINE_NUMBER.SHIPMENT_NUMBER.OPTION_NUMBE R.COMPONENT_NUMBER.SERVICE_NUMBER) OE_ORDER_LINES_ALL.TOP_MODEL_LINE_ID OE_ORDER_LINES_ALL.SPLIT_FROM_LINE_ID OE_ORDER_LINES_ALL.LINK_TO_LINE_ID OE_ORDER_LINES_ALL.ATO_LINE_ID OE_ORDER_LINES_ALL.ITEM_TYPE_CODE MTL_SYSTEM_ITEMS_B.SEGMENT1..SSEGMENT15 for INVENTORY_ITEM_ID in OE_ORDER_LINES_ALL
Note
Contains the Order Header Information. Order Number Order Type Operating Unit Purchase Order Number Currency Conversion Conversion Rate Date of Order Order Line Number
Mand atory
Y
Y Y Y N N N N N
<order_line_number>
<top_model_line_id> <split_from_line_id> <link_to_line_id> <ato_line_id> <item_type> <item_code> <ship_from_org_code>
Top Model Line ID Split From Line ID Link to Line ID ATO Line ID Item Type Code Item Number Ship From Organization Code
OE_ORDER_LINES_ALL.SHIPPING_METHOD_CODE OE_ORDER_LINES_ALL.REQUEST_DATE OE_ORDER_LINES_ALL.FREIGHT_TERMS_CODE RA_TERMS_TL.NAME (Name of the payment terms) OE_ORDER_HEADERS_ALL.PAYMENT_TERM_ID OE_ORDER_LINES.ORDERED_QUANTITY * OE_ORDER_LINES_ALL.UNIT_SELLING_PRICE OE_ORDER_LINES_ALL.LINE_NUMBER OE_ORDER_LINES_ALL.UNIT_LIST_PRICE OE_ORDER_LINES_ALL.UNIT_SELLING_PRICE ITEM_ID
Ship Method Request Date Freight Terms Payment Terms Quantity Ordered Selling Price Line Number
Item ID, which 3rd Party Partner application can recognize as a primary key. Order Line Descriptive Flexfield Customer Number
N N N N N N N Y N N Y
PARTY <descriptive_flexfield> <attribute1 to 15> <party_id> <type>
Same as currently used Party for Denied Party WSH_ITM_REQUEST_CONTROL.ATTRIBUTE1-15 HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER Identification From Adapter Type like SHIP_FROM, PTNR_SHIP_TO, DELIVER To, Sold To, intermediate Ship To The party type is just an informatory field, which doesnt have any functional significance for provider. Adapter can send any thing, which is populated by application. So application can maintain any codes/lookups for this. HZ_CUST_SITE_USES_ALL.SITE_USE_ID HZ_CUST_SITE_USES_ALL. LOCATION Party Name Address 1 Address 2 Address 3 Address 4 Address 5 City State Country Country Code
Y N
Site Use ID Site Use Code N N N N N N N N N N
<name> <address1> <address2> <address3> <address4> <address5> <city> <state_or_province> <country> <code>
Intlptnrint.doc
36
Specifications
<name> <postal_code> <contact_name> <email> <phone> <fax> <web> <addl_info>
Country Name Postal Code Contact Name e-mail Phone Fax www URL Additional Info to include DFFs and other extra parameters
N N N N N N N N
Table 8: Element description of Order Compliance Request Message
Element/Attribute
Description
The Verb is the actual service to be performed. (SYNC) The Noun indicates the object the service is to be performed on(CUSTOMER)
logical location of the server and application from which the message originated. (ORACLE) business application that issued the message (ITM Application)) Event that initiated this message (Party Synchronization) Reference Identifier (Message Id) Whether Confirmation is required or not Language code. The entire message is sent in this language. Basically the base language of the installation. Character set User Name-Password
Table 9: Element description of Control Area Elements of Order Request XML
Intlptnrint.doc
37
Specifications
Appendix D Export Compliance Response XML
The purpose Export Compliance response XML is to receive the overall export compliance status of a transaction (order line/delivery) from the partner ITM application. The response DTD, its element description and a sample of the request is provided in Appendix 5. The same message is used from Order Management as well as Shipping. The structure of the message is illustrated in the following diagram: This diagram illustrates the following attributes of the request message: Hierarchy of Elements Each element is shown as a box in the diagram. Top-to-bottom; left-toright. "Parent" elements are shown with "child" elements below them. Required/Optional elements. A required element is depicted via solid boxes. An optional element is depicted via a dashed line. When an element has attributes or children, it is possible for the (parent) element to be optional, while the child or attribute is required. This indicates that when that (parent) element is present, its required attributes and/or children must also be present Repetition of elements. Two types of relationships are illustrated in this diagram: one-to-one and one-to-many. One-to-one relationships are represented by a single box. One-to-many relationships are represented by multiple boxes.
EXPORT COMPL RESPONSE CNTROLAREA DATAAREA

MESSAGE TRANSACTION_KEY TRIGERRING_POINT
EXPORT_COMP_RESULT
ERROR
Fig 22: Export Compliance Response Message Structure
Intlptnrint.doc
38
Specifications
Element/Attribute
Description
TRANSACTION_KEY TRIGGERING_POINT EXPORT_COMP_RESULT SUCCESS TYPE DESCRIPTION ERROR CODE TYPE DESCRIPTION
Key referencing the Line of transaction. For Order Screening it could be something like <order_number>-<order_type>-<line_number>. Point of request for the Export Complaince OM-Booking, Pick Release(?), Ship Confirm..etc could be used as possible values. Y/N (Y- Yes, N- Failure) Type of Export Compliance Done Free flow text as reason/message for success/failure of the compliance conducted.
Type can be All Export Compliance Checks or Denied Party Screening or Embargo Screening etc. Error Type is also included in case its an error. Description of the Error.
Table 10: Element description of Export Compliance Response Message
Intlptnrint.doc
39
Specifications
Appendix E Delivery Compliance Request XML

The OAGs SHOW SHIPMENT DTD is used as a basis for this transaction. The purpose of delivery compliance request XML is to communicate all the compliance relevant delivery attributes to the partner application.
Reqd X X X X
Element/Attribute SHIPMENT.DATETTIME (Document) (required) SHIPMENT.DOCUMENTID (Shipment) (required) SHIPMENT.SHIPPERID (required) SHIPMENT.SYNCID (required)
Source (Table.Column Name ) Sys date time WSH_TRANSACTIONS_HISTORY.DOCUMENT_ID WSH_NEW_DELIVERIES.INITIAL_PICKUP_LOCATION_ID converted to code XML: A = Add, D = Delete C = Change EDI: N for Add, F for Delete
SHIPMENT.AMOUNT (DECLAREVAL) SHIPMENT.AMOUNT (DOCUMENT) (T) SHIPMENT.AMOUNT (ESTFREIGHT) SHIPMENT.AMOUNT (FREIGHT) (T) SHIPMENT.AMOUNT (ITEM) (T) SHIPMENT.CARRIER SHIPMENT.CARRIERSRVLVL SHIPMENT.COUNTRYDST SHIPMENT.COUNTRYORG SHIPMENT.DATETIME (CREATION) SHIPMENT.DATETIME (DELIVACT) SHIPMENT.DATETIME (DELIVSCHED) SHIPMENT.DATETIME (EARLSTSHIP) SHIPMENT.DATETIME (LOADING) SHIPMENT.DATETIME (NEEDDELV) SHIPMENT.DATETIME (PROMDELV) SHIPMENT.DATETIME (PROMSHIP) SHIPMENT.DATETIME (SHIP) SHIPMENT.DATETIME (SHIPSCHED) SHIPMENT.DESCRIPTN SHIPMENT.DISTCENTER SHIPMENT.DOCKID SHIPMENT.DOCTYPE
WSH_FREIGHT_COSTS.TOTAL_AMOUNT WSH_NEW_DELIVERIES.CARRIER_ID, converted to external value WSH_NEW_DELIVERIES.SERVICE_LEVEL, converted to external value For wsh_new_deliveries. Ultimate_dropoff_location_id, Get the country from hz_locations WSH_NEW_DELIVERIES.CREATION_DATE WSH_TRIP_STOPS.ACTUAL_ARRIVAL_DATE WSH_NEW_DELIVERIES. .ULTIMATE_DROPOFF_DATE
WSH_NEW_DELIVERIES. .ULTIMATE_DROPOFF_DATE
WSH_TRIP_STOPS.ACTUAL_DEPARTURE_DATE WSH_NEW_DELIVERIES.INITIAL_PICKUP_DATE WSH_NEW_DELIVERIES.DESCRIPTION
SHIPMENT REQUEST for 940 SHIPMENT ADVICE for 945
SHIPMENT.DOCUMENTRV
001 for ADD 002 for DELETE 003 for CHANGE
SHIPMENT.DROPSHIP SHIPMENT.EXPORTLIC SHIPMENT.FRGHTCLS SHIPMENT.FRGHTTERMS SHIPMENT.HAZRDMATL SHIPMENT.HDRSTATUS SHIPMENT.IMPORTLIC SHIPMENT.LOADPOINT SHIPMENT.NOTES1 NOTES9 SHIPMENT.OPERAMT (FREIGHT) (T) SHIPMENT.PARTIALSHP SHIPMENT.PRIORITY SHIPMENT.QUANTITY (ESTWEIGHT)
WSH_NEW_DELIVERIES.FREIGHT_TERMS_CODE
WSH_NEW_DELIVERIES.GROSS_WEIGHT WSH_NEW_DELIVERIES.WEIGHT_UOM
Intlptnrint.doc
40
Specifications
Reqd
Element/Attribute SHIPMENT.QUANTITY (LOADINGWT)
Source (Table.Column Name ) Calculate using WSH_NEW_DELIVERIES.GROSS WEIGHT WSH_NEW_DELIVERIES.NET WEIGHT WSH_NEW_DELIVERIES.NET_WEIGHT WSH_NEW_DELIVERIES.WEIGHT_UOM WSH_NEW_DELIVERIES.NUMBER_OF_LPN WSH_NEW_DELIVERIES.GROSS_WEIGHT WSH_NEW_DELIVERIES.WEIGHT_UOM WSH_NEW_DELIVERIES.VOLUME WSH_NEW_DELIVERIES.VOLUME_UOM
SHIPMENT.QUANTITY (NETWEIGHT) SHIPMENT.QUANTITY (SHIPUNIT) SHIPMENT.QUANTITY (TOTWEIGHT) SHIPMENT.QUANTITY (VOLUME) SHIPMENT.ROUTEID SHIPMENT.RELEASENUM SHIPMENT.RELEASENUMTOT SHIPMENT.ROUTETYPE SHIPMENT.SHIPNOTES SHIPMENT.SHIPPOINT SHIPMENT.SHIPPRIOR SHIPMENT.SHIPSRVLVL SHIPMENT.SPECIALHND SHIPMENT.STAGEPOINT SHIPMENT.TEMPRATURE (ACTUAL) SHIPMENT.TEMPRATURE (DELIVERY) SHIPMENT.TEMPRATURE (LOADING) SHIPMENT.TRANSMETHD SHIPMENT.TRANSTERMS SHIPMENT.WAREHOUSE SHIPMENT.USERAREA
Type of routing. WSH_NEW_DELIVERIES.SHIPPING_MARKS WSH_NEW_DELIVERIES.ULTIATE_DROPOFF_LOCATION_ID converted to code WSH_NEW_DELIVERIES.SERVICE_LEVEL
WSH_NEW_DELIVERIES.MODE_OF_TRANSPORT WSH_NEW_DELIVERIES.FOB_CODE WSH_NEW_DELIVERIES.ORGANIZATION_ID converted to code WSH_NEW_DELIVERIES.DELIVERY_NAME WSH_NEW_DELIVERIES.LOADING_SEQUENCE WSH_NEW_DELIVERY descriptive flex fields WSH_TRIPS.VEHICLE_NUM_PREFIX WSH_TRIPS.VEHICLE_NUMBER WSH_TRIPS.ROUTE_ID WSH_TRIPS.ROUTING_INSTRUCTIONS WSH_TRIP_STOPS.DEPARTURE_SEAL_CODE WSH_NEW_DELIVERIES.SHIP_METHOD_CODE
NVL(WSH_TRIPS.SHIP_METHOD_CODE,
WSH_NEW_DELIVERIES.SHIP_METHOD_CODE) WSH_NEW_DELIVERIES.WAYBILL WSH_ITM_REQUEST_CONTROL.ATTRIBUTEn_NAME/ATTRIBUTEn_VA LUE Where n=1 to 20 WSH_ITM_REQUEST_CONTROL.TRIGGERING_POINT X PARTNER. PARTNER.NAME1 - If this partner segment is the Ship To segment, get the HZ_PARTIES.NAME for the WSH_NEW_DELIVERIES.ULTIMATE_DROPOFF_LOCATION_ID - If this partner segment is the Ship from segment, get the HZ_PARTIES.NAME for the WSH_NEW_DELIVERIES.ORGANIZATION_ID - If this partner segment is the Customer segment, get the HZ_PARTIES.NAME for the WSH_NEW_DELIVERIES.CUSTOMER_ID - If this partner segment is the Supplier segment, get the HZ_PARTIES.NAME for the WSH_NEW_DELIVERIES.ORGANIZATION_ID WSH_NEW_DELIVERIES.ULTIMATE_DROPOFF_LOCATION_ID converted to external value, or WSH_NEW_DELIVERIES.ORGANIZATION_ID converted to external value. PARTNRTYPE indicates the type of partner entity. Valid values are: ShipTo - The delivery location of the customer. BillTo - The customer location the bill goes to. SoldTo - The customer who is responsible for ordering the goods or services. Could be at multiple organizational levels. Supplier - The partner who is responsible for providing the goods or services. Supplier can be at multiple organizational levels. Carrier - The partner responsible for delivering the goods or services.
X X
PARTNER.ONETIME PARTNER.PARTNRID (required)
PARTNER.PARTNRTYPE (required)
Intlptnrint.doc
41
Specifications
Reqd
Element/Attribute
Source (Table.Column Name ) ShipFrom - The shipping location of the partner who is responsible for providing the goods or services. Ship from can be at multiple organizational levels. Intmd_ShipTo Intermeidate Ship for the delivery FOB- FOB for the delivery
PARTNER.ACTIVE PARTNER.CURRENCY PARTNER.DESCRIPTN PARTNER.DUNSNUMBER PARTNER.GLENTITYS PARTNER.NAME2-NAME9 PARTNER.PARENTID PARTNER.PARTNIDX PARTNER.PARTNRRATG PARTNER.PARTNRROLE PARTNER.PAYMETHOD PARTNER.TAXEXEMPT PARTNER.TAXID PARTNER.TERMID PARTNER.USERAREA
WSH_NEW_DELIVERIES.CURRENCY_CODE for the supplier and ship from partner segments HZ_PARTIES.DUNS_NUMBER for all partner types
Could use HZ_PARTIES.DUNS_NUMBER for the HZ_PARITES.PARTY_ID that matches the Ship From, Ship To, Customer and Supplier segments
WSH_NEW_DELIVERIES.INTMED_SHIP_TO_LOCATION_ID WSH_ NEW_DELIVERIES.POOLED_SHIP_TO_LOCATION_ID HZ_CUST_SITE_USES_ALL.SITE_USE_ID HZ_CUST_SITE_USES_ALL.LOCATION
PARTNER ADDRESS. PARTNER ADDRESS.ADDRLINE1ADDRLINE9 PARTNER ADDRESS.ADDRTYPE PARTNER ADDRESS.CITY
Extracted from the HZ_LOCATIONS using the party id that matches the Ship From, Ship TO, Customer and Supplier from the WSH_NEW_DELIVERIES or WSH_DELIVERY_DETAILS table, via the HZ_PARTY_SITES table. Extracted from the HZ_LOCATIONS using the party id that matches the Ship From, Ship TO, Customer and Supplier from the WSH_NEW_DELIVERIES or WSH_DELIVERY_DETAILS table, via the HZ_PARTY_SITES table. Extracted from the HZ_LOCATIONS using the party id that matches the Ship From, Ship TO, Customer and Supplier from the WSH_NEW_DELIVERIES or WSH_DELIVERY_DETAILS table, via the HZ_PARTY_SITES table. Extracted from the HZ_LOCATIONS using the party id that matches the Ship From, Ship TO, Customer and Supplier from the WSH_NEW_DELIVERIES or WSH_DELIVERY_DETAILS table, via the HZ_PARTY_SITES table. HZ_CONTACT_POINTS.RAW_PHONE_NUMBER for the PARTY_ID, and CONTACT_POINT_TYPE = FAX Extracted from the HZ_LOCATIONS using the party id that matches the Ship From, Ship TO, Customer and Supplier from the WSH_NEW_DELIVERIES or WSH_DELIVERY_DETAILS table, via the HZ_PARTY_SITES table. Extracted from the HZ_LOCATIONS using the party id that matches the Ship From, Ship TO, Customer and Supplier from the WSH_NEW_DELIVERIES or WSH_DELIVERY_DETAILS table, via the HZ_PARTY_SITES table. Extracted from the HZ_LOCATIONS using the party id that matches the Ship From, Ship TO, Customer and Supplier from the WSH_NEW_DELIVERIES or WSH_DELIVERY_DETAILS table, via the HZ_PARTY_SITES table. HZ_CONTACT_POINTS.RAW_PHONE_NUMBER for the PARTY_ID, and CONTACT_POINT_TYPE = GEN HZ_CONTACT_POINTS.URL for the PARTY_ID and CONTACT_POINT_TYPE = GEN
PARTNER ADDRESS.COUNTRY
PARTNER ADDRESS.COUNTY
PARTNER ADDRESS.DESCRIPTN PARTNER ADDRESS.FAX1-FAX9 PARTNER ADDRESS.POSTALCODE
PARTNER ADDRESS.REGION
PARTNER ADDRESS.STATEPROVN
PARTNER ADDRESS.TAXJRSDCTN PARTNER ADDRESS.TELEPHONE1TELEPHONE9 PARTNER ADDRESS.URL PARTNER ADDRESS.USERAREA PARTNER CONTACT. PARTNER CONTACT.NAME1 (Required) PARTNER CONTACT.CONTCTTYPE PARTNER CONTACT.DESCRIPTN PARTNER CONTACT.EMAIL PARTNER CONTACT.FAX1 - FAX9
Intlptnrint.doc
42
Specifications
Reqd
Element/Attribute PARTNER CONTACT.NAME2 - NAME9 PARTNER CONTACT.TELEPHONE1 TELEPHONE9 PARTNER CONTACT.USERAREA DOCUMNTREF.
Source (Table.Column Name ) Extracted from the HR_LOCATIONS_ALL using the WSHID
X X X X
DOCUMNTREF.DOCTYPE (required) DOCUMNTREF.DOCUMENTID (required) DOCUMNTREF.PARTNRID (required) DOCUMNTREF.PARTNRTYPE (required)
We need to send this segment twice once to represent the ship from delivery name, and for each ship to purchase order number SHIPMENT REQUEST WSH_TRANSACTIONS_HISTORY.Orig_Document_ID WSH_NEW_DELIVERIES.ORGANIZATION_ID converted to code ShipFrom - The shipping location of the partner who is responsible for providing the goods or services. Ship from can be at multiple organizational levels
DOCUMNTREF.DESCRIPTN DOCUMNTREF.DOCUMENTRV DOCUMNTREF.LINENUM DOCUMNTREF.NOTES1 NOTES9 DOCUMNTREF.SCHLINENUM DOCUMNTREF.SUBLINENUM DOCUMNTREF.USERAREA SHIPITEM. SHIPITEM.ITEM (REQUIRED)
WSH_DELIVERY_DETAILS.INVENTORY_ITEM_ID (foreign key to MTL_SYSTEM_ITEMS) Derive Item_Number from MTL_SYSTEM_ITEMS WSH_DELIVERY_DETAILS.REQUESTED_QUANTITY
SHIPITEM.QUANTITY (ITEM) SHIPITEM.AMOUNT (EXTENDED) (T) SHIPITEM.AMOUNT (ITEM) (T) SHIPITEM.COUNTRYORG SHIPITEM.DISPOSITN SHIPITEM.EXPORTLIC SHIPITEM.FRGHTCLS SHIPITEM.FRGHTITEM SHIPITEM.HAZRDMATL
WSH_DELIVERY_DETAILS.COUNTRY_OF_ORIGIN
WSH_DELIVERY_DETAILS.FREIGHT_CLASS_CAT_ID converted to external value WSH_DELIVERY_DETAILS.HAZARD_CLASS_ID converted to external value. Pass it, but may not be used in the inbound side. Extract the data from tables. This value will be passed in the outbound transaction.
SHIPITEM.IMPORTLIC SHIPITEM.ITEMDESC SHIPITEM.ITEMRV SHIPITEM.ITEM_ID SHIPITEM.ITEMRVX SHIPITEM.ITEMX SHIPITEM.LINENUM SHIPITEM.LOTLEVEL1 LOTLEVEL2 SHIPITEM.NOTES1 NOTES9 SHIPITEM.OWNRSHPCDE SHIPITEM.PACKING SHIPITEM.PACKINGDESC SHIPITEM.PARTIALSHIP SHIPITEM.QUANTITY (BACKORDERD) SHIPITEM.QUANTITY (OPEN) SHIPITEM.QUANTITY (ORDERED) SHIPITEM.QUANTITY (SHIPPED) SHIPITEM.QUANTITY (VOLUME) SHIPITEM.QUANTITY (WEIGHT)
WSH_DELIVERY_DETAILS.ITEM_DESCRIPTION WSH_DELIVERY_DETAILS.REVISION MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID WSH_DELIVERY_DETAILS.CUSTOMER_ITEM_ID Converted to Item_number by joining to mtl_customer_items Moved the mapping to INVDETAIL section. Notes 1 WSH_DELIVERY_DETAILS.PACKING_INSTRUCTIONS WSH_DELIVERY_DETAILS.FOB_CODE
0 means partial shipment not allowed (i.e when ship_set_id is not null) 1 means partial shipment is allowed(i.e when ship_set_id is null) Calculate WSH_DELIVERY_DETAILS.REQUESTED_QUANTITY WSH_DELIVERY_DETAILS.SHIPPED_QUANTITY for 945 inbound only. WSH_DELIVERY_DETAILS.SRC_REQUESTED_QUANTITY WSH_DELIVERY_DETAILS.SHIPPED_QUANTITY WSH_DELIVERY_DETAILS.VOLUME WSH_DELIVERY_DETAILS.NET_WEIGHT
Intlptnrint.doc
43
Specifications
Reqd
Element/Attribute SHIPITEM.SHIPMATLID SHIPITEM.SHIPNOTES SHIPITEM.SHIPPRIOR SHIPITEM.SHIPMTLDESC SHIPITEM.UPC SHIPITEM.USERAREA (Use ITEMCATID for commodity code this is a valid OAG field, but just not on this message).
Source (Table.Column Name )
WSH_DELIVERY_DETAILS.SHIPPING_INSTRUCTIONS
DOCUMNTREF. X XX DOCUMNTREF.DOCTYPE (required)DOCUMNTREF. DOCUMNTREF.DOCUMENTID (required)DOCUMNTREF.DOCTYPE (required) DOCUMNTREF.PARTNRID (required)DOCUMNTREF.DOCUMENTID (required) DOCUMNTREF.PARTNRTYPE (required)DOCUMNTREF.PARTNRID (required) DOCUMNTREF.DESCRIPTNDOCUMNTRE F.PARTNRTYPE (required) DOCUMNTREF.DOCUMENTRVDOCUMNT REF.DESCRIPTN DOCUMNTREF.LINENUMDOCUMNTREF. DOCUMENTRV DOCUMNTREF.NOTES1 NOTES9DOCUMNTREF.LINENUM DOCUMNTREF.SCHLINENUMDOCUMNT REF.NOTES1 NOTES9 DOCUMNTREF.SUBLINENUMDOCUMNT REF.SCHLINENUM DOCUMNTREF.USERAREADOCUMNTRE F.SUBLINENUM DOCUMNTREF.USERAREA CHARGE. CHARGE.CHARGEID (REQUIRED)CHARGE. CHARGE.OPERAMT (EXTENDED) (T) (REQUIRED)CHARGE.CHARGEID (REQUIRED) CHARGE.AMOUNT (EXTENDED) (T)CHARGE.OPERAMT (EXTENDED) (T) (REQUIRED) CHARGE.CHARGETYPECHARGE.AMOUN T (EXTENDED) (T) CHARGE.CHGLINENUMCHARGE.CHARG ETYPE CHARGE.DESCRIPTNCHARGE.CHGLINEN
Use this to store: WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID WSH_DELIVERY_ASSIGNMENTS.PARENT_DELIVERY_DETAIL_ID WSH_DELIVERY_DETAILS.SHIP_TOLERANCE_ABOVE WSH_DELIVERY_DETAILS.SHIP_TOLERANCE_BELOW WSH_DELIVERY_DETAILS.LOAD_SEQUENCE_NUMBER WSH_DELIVERY_DETAILS descriptive flexfields WSH_DELIVERY_DETAILS.SHIP_SET_ID WSH_DELIVERY_DETAILS.SUBINVENTORY WSH_DELIVERY_DETAILS.TOP_MODEL_LINE_ID WSH_DELIVERY_DETAILS.SHIP_MODEL_COMPLETE_FLAG WSH_DELIVERY_DETAILS.COMMODITY_CODE_CAT_ID converted to code WSH_DELIVERY_DETAILS.SHIPMENT_PRIORITY_CODE converted to 01, 02, or 03 for XML,. WSH_DELIVERY_DETAILS.DELIVER_TO_LOCATION_ID WSH_DELIVERY_DETAILS.SOURCE_LINE_NUMBER WSH_DELIVERY_DETAILS.SOURCE_LINE_ID We need to send this segment for each customer purchase order number for all the delivery details on this delivery. PURCHASEORDERWe need to send this segment for each customer purchase order number for all the delivery details on this delivery. WSH_DELIVERY_DETAILS.CUST_PO_NUMBER PURCHASEORDER
XX
XX
WSH_NEW_DELIVERIES.ULTIMATE_DROPOFF_LOCATION_ID converted to external value for for Customer POWSH_DELIVERY_DETAILS.CUST_PO_NUMBER ShipTo - The delivery location of the customerWSH_NEW_DELIVERIES.ULTIMATE_DROPOFF_LOCATION_ID converted to external value for for Customer PO ShipTo - The delivery location of the customer
X XX
WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to external value WSH_FREIGHT_COSTS.TOTAL_AMOUNT WSH_FREIGHT_COSTS.CURRENCY_CODEWSH_FREIGHT_COSTS.FREI GHT_COST_TYPE_ID converted to external value WSH_FREIGHT_COSTS.TOTAL_AMOUNT WSH_FREIGHT_COSTS.CURRENCY_CODE WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to FREIGHT_COST_TYPE WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to FREIGHT_COST_TYPE
Intlptnrint.doc
44
Specifications
Reqd
Element/Attribute UM CHARGE.USERAREA CHARGE.DESCRIPTN INVDETAIL. CHARGE.USERAREA INVDETAIL.DESCRIPTNINVDETAIL. INVDETAIL.DISPOSITNINVDETAIL.DESC RIPTN INVDETAIL.LOTLEVEL1 LOTLEVEL2INVDETAIL.DISPOSITN
WSH_FREIGHT_COSTS descriptive flexfields WSH_FREIGHT_COSTS descriptive flexfields WSH_DELIVERY_DETAILS.ITEM_DESCRIPTION WSH_DELIVERY_DETAILS.ITEM_DESCRIPTION WSH_DELIVERY_DETAILS.LOT_NUMBER WSH_DELIVERY_DETAILS.SUBLOT_NUMBER
INVDETAIL.NOTES1 NOTES9INVDETAIL.LOTLEVEL1 LOTLEVEL2 INVDETAIL.QUANTITY (ITEM)INVDETAIL.NOTES1 - NOTES9 INVDETAIL.SERIALNUMINVDETAIL.QUA NTITY (ITEM) INVDETAIL.USERAREAINVDETAIL.SERIA LNUM INVDETAIL.USERAREA
WSH_DELIVERY_DETAILS.LOT_NUMBER WSH_DELIVERY_DETAILS.SUBLOT_NUMBER WSH_DELIVERY_DETAILS.REQUESTED QUANTITY/WSH_DELIVERY_DETAILS.REQUESTED_QUANTITY_UOM WSH_DELIVERY_DETAILS.SERIAL_NUMBERWSH_DELIVERY_DETAIL S.REQUESTED QUANTITY/WSH_DELIVERY_DETAILS.REQUESTED_QUANTITY_UOM WSH_DELIVERY_DETAILS.TO_SERIAL_NUMBER WSH_DELIVERY_DETAILS.PREFERRED_GRADE WSH_DELIVERY_DETAILS.SERIAL_NUMBER WSH_DELIVERY_DETAILS.TO_SERIAL_NUMBER WSH_DELIVERY_DETAILS.PREFERRED_GRADE
X XX
CHARGE. CHARGE.CHARGEID (REQUIRED)CHARGE. CHARGE.OPERAMT (EXTENDED) (T) (REQUIRED)CHARGE.CHARGEID (REQUIRED) CHARGE.AMOUNT (EXTENDED) (T)CHARGE.OPERAMT (EXTENDED) (T) (REQUIRED) CHARGE.CHARGETYPECHARGE.AMOUN T (EXTENDED) (T) CHARGE.CHGLINENUMCHARGE.CHARG ETYPE CHARGE.DESCRIPTNCHARGE.CHGLINEN UM CHARGE.USERAREA CHARGE.DESCRIPTN CHARGE.USERAREA DISTRIBUTION. DISTRIBUTION.BUSNAREADISTRIBUTIO N. DISTRIBUTION.COSTCENTERDISTRIBUTI ON.BUSNAREA DISTRIBUTION.DEPARTMENTDISTRIBUT ION.COSTCENTER DISTRIBUTION.DIVISIONDISTRIBUTION. DEPARTMENT DISTRIBUTION.ELEMENT1 - ELEMENT 999DISTRIBUTION.DIVISION DISTRIBUTION.FUNDDISTRIBUTION.ELE MENT1 - ELEMENT 999 DISTRIBUTION.GEOGRAPHYDISTRIBUTI ON.FUND DISTRIBUTION.GLENTITYSDISTRIBUTIO N.GEOGRAPHY DISTRIBUTION.GLNOMACCTDISTRIBUTI ON.GLENTITYS DISTRIBUTION.OPERAMT (EXTENDED)
WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to external value WSH_FREIGHT_COSTS.TOTAL_AMOUNT WSH_FREIGHT_COSTS.CURRENCY_CODEWSH_FREIGHT_COSTS.FREI GHT_COST_TYPE_ID converted to external value WSH_FREIGHT_COSTS.TOTAL_AMOUNT WSH_FREIGHT_COSTS.CURRENCY_CODE WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to FREIGHT_COST_TYPE WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to FREIGHT_COST_TYPE
WSH_FREIGHT_COSTS descriptive flexfields WSH_FREIGHT_COSTS descriptive flexfields
Intlptnrint.doc
45
Specifications
Reqd
Element/Attribute (T)DISTRIBUTION.GLNOMACCT DISTRIBUTION.PROFITCTRDISTRIBUTIO N.OPERAMT (EXTENDED) (T) DISTRIBUTION.PROJECTDISTRIBUTION. PROFITCTR DISTRIBUTION.UNITDISTRIBUTION.PROJ ECT DISTRIBUTION.WAREHOUSEDISTRIBUTI ON.UNIT DISTRIBUTION.USERAREADISTRIBUTIO N.WAREHOUSE DISTRIBUTION.USERAREA SHIPUNIT. SHIPUNIT.CARRIER (REQUIRED)SHIPUNIT. SHIPUNIT.SHIPPERID (REQUIRED)SHIPUNIT.CARRIER (REQUIRED) SHIPUNIT.TRACKINGID (REQUIRED)SHIPUNIT.SHIPPERID (REQUIRED) SHIPUNIT.AMOUNT (DECLAREVAL)SHIPUNIT.TRACKINGID (REQUIRED) SHIPUNIT.AMOUNT (FREIGHT( (T)SHIPUNIT.AMOUNT (DECLAREVAL) SHIPUNIT.AMOUNT (ITEM) (T)SHIPUNIT.AMOUNT (FREIGHT( (T) SHIPUNIT.AMOUNT (TOTAL) (T)SHIPUNIT.AMOUNT (ITEM) (T) SHIPUNIT.CARRSRVLVLSHIPUNIT.AMOU NT (TOTAL) (T) SHIPUNIT.CONTAINRIDSHIPUNIT.CARRS RVLVL SHIPUNIT.CONTNRGRPIDSHIPUNIT.CONT AINRID SHIPUNIT.CONTNRSEALSHIPUNIT.CONT NRGRPID SHIPUNIT.CONTRTYPESHIPUNIT.CONTN RSEAL SHIPUNIT.COUNTRYDSTSHIPUNIT.CONT RTYPE SHIPUNIT.COUNTRYORGSHIPUNIT.COUN TRYDST SHIPUNIT.DATETIME (DELIVACT)SHIPUNIT.COUNTRYORG SHIPUNIT.DATETIME (DELIVSCHED)SHIPUNIT.DATETIME (DELIVACT) SHIPUNIT.DATETIME (LOADING)SHIPUNIT.DATETIME (DELIVSCHED) SHIPUNIT.DATETIME (SHIP)SHIPUNIT.DATETIME (LOADING) SHIPUNIT.DESCRIPTNSHIPUNIT.DATETI ME (SHIP) SHIPUNIT.EXPORTLICSHIPUNIT.DESCRIP TN SHIPUNIT.FRGHTCLSSHIPUNIT.EXPORTL IC SHIPUNIT.FRCHTITEMSHIPUNIT.FRGHTC LS SHIPUNIT.FRGTHTERMSSHIPUNIT.FRCHT ITEM SHIPUNIT.HAZRDMATLSHIPUNIT.FRGTH TERMS
X XX
WSH_DELIVERY_DETAILS.CARRIER_ID converted to external value WSH_DELIVERY_DETAILS.SHIP_FROM_LOCATION_ID converted to external value.WSH_DELIVERY_DETAILS.CARRIER_ID converted to external value WSH_DELIVERY_DETAILS.TRACKING_NUMBERWSH_DELIVERY_DET AILS.SHIP_FROM_LOCATION_ID converted to external value. WSH_DELIVERY_DETAILS.TRACKING_NUMBER
XX
WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID WSH_DELIVERY_DETAILS.MASTER_CONTAINER_ITEM_ID converted to external valueWSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID WSH_DELIVERY_DETAILS.SEAL_CODEWSH_DELIVERY_DETAILS.MA STER_CONTAINER_ITEM_ID converted to external value WSH_DELIVERY_DETAILS.CONTAINER_TYPE_CODE WSH_DELIVERY_DETAILS.SEAL_CODE WSH_DELIVERY_DETAILS.CONTAINER_TYPE_CODE WSH_DELIVERY_DETAILS.COUNTRY_OF_ORIGIN WSH_TRIP_STOPS.ACTUAL_ARRIVAL_DATEWSH_DELIVERY_DETAIL S.COUNTRY_OF_ORIGIN WSH_DELIVERY_DETAILS.DATE_SCHEDULEDWSH_TRIP_STOPS.ACT UAL_ARRIVAL_DATE WSH_DELIVERY_DETAILS.DATE_SCHEDULED
WSH_TRIP_STOPS.ACTUAL_DEPARTURE_DATE WSH_TRIP_STOPS.ACTUAL_DEPARTURE_DATE
WSH_DELIVERY_DETAILS.FREIGHT_CLASS_CAT_ID converted to external value WSH_DELIVERY_DETAILS.FREIGHT_CLASS_CAT_ID converted to external value WSH_DELIVERY_DETAILS.FREIGHT_TERMS_CODE converted to external value WSH_DELIVERY_DETAILS.HAZARD_CLASS_ID converted to external valueWSH_DELIVERY_DETAILS.FREIGHT_TERMS_CODE converted to
Intlptnrint.doc
46
Specifications
Reqd
Element/Attribute
Source (Table.Column Name ) external value WSH_DELIVERY_DETAILS.HAZARD_CLASS_ID converted to external value
SHIPUNIT.IMPORTLICSHIPUNIT.HAZRDM ATL SHIPUNIT.LOADPOINTSHIPUNIT.IMPORT LIC SHIPUNIT.NOTES1 NOTES9SHIPUNIT.LOADPOINT SHIPUNIT.OPERAMT (FREIGHT) (T)SHIPUNIT.NOTES1 - NOTES9 SHIPUNIT.PACKINGSHIPUNIT.OPERAMT (FREIGHT) (T) SHIPUNIT.PACKINGDESCSHIPUNIT.PACK ING SHIPUNIT.QUANTITY (ESTWEIGHT)SHIPUNIT.PACKINGDESC SHIPUNIT.QUANTITY (HEIGHT)SHIPUNIT.QUANTITY (ESTWEIGHT) SHIPUNIT.QUANTITY (LENGTH)SHIPUNIT.QUANTITY (HEIGHT) SHIPUNIT.QUANITTY (LOADINGWT)SHIPUNIT.QUANTITY (LENGTH) SHIPUNIT.QUANTITY (NETWEIGHT)SHIPUNIT.QUANITTY (LOADINGWT)
WSH_DELIVERY_DETAILS.PACKING_INSTRUCTIONS WSH_DELIVERY_DETAILS.PACKING_INSTRUCTIONS
Populate from MTL_SYSTEM_ITEMS
Populate from MTL_SYSTEM_ITEMSPopulate from MTL_SYSTEM_ITEMS Calculate WSH_DELIVERY_DETAILS.GROSS WEIGHT WSH_DELIVERY_DETAILS.NET WEIGHTPopulate from MTL_SYSTEM_ITEMS WSH_DELIVERY_DETAILS.NET_WEIGHT + WSH_DELIVERY_DETAILS.WEIGHT_UOM_CODE for delivery lines = container itemCalculate WSH_DELIVERY_DETAILS.GROSS WEIGHT WSH_DELIVERY_DETAILS.NET WEIGHT WSH_DELIVERY_DETAILS.GROSS_WEIGHT + WSH_DELIVERY_DETAILS.WEIGHT_UOM_CODEWSH_DELIVERY_DET AILS.NET_WEIGHT + WSH_DELIVERY_DETAILS.WEIGHT_UOM_CODE for delivery lines = container item WSH_DELIVERY_DETAILS.VOLUME + WSH_DELIVERY_DETAILS.VOLUME_UOM_CODE for delivery lines = container itemWSH_DELIVERY_DETAILS.GROSS_WEIGHT + WSH_DELIVERY_DETAILS.WEIGHT_UOM_CODE WSH_DELIVERY_DETAILS.VOLUME + WSH_DELIVERY_DETAILS.VOLUME_UOM_CODE for delivery lines = container item WSH_DELIVERY_DETAILS.INVENTORY_ITEM_ID converted to Item Number by joining to mtl_system_items ( this delivery detail id is the delivery detail id of the container record) WSH_DELIVERY_DETAILS.SHIPPING_INSTRUCTIONSWSH_DELIVERY _DETAILS.INVENTORY_ITEM_ID converted to Item Number by joining to mtl_system_items ( this delivery detail id is the delivery detail id of the container record) WSH_DELIVERY_DETAILS.DELIVER_TO_LOCATION_IDWSH_DELIVER Y_DETAILS.SHIPPING_INSTRUCTIONS WSH_DELIVERY_DETAILS.SHIP_METHOD_CODEWSH_DELIVERY_DE TAILS.DELIVER_TO_LOCATION_ID WSH_DELIVERY_DETALS.ITEM_DESCRIPTIONWSH_DELIVERY_DETA ILS.SHIP_METHOD_CODE WSH_DELIVERY_DETALS.ITEM_DESCRIPTION
SHIPUNIT.QUANTITY (TOTWEIGHT)SHIPUNIT.QUANTITY (NETWEIGHT)
SHIPUNIT.QUANTITY (VOLUME)SHIPUNIT.QUANTITY (TOTWEIGHT) SHIPUNIT.QUANTITY (WIDTH)SHIPUNIT.QUANTITY (VOLUME) SHIPUNIT.SHIPMATLIDSHIPUNIT.QUANT ITY (WIDTH) SHIPUNIT.SHIPNOTESSHIPUNIT.SHIPMAT LID
SHIPUNIT.SHIPPOINTSHIPUNIT.SHIPNOT ES SHIPUNIT.SHIPSRVLVLSHIPUNIT.SHIPPOI NT SHIPUNIT.SHPMTLDESCSHIPUNIT.SHIPS RVLVL SHIPUNIT.SHPUNITSEQSHIPUNIT.SHPMT LDESC SHIPUNIT.SHPUNITSTSSHIPUNIT.SHPUNI TSEQ SHIPUNIT.SHPUNITTOTSHIPUNIT.SHPUNI TSTS SHIPUNIT.SPECIALHNDSHIPUNIT.SHPUNI TTOT SHIPUNIT.STAGEPOINTSHIPUNIT.SPECIA LHND SHIPUNIT.TEMPRATURE (ACTUAL)SHIPUNIT.STAGEPOINT
Intlptnrint.doc
47
Specifications
Reqd
Element/Attribute SHIPUNIT.TEMPRATURE (DELIVERY)SHIPUNIT.TEMPRATURE (ACTUAL) SHIPUNIT.TEMPRATURE (LOADING)SHIPUNIT.TEMPRATURE (DELIVERY) SHIPUNIT.TRACKINGIDTYPESHIPUNIT.T EMPRATURE (LOADING) SHIPUNIT.TRANSMETHDSHIPUNIT.TRAC KINGIDTYPE SHIPUNIT.TRANSTERMSSHIPUNIT.TRAN SMETHD SHIPUNIT.USERAREASHIPUNIT.TRANSTE RMS
Write Procedure to Populate this column. WSH_DELIVERY_DETAILS.SHIP_METHOD_CODEWrite Procedure to Populate this column. WSH_NEW_DELIVERIES.FOB_CODEWSH_DELIVERY_DETAILS.SHIP_M ETHOD_CODE WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID (To be called as DELIVERY_DETAIL_NUMBER) WSH_DELIVERY_DETAILS.PACKING_INSTRUCTIONS WSH_DELIVERY_DETAILS.DESCRIPTIVE_FLEXFIELDS WSH_DELIVERY_DETAILS.LOT_NUMBER WSH_DELIVERY_DETAILS.SUBLOT_NUMBER WSH_DELIVERY_DETAILS.REVISION WSH_DELIVERY_DETAILS.SERIAL NUMBER WSH_DELIVERY_DETAILS.TO_SERIAL NUMBER WSH_NEW_DELIVERIES.FOB_CODE WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID (To be called as DELIVERY_DETAIL_NUMBER) WSH_DELIVERY_DETAILS.PACKING_INSTRUCTIONS WSH_DELIVERY_DETAILS.DESCRIPTIVE_FLEXFIELDS WSH_DELIVERY_DETAILS.LOT_NUMBER WSH_DELIVERY_DETAILS.SUBLOT_NUMBER WSH_DELIVERY_DETAILS.REVISION WSH_DELIVERY_DETAILS.SERIAL NUMBER WSH_DELIVERY_DETAILS.TO_SERIAL NUMBER If the Ship Unit is a container, these are the details about the item(s) in the container. If the Ship Unit is a container, these are the details about the item(s) in the container.
SHIPUNIT.USERAREA
INVITEM. X XX X INVITEM.ITEM (REQUIRED)INVITEM. INVITEM.QUANTITY (ITEM) (REQUIRED)INVITEM.ITEM (REQUIRED) INVITEM.AMOUNT (EXTENDED) (T)INVITEM.QUANTITY (ITEM) (REQUIRED) INVITEM.AMOUNT (ITEM) (T)INVITEM.AMOUNT (EXTENDED) (T) INVITEM.COUNTRY ORGINVITEM.AMOUNT (ITEM) (T) INVITEM.FRGHTCLSINVITEM.COUNTRY ORG INVITEM.FRGHTITEMINVITEM.FRGHTCL S INVITEM.HAZRDMATLINVITEM.FRGHTIT EM INVITEM.ITEMDESCINVITEM.HAZRDMA TL INVITEM.ITEMRVINVITEM.ITEMDESC INVITEM.ITEMRVXINVITEM.ITEMRV INVITEM.LOTLEVEL1 LOTLEVEL2INVITEM.ITEMRVX INVITEM.NOTES 1 - NOTES 9INVITEM.LOTLEVEL1 - LOTLEVEL2 INVITEM.OWNRSHPCDEINVITEM.NOTES 1 - NOTES 9 INVITEM.QUANTITY (VOLUME)INVITEM.OWNRSHPCDE INVITEM.QUANTITY (WEIGHT)INVITEM.QUANTITY (VOLUME) INVITEM.SHIPNOTESINVITEM.QUANTIT
Intlptnrint.doc
48
Specifications
Reqd
Element/Attribute Y (WEIGHT) INVITEM.UPCINVITEM.SHIPNOTES INVITEM.USERAREAINVITEM.UPC INVITEM.USERAREA
CONTAINER.
CONTAINER.CONTAINRIDCONTAINER.
CONTAINER.CONTNRSEALCONTAINER.C ONTAINRID CONTAINER.CONTNRTYPECONTAINER.C ONTNRSEAL CONTAINER.DESCRIPTNCONTAINER.CO NTNRTYPE CONTAINER.NOTES 1 - NOTES 9CONTAINER.DESCRIPTN CONTAINER.PACKINGCONTAINER.NOTE S 1 - NOTES 9 CONTAINER.PACKINGDESCCONTAINER. PACKING CONTAINER.PARCNTNRIDCONTAINER.P ACKINGDESC CONTAINER.SHIPMATLIDCONTAINER.P ARCNTNRID CONTAINER.SHPMTLDESCCONTAINER.S HIPMATLID CONTAINER.USERAREACONTAINER.SHP MTLDESC
This is used to send intermediate packaging info. We do not have the ability to send intermediate packaging within the shipping unit, so we will not use this segment. WSH_DELIVERY_DETAILS.CONTAINER_NAMEThis is used to send intermediate packaging info. We do not have the ability to send intermediate packaging within the shipping unit, so we will not use this segment. WSH_DELIVERY_DETAILS.SEAL_CODEWSH_DELIVERY_DETAILS.CO NTAINER_NAME WSH_DELIVERY_DETAILS.CONTAINER_TYPE_CODE WSH_DELIVERY_DETAILS.SEAL_CODE WSH_DELIVERY_DETAILS.CONTAINER_TYPE_CODE
WSH_DELIVERY_DETAILS.INVENTORY_ITEM_ID converted to ITEM NUMBER by joining to mtl_system_items WSH_DELIVERY_DETAILS.ITEM_DESCRIPTION WSH_DELIVERY_DETAILS.INVENTORY_ITEM_ID converted to ITEM NUMBER by joining to mtl_system_items WSH_DELIVERY_ASSIGNMENTS.DELIVERY_DETAIL_ID (To be called as DELIVERY_DETAIL_NUMBER) WSH_DELIVERY_ASSIGNMENTS.PARENT_DELIVERY_DETAIL_ID (To be called as PARENT_DELIVERY_DETAIL_NUMBER) HEIGHT From mtl_system_items LENGTH - From mtl_system_items WEIGHTWSH_DELIVERY_DETAILS. GROSS_WEIGHT WSH_DELIVERY_DETAILS. NET_WEIGHT VOLUME WSH_DELIVERY_DETAILS. VOLUME WIDTH- From mtl_system_items LOT- WSH_DELIVERY_DETAILS. LOT_NUMBER SUBLOTWSH_DELIVERY_DETAILS. SUBLOT_NUMBER WSH_DELIVERY_DETAILS. REVISION WSH_DELIVERY_DETAILS. SERIAL NUMBER WSH_DELIVERY_DETAILS. TO_SERIAL NUMBER WSH_DELIVERY_DETAILS. SHIP_FROM_LOCATION_ID converted to code (To be called as SHIP_FROM_LOCATION LOCATION) WSH_DELIVERY_DETAILS. DELIVER_TO_LOCATION_ID converted to code (To be called as DELIVER_TO_LOCATION) WSH_DELIVERY_DETAILS. TRACKING_NUMBER WSH_DELIVERY_DETAILS. COUNTRY_OF_ORIGIN WSH_TRIP_STOPS.ACTUAL_ ARRIVAL_DATE WSH_DELIVERY_DETAILS. DATE_SCHEDULED WSH_TRIP_STOPS.ACTUAL_ DEPARTURE_DATE WSH_DELIVERY_DETAILS. SHIP_METHOD_CODE WSH_DELIVERY_DETAILS. FREIGHT_CLASS_CAT_ID converted to external value (To be called as FREIGHT_CLASS_CATEGORY) WSH_DELIVERY_DETAILS. FREIGHT_TERMS_CODE converted to external value WSH_DELIVERY_DETAILS. HAZARD_CLASS_ID converted to external value
Intlptnrint.doc
49
Specifications
Reqd
Element/Attribute
Source (Table.Column Name ) (To be called as HAZARD_CLASS or as HAZARD_CLASS_CODE) WSH_DELIVERY_DETAILS. FOB_CODE WSH_DELIVERY_DETAILS. SHIPPING_INSTRUCTIONS WSH_DELIVERY_DETAILS. PACKING_INSTRUCTIONS WSH_DELIVERY_DETAILS. Descriptive Flexfields WSH_DELIVERY_DETAILS.ITEM_DESCRIPTION
CONTAINER.USERAREA
WSH_DELIVERY_ASSIGNMENTS.DELIVERY_DETAIL_ID (To be called as DELIVERY_DETAIL_NUMBER) WSH_DELIVERY_ASSIGNMENTS.PARENT_DELIVERY_DETAIL_ID (To be called as PARENT_DELIVERY_DETAIL_NUMBER) HEIGHT From mtl_system_items LENGTH - From mtl_system_items WEIGHTWSH_DELIVERY_DETAILS. GROSS_WEIGHT WSH_DELIVERY_DETAILS. NET_WEIGHT VOLUME WSH_DELIVERY_DETAILS. VOLUME WIDTH- From mtl_system_items LOT- WSH_DELIVERY_DETAILS. LOT_NUMBER SUBLOTWSH_DELIVERY_DETAILS. SUBLOT_NUMBER WSH_DELIVERY_DETAILS. REVISION WSH_DELIVERY_DETAILS. SERIAL NUMBER WSH_DELIVERY_DETAILS. TO_SERIAL NUMBER WSH_DELIVERY_DETAILS. SHIP_FROM_LOCATION_ID converted to code (To be called as SHIP_FROM_LOCATION LOCATION) WSH_DELIVERY_DETAILS. DELIVER_TO_LOCATION_ID converted to code (To be called as DELIVER_TO_LOCATION) WSH_DELIVERY_DETAILS. TRACKING_NUMBER WSH_DELIVERY_DETAILS. COUNTRY_OF_ORIGIN WSH_TRIP_STOPS.ACTUAL_ ARRIVAL_DATE WSH_DELIVERY_DETAILS. DATE_SCHEDULED WSH_TRIP_STOPS.ACTUAL_ DEPARTURE_DATE WSH_DELIVERY_DETAILS. SHIP_METHOD_CODE WSH_DELIVERY_DETAILS. FREIGHT_CLASS_CAT_ID converted to external value (To be called as FREIGHT_CLASS_CATEGORY) WSH_DELIVERY_DETAILS. FREIGHT_TERMS_CODE converted to external value WSH_DELIVERY_DETAILS. HAZARD_CLASS_ID converted to external value (To be called as HAZARD_CLASS or as HAZARD_CLASS_CODE) WSH_DELIVERY_DETAILS. FOB_CODE WSH_DELIVERY_DETAILS. SHIPPING_INSTRUCTIONS WSH_DELIVERY_DETAILS. PACKING_INSTRUCTIONS WSH_DELIVERY_DETAILS. Descriptive Flexfields This CHARGE section is for a CONTAINER. WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to external valueThis CHARGE section is for a CONTAINER. WSH_FREIGHT_COSTS.TOTAL_AMOUNT WSH_FREIGHT_COSTS.CURRENCY_CODEWSH_FREIGHT_COSTS.FREI GHT_COST_TYPE_ID converted to external value WSH_FREIGHT_COSTS.TOTAL_AMOUNT WSH_FREIGHT_COSTS.CURRENCY_CODE WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to FREIGHT_COST_TYPE WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to FREIGHT_COST_TYPE
X XX
CHARGE. CHARGE.CHARGEID (REQUIRED)CHARGE. CHARGE.OPERAMT (EXTENDED) (T) (REQUIRED)CHARGE.CHARGEID (REQUIRED) CHARGE.AMOUNT (EXTENDED) (T)CHARGE.OPERAMT (EXTENDED) (T) (REQUIRED) CHARGE.CHARGETYPECHARGE.AMOUN T (EXTENDED) (T) CHARGE.CHGLINENUMCHARGE.CHARG ETYPE CHARGE.DESCRIPTNCHARGE.CHGLINEN UM CHARGE.USERAREA CHARGE.DESCRIPTN CHARGE.USERAREA
Intlptnrint.doc
50
Specifications
Reqd
Element/Attribute INVITEM. INVITEM.ITEM (REQUIRED)INVITEM. INVITEM.QUANTITY (ITEM) (REQUIRED)INVITEM.ITEM (REQUIRED) INVITEM.AMOUNT (EXTENDED) (T)INVITEM.QUANTITY (ITEM) (REQUIRED) INVITEM.AMOUNT (ITEM) (T)INVITEM.AMOUNT (EXTENDED) (T) INVITEM.COUNTRY ORGINVITEM.AMOUNT (ITEM) (T) INVITEM.FRGHTCLSINVITEM.COUNTRY ORG INVITEM.FRGHTITEMINVITEM.FRGHTCL S INVITEM.HAZRDMATLINVITEM.FRGHTIT EM INVITEM.ITEMDESCINVITEM.HAZRDMA TL INVITEM.ITEMRVINVITEM.ITEMDESC INVITEM.ITEMRVXINVITEM.ITEMRV INVITEM.LOTLEVEL1 LOTLEVEL2INVITEM.ITEMRVX INVITEM.NOTES 1 - NOTES 9INVITEM.LOTLEVEL1 - LOTLEVEL2 INVITEM.OWNRSHPCDEINVITEM.NOTES 1 - NOTES 9 INVITEM.QUANTITY (VOLUME)INVITEM.OWNRSHPCDE INVITEM.QUANTITY (WEIGHT)INVITEM.QUANTITY (VOLUME) INVITEM.SHIPNOTESINVITEM.QUANTIT Y (WEIGHT) INVITEM.UPCINVITEM.SHIPNOTES INVITEM.USERAREAINVITEM.UPC INVITEM.USERAREA CHARGE. CHARGE.CHARGEID (REQUIRED)CHARGE. CHARGE.OPERAMT (EXTENDED) (T) (REQUIRED)CHARGE.CHARGEID (REQUIRED) CHARGE.AMOUNT (EXTENDED) (T)CHARGE.OPERAMT (EXTENDED) (T) (REQUIRED) CHARGE.CHARGETYPECHARGE.AMOUN T (EXTENDED) (T) CHARGE.CHGLINENUMCHARGE.CHARG ETYPE CHARGE.DESCRIPTNCHARGE.CHGLINEN UM CHARGE.USERAREA CHARGE.DESCRIPTN CHARGE.USERAREA
X XX X
X XX
This CHARGE section is for SHIPUNIT. WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to external valueThis CHARGE section is for SHIPUNIT. WSH_FREIGHT_COSTS.TOTAL_AMOUNT WSH_FREIGHT_COSTS.CURRENCY_CODEWSH_FREIGHT_COSTS.FREI GHT_COST_TYPE_ID converted to external value WSH_FREIGHT_COSTS.TOTAL_AMOUNT WSH_FREIGHT_COSTS.CURRENCY_CODE WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to FREIGHT_COST_TYPE WSH_FREIGHT_COSTS.FREIGHT_COST_TYPE_ID converted to FREIGHT_COST_TYPE
Table 11: Element description of Delivery Compliance Request Message
Intlptnrint.doc
51
Specifications
Appendix F Acknowledgements
XML Acknowledgement
Oracle ITM adapter requires a synchronous acknowledgment from the partner ITM application. This ensures that a proper connection has been established and the request is received successfully. The ITM adapter supports Open Application Group (OAG) Confirmation Business Object Document (Revision 7.2.1) for inbound acknowledgements. Additionally, Oracle XML Gateway can also be setup to provide asynchronous XML acknowledgements for the response messages from partner application. The structure of the XML acknowledgment message is illustrated below. For additional details about the XML acknowledgment message please review Oracle XML Gateway documentation.
Diagram Note: CONFIRM Required = Solid boxes Optional = Dashed boxes
CONFIRMMSG
Fig 23: Acknowledgement Message Structure (Confirm_BOD_004)
HTML Acknowledgement
The transport layer in Oracle XML Gateway provides a HTML based messaging acknowledgement upon receiving a response from the partner ITM application. The details of the HTML acknowledgment message are given below. For additional information about the XML acknowledgment message please review Oracle XML Gateway documentation.
Intlptnrint.doc
52
Specifications
<HTML><BODY><TABLE> <TR> <TD>STATUS_CODE</TD> <TD>2001</TD> </TR> <TR> <TD>STATUS_DESCRIPTION</TD> <TD></TD> </TR> <TR> <TD>MESSAGE_RECEIPT_ID</TD> <TD></TD> </TR> </TABLE></BODY></HTML>
Intlptnrint.doc
53
Specifications
Appendix G Oracle XML Gateway Setup
Oracle ITM adapter leverages many of the messaging and interface capabilities of Oracle XML Gateway. This makes it imperative that all the setup of XML Gateway are complete before the ITM adapter can be utilized for a successful end to end communication. The setups described in this section are the additional setup needed in XML Gateway for ITM adapter. For a complete list of setup in Oracle XML Gateway please refer to Oracle XML Gateway documentation available on Metalink (metalink.oracle.com).
Define Transactions
Resp: XML Gateway Navigate: XML Gateway Header: Party Type: Customer Transaction Type: ITM Transaction Sub Type: EXPORT_COMPLIANCE External Transactions (Lines): Standard Code: OAG External Transaction Type: ITM External Transaction Sub Type: EXPORT_COMPLAINCE Queue: APPS.ECX_IN_OAG_Q Save & Close the form.
Define Transactions
Define Trading Partners

Resp: XML Gateway Navigate: XML Gateway Header: Trading Partner Type: Customer Trading Partner Name: ITM Application Trading Partner Site: Will automatically display the customer address on enabling the LOV Company Admin Email: john.Doe@abc.com
Define Trading Partners
Intlptnrint.doc
54
Specifications
Trading Partner Details: Transaction Type: ITM Map: WSHITEIN Source Trading Partner Location Code: ITM Application (should be the value defined in EDI Location for customer) Save & Close the form.
Intlptnrint.doc
55
Specifications
Appendix H Additional Resources
The following are some of the additional documentation, which will help setup various Oracle Applications including Oracle XML Gateway. These are available on metalink (metalink.oracle.com) under the product documentation section. Oracle Shipping Execution User Guide. Oracle Order Management Implementation Guide. Oracle XML Gateway User Guide. Understanding the Oracle Transport Agent Messaging Protocol, White Paper. XML Gateway Setup Testing and Diagnostics, White Paper. Configuring the Oracle XML Transport Agent (OXTA) With Oracle Applications 11i, White Paper.
Intlptnrint.doc
56

ITM Partner Cookbook

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ITM Partner Cookbook

Uploaded by

Copyright:

Available Formats

Oracle International Trade Management (ITM) Partner Integration: Specifications

Oracle International Trade Management Partner Integration

Oracle Confidential - For internal use only

Oracle International Trade Management Partner Integration

Figures & Tables

Oracle Confidential - For internal use only

Oracle International Trade Management Partner Integration

ITM Process Flow

It is important to point out that an international trade involves both of these

Oracle International Trade Management Partner Integration

International Trade Management: Process Flow

Freight Forwarder/ Consolidator

Exports Flow: Sell Side

Embargo Country Screening Restricted Party Screening

Item Embargo Country Screening Classification Restricted Party Screening

Imports Flow: Buy Side

Fig 1: International Trade Management Process Flow Diagram

Oracle Confidential - For internal use only

Oracle International Trade Management Partner Integration

Interfaces with Partner Application

Oracle Quoting and other Apps

Oracle Order Management Oracle Shipping Execution

Oracle ITM Partner Integration

Oracle Purchasing/iProcurement Oracle Payables

Fig 2: Oracle ITM Partner Integration - Flow Diagram

Oracle Confidential - For internal use only

Oracle International Trade Management Partner Integration

Export Compliance Screening

Oracle Confidential - For internal use only

Oracle International Trade Management Partner Integration

Oracle Confidential - For internal use only

Oracle International Trade Management Partner Integration

(Oracle Order Mgt.)

(Oracle Shipping Execution)

Oracle XML Gateway

ITM Application XML Adapter

Partner ITM Application

Create / Update Product

Create / Update Partner

Export Compliance Determination

Send XML Response

Export Compliance Determination

Send XML Response

Compliance User Review

Compliance User Review

Fig 3: Integration Flow Diagram along with Overview Messaging

Oracle Confidential - For internal use only

Oracle International Trade Management Partner Integration

Oracle Bill of Material

Oracle ITM Adapter

Partner ITM Application

Party Synchronization Request XML

Oracle ITM Adapter

Partner ITM Application

Fig 5: Party Synchronization Overview Messaging

Oracle Confidential - For internal use only

Oracle International Trade Management Partner Integration

Order Compliance Request XML Generic Export Compliance

Oracle Order Management

Oracle ITM Adapter

Partner ITM Application

Oracle XML Gateway