This appendix covers the following topics:
Oracle Collaborative Planning enables trading partners to establish and maintain an electronic relationship by transmitting order information via XML. Oracle Collaborative Planning is capable of receiving as well as sending XML compliant documents for supply and demand transactions.
Any supply chain participant, with an established trading partner relationship, can post transactions to Oracle Collaborative Planning. Based on the specifications embedded in an XML transaction, Oracle Collaborative Planning can interpret supply and demand order information.
The execution engine is an XML Gateway execution engine interfaces with the Oracle e-Business Suite to retrieve data from, and populate data into, tables
Currently, support through the XML gateway is restricted to inbound transactions; i.e. transactions publishing forecast and supply commit data into Collaboration Planning. Outbound transactions are currently not supported through the XML gateway. For more information about how Collaborative Planning integrates with XML Gateway, refer to Oracle XML Gateway User Guide.
There are two major ways by which you can populate Oracle Collaborative Planning using XML.
Supply/Demand load
Legacy Integration Load
Like loading flat file, you can communicate supply demand transactions using XML with Oracle Collaborative Planning. By this, your data is populated directly in Oracle Collaborative Planning. You can also integrate with legacy systems by providing different order types to be used in Collaborative Planning, such as sales forecast, purchase order, sales order, safety stock, projected available balance, order forecast, and supply commit as XML documents into Collaborative Planning.
The DTD (Document Type Definition) used for Supply/Demand XML loads is
000_sync_forecast_001.dtd
Some of the key fields in the Supply/Demand XML load are:
Order's change status or Sync indicator (R: Replace or Add, D: Delete)
Order type
Order number
Line number
Customer's name and site
Supplier's name and site
Item
Quantity
UOM
Date information (Ship Date, Receipt Date)
Shipment information (Ship From or Ship To information)
Version (if applicable)
Forecast name (if applicable)
For more information about XML, contact your System Administrator or review the DTD. The content of an XML transaction for supply and demand information is similar to flat file loads for supply and demand. You can download the OA Template using Oracle Collaborative Planning. The supplydemand.dat flat file can be used as a template for the content of an XML transaction. For more information about downloading and uploading flat files into Oracle Collaborative Planning, refer to Loading and Publishing Data in Setup.
Perform the following steps to set up XML Gateway:
Set up the profile ECX: Log File Path with a valid path. Include this path in the utl_file_dir parameter in the init.ora file.
Set up the profile ECX: System Administrator e-mail Address with the e-mail address of the error notification recipient.
Another type of XML transaction available in Oracle Collaborative Planning is called Legacy Integration Loads. The difference between Legacy Integration loads and Supply/Demand loads is that all data loaded through Legacy Integration loads is also available to other Oracle Advanced Planning products such as Oracle Advanced Supply Chain Planning. In Legacy Integration loads data from XML documents are first loaded to interface tables for Oracle Advanced Supply Chain Planning and then the appropriate data is transferred to Oracle Collaborative Planning.
There are separate DTDs used for different entities. Contact your system administrator to find the right DTD for your transaction.
XML Legacy Integration loads are most suitable for synchronizing setup data among instances and among trading partners. Supply/Demand loads are most suitable for communicating supply and demand transactions among trading partners.