Document History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Update Version	Notes
18 DEC 2018	Update 18C	Revised update 18C.
20 APR 2018	Update 18B	Delivered new features in update 18B.
02 FEB 2018	Update 18A	Revised update 18A.

Update 18C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Feature	Notes
18-DEC-2018	Manage Collaboration Order Forecasts Using a REST Service	Updated document. Corrected role details.
18 DEC 2018	Manage Collaboration Order Forecast History Using a REST Service	Updated document. Corrected role details.
18 DEC 2018	Manage Collaboration Order Forecast Requests Using a REST Service	Updated document. Corrected role details.
09 OCT 2018	Manage Collaboration Order Forecast History Using a REST Service	Updated document. Added role details.
09 OCT 2018	Manage Collaboration Order Forecasts Using a REST Service	Updated document. Added role details.
27 SEP 2018		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

Optional Uptake of New Features (Opt In)

We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can opt in to a feature in two ways:  by using the New Features work area, or by using the Setup and Maintenance work area.

To opt in using the New Features work area:

1. Click the Navigator, and then click New Features (under the My Enterprise heading).
2. On the New Features page, select the offering that includes new features you’d like to review.
3. Click Go to Opt In for any feature that you want to opt in to.
4. On the Edit Features page, select the Enable option for the feature, and then click Done.

To opt in using the Setup and Maintenance work area:

1. Click the Navigator, and then click Setup and Maintenance.
2. On the Setup page, select your offering, and then click Change Feature Opt In.
3. On the Opt In page, click the Edit Features icon.
4. On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close. 
5. Click Done.

Feature Summary

Supply Chain Collaboration

Today’s global supply chains increase manufacturers’ reliance on suppliers, contract manufacturers, and other trading partners. To be successful, companies must synchronize their activities across multiple tiers of trading parties. Oracle Supply Chain Collaboration Cloud enables companies to jointly plan supply, gain visibility into trading partner data, coordinate contract manufacturing execution, and measure performance across their trading networks. Trading partners are actively involved in the decision-making process, so they can exchange early warning signs and collaboratively resolve supply chain issues. Depending on the size and technical sophistication of each supplier, your company can interact using a portal-based user interface, standards-based B2B messages, or web services. Customers can also tailor Oracle Supply Chain Collaboration Cloud’s flexible, predefined business processes to their unique requirements. Enhanced collaboration results in more dynamic trading relationships, as well as increased reliability and efficiency of supply.

Integrate and Extend Supply Chain Collaboration Using REST Services

Oracle Supply Chain Collaboration Cloud provides web services to enable and simplify integration with external systems.

Manage Collaboration Planners Using a REST Service

Use a public REST API to create and manage collaboration planners. You can use this service to define collaboration planners at the ship-from/supplier level or the ship-from/supplier site level, depending upon whether you want the planners to have access to all sites and items collaborated with the specific supplier, or only to items from a specific supplier site.

Use the Collaboration Planners REST service to do the following:

• Create a collaboration planner for supplier order forecast collaboration
• Update a collaboration planner's data access security
• Delete a collaboration planner
• Search for collaboration planners by key attributes such as status, username, and security context

With the Collaboration Planners REST service, you can now integrate user creation with your business process for improved speed and efficiency.

Steps to Enable

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Key Resources

• REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role Information

• Privilege Name and Code:
  • Manage Collaboration Planners (VCS_MANAGE_COLLAB_PLANNERS)
• Job Role Name and Code:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Manage Collaboration Order Forecast Requests Using a REST Service

Use a public REST API to create and manage current collaboration cycle order forecasts from external planning applications. You can also use this service to submit mid-cycle updates to order forecasts, and to monitor the status of your forecast submissions.

Use the Collaboration Order Forecast Request REST service to do the following:

• Create and update current collaboration cycle order forecasts 
• Monitor and review the status of forecast requests submitted within the last 7 days
• Search for forecast requests submitted within the last 7 days by using key attributes such as status, ship-from supplier, ship-to organization, and item

Steps to Enable

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Key Resources

• REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role Information

• Privilege Name and Code:
  • Import Collaboration Order Forecast Requests using a Web Service (VCS_IMPORT_COLLAB_ORDER_FORECAST_REQUESTS_WEBSERVICE)

• Job Role Name and Code:
  • Supply Chain Integration Specialist (ORA_RCS_SUPPLY_CHAIN_INTEGRATION_SPECIALIST)

Manage Collaboration Order Forecast History Using a REST Service

Use a public REST API to view historical collaboration cycle order forecasts and commits. You can use this REST API to retrieve the historical order forecasts for analytical purposes across multiple collaboration cycles.

Use the Collaboration Order Forecast History REST service to do the following:

• View historical collaboration order forecasts 
• Search for historical collaboration order forecasts by using key attributes such as ship-from supplier, ship-to organization, item, and collaboration cycle.

Steps to Enable

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Key Resources

• REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role Information

To use this feature, the following privileges or roles are required:

ENTERPRISE USERS

• Privilege Name and Code:
  • View Order Forecasts (VCS_VIEW_ORDER_FORECAST )
• Job Role Name and Code:
  • Supply Chain Collaboration Planner (ORA_VCS_SUPPLY_CHAIN_COLLABORATION_PLANNER)

SYSTEM INTEGRATION USERS

For system integration use cases where data security is not needed, the following privilege or job role can be used.

• Privilege Name and Code:
  • Manage Collaboration Order Forecasts using Web Service (VCS_MANAGE_COLLAB_ORDER_FORECAST_WEBSERVICE)
• Job Role Name and Code:
  • Supply Chain Integration Specialist (ORA_RCS_SUPPLY_CHAIN_INTEGRATION_SPECIALIST)

Manage Collaboration Order Forecasts Using a REST Service

Use a public REST API to view and manage current collaboration cycle order forecasts from Oracle Planning Central Cloud, Oracle Supply Planning Cloud and from external planning applications. You can use this REST API to update the order forecast in the current collaboration cycle, or make mid-cycle changes.

Use the Collaboration Order Forecast REST service to do the following:

• View collaboration order forecasts for the current collaboration cycle 
• Search for current collaboration cycle order forecasts by using key attributes such as status, ship-from supplier, ship-to organization, and item.
• Commit to collaboration order forecasts as a supplier, contract manufacturer, or enterprise user
• Edit forecasts as a contract manufacturer or enterprise user

Steps to Enable

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Key Resources

• REST API for Oracle Supply Chain Management Cloud, available on the Oracle Help Center.

Role Information

To use this feature, the following privileges or roles are required:

ENTERPRISE USERS

• Privilege Name and Code:
  • View Order Forecasts (VCS_VIEW_ORDER_FORECAST)
  • Commit to Order Forecasts as Enterprise User (VCS_COMMIT_ORDER_FORECAST_ENTERPRISE)
  • Edit Forecasts as Enterprise User (VCS_EDIT_ORDER_FORECAST_ENTERPRISE)

These privileges are assigned to:

• Job Role Name and Code:
  • Supply Chain Collaboration Planner (ORA_VCS_SUPPLY_CHAIN_COLLABORATION_PLANNER)

SUPPLIER USERS

• Privilege Name and Code:
  • View and Commit to Order Forecasts as Supplier User (VCS_COMMIT_ORDER_FORECAST_SUPPLIER)
  • Edit Forecasts as Ship-to Supplier (VCS_EDIT_ORDER_FORECAST_SHIPTO)
  • Edit Commits as Ship-to Supplier (VCS_COMMIT_ORDER_FORECAST_SHIPTO)

These privileges are assigned to:

• Job Role Name and Code:
  • Supplier Demand Planner (ORA_POS_SUPPLIER_DEMAND_PLANNER)

SYSTEM INTEGRATION USERS

For system integration use cases where data security is not needed, the following privilege or job role can be used

• Privilege Name and Code:
  • Manage Collaboration Order Forecasts using a Web Service (VCS_MANAGE_COLLAB_ORDER_FORECAST_WEBSERVICE)

• Job Role Name and Code:
  • Supply Chain Integration Specialist (ORA_RCS_SUPPLY_CHAIN_INTEGRATION_SPECIALIST)

Collaboration Messaging Framework

Business-to-business (B2B) messaging is a key component of collaborative relationships and can increase the quality, quantity, and frequency of information that can be exchanged between trading partners.  However, the differences in B2B standards, technical capabilities of trading partners, and the diversity of trading partners can make this costly to establish and maintain.  Oracle Supply Chain Collaboration and Visibility Cloud manages B2B communications with trading partners by leveraging the Oracle Collaboration Messaging Framework, a next-generation B2B messaging platform that maps and routes standards-based B2B messages through a B2B solution provider, on-premise B2B application, or direct to the trading partner.  Oracle Collaboration Messaging Framework is a common infrastructure component that is included with all Oracle Cloud Applications environments at no additional charge.  It is also tightly integrated with Oracle Cloud Applications, making it easy for Oracle Supply Chain Collaboration Cloud customers to set up and manage multiple trading partner connections.

Manage B2B Message Transactions Using a REST Service

Use a public REST API to view all B2B messages that Oracle Collaboration Messaging Framework Cloud processes. You can also view this information online by clicking the Manage Collaboration Messaging History task

Use the B2B Message Transactions REST service to:

• Find all B2B messages processed for a particular date or date range.
• Find all B2B messages processed for a specific trading partner.
• Find all B2B messages processed for a specific document type (for example, a purchase order).

Steps to Enable

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Key Resources

• REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role Information

• Privilege Name and Code:
  • Manage B2B Message Transactions using a REST Service (CMK_B2B_MESG_TRXN_REST_SERVICE)
• Job Role Name and Code:
  • B2B Administrator (ORA_CMK_B2B_ADMINISTRATOR)

Support PEPPOL for European Regulatory Requirements

Support Pan-European Public Procurement On-Line (PEPPOL) regulatory requirements by sending and receiving invoices using the UBL XML format. This B2B message format is provided in addition to the standard OAGIS XML format.

Support for inbound invoices in UBL XML format is available as a new collaboration messaging definition. You can receive invoices in the UBL XML format in addition to the existing ability to send UBL XML invoices.

Steps to Enable

To enable this feature:

1. In the Setup and Maintenance work area, select your offering.
2. In your offering, search for and select the Manage B2B Configuration setup task.
3. Set up a trading partner agreement for your trading partner using the pre-seeded UBL message definition. 
4. Set up service providers, if required, and trading partners to start receiving UBL invoices from suppliers.

Key Resources

• Oracle Supply Chain Management Cloud: Implementing Common Features for SCM Cloud guide, available on the Oracle Help Center.

Use Infolets to View Collaboration Messaging Status

Use new infolets available in the Collaboration Messaging work area to monitor the status of inbound and outbound B2B messages with your trading partners. Each infolet displays a pie chart that shows the number of messages in different processing statuses, for example, Success, Failure, and Error.

There are 9 infolets, 2 for each supported business process, and 1 that displays an overall count of the messages that have been broken down by status. The count displayed in the infolets default to a 24-hour duration. The user can change this to 7 days or 30 days.

The information in the business process specific infolets is presented by messaging direction, so every business process has 2 infolets, one that displays information about outbound messages and the other about inbound messages.

Selecting any segment of the pie-chart in any infolet opens the Manage Collaboration Messages page with all the messages that constitute the count displayed in the selected segment.

All the infolets can be reversed. The reverse side of the Message Count infolet shows the count of messages by business process. The reverse side of the business process specific infolets shows the count of messages by message name.

In the case of Message Count infolet, selecting any business process on the reverse side of the infolet opens the Manage Collaboration Messages page with all the messages that constitute the count displayed for the selected business process.

In the case of business process specific infolets, selecting any message name on the reverse side of the infolet opens the Manage Collaboration Messages page with all the messages that constitute the count displayed for the selected message name.

From the Manage Collaboration Messages page, the user can view details of the messages or perform specific tasks such as Reprocess or Cancel on one or more messages.

The user can choose the infolets they want to see using the My Infolets task. So, for example, if a business is only implementing Procure to Pay, they can deselect all the infolets related to other business processes that are not applicable to them.

The available infolets are Message Count, Procure to Pay Inbound Messages, Procure to Pay Outbound Messages, Order to Cash Inbound Messages, Order to Cash Outbound Messages, Supply Chain Operations Inbound Messages, Supply Chain Operations Outbound Messages, Brazil Invoicing Inbound Messages, and Brazil Invoicing Outbound Messages.

Steps to Enable

You must opt in to and enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Tips And Considerations

The set of infolets that are displayed is dependent on your data security privileges. For example, if you do not have data security privileges for any document of a business process, then the entire infolet will not be displayed. However, if you have data security privileges for at least one document of a business process (for example, Purchase Orders from Customers), you will see the Order-to-Cash infolet but only purchase order information will be available. This would also apply to all summary information such as message counts, so you will only see message counts for the documents for which you have data security privileges.

Role Information

• Privilege Name and Code:
  • Monitor Collaboration Messaging (CMK_MONITOR_COLLB_MESG
• Job Role Name and Code:
  • B2B Administrator (ORA_CMK_B2B_ADMINISTRATOR)

Send a B2B Message to Multiple Trading Partners

Send a B2B message to more than one recipient in situations when more than one trading partner requires the same type of information to complete your business process. For example, when you send a purchase order to a supplier, you may also want to send a copy of that purchase order to a third-party service provider that processes invoices received from suppliers.

When an outbound document is being set up for a supplier site, customer, or customer account, you can now setup multiple recipients for a document.

Steps to Enable

If multiple partners are set up, then one partner must be identified as the primary recipient.

Each partner can be setup with different message types and delivery methods – e.g. the supplier may require a pdf copy of the PO to be sent via email, and the service provider may require an OAGIS 7.2.1 version of the PO sent via B2B/ HTTP POST.

When a message is published to multiple recipients, a Publication ID is generated to group them together. This is visible in the Manage Collaboration Messaging History UI.

In the “Validate Outbound Collaboration Messaging Setup” task, select Recipient page, when a supplier, customer or customer account is selected, if there are multiple recipients setup for the outbound message, they will be displayed in the “Trading Partners” table that has been added in this page.

Additionally, if there are multiple recipients for a message, the Message ID in the View Results page will be a drop down that lists the messages that were generated for each recipient.

Tips And Considerations

If setup validations fail for any of the recipients, then the message is logged with error status and the message is not sent to any recipient. The log will then only contain a single record as the message is not processed. For example, if the message is set up for publication to 3 recipients, only one 1 record will be created, with the trading partner identified as the primary recipient.

You can resolve the setup issues and reprocess the failed/errored records in both cases. In this case, if the setup issues are resolved, reprocessing will result in multiple log records being created.

If setup validations are successful, but message processing is aborted for one or more of the recipients, then the log will contain recipient-specific records, one for each recipient. For example, if the message is set up for publication to 3 recipients, and processing succeeds for 1 recipient, errors for the second, and fails for the third, then 3 log records will be created, one for each recipient.

Add Line-Level Detail to Outbound Acknowledge PO

Send customers an Outbound Acknowledge Purchase Order B2B message that includes line-level details such as item, quantity, price, and ship-to.

Steps to Enable

No steps are required to enable this feature. Trading partners who are set up to receive the ACKNOWLEDGE_PO_OUT document will receive the enhanced message information.

Supply Chain Orchestration

Integrate and Extend Supply Chain Orchestration Using REST Services

Create and View Production Reports Using a REST Service

Contract manufacturers can update production report data, including material consumption and resource utilization, using a REST service. The uploaded production report data will automatically progress the contract manufacturing supply order and work order. The REST service can also be used to retrieve production report data for contract manufacturing supply orders.

With this service, you can:

• Update production report data for contract manufacturing supply orders
• Update material consumption for a contract manufacturing supply order
• Update resource utilization for a contract manufacturing supply order
• Report operation completion for a contract manufacturing supply order
• Request production report data for a contract manufacturing supply order

Steps to Enable

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Key Resources

• REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role Information

• Job Role Names and Codes:
  • Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)
  • Supplier Inventory Manager (ORA_INV_SUPPLIER_INVENTORY_MANAGER_JOB)

Create and View Supply Requests Using a REST Service

You can now use a REST service to create, view, or modify an interorganization or intraorganization material transfer request to an inventory or expense destination. You can use this service to streamline integration to external systems and reduce integration costs.

With this service, you can:

• Create supply requests that will result in an inventory destination transfer order
• Create supply requests that will result in an expense destination transfer order
• Specify transfer order charges
• Retrieve supply request and supply order details for previously requested supply orders
• Retrieve transfer order details for previously requested supply orders

Steps to Enable

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Key Resources

• REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role Information

• Job Role Name and Code:
  • Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)

Manage Configured Items Using a REST Service

Use a REST API to expose a configured item structure to the calling application. The returned structure consists of customer-selected options (that is, the sales structure, including option classes and options), mandatory items, substitute items, and transactional item attributes. You can also use the public web service to provide item configuration details to manufacturers and buyers, and to help shippers prepare accurate customs-compliant shipping documents.

With this service you can:

• Request the sales or complete Instance structure of an individual configuration item
• Request the sales structure of all the configuration items ordered for a specific model
• Request the complete instance structure of all the configuration items ordered for a specific model with certain transactional item values
• Allow for end-of-life components and date-specific model changes when providing structural data to other systems

Steps to Enable

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Tips And Considerations

• Consider the number of records to be returned from an individual request. You can include only a maximum of 500 records in each query. However, you can use sequential requests to retrieve a complete data set.
• Configured items are created by ordering assemble-to-order models with back-to-back and drop ship flows in Order Management. 

Key Resources

• REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center
• For additional information on CTO run time or set-up considerations, see CTO – Configure to Order: A Guide to Key Application Setups in White Papers for Oracle Fusion Supply Chain Orchestration (My Oracle Support: Doc ID 2257314.1)

Role Information

• Job Role Name and Code:
  • Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)

Update 18B

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Feature	Notes
20 APR 2018		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

Customers Upgrading from Release 12

If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (updates 17B - 17D, as well as, updates 18A - 18B) to learn about all of the features available in release 13.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

Optional Uptake of New Features (Opt In)

We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can opt in to a feature in two ways:  by using the New Features work area, or by using the Setup and Maintenance work area.

To opt in using the New Features work area:

1. Click the Navigator, and then click New Features (under the My Enterprise heading).
2. On the New Features page, select the offering that includes new features you’d like to review.
3. Click Go to Opt In for any feature that you want to opt in to.
4. On the Edit Features page, select the Enable option for the feature, and then click Done.

To opt in using the Setup and Maintenance work area:

1. Click the Navigator, and then click Setup and Maintenance.
2. On the Setup page, select your offering, and then click Change Feature Opt In.
3. On the Opt In page, click the Edit Features icon.
4. On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close. 
5. Click Done.

Feature Summary

Supply Chain Collaboration

Today’s global supply chains increase manufacturers’ reliance on suppliers, contract manufacturers, and other trading partners. To be successful, companies must synchronize their activities across multiple tiers of trading parties. Oracle Supply Chain Collaboration Cloud enables companies to jointly plan supply, gain visibility into trading partner data, coordinate contract manufacturing execution, and measure performance across their trading networks. Trading partners are actively involved in the decision-making process, so they can exchange early warning signs and collaboratively resolve supply chain issues. Depending on the size and technical sophistication of each supplier, your company can interact using a portal-based user interface, standards-based B2B messages, or web services. Customers can also tailor Oracle Supply Chain Collaboration Cloud’s flexible, predefined business processes to their unique requirements. Enhanced collaboration results in more dynamic trading relationships, as well as increased reliability and efficiency of supply.

Provide an Open and Extensible Platform

This update of Oracle Supply Chain Supply Collaboration Cloud enhances integration with external applications by using new flat file upload and download capabilities.

Upload Collaboration Order Forecasts Using Flat Files

Using flat-file uploads is a convenient way to update collaboration records. You can now upload order forecasts from any external planning system using flat files. This feature enables enterprises to integrate seamlessly with their native systems, while taking advantage of Oracle Supply Chain Collaboration Cloud to interoperate with the service providers.

Supply Chain Collaboration uses the file-based data import feature to load order forecasts from external sources. Perform the following steps to collaborate using external order forecasts:

1. Setup your collaboration network

• Create collaboration relationships using the Manage Supply Collaboration Network page.
• Create a collaboration plan using the Manage Collaboration Plans page. Set Supply Plan Source to External Application and enter a supply plan name. The following screenshot shows an external collaboration plan with the supply plan name External Supply Plan.

Collaboration Plan with External Supply Plan Source

2. Prepare your data

• Download the Collaboration Order Forecast file-based data import template from the File-Based Data Import for Oracle Supply Chain Management Cloud guide.
• Enter the order forecast data, generate the csv zip file and save the data file locally.

3. Upload your file

• Upload the external supply plan using the Load Interface File for Import scheduled process. The following screenshot shows the Load Interface File for Import process details. Select the Import Collaboration Order Forecasts import process and the data file to import.

Load Interface File for Import Process Details

If you had previously uploaded a file to the scm/collaborationOrderForecast/import account using File Import and Export, you can select the file from the list of values for Data File. To upload a new file from this location, select Upload a new file.

4. Schedule Decomposition

• Schedule the Supply Planning Collaboration Decomposition scheduled process to decompose the imported data, making it available for supplier collaboration. 

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

If you have not yet created a collaboration relationship, the uploaded order forecasts will appear as collaboration candidates. You can use these collaboration candidates to create relationships that you may have missed. After you convert the candidates to collaboration relationships, you must again upload the order forecasts that you want to participate in the current collaboration cycle.

Key Resources

• File-Based Data Import for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role Information

Access to this feature is available using the existing Supply Chain Integration Specialist role. If not using this role, the following duty role and privilege are required:

• Duty Role Name and Code: 
  • Upload data for Collaboration Order Forecast Import (SCM_COLLABORDERFORECAST_IMPORT_RWD)
• Privilege Name and Code:
  •  Import Collaboration Order Forecasts (VCS_COLLABORDERFORECAST_IMPORT_PRIV)

Download Supplier Commits Using Flat Files

Using flat-file downloads is a convenient way to manage supplier commitments. You can now download supply commitments from Oracle Supply Chain Collaboration Cloud to a flat file. This feature enables enterprises to integrate seamlessly with their native systems, while taking advantage of Supply Chain Collaboration to interoperate with the service providers.

You can export collaboration order forecasts using the Export Collaboration Order Forecasts scheduled process. The Export Collaboration Order Forecasts process parameters allow you to control the data that is included in your export. The following screenshot shows the Export Collaboration Order Forecasts process details.

Export Collaboration Order Forecasts Process Details

You can specify the following information in the process details:

• Select or enter the supply plan to export and further filter the export collection by specifying a supplier or item.
• Select the measures to include in your export.
• Select Current Forecast and Current Commit to export the current cycle collaboration data.
• Select Previous Forecast or Previous Commit to include data from the immediate previous collaboration cycle.

After the process is run successfully, you can download the file using the File Import and Export work area. You can find all the collaboration order forecast exports in the scm/collaborationOrderForecast/export account. You can filter your results by providing the Export Collaboration Order Forecasts scheduled process ID. The following screenshot shows the File Import and Export page where you specify the Export Collaboration Order Forecasts scheduled process ID.

File Import and Export File Download

Steps to Enable

No steps are required to enable this feature.

Role Information

This feature is intended for integration use cases allowing you to download all collaboration data regardless of data security. Access to this feature is available using the existing Supply Chain Integration Specialist role. If not using this role, the following duty role and privilege is required:

• Duty Role Name and Code: 
  • Export Collaboration Order Forecasts (SCM_COLLABORDERFORECAST_EXPORT_RWD)
• Privilege Name and Code: 
  • Export Collaboration Order Forecasts (VCS_COLLABORDERFORECAST_EXPORT_PRIV)

Accelerate Adoption and Innovation

Streamline the end-to-end collaboration process and ensure that trading partners participate in the decision-making process while providing visibility to inventory.

Share On-Hand Inventory Balance with Suppliers

During a collaboration cycle, enterprises and suppliers continue to procure, ship, and receive goods, which reduce the net quantity that remains to be committed. In Oracle Supply Chain Collaboration Cloud, you can now view the on-hand inventory balance along with the order forecast. This feature ensures both suppliers and enterprises have visibility to the same information in their decision making process, which will improve supply chain efficiency and minimize delays in decision making.

When publishing a supply plan, you can select the Publish order details checkbox to push the on-hand inventory balance to Supply Chain Collaboration.

The following screenshots show where in Supply Chain Collaboration you and your suppliers can view the on-hand quantity published from planning.

Manage Order Forecasts and Commits

Edit Order Forecast Details

Steps to Enable

No steps are required to enable this feature.

Update 18A

Revision History

This document will continue to evolve as existing sections change and new information is added.  All updates appear in the following table:

Date	Feature	Notes
02 FEB 2018	Review and Manage Collaboration Relationship Candidates	Updated document. Revised screenshots.
02 FEB 2018	Commit to Order Forecasts Across Multiple Facilities	Updated document. Revised screenshot.
02 FEB 2018	Monitor Supplier Order Forecast Commit Performance	Updated document. Revised screenshot.
02 FEB 2018	Monitor Supplier Response Cycle Time Performance	Updated document. Revised screenshot.
19 JAN 2018		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

Customers Upgrading from Release 12

If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (updates 17B - 17D, as well as, updates 18A - 18B) to learn about all of the features available in release 13.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

Optional Uptake of New Features (Opt In)

We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can opt in to a feature in two ways:  by using the New Features work area, or by using the Setup and Maintenance work area.

To opt in using the New Features work area:

1. Click the Navigator, and then click New Features (under the My Enterprise heading).
2. On the New Features page, select the offering that includes new features you’d like to review.
3. Click Opt In for any feature that you want to opt in to.
4. On the Edit Features page, select the Enable option for the feature, and then click Done.

To opt in using the Setup and Maintenance work area:

1. Click the Navigator, and then click Setup and Maintenance.
2. On the Setup page, select your offering, and then click Change Feature Opt In.
3. On the Opt In page, click the Edit Features icon.
4. On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close. 
5. Click Done.

Feature Summary

Supply Chain Collaboration

Commit to Order Forecasts Across Multiple Facilities

As a supplier, you may prefer to review the order forecasts assigned to you by the consuming facilities such as contract manufacturers or enterprise facilities and commit to all the order forecasts at the same time. You can now commit to order forecasts across relationships from the Manage Order Forecasts and Commits work area. You can view the aggregated order forecasts and commits across the commit horizon for each relationship. While committing from this view, you can either match to the current order forecast or set to your previous commit quantity. This feature streamlines routine forecast commits, so that you can focus on managing issues with specific items, dates, or relationships.

The following screenshot shows the Commit Order Forecasts dialog box on the Manage Order Forecasts and Commits page. Your collaboration planner and supplier contact can select one or more rows and then select Commit Order Forecasts from the Actions menu to open the Commit Order Forecasts dialog box. You can either match the commits to the current order forecast or set the commits to your previous commit quantity. 

Manage Order Forecasts and Commits: Commit Order Forecasts

Steps to Enable

You must opt in to and enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Role Information

Access to this feature is available through the shipped job roles and privileges. Use the existing Supply Chain Collaboration Planner role to commit to multiple order forecasts on the Manage Order Forecasts and Commits page as an enterprise user in Oracle Supply Chain Collaboration Cloud. Use the existing Supplier Demand Planner role to commit to multiple order forecasts on the Manage Order Forecasts and Commits page as a supplier contact in Oracle Supplier Portal Cloud.

SUPPLY CHAIN COLLABORATION

• Privilege Name and Code: Commit to Order Forecasts as Enterprise User (VCS_COMMIT_ORDER_FORECAST_ENTERPRISE)
• Job Role Name and Code: Supply Chain Collaboration Planner (ORA_VCS_SUPPLY_COLLAB_PLANNER)

SUPPLIER PORTAL

• Privilege Name and Code: Commit to Order Forecasts as Supplier (VCS_COMMIT_ORDER_FORECAST_SUPPLIER)
• Job Role Name and Code: Supplier Demand Planner (ORA_POS_SUPPLIER_DEMAND_PLANNER)

Review and Manage Collaboration Relationship Candidates

To ensure seamless operations, it is important for all published order forecasts to be transmitted to the suppliers. In Oracle Supply Chain Collaboration Cloud, you can flag an Oracle Supply Chain Planning Cloud order forecast as a potential collaboration relationship, or collaboration relationship candidate, if one does not exist. As a Supply Chain Collaboration administrator, you can view and create collaboration relationships from a list of potential relationships.

Using Supply Chain Collaboration, you can:

• Display the supply plans that do not have a corresponding collaboration plan.
• Display the number of collaboration relationship candidates in an infolet. This includes records defined for B2B-only transaction processing and records without a relationship defined in Supply Chain Collaboration (collaboration relationship candidates).
• Access the list of potential relationships from the infolet.
• Filter on collaboration plans, items, supplier sites, and ship-to organizations.
• Select multiple candidates and create collaboration relationships.

The following screenshot shows the Manage Supply Collaboration Network page. You can select Relationship candidates and search for potential relationships for an existing collaboration plan published in the last seven days.

Manage Supply Collaboration Network: Relationship Candidates

As an administrator, you can convert one or more potential relationships at the same time by using the Convert to Relationship button. You can then edit the relationships using the Update Collaboration Parameters Across Multiple Facilities feature.

If a collaboration plan does not exist, then select Plan candidates on the Manage Collaboration Plans page to create a collaboration plan from the list of published supply plans.

The following screenshot shows the Manage Collaboration Plans page. You can select Plan candidates and search for potential plans published in the last seven days.

Manage Collaboration Plans: Plan Candidates

The following screenshot shows the new columns available on the Manage Collaboration Plans page:

• Last Published: Displays the last time the supply plan was published to Supply Chain Collaboration.
• Relationship Candidates: Displays the number of relationship candidates you are not tracking exceptions or collaborating on.
• Collaboration Relationships: Displays the number of collaboration relationships you created.
• Order Forecasts: Displays the number of order forecasts you have in the current planning cycle.

Manage Collaboration Plans: Collaboration Plans

The following screenshot shows the infolets in the Supply Chain Collaboration work area:

• Plan Candidates: Displays the number of new collaboration plan candidates published within the last seven days. You can also show the collaboration plan candidates published in the last 30, 90, or 120 days.
• Relationship Candidates: Displays the number of new collaboration relationships for existing collaboration plans published within the last seven days. You can also show the collaboration relationships published in the last 30, 90, or 120 days. You can view the number of relationship candidates separated into unprocessed and B2B only.

Infolets in the Supply Chain Collaboration Work Area

Steps to Enable

You must opt in to and enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Role Information

Access to this feature is available through the shipped job roles and privileges. Use the Supply Chain Application Administrator to view relationship candidates on the Manage Supply Collaboration Network page and and plan candidates on the Manage Collaboration Plans page.

• Privilege Name and Code: Manage Partner Relationships (VCS_MANAGE_SUPPLY_RELATIONSHIPS)
• Job Role Name and Code: Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_DUTY)

Update Collaboration Parameters Across Multiple Facilities

Collaboration parameters such as the order forecast horizon, commit horizon, and commit cycle time need to be defined for each collaboration relationship. These parameters are typically the same for all contract manufacturer’s or enterprise facilities that the supplier or supplier site serves. As a collaboration planner, you can edit multiple parameters across relationships for a given supplier or supplier site. This feature helps reduce the effort to manage collaboration. Planners can also override a collaboration parameter at the relationship level as needed.

On the Manage Supply Collaboration Network page, you can now select multiple rows and click Edit. When you select multiple rows, the edit action will open the new Edit Relationships page.

The following screenshot shows the Edit Relationships page when you select multiple relationships to edit.

Edit Relationships

Steps to Enable

You must opt in to and enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Role Information

Access to this feature is available through the shipped job roles and privileges. Use the Supply Chain Application Administrator to edit multiple relationships at the same time.

• Privilege Name and Code: Manage Partner Relationships (VCS_MANAGE_SUPPLY_RELATIONSHIPS)
• Job Role Name and Code: Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_DUTY)

Monitor Supplier Order Forecast Commit Performance

Understanding the supplier commitment deviations over time will help an enterprise analyze the supplier's performance and accountability, and help ensure that you meet the finished good demands on time. The new historical performance reports show the percentage of order forecasts fulfilled by a supplier and their variability over time. This information is computed based on the order forecasts and commits of previous versions that have been saved for analysis and reporting purposes.

Using Oracle Supply Chain Collaboration Cloud, you can:

• View and analyze predefined historical performance reports aggregated by collaboration plan, supplier, ship to, and item.
• Select and display data for the previous collaboration cycle or all collaboration cycles.

The following screenshot shows the Historical Performance by Collaboration Plan report:

Historical Performance by Collaboration Plan Report

Steps to Enable

No steps are required to enable this feature.

Role Information

• Job Role Name and Code: Supply Chain Collaboration Planner (ORA_VCS_SUPPLY_CHAIN_COLLABORATION_PLANNER_JOB)

Monitor Supplier Response Cycle Time Performance

Collaboration planners need to understand order forecast commit cycle times to highlight the supplier's performance and to ensure the supplier's accountability. The new historical performance reports display the average response time analysis that shows the difference between order forecast publish dates and supplier commit dates. Oracle Supply Chain Collaboration Cloud saves the previous versions of these dates for analysis and reporting purposes. With complete versioning and audit trail, enterprises can work with suppliers to improve the collaboration process.

Using Supply Chain Collaboration, you can:

• View and analyze predefined historical performance reports aggregated by collaboration plan, supplier, ship to, and item.
• Select and display data for the previous collaboration cycle or all collaboration cycles.

The following screenshot shows the Historical Performance by Supplier report:

Historical Performance by Supplier Report

Steps to Enable

No steps are required to enable this feature.

Role Information

• Job Role Name and Code: Supply Chain Collaboration Planner (ORA_VCS_SUPPLY_CHAIN_COLLABORATION_PLANNER_JOB)

Manage the Collaboration Network Using a REST API

Collaboration plan name and relationships define a collaboration network, which is the key to Oracle Supply Chain Collaboration Cloud. Two new REST APIs allow systems integrators to create, update, and query collaboration plans and relationships from any external system or product extension. Integrating this information allows enterprises to seamlessly extend their native systems to work with Supply Chain Collaboration.

The Collaboration Relationships API allows you to retrieve and create collaboration relationships. The information gathered includes relationship identity attributes for supplier, supplier site, organization, and item. Each relationship also includes all the attributes on the UI, including effective dates, commit horizon, and forecast horizon.

The Collaboration Relationships API supports the query request parameter allowing you to query by attribute. To use simple queries the request URL needs to have the pattern:

https://[Endpoint][Resource]/q=[AttributeName]=[Value]

For example, if you wanted to find all relationships for a specific item, the following request URL queries the collaboration relationships records for the item Motherboard85:

http://MYENDPOINT/collaborationRelationships?q=ItemNumber=Motherboard85

The Collaboration Plans API allows you to retrieve and create collaboration plans. The information gathered includes plan identity attributes for supply plan name and collaboration plan name. Each plan also includes the publish cycle and status.

The Collaboration Plans API supports the query request parameter allowing you to query by attribute. To use simple queries the request URL needs to have the pattern:

https://[Endpoint][Resource]/q=[AttributeName]=[Value]

For example, if you wanted to find all plans that you published on a Monday, the following request URL queries the collaboration plans records for the start day Monday:

http://MYENDPOINT/collaborationPlans?q=StartDay=Monday

Steps to Enable

No steps are required to enable this feature.

Key Resources

• Oracle SCM Cloud: REST API for Oracle Supply Chain Management Cloud Guide, available on the Oracle Help Center.

Collaboration Messaging Framework

Define Processing Rules for Message Transformations

Your implementation may require values in specific fields of an inbound message from a trading partner yet those values may not be available in the partner’s application. Similarly, a trading partner may require a specific field to have a value, but the field is not specified in messages sent by Oracle Collaboration Messaging Framework.

For any field in an outbound or inbound partner message, the Message Processing rules provide you the ability to either specify a default value or indicate that the field must have a value.Since the rules are specified on the external message type, the collaboration messaging framework processes them after transformation in the case of outbound messages and before transformation in the case of inbound messages.

When rules are processed, you may get one of the following results: 

• Required fields are missing or have no value: Message processing reports an error and the list of fields are logged in the error details.
• Fields that have default values specified are missing in the input XML: Message processing is successful and the list of fields are logged and can be seen in the ValidationResult element of the transformed XML.

Steps to Enable

You use the new Manage Message Processing Rules action in the Edit Trading Partner task to set up trading partner message rules.

You can set up message processing rules by a:

• Combination of trading partner and a document if a service provider is defined.
• Combination of trading partner and a message if a service provider is not defined.

You can set up rules for individual fields in the message or set up multiple rules for a trading partner document or trading partner message. Each rule must have a unique name and Xpath that identifies the field to which the rule is applied.

NOTE: You can specify only one rule for a field.

The XPath is always specified based on the external message type that is set up for the trading partner message or the external message type of the service provider is specified for the trading partner. The root element of the XPath is the root element of the external message type; for example, the root element in the case of OAGIS 10 would be:

/CollaborationMessage/BusinessObjectDocument/DataArea/PurchaseOrder/PurchaseOrderHeader/RevisionID

Include B2B Trading Partners in Customer Account Import

Customer Account Import now includes B2B invoice setup information, such as B2B service provider and B2B trading partner ID, so that you can easily migrate all your customer account information at one time.

Steps to Enable

The existing Import Bulk Customer Data process is enhanced so that you can now include the B2B trading partner information in the File-Based Data Import (FBDI) spreadsheet template and schedule the import process.

Schedule New Process: Import Bulk Customer Data

Tips And Considerations

B2B SERVICE PROVIDERS

If the B2B trading partners to be imported use B2B service providers, the B2B service provider records must already be defined in Oracle Collaboration Messaging Framework before running the import process.

Key Resources

For more information on this feature, refer to following guides, available on the Oracle Help Center:

• Oracle Customer Data Management Cloud: Using Customer Data Management
• File-Based Data Import for Oracle Sales Cloud