Integrating with Oracle Fusion Cloud Supply Chain Collaboration

This use case provides information about the various ways to load forecast data into Oracle Supply Chain Collaboration.

Description	Integration Type	Integration Options	Notes
Load order forecast data into Supply Chain Collaboration using files. Import collaboration order forecasts into the Oracle Supply Chain Collaboration interface tables using the file-based data import (FBDI) Collaboration Order Forecasts process. The data contains plan source, supplier item header data, and date-specific quantities. After loading, run the Supply Planning Collaboration Decompostion scheduled process.	Inbound	FBDI	The supply plan name is the supply plan used to generate the collaboration order forecasts. It can be a supply plan from Oracle Fusion Cloud Supply Chain Planning or a plan from an external planning application. The name should map to an existing collaboration plan that's defined in Oracle Supply Chain Collaboration.
Load order forecast data into Oracle Supply Chain Collaboration using REST APIs. Use the Collaboration Order Forecast Requests REST API to create order forecast requests. The data that's submitted will be processed asynchronously. The response of the REST API call will include a CollaborationOrderForecastRequestId, which can be used to query the status of the overall request and of individual entries included in the original request.	Inbound	REST API	The requestStatusDetails child resource of the response provides the status of the request.
Decompose imported data into Oracle Supply Collaboration. After the order forecast data is loaded into the interface tables, run the Supply Planning Collaboration Decomposition scheduled process to process the data, evaluate forecast exceptions, and make the order forecast data available to suppliers and collaboration planners. The decomposition process is run automatically by the Publish Order Forecast scheduled process but must be manually scheduled when loading data with FBDI.	Inbound	Scheduled process	If the Exclude unpublished order forecasts with zero quantities from the decomposition process option is set to Yes in the Manage Supply Chain Collaboration Settings page, then relationship candidates and related order forecasts (if a previous forecast doesn’t exist) aren't created for zero quantity order forecast during Decomposition process
Export collaboration order forecasts and commit data to files. Use the Export Collaboration Order Forecasts scheduled process to export collaboration order forecasts or commit data to comma-separated values (CSV) files. When setting up this process in Oracle Enterprise Scheduler, you can set the supply plan to export and filter the export collection by specifying a supplier or item, and choose to include current forecasts, current commits, previous forecasts, and previous commits.	Outbound	Scheduled process	–
Import supply commits quantities to existing order forecasts using files. Suppliers can download order forecasts to a spreadsheet, fill in the commit values, and upload the new commit data back into the forecast.	Inbound	CSV files Scheduled processes	Both downloads and uploads will be processed using scheduled processes available on the Oracle Supply Chain Collaboration Download Files and Upload Files pages.
Export collaboration order forecasts and commit data using REST APIs. Use the Collaboration Order Forecasts REST resource to get the current planning cycle order forecasts that are published for supplier collaboration. This includes: Any existing commit quantities. Forecast and commit exceptions associated with the collaboration order forecast, such as forecast changes and commit mismatches. Reference quantities, such as purchasing measures. Import supply commits quantities to existing order forecasts using REST APIs. You can use this same Collaboration Order Forecasts REST resource to respond to collaboration order forecasts by providing supply commits.	Inbound Outbound	REST APIs	See the Use Cases section in REST API for Oracle Fusion Cloud SCM for examples of how to integration with Oracle Supply Collaboration using REST APIs.
Exchange forecast and commit data with suppliers using B2B messaging. You can publish order forecasts to suppliers using outbound B2B messaging in Oracle Fusion Collaboration Messaging Framework. Suppliers can send commit responses using inbound B2B messaging. Commit exceptions are run and commit decomposition started.	Inbound Outbound	B2B Messaging using Oracle Fusion Collaboration Messaging Framework	There are two different processes available for the orchestration of B2B messages. For more information, see Overview of Orchestration.
Import supplier on-hand quantitites using files. You can upload supplier on-hand quantities for your items using CSV files. Download the spreadsheet template from the Manage Supplier On-Hand Quantities page and populate the available item quantities.	Inbound	CSV files Scheduled processes	Uploaded files will be processed using a scheduled process that's available on the Oracle Supply Chain Collaboration Upload Supplier On-Hand Quantities page for review and error diagnosis. The uploaded file will be available for 30 days.