1. Collaborative Planning Training

2. Agenda  Collaboration Overview  Setting up Collaborative Planning  User Setups  Collaborative Planning and Forecasting  Vendor Managed Inventory (VMI)  Collaborative Inventory Visibility  Advanced Topics  Installing Collaborative Planning  Troubleshooting Tips

3. Collaborative Planning  Architecture  Deployment configurations  Installation checklist  Setting up XML gateway Installing Collaborative Planning

4. Architecture  CP shares the same component architecture as APS – Separates transaction processing in source ERP instances from the planning calculations in the destination – Allows installation on separate machines to optimize performance – Supports multiple source instances Component architecture

5. Architecture  Key tables – MSC_SUP_DEM_ENTRIES: A fully de-normalized table that stores all supplies and demands in Collaborative Planning.  Data is loaded into this table using: ­ Flat file loads ­ XML loads ­ Collections from ERP ­ Manually, through the UI ­ Publish processes in ASCP and ODP Data model overview

6. Architecture  Key tables – MSC_COMPANIES: Stores the list of companies (customers and suppliers)  The company name in the profile option MSC: Operator Company Name is seeded into this table with Company_ID = 1 – MSC_COMPANY_SITES: Stores the list of company sites. Sites may be customer sites, supplier sites, or inventory organizations. – MSC_COMPANY_RELATIONSHIPS: Stores the relationships – customer of and supplier of - between companies in Collaborative Planning. – MSC_x_EXCEPTION_DETAILS: Stores the exceptions generated by the Supply Chain Event Manager, Custom Exceptions, and VMI Replenishment Engine Data model overview

7. Architecture  Key tables – MSC_SECURITY RULES: Stores the security rules defined in Collaborative Planning. Data model overview

8. Architecture  CP supports flat file data loads for the following supply/demand order types: – ASN – Historical sales – Negotiated capacity – Order forecast – Purchase order – Purchase order acknowledgement – Purchase requisition – Safety stock – Sales forecast – Sales order – Sell through forecast – Shipment receipt – Supply commit Flat file data loads

9. Architecture  During flat file uploads, you can specify a sync indicator to denote if you are deleting records or inserting records – R (Replace): For a row in the upload file, the system will search for all records in CP that match the item, publisher, publisher site, supplier, supplier site (or customer, customer site for sales orders), order type, order number, release number, line number, key date, end order number, and end order line number and delete them. This is done for each row in the upload file, at the end of which the new rows are inserted into CP. – D (Delete): Allows you to only delete rows that match the above criteria. Flat file data loads

10. Deployment configurations Single machine implementation ERP Concurrent Manager ASCP/CP Staging tables For small implementations

11. Deployment configurations 2 machine implementation Concurrent Manager ASCP/CP Staging tables ERP For larger implementations

12. Deployment configurations 3 machine implementation Concurrent Manager ASCP/CP Staging tables ERP Legacy Multiple source instances

13. Installation checklist  Acquire and install the 11.5.8 CD  If you are planning to run collections from Oracle 11i, 11.0, or 10.7 instances, install all collection patches available to date  Set the MSC: Configuration profile option to the desired value (APS+CP or CP as appropriate)  Set the MSC: Operator Company Name profile option to the desired name of your company  Ensure that the OA_FRAME_WORK points to the correct url: generally the Apache server port  When running data collections from Oracle source systems, set the option to enable User Company association to yes. This ensures that supplier and customer users created in the source system are created in the planning server  Run the program ‘Build Collaborative Planning Calendar’ Steps

14. Setting up XML Gateway  XML Gateway receives inbound transactions from trading partners  Message designer – A wizard-based tool used to define message maps  Message setup – Used to define how messages will be exchanged between your company and trading partners  Execution engine – XML Gateway execution engine interfaces with the E-Business suite to retrieve data from, and populate data into, tables * Refer to the XML Gateway Users Guide for more information Overview

15. Setting up XML Gateway Transaction delivery overview Filter to eliminate, Custom and seeded exceptions Pegging Demand-supply allocation, Simulation, Workflow Business intelligence Trading partner transmits XML message Queue handler raises business event OXTA listens for XML messages and deposits in queue Seeded APS subscription for inbound message fires a procedure Procedure parses the incoming XML and inserts data into CP tables Oracle Collaborative Planning

16. Setting 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 Email Address with the email id of the recipient of error notifications * Refer to the XML Gateway Users Guide for more information Checklist

17. Setting up XML Gateway  In the event that the XML Gateway execution engine fails to process XML messages: – Review the error messages in the log file located in the directory specified in ECX: Log File Path profile option – Review ECX_OBJECTS and ensure that 000_sync_forecast_001.dtd has been loaded – Review ECX_OBJECTS and ensure that a map has been loaded. * Refer to the XML Gateway Users Guide for more information Troubleshooting