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 |
|---|---|---|
| 22 MAY 2019 | Update 17D | Revised update 17D. |
| 02 FEB 2018 | Update 17C | Revised update 17C. |
| 02 FEB 2018 | Update 17B | Revised update 17B. |
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 |
|---|---|---|
| 22 MAY 2019 | Updated document. Revised feature description. | |
| 02 FEB 2018 | View Purchase Orders and Shipments | Updated document. Revised screenshots. |
| 20 OCT 2017 | Created initial document. |
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 in this guide 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 you have created custom 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:
- Click the Navigator, and then click New Features (under the My Enterprise heading).
- On the New Features page, select the offering that includes new features you’d like to review.
- Click Opt In for any feature that you want to opt in to.
- 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:
- Click the Navigator, and then click Setup and Maintenance.
- On the Setup page, select your offering, and then click Change Feature Opt In.
- On the Opt In page, click the Edit Features icon.
- 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.
- Click Done.
This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.
| Action Required to Enable Feature |
|||||
|---|---|---|---|---|---|
| Feature |
None (Automatically Available) |
Enable via Opt In UI Only |
Enable via Opt In UI Plus Additional Steps |
Not Enabled via Opt In UI but Setup Required |
Issue Service Request |
 |
|||||
|
|||||
Manage Collaboration Relationship Candidates Using a REST API |
|
||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
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.
Streamline Collaboration Relationship Creation
Some organizations have a large number of collaborative trading relationships. Streamlining the setup process can save time and reduce errors. This feature enables administrative users to create or duplicate relationships along with the collaboration attributes in a user friendly manner, without changing screens.
You can save a newly created relationship and immediately create another by clicking the Save and Create Another action on the collaboration relationship create dialog.
Create Relationship Dialog
Steps to Enable
No steps are required to enable this feature.
Automate Actions for Past-Due Supplier Commitments
If a supplier does not commit to order forecasts within the contractually specified time window, other enterprise planning processes may be delayed. To reduce the disruption of late commitments, you can set an automatic commit horizon that uses the commits from the previous cycle, or sets the commit to a percentage of the current forecast for a specified set of time buckets. These rules are specified at the Relationship (Item, Organization, or Supplier Site) level.
The following screenshot shows SLA Action, which is defined on the Edit Collaboration Relationship page. To automatically commit when the commit is past due, you must first define a due date by populating the Commit SLA in Days. Then select the Commit automatically option for SLA Action. You can then select the Commit Period and Commit Quantity you would like to use. Commit Period allows you to commit for the entire commit horizon or specify how many days you would like to automatically provide commits for. Commit Quantity allows you to match commit quantities to the previous cycle commit, the current forecast, or specify a percentage of the current forecast. For example, when the order forecast commit is late, the application will provide commits for the defined commit horizon at 80% of the current forecast.
Automate Actions: Edit Collaboration Relationship
Steps to Enable
No steps are required to enable this feature.
Manage Collaboration Relationship Candidates Using a REST API
Collaboration order forecasts are published by Oracle Planning Central Cloud. These order forecasts are made visible to collaboration planners and to supplier users only if there is a collaboration relationship defined in Oracle Supply Chain Collaboration Cloud. A new Collaboration Relationship Candidates REST API provides visibility to potential order forecasts that do not have a relationship defined. This feature allows you to quickly determine which relationships need to be created in Supply Chain Collaboration to ensure operational efficiency.
The Collaboration Relationship Candidates API allows you to get all collaboration relationship candidates. The information gathered includes relationship identity attributes for Supplier, Supplier Site, Organization, and Item. Each candidate also includes the date it was last published and the candidate type. There are two candidate types:
- ORA_VCS_B2BONLY: These are B2B-only candidates. The supplier site is enabled for B2B Collaboration but a collaboration relationship does not exist in Supply Chain Collaboration. Collaboration order forecast data is published to the supplier using only B2B messaging. These collaboration order forecasts are not available within the Supply Chain Collaboration user interface and historical collaboration is not retained.
- ORA_VCS_UNPROCESSED: These are unprocessed candidates. Collaboration order forecast data was not published to suppliers or retained by Supply Chain Collaboration.
The Collaboration Relationship Candidates 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 candidates for a specific item, the following request URL queries the collaboration relationship candidate records for the Item Motherboard85:
http://MYENDPOINT/collaborationRelationshipCandidates?q=ItemNumber=Motherboard85
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.
View Purchase Orders and Shipments
During each collaboration cycle, OEMs and suppliers continue to procure, ship, and receive goods, which reduce the net quantity that remain to be forecasted or committed. This feature ensures both suppliers and enterprise planners have visibility to the gross commitment for a given item in a given time bucket. Oracle Supply Chain Collaboration Cloud provides visibility to procurement order types in addition to order forecasts namely, Open Purchase Orders, Purchase Requisitions, In-Transit Shipments, and Shipments in Receiving.
Using Supply Chain Collaboration Cloud, you can do the following:
- View procurement order types in the Manage Order Forecasts and Commits and Edit Order Forecast Details pages in both enterprise view and in Oracle Supplier Portal Cloud. These include Open Purchase Orders, In-Transit Shipments and Shipments in Receiving.
- The enterprise can view Purchase Requisitions; however, Purchase Requisitions are not visible to suppliers.
- Users will have visibility to Purchase Order header information within each time bucket.
- Users will not be able edit quantities or dates.
The following screenshot shows the purchasing measures displayed along with the order forecast on the Edit Order Forecast Details page. These quantities are aggregated using all the purchasing measures for that specific date. You can view the individual purchasing measures by selecting View Purchasing Measures from the Actions menu, or by clicking the link for a purchasing measure to view only the measures used to calculate that value.
Edit Order Forecast Details: Purchase Orders and Shipment Measures
The following screenshot shows the individual purchasing measures. You can view details of Purchase Order, Shipment in Receiving, or In-Transit Shipment by clicking the link in the Reference Number column.
Purchasing Measures
These measures are pushed to Supply Chain Collaboration when the supply plan is published. You can decide to include these measures by selecting the Publish order details checkbox when publishing your supply plan.
Publish Order Forecast Scheduled Process: Publish Order Details
Steps to Enable
No steps are required to enable this feature.
Collaboration Messaging Framework
Search and Manage All B2B Messages From a Single Page
Search, view, and manage failed, undelivered, and processed B2B messages from the Manage Collaboration Messaging History page.
In previous releases of Oracle Collaboration Messaging Framework, information about the processed messages was displayed across multiple pages: Manage Undelivered Collaboration Messages, Manage Failed Collaboration Messages, and Manage Collaboration Messaging History.
This feature combines the functionality of these pages into the Manage Collaboration Messaging History page. On this page, you can find information about your message without needing to know the status of the message.
Manage Collaboration Messaging History
Steps to Enable
No steps are required to enable this feature.
Use New B2B Protocol Options for Exchanging B2B Messages
Send and receive B2B messages using standard HTTP in addition to SOAP web services.
This feature expands the number of protocols available for exchanging B2B messages. You can now use HTTP to connect with B2B service providers and trading partners who may not have the technical infrastructure to support SOAP web services.
Oracle Collaboration Messaging Framework Cloud leverages the Oracle SOA B2B components, which are included with all Oracle SaaS offerings, to send and receive B2B messages through SOA Cloud Service B2B. To send and receive B2B messages through SOA Cloud Service B2B, use the new B2B Adapter delivery method type.
Steps to Enable
(CONDITIONAL) ADD B2B SERVICE PROVIDER DELIVERY METHOD
If you rely on a B2B Service Provider to send or receive messages, you must add a new delivery method with B2B Adapter as Delivery Method Type. If a B2B Service Provider is not used, specify a new delivery method with B2B Adapter as Delivery Method Type for the trading partner.
Collaboration Messaging Service Provider: Delivery Methods
You must associate the delivery method name with all inbound and outbound B2B messages to use B2B Adapter as Delivery Method Type.
Collaboration Messaging Service Provider: Outbound Message
(REQUIRED) CONFIGURE ORACLE SOA Cloud Service B2B
Use the following steps to setup and configure Oracle SOA B2B.
Configure Oracle B2B e-Commerce Gateway: In the Setup and Maintenance work area, search for the Configure Oracle B2B e-Commerce Gateway Setups task to configure Oracle B2B e-Commerce Gateway.
Configure Oracle B2B e-Commerce Gateway Setups
Set up B2B Service Providers or trading partners: You must setup an Oracle B2B trading partner profile for every B2B Service Provider or trading partner with B2B Adapter as the Delivery Method Type. You can have multiple identifiers defined, but you must have one identifier that matches the B2B Service Provider or trading partner ID in Oracle Collaboration Messaging Framework.
Oracle B2B Trading Partner Profile
Set up channels: You can select any of the transportation protocols supported by Oracle B2B such as AS2 or HTTP. You can configure the information required for the selected protocol in the Channel Details section.
Oracle B2B Channels
Set up trading partner agreements: Oracle B2B Trading Partner Agreements are a combination of Trading Partner Profile, Document, and Connection.
NOTE: Oracle B2B Documents are predefined and require no additional setup.
Oracle B2B Trading Partner Agreements
Key Resources
- Oracle Fusion Middleware User's Guide for Oracle B2B, Release 11.1.1.9, available on the Oracle Help Center.
Send the same OAGIS XML B2B message used in system-to-system automation as an email to your trading partners.
Automation and efficiency are some of the key benefits of B2B messaging. Realization of these benefits can range from hands-free, system-to-system automation, to automated delivery of B2B messages using email.
By providing an option for email delivery of B2B messages, you can remove any technical barriers to participate in B2B messaging. This can result in dramatic growth of your trading partner community and significant cost savings.
The OAGIS XML B2B messages are sent as email attachments. In addition to the XML attachment, the subject and body of the email can be configured to meet your unique requirements.
Steps to Enable
(CONDITIONAL) ADD B2B SERVICE PROVIDER DELIVERY METHOD
If you rely on a B2B Service Provider to send or receive messages, you must add a new delivery method with Email as Delivery Method Type. If a B2B Service Provider is not used, specify a new delivery method with Email as Delivery Method Type for the trading partner.
Select Attach XML Message to send the XML message as the email attachment. If Attach XML Message is not selected, the information sent is what you set up and configure for the email body.
Collaboration Messaging Service Provider: Delivery Methods
Collaboration Messaging Service Provider: Outbound Messages
Tips And Considerations
EMAIL ID USED TO SEND B2B MESSAGES
The email IDs may exist or are derived from a number of sources. The sources include:
- Oracle Cloud product: Products such as Payables, Receivables, Purchasing, or Order Management may already define an email address for customers or suppliers.
- Use attribute from B2B message: By using the Configure Message Maps feature, you can use XPath to point to an attribute in the B2B message that contains the email ID where the message should be sent.
- Delivery method email ID: When creating the email delivery method in Oracle Collaboration Messaging Framework, you can define an email ID.
Collaboration Messaging Framework processes these email sources in sequence to determine which email ID to use to send the B2B message. When Collaboration Messaging Framework finds a valid email ID, it will use that email ID without proceeding to other options.
USER-DEFINED EMAIL SUBJECT AND BODY
To define a user-defined email subject or body, you can use the Configure Message Maps feature.
You can map attributes from the B2B message to the email body using the new attributes in the Oracle pre-defined XSLT file. The information is formatted as a table in the email body, where the column titles are user-defined.
Send Invoice Rejection Notifications to Suppliers
Send notifications back to your suppliers if the B2B invoices received from them result in any validation or processing errors. In general, automation of a business process using B2B messaging starts with a single transaction such as a Purchase Order, ASN, or Invoice. Once you automate these transactions, you can add additional layers of sophistication to automate the business process, resulting in cost savings and efficiency.
The new B2B message enables you to avoid spending several hours (perhaps days) researching the problem and exchanging emails or phone calls with your supplier.
PROCESSING
Once you add and enable the B2B message for your trading partner, the rejection notifications are automatically triggered.
Steps to Enable
(CONDITIONAL) UPDATE B2B SERVICE PROVIDER
If your supplier receives B2B messages using a B2B Service Provider, you must update the B2B Service Provider to include the invoice rejection message.
Manage Collaboration Messaging Service Provider
(REQUIRED) UPDATE SUPPLIER
You must update your supplier to enable the invoice rejection message. This process is similar to any predefined B2B message.
Manage Supplier Sites
Tips And Considerations
BATCH PROCESSING
When a batch of invoices are processed in Oracle Collaboration Messaging Framework, the rejection messages are grouped by trading partner and vendor email address is taken from the original invoice message.
VENDOR EMAIL ADDRESS
If the original invoice message does not contain a vendor email address, rejection messages are not initiated.
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 | Control Access to Trading Partner Data | Updated document. Revised screenshots. |
| 02 FEB 2018 | Perform Order Forecast Commit Waterfall Analysis | Updated document. Revised screenshots. |
| 01 SEP 2017 | Created initial document. |
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 & NEW FEATURES
If your system has modified security structures, you may need to advise your security administrator of new features you would like to take advantage of.
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 Oracle Cloud Applications and we now give you the option to take advantage of new functionality at a pace that suits you. The ‘New Features UI’ is available to you from your cloud homepage, where you can make your choices and do any configuration necessary.
This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.
| Action Required to Enable Feature |
||||
|---|---|---|---|---|
| Feature |
Automatically Available |
End User Action Required |
Administrator Action Required |
Oracle Service Request Required |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Public Service to Expose Complete Structure of Configured Item |
|
|||
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 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 upon the size and technical sophistication of each supplier, your company can interact via 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.
Manage the Collaboration Process More Efficiently
Control Access to Trading Partner Data
Trading partner collaboration data is commercially sensitive and should be treated with utmost care. Trading partners would not want the data to be available to unauthorized personnel or shared with competitors. Oracle Supply Chain Collaboration Cloud provides a robust security framework that enables users (both enterprise planners and trading partners) to access only the supply chain information that is assigned to them.
Using Oracle Supply Chain Collaboration Cloud, you can do the following:
- Secure data by suppliers and supplier sites.
- Assign suppliers, or supplier sites, or both to Supply Chain Collaboration Planners.
- Limit the data displayed on Supply Chain Collaboration work area Infolets to suppliers, or supplier sites, or both accessible to the collaboration planner.
- Return only order forecasts on the Manage Order Forecast Commits page that is associated with the collaboration planner’s sites.
You use the Manage Collaboration Planners page to define collaboration planners and set the security context as supplier or supplier site. In the following screenshot, two collaboration planners are defined.
Manage Collaboration Planners
On the Edit Relationship page, when creating a collaboration relationship, you can view the list of collaboration planners associated with the relationship. Using the Edit Relationship page, you can associate more collaboration planners with the relationship. In the following screenshot, five collaboration planners are associated with the relationship. Three collaboration planners have the security context set to full access. A collaboration planner with security context set to full access is granted access to all the secured collaboration relationships.
Collaboration Relationship View
Steps to Enable
By default, data access security is disabled. You use the Enable data access security parameter in the Setup and Maintenance work area to enable data access security.
The following steps enable data access security:
- In the Setup and Maintenance work area, select the Manufacturing and Supply Chain Materials Management offering.
- On the Setup: Manufacturing and Supply Chain Materials Management page, click Supply Chain Collaboration functional area, and then click the Manage Supply Chain Collaboration Settings task.
- On the Manage Supply Chain Collaboration Settings page, set Enable data access security to Yes.
- Set Allow full access if no data access is assigned to one of the following values:
- No is most restrictive, treating all order forecasts as confidential and requiring a collaboration planner to be explicitly granted access to the supplier or supplier site.
- Yes to make all order forecasts without a collaboration planner assigned to be available to all collaboration planners.
- Click Save and Close.
The configuration setting in following screenshot will enable data access security. If Allow full access if no data access is assigned is set to Yes, all the collaboration order forecasts will be visible to all collaboration planners unless the order forecasts are secured by explicitly associating a collaboration planner to the collaboration relationship.
Manage Supply Chain Collaboration Settings
Tips And Considerations
This feature applies only to order forecast data and does not control access to administrative data such as collaboration relationships.
Manage Functional Privileges by Roles
Users with different roles require different privileges. A small number of administrative users can manage access for a community of planners, enhancing the security of the environment. Supply Chain Application Administrators can search and associate collaboration planners with suppliers, or supplier sites, or both. They can also assign trading partners to tier 1 or tier 2 suppliers and provide them with the ability to edit or view measures such as order forecasts. Administrative users can search, edit, and duplicate existing relationships to create new ones for their assigned suppliers, or supplier sites, or both. They can also upload or download into a spreadsheet information about their assigned suppliers, or supplier sites. Functional users on the other hand are given the ability to edit and view measures. These users do not have access to the admin functions.
Steps to Enable
No steps are required to enable this feature.
Sometimes a collaboration planner needs to adjust the order forecasts in a plan before sharing it with a supplier, either due to sensitivity about some of the numbers, or for negotiation purposes. This release allows collaboration planners to edit order forecasts received from Oracle Planning Central Cloud or Oracle Supply Planning Cloud. The edited order forecasts are republished to the trading partners. However, the edits are not sent to Oracle Planning Central Cloud or Oracle Supply Planning Cloud.
You can adjust the order forecast quantities by editing the values inline, multi-select editing, or editing multiple order forecasts using a spreadsheet. The following screenshot shows the current forecast being adjusted using inline editing. The draft values are indicated by a yellow background and italicized text.
Edit Current Forecast - Inline Editing
Forecasts are published to suppliers using the new publish action available from the actions menu.
Publish Action
Steps to Enable
No steps are required to enable this feature.
Perform Order Forecast Commit Waterfall Analysis
Collaboration planners need to understand how the order forecasts and supplier commitments change over time to address supply volatility and ensure supplier accountability. A new waterfall analysis report shows order forecasts and supplier commits in detail over time. As Oracle Planning Central Cloud or Oracle Supply Planning Cloud publishes new versions of order forecasts, Oracle Supply Chain Collaboration Cloud saves the previous versions and associated commits for analysis and reporting. With complete visibility, versioning, and audit trail, enterprises can work to continuously improve the collaboration process with their trading partners.
Using Oracle Supply Chain Collaboration Cloud, you can do the following:
- Predefined waterfall reports aggregated by Relationship, Supplier, Supplier Site, Ship To, and Item are available for analysis.
- Define the number of planning cycles and time range for the waterfall report.
- Select the time aggregation level at which data is displayed, weekly or monthly.
A new Supply Chain Collaboration - Supply Planning subject area has been created. This subject area includes all historical collaboration data. To create your own historical collaboration reports, select the criteria for your report using the new Supply Chain Collaboration - Subject Area.
Supply Chain Collaboration - Supply Planning Subject Area
Predefined waterfall reports are available aggregated by Relationship, Supplier, Supplier Site, Ship To, and Item.
The following screenshot shows the Order Forecast Waterfall by Relationship report.
Waterfall by Relationship Report
The following screenshot shows the Waterfall chart.
Waterfall Chart
Steps to Enable
No steps are required to enable this feature.
Provide Planners with Visibility to Item Attributes
When planners negotiate with other planners or supplier users, they need as much business context as possible to identify and resolve issues. This release provides visibility to Buyer Code, Category, and Planner in the Manage Order Forecast Commits page. These attributes provide you the flexibility to segment and work on order forecasts in smaller groups.
The following new search criteria are added:
- Item Category: The default planning catalog is used.
- Supply Plan Publisher: The supply chain planner who published the supply plan for collaboration.
- Supply Plan Owner: The supply chain planner who is designated as the owner on the supply plan.
- Item Planner: The planner who is designated on the item record within the planning specification.
- Buyer: The buyer who is designated on the item record within the purchasing specification.
Manage Order Forecasts and Commits Search Criteria
Steps to Enable
No steps are required to enable this feature.
Adjust the Exception Start Date
Typically, order forecasts and commits are stable in the short-term window. Any mismatches between them in the short-term are primarily due to statistical variations rather than a business issue that needs resolution. Oracle Supply Chain Collaboration Cloud provides a new date option that enables forecast commit exceptions to be displayed starting from this date in the future. You can reduce the number of unwanted exceptions by setting an appropriate date value. The default value for this date is the current date.
The following new search criteria have been added:
- Forecast Commit Mismatch Date: Allows you to find order forecasts that contain a forecast commit mismatch exception within a certain date range.
- Forecast Change Date: Allows you to find order forecasts that contain a forecast change exception within a certain date range.
In the following screenshot, the order forecasts returned will contain a forecast change or commit mismatch on or before September 15, 2018.
Manage Order Forecasts and Commits Search Criteria
Steps to Enable
No steps are required to enable this feature.
View Collaboration Plans Across Multiple Tiers
Enterprises depend on working with suppliers across multiple tiers. Sometimes tier 1 suppliers need to have visibility to tier 2 commits so tier 1 supplier can determine how much they can commit themselves. Oracle Supply Chain Collaboration Cloud allows you to:
- Provide a third party trading partner the ability to view and edit order forecasts between the enterprise and tier 1 or tier 2 suppliers.
- Provide all partners (enterprise, tier 1 or tier 2 supplier and the third party trading partner) visibility to commits.
The following figure shows a multi-tiered relationship between a contract manufacturer and a supplier.
Multi-Tiered Relationship
The following screenshot shows two order forecasts participating in a multi-tiered relationship:
- The order forecast sent to supplier B for the AI-1TB item that is used within the AI-1TB-Assembly item.
- The order forecast sent to Contract Manufacturer A concerning the AI-1TB-Assembly.
With appropriate permissions for the collaboration relationship, Contract Manufacturer A will be able to view and manage the order forecast sent to Supplier B.
Multi-Tiered Forecast View
The following screenshot shows the new Trading Partner Access section in the Edit Relationship page. This section will appear if the Ship-to Organization is associated to a supplier site within Oracle Supply Chain Planning Supply Network Model. Contract Manufacturer A will be allowed to view order forecasts for this relationship and can commit on behalf of the supplier.
Define Trading Partner Access on the Collaboration Relationship
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
To model a multi-tiered relationship between a contract manufacturer and a supplier:
- Setup contract manufacturers (Ship-to Supplier Sites) as organizations associated with a supplier site in Oracle Supply Chain Planning Supply Network Model.
- Define a relationship in Supply Chain Collaboration by defining the ship-to as the contract manufacturer organization.
- Enable the contract manufacturer to view forecasts, edit forecast quantities, and commit on behalf of their upstream suppliers within the Trading Partner Access section of the collaboration relationship.
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 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 SaaS environments at no additional charge. It is also tightly integrated with Oracle SaaS applications, making it easy for Oracle Supply Chain Collaboration Cloud customers to set up and manage multiple trading partner connections.
Exchange New B2B Messages with Your Trading Partners
A fully-automated Order-to-Cash business process using B2B messaging requires three key messages: Orders, ASNs and Invoices. Now, with the ability to electronically send invoices to customers for goods and services they have ordered completes this business process and enables customers to implement a completely automated, efficient, and high quality process with their customers.
SETUP AND CONFIGURATION
Setup of Invoice messages is the same as all of the other pre-built B2B messages provided by Oracle Collaboration Messaging Framework Cloud:
- B2B service providers (if used) must be enabled to send Invoices
- Trading partners must also be enabled to send Invoices
In addition to these standard B2B message setup functions, there is a new Number of invoices processed concurrently field on the Manage Collaboration Messaging Configuration page that allows you to determine how many invoices will be processed at one time if there is a large batch of new Invoices.
You will also need to update Preferred Delivery Method to XML on the Manage Customer Accounts page.
PROCESSING
The Invoice B2B message process begins with execution of the Print Receivables Transactions program, which you configure to run automatically at set intervals; for example, hourly or daily.
During the Print Receivables Transaction process, the invoices where Customer Account Preferred Delivery Method is XML are sent to Collaboration Messaging Framework. Collaboration Messaging Framework validates trading partner and B2B service provider for each invoice and formats invoices to the OAGIS XML 10.1 standard. Invoices are then sent automatically to the B2B service provider or trading partner depending on your setup information.
After Collaboration Messaging Framework processes the invoice, it sends the processing status back to Oracle Financial Cloud, where the invoice record is updated. Detailed B2B processing status can also be viewed in Collaboration Messaging Framework using the Manage Collaboration Messaging History page. If there is a problem, you can view the status using the Manage Undelivered (or Failed) Collaboration Messages page.
Steps to Enable
(Optional) UPDATE THE NUMBER OF INVOICES PROCESSED CONCURRENTLY PARAMETER
The value of the Number of invoices processed concurrently parameter defaults to 25 so this step is not required unless you want to change the default value.
Manage Collaboration Messaging Configuration
The Number of invoices processed concurrently parameter is used to control how many invoices at one time are sent from the Print Receivables Transactions program to Collaboration Messaging Framework. This provides your B2B administrator with an option to optimize the performance of B2B message processing if it is necessary.
(Conditional) SET PREFERRED DELIVERY METHOD TO XML IN THE MANAGE CUSTOMER ACCOUNTS PAGE
This step is required for all new customer accounts. However, if you are using XML in the releases prior to Release 13, the value should already be set to XML, so no action may be required.
Manage Customers - Account Profile
All customer accounts that will send electronic invoices using Collaboration Messaging Framework must have Preferred Delivery Method set to XML. This notifies the Print Receivables Transactions program to send the invoice to Collaboration Messaging Framework instead of an alternative delivery method.
(Required) SEUP CUSTOMER ACCOUNT COLLABORATION
This setup step is required for the Outbound Invoice B2B message sent to customers and does not apply to the other pre-built B2B messages supported by Collaboration Messaging Framework.
Manage Customer Account Collaboration Configuration
This setup is similar to the Manage Customer Collaboration Configuration and Manage Supplier Collaboration Configuration tasks, with a difference that the B2B service provider and the Outbound Invoice B2B message are associated at the customer account level rather than customer or supplier.
To setup a customer account collaboration to generate and send electronic invoices:
-
Select the Customer Account to receive electronic invoices.
Manage Customer Account Collaboration Configuration
- Perform the steps to setup a Collaboration Messaging Framework trading partner.
- Select B2B Service Provider and Trading Partner ID, then select the PROCESS_INVOICE_OUT document and enable the document for the Customer Account.
Tips And Considerations
- This feature is related to the Receive Message Confirmation Messages feature.
- Using both the Send Invoices to Customers feature and the Receive Message Confirmation Messages feature you will be able to send electronic invoices to customers and also receive a confirmation message back from the customer.
Key Resources
For more information on this feature, refer to following guides, available on the Oracle Help Center:
- Oracle Financials Cloud: Implementing Receivables Credit to Cash
- Oracle Financials Cloud: Using Receivables Credit to Cash
Receive Message Confirmation Messages
Most B2B integration patterns are asynchronous in nature: you send a B2B message, the receiver processes the message, and may or may not send an acknowledgement or confirmation for the message. In some cases, B2B standards clearly define the acknowledgement or confirmation messages.
The Message Confirmation Message is a generic OAGIS 10.1 acknowledgement or confirmation message that can be applied to situations where B2B standards do not explicitly define a response message.
The Collaboration Messaging Framework uses this message to receive confirmations from your customers in response to the invoice message.
PROCESSING
The confirmation messages are processed as follows:
- The confirmation messages received by Collaboration Messaging Framework validated to ensure all the required information has been provided and the B2B service provider or trading partner setup is valid.
- The confirmation message is saved to the Collaboration Messaging Framework transaction log, including all the correlation information to associate the confirmation with the original B2B message.
- An internal business event is raised to notify any interested parties that the confirmation message has been received and processed. In some cases, the Oracle Cloud product owning the original B2B message will subscribe to this business event and update their business object.
For example, a confirmation message is received from your customer indicating their electronic invoice has been received and processed by your customer's system. Collaboration Messaging Framework processes the confirmation message and raises a business event to indicate that the confirmation is successfully processed. Oracle Financials Cloud will subscribe to this business event and mark the invoice as confirmed.
Steps to Enable
(Required) ADD MESSAGE CONFIRMATION MESSAGE TO OUR B2B SERVICE PROVIDER OR TRADING PARTNER SETUP
The Message Confirmation message is similar to the other pre-built B2B messages, but the confirmation message is correlated to the original B2B message it is confirming; for example, Invoice, Purchase Order, ASN. For collaboration messaging to process confirmations for a document type, you must setup and configure the Message Confirmation message in the list of active and enabled messages.
The following screenshot shows the OAGIS_10.1_CONFIRM_BOD_COLLAB_MSG_IN collaboration message added to a trading partner record.
Manage Trading Partner - Inbound Collaboration Messages
(Required) DEFINE B2B MESSAGES ENABLED TO RECEIVE CONFIRMATIONS
You must edit the original B2B message in B2B service provider or trading partner setup to enable the message to receive confirmation messages using the new Confirmation Message column. If an outbound B2B message, such as invoice, is supposed to receive a confirmation message, enter the name of the confirmation message in the Confirmation Message column.
The following screenshot shows the OAGIS_10.1_PROCESS_INVOICE_COLLAB_MSG_OUT collaboration message configured to use the OAGIS_10.1_CONFIRM_BOD_COLLAB_MSG_IN confirmation message added in the Confirmation Message column.
Manage Trading Partner - Outbound Collaboration Messages
(Optional) DEFINE CONFIRMATION CODE CROSS-REFERENCES
You may need to define the Confirmation Code cross-reference values if the Confirmation Code values received from your trading partner cannot be interpreted or processed by the Oracle Cloud product receiving the confirmation.
For example, your trading partner may be sending a confirmation message with Processing Result Code as 00, which is their code for Success. The Oracle Cloud product may require S to indicate Success, else it will result in an error. In this case, you must define the Confirmation Code cross-reference value to interpret 00 received from your trading partner as S for the Oracle Cloud product receiving the confirmation.
NOTE: Collaboration Messaging Framework will always log Processing Result Code received from your trading partner, so the cross-reference is not necessary if the confirmation will not be processed by the Oracle Cloud product owning the original B2B message.
Manage Trading Partners - Manage Confirmation Codes
Tips And Considerations
NO OUTBOUND CONFIRMATION MESSAGES
This feature applies to confirmation messages in response to an outbound B2B message processed by Collaboration Messaging Framework. Outbound confirmation messages in response to an inbound B2B message processed by Collaboration Messaging Framework is not supported in the current release.
MULTIPLE CONFIRMATION MESSAGE SUPPORT
Once you configure a B2B message to receive confirmations, there is no limit to the number of confirmation messages that can be received. Therefore, if Collaboration Messaging Framework receives an initial invoice confirmation indicating an issue, it can still receive a subsequent invoice confirmation indicating success.
ORACLE CLOUD PRODUCT SUPPORT
You can implement Message Confirmation messages for any outbound, pre-built B2B message supported by Collaboration Messaging Framework. The confirmation message is always validated and stored in the Collaboration Messaging Framework transaction log. Collaboration Messaging Framework will always raise a business event to indicate processing status but not all Oracle Cloud products will uptake this event and update their business object with this information.
Enhance B2B Message Processing
In releases prior to Oracle Supply Chain Management Cloud Release 11, Business to Business (B2B) messaging support was provided at the product level; for example, Oracle Procurement Cloud, Oracle Inventory Management Cloud, and Oracle Product Hub Cloud. Oracle Collaboration Messaging Framework introduces a common architecture and process for B2B messaging across all Oracle SCM Cloud, Oracle Procurement Cloud, and Oracle Financials Cloud products.
If you implemented B2B messaging prior to Release 11, you can now quickly and easily migrate all your B2B trading partners from Service-Oriented Architecture (SOA) B2B (used pre-Release 11) to Collaboration Messaging Framework. Migrating your B2B messaging implementation to Collaboration Messaging Framework has the following advantages:
- Open Applications Group Integration Specification (OAGIS) 10.1 XML: The older implementations of B2B messaging used OAGIS 7.2.1, which is an old standard and did not utilize the current industry best practices for XML and XML schema.
- More pre-built B2B messages: Collaboration Messaging Framework currently supports more than 15 pre-built B2B messages spanning multiple business processes with more being added every release. The previous implementation supported only four B2B messages for the Procure-to-Pay business process.
- Integrated B2B message processing: The previous implementations of B2B messaging had technical dependencies on multiple Oracle technologies that resulted in a complicated and inefficient setup and maintenance process. Collaboration Messaging Framework also relies on multiple Oracle technologies but it has done so in a way that is seamless to customers.
Once trading partners have been imported, you can view the import status using the new Manage Collaboration Messaging Setup Data Import page. This page allows you to view all successfully imported trading partners as well as highlight issues encountered during trading partner import processing.
Manage Collaboration Messaging Setup Data Import
Steps to Enable
(Required) EXPORT TRADING PARTNERS FROM SOA B2B
You must export trading partner definitions from SOA B2B. This process creates a .zip file which must be loaded into the content management server.
SOA B2B Import/Export
(Required) CREATE COLLABORATION MESSAGING SETUP DATA FILE
You must run the Create Collaboration Messaging Setup Data File program as an ESS job. This process will read all trading partners data exported from SOA B2B, validate whether the trading partner is a candidate for import, and create the Import Collaboration Messaging Setup Data file.
Create Collaboration Messaging Setup Data File
(Required) IMPORT COLLABORATION MESSAGING SETUP DATA FILE
You must run the Import Collaboration Messaging Setup Data File program as an ESS job after the Create Collaboration Messaging Setup Data File program run successfully. There are two import processing modes to choose from: Import to CMK or Validate Only. Validate Only will run all validations required to import supplier trading partners into Collaboration Messaging Framework but will not commit the transactions. Use the Validate Only processing mode to review any errors and make corrections before your final import.
Import Collaboration Messaging Setup Data
Tips And Considerations
CREATE COLLABORATION MESSAGING SETUP DATA FILE VALIDATION AND PROCESSING RULES
There are several validation rules executed during the Create Collaboration Messaging Setup Data File process. The following is a summary of the most important validations:
- The ID Type must be B2BSiteCode. If the trading partner in SOA B2B does not have an ID with ID Type B2BSiteCode, the trading partner will not be imported into Collaboration Messaging Framework.
- The trading partner documents must be pre-seeded Oracle documents. If the documents associated with the SOA B2B trading partner do not include at least one pre-seeded Oracle document, the trading partner will not be imported into Collaboration Messaging Framework.
Some key processing rules that you should be aware of are:
- RECEIVER_ID and RECEIVER_ID_TYPE are mapped to Partner ID and Partner ID Type
- All trading partners imported with B2B Service Provider as OSNTest
- B2B Site Code value is mapped to PartnererKey1 with PartnerKeyType as B2BSiteCode
Embed Attachments in Outbound Messages
Attachments to electronic messages have been in use for some time and are becoming more and more common; for example, a scanned paper Invoice attached to an electronic shipment message or product images attached to an electronic product catalog message. Currently attachments are sent as separate objects from the message payload. Now you can embed attachments directly into the body of the message, ensuring the attachment can never be separated from the message body.
Availability of this feature for specific pre-built B2B messages depends on the Oracle Cloud product owning the business object and it's ability to publish and consume attachments; for example, Oracle Inventory Management Cloud must support attachments in order for them to be available on the ASN B2B message.
Attachments are processed one at a time starting with the top level of the message hierarchy; for example, PO Header, then moving to child levels; for example, PO Lines, once all top-level attachments have been processed.
The Collaboration Messaging Framework process will monitor the total size of all attachments for a specific B2B message instance and if the total size exceeds the Maximum attachment size for outbound messaging parameter (default value 2 MB), any subsequent attachments will not be processed and are flagged as unsent.
Manage Collaboration Messaging History - Attachments
The Manage Collaboration Messaging History page includes the Total Attachments and Number of Attachments Processed parameters for each B2B message. You can also view details for each of the attachments from this page.
Steps to Enable
(Optional) UPDATE THE NEW MAXIMUM ATTACHMENT SIZE FOR OUTBOUND MESSAGING PARAMETER
You can update the new Maximum attachment size for outbound messaging parameter on the Manage Collaboration Messaging Configuration page. The default value of this parameter is 2 MB. You need to update this parameter only if you want to change the default value.
Manage Collaboration Messaging Configuration
Tips And Considerations
ENCODING AND DECODING OF ATTACHMENTS
Attachments may come in any of the multiple file formats: .pdf, .jpg, .docx, etc. Before these files can be embedded and transmitted in a XML file, they must be encoded into a standardized base64Binary format.
IMPORTANT: Once an attachment has been encoded to base64Binary, it cannot be read until it is decoded. If you want to actually see an attachment by viewing the raw XML message, you will not be able to do so.
Key Resources
- RFC 2045. N. Freed and N. Borenstein. RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. 1996.
All B2B messages supported by Oracle Collaboration Messaging Framework are delivered with pre-defined maps to convert Oracle's internal object format to standards-based OAGIS format. However, in many cases, industry guidelines, company policy or procedures or some other factors may require a different mapping rule or perhaps a new data element in your B2B message. It is now possible to download pre-defined maps, update the map (expressed as an XSLT file) and upload to Collaboration Messaging Framework. Changes can be as small as updating source or target for a single data element or adding a new set of data elements. All changes must be valid XSLT and must conform to the OAGIS standard used by the pre-defined map. In addition, changes are preserved during upgrade and will not be overwritten.
PROCESSING
The new Collaboration Message is processed similar as any other pre-built B2B message, with the difference that instead of using the pre-defined map, the new Collaboration Message will use the updated, user-defined map.
Steps to Enable
To implement this feature you must download Oracle's pre-defined XSLT and related XSDs and update the pre-defined map using any text or XSLT editor. After you make the updates and verify the updated map, you can duplicate the pre-built B2B message and associate the updated map to this new B2B message using Collaboration Messaging Framework.
IMPORTANT: You must create a new Collaboration Message to use your updated map. You cannot update the existing, pre-built Collaboration Message with your updated map.
You can then update the B2B service providers and trading partners you have defined to include your new Collaboration Message and remove the existing, pre-built Collaboration Message.
To configure message maps and associate and enable your new Collaboration Message:
- From the Manage Collaboration Messages page, select the Collaboration Message you want to update and click Actions> Export Transformation Package to download a .zip file of .XSL and .XSD files.
Manage Collaboration Messages
- You can make any valid .XSL change to the map file. This could include mapping of new attributes such as flex fields, addition of rules such as required or default values, or any other mapping update you may require.
NOTE: Updates are made only to the .XSL map file. You cannot update the source and target definitions. You must validate any mapping changes against the source and target before using.
Manage Collaboration Message - Duplicate
- Click Actions > Duplicate Collaboration Messages.
- Define a new, unique name for the message and specify which map file should be associated to the message. The following screenshot shows the new OAGIS_10_1_PROCESS_PO_COLLAB_MSG_OUT_001) Collaboration Message.
Manage Trading Partners
- Click Save.
- Associate and enable your new Collaboration Message to any B2B service providers or trading partners.
Public Service to Expose Complete Structure of Configured Item
A public service is now available to expose the current structure of a configured item to the calling application. The returned structure consists of customer-selected options (that is, Sales View), compulsory items, substitute items, and transactional item attributes. This feature enables enterprises to pass on detailed configuration to the contract manufacturers, and helps shippers prepare accurate customs-compliant shipping documents.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
- With this service you can:
- Request the Sales or Complete Instance structure of an individual configuration item
- Request the Sales structure of all of 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
- Consider the number of records to be returned from an individual request. You can include only a maximum of 500 records in each query, but you can use the fetchSize and fetchStart parameters with sequential requests to retrieve a complete data set.
- Use assemble-to-order models with back-to-back and drop ship flows in Order Management. Planning forecasts of models and their components are also supported.
Key Resources
- Oracle Supply Chain Management Cloud: SOAP Web Services for SCM Cloud, 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)
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 | Create and Manage Your Supply Collaboration Network | Updated document. Revised screenshot. |
| 02 FEB 2018 | Collaborate with Suppliers on Order Forecast Commitments | Updated document. Revised screenshot. |
| 21 APR 2017 | Created initial document. |
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 & New Features
If your system has modified security structures, you may need to advise your security administrator of new features you would like to take advantage of. Appendix A provides a listing of the security attributes needed to employ the new features after you have decided to implement them.
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 Oracle Cloud Applications and we now give you the option to take advantage of new functionality at a pace that suits you. The ‘New Features UI’ is available to you from your cloud homepage, where you can make your choices and do any configuration necessary.
This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.
| Action Required to Enable Feature |
||||
|---|---|---|---|---|
| Feature |
Automatically Available |
End User Action Required |
Administrator Action Required |
Oracle Service Request Required |
|
||||
Review Status and Take Action Through Graphical Infolet-Based Views |
|
|||
|
||||
Collaborate with Contract Manufacturers on Production Status |
|
|||
|
||||
|
||||
|
||||
|
||||
|
||||
APPENDIX A: FUNCTION SECURITY PRIVILEGES AND AGGREGATE PRIVILEGES |
||||
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 you to jointly plan supply, gain visibility into trading partner data, coordinate contract manufacturing execution, and measure performance across your trading networks. Your trading partners are actively involved in the decision-making process, so they can exchange early warning signs and collaboratively resolve supply chain issues. Depending upon the size and technical sophistication of each supplier, your company can interact by way of a portal-based user interface, standards-based B2B messages, or web services. You can also tailor Supply Chain Collaboration’s flexible, predefined business processes to your own unique requirements. Enhanced collaboration results in more dynamic trading relationships, as well as increased reliability and efficiency of supply.
To use Supply Chain Collaboration features, you must enable the Supply Chain Collaboration functional area in the Manufacturing and Supply Chain Materials Management setup offering. Do the following:
- In the Navigator, click Setup and Maintenance.
- Select the Manufacturing and Supply Chain Materials Management offering. Click Actions > Change Configuration.
- Select the Enable for Implementation check box for the Supply Chain Collaboration functional area.
- Click Setup, and verify that the Supply Chain Collaboration functional area appears in the list of functional areas for the offering.
Collaborate with Trading Partners on a Common Platform
Supply Chain Collaboration breaks down the barriers between enterprise systems so you can enhance collaboration with your trading partners. By using a common collaboration platform, you can replace siloed, unsynchronized data exchange with a real-time shared version of the truth. You can collaborate on forecast mismatches, inventory shortages, shipment delays, and other issues. The collaboration is supported by common analytics, social networking, and business transactions. You can also engage trading partners in the decision-making process by way of a portal-based user interface, standards-based Business-to-Business (B2B) messages, or web services, depending upon the trading partner’s size and sophistication.
Collaborative trading relationships are more dynamic, reliable, and efficient, enhancing the flexibility and throughput of your whole supply chain.
Create and Manage Your Supply Collaboration Network
A common definition of your supplier network is central to effective supply chain collaboration. Supply Chain Collaboration unifies the setup and management of your supplier networks across all communication mechanisms (portal, web service, and B2B messaging) to streamline the configuration of collaboration processes and reduce the cost of on-boarding suppliers.
You can do the following:
- Define relationships with your suppliers at the supplier site, ship-to organization, and item level.
- Search, edit, and duplicate existing relationships to create new ones.
- Set attributes such as the commit horizon, forecast horizon, and commit and cycle time to be used.
- Enable B2B messaging for supplier sites, and specify the messages that might transact with them.
- Identify the supply plans within Oracle Supply Chain Planning Cloud that you want to use in collaboration.
- Specify the frequency of collaboration.
- Specify the aggregation schedule that will be used to view the measures and exceptions.
The following screenshot shows the Manage Supply Collaboration Network page with three relationships created.
Manage Supply Collaboration Network Page
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Suppliers, Supplier Sites, Organizations, and Items are used to create relationships. All of these must exist to enable collaboration.
Key Resources
- Oracle SCM Cloud: Implementing Manufacturing and Supply Chain Materials Management, available on the Oracle Help Center.
Review Status and Take Action Through Graphical Infolet-Based Views
Users can only address the trading partner issues that they can clearly identify. The Supply Chain Collaboration work area landing page uses infolets with embedded analytics to orient users to the status of their trading relationships, so they can prioritize their actions. (Infolets are card-like, interactive containers that use a “Glance, Scan, Commit” design principle to help you visualize high-level information, review relevant details, and proceed to action as quickly as possible.) Depending on their role, users can assess planning collaboration, contract manufacturing collaboration, and business-to-business messaging performance in one consolidated view. Both enterprise users and trading partners can see any changes or exceptions at a glance, flip or expand an Infolet to get more detail, and drill down to perform transactions with a single click. Users can monitor more relationships and respond to critical issues more rapidly as a result.
The Supply Chain Collaboration work area landing page includes the following infolets:
- Collaboration Tasks. This infolet indicates the number of item-site combinations across all relationships that have order forecasts and supply commits to review. Users can click on the values to see the underlying data and make changes.
- Order Forecasts Changes. This infolet shows the number of order forecast changes across all relationships between the current and previous collaboration cycles. Users can either click the total to review all the changes, or expand the infolet to see a prioritized list of items with order forecast changes, along with the mean absolute percentage deviation of the current forecast from the previous one.
- Past Due Commits. This infolet highlights the number of commits that are overdue across all relationships based upon their service-level agreements. Users can expand this Infolet to review a bar chart illustrating the top five suppliers with the most violations.
- Forecast Commit Status. This infolet illustrates a pie chart that shows the number of relationships that have submitted their commits, not submitted their commits, or have order forecast commit mismatches. Users can drill down to any slice to see the specific forecasts and commits in each status.
- Production Reports. This infolet shows the number of contract manufacturer production reports received across all relationships in the last three, seven, and fourteen days.
- Undelivered B2B Messages. This infolet makes users aware of any undelivered B2B transactions. It displays the number of ProcessPlanningSchedule (outbound forecast) and AcknowledgePlanningSchedule (inbound commit) transactions that have not been delivered in the current collaboration cycle. Appropriately privileged users can drill down on this number to see which specific transactions have not been delivered.
- Failed B2B Messages. This infolet highlights any failed B2B transactions. It displays the number of ProcessPlanningSchedule (outbound forecast) and AcknowledgePlanningSchedule (inbound commit) transactions that have failed. Appropriately privileged users can drill down on this number to see which specific transactions failed.
The following screenshot shows infolets on the Supply Chain Collaboration work area landing page.
Supply Chain Collaboration Landing Page
Steps to Enable
No steps are required to enable this feature.
Collaborate with Suppliers on Order Forecast Commitments
In any outsourced supply situation, it is critical to share clear and accurate order forecasts with suppliers, so they can assure the supply of critical components, assemblies, and products you need to reach your goals. By sharing forecasts and getting supplier commitments to future deliveries, Supply Chain Collaboration can reduce the risk of supply shortages and disruptions. Effective collaboration can also uncover opportunities to reduce costs or improve the quality of supply.
Using Supply Chain Collaboration, you can:
- Receive and publish order forecasts from Oracle Planning Central Cloud or Oracle Supply Planning Cloud to trading partners.
- Review order forecasts and provide commits by way of the Supplier Portal, spreadsheets, B2B messaging, or web services, depending upon each supplier’s capability.
- Review supplier commitments received interactively with mismatches highlighted.
- Interact with suppliers to negotiate adjustments to their commitments, address supply issues, or discuss product changes.
- Update commitment on behalf of the supplier on-line or by way of spreadsheet uploads.
- Post supplier commitments to Oracle Planning Central Cloud or Oracle Supply Planning Cloud.
- Search by several criteria (supplier, supplier site, item, supply plan, and ship to organization) to refine the scope of collaboration, and save your searches for one-click access.
- Compare current planning cycle order forecasts and commitments with previous values.
- Get alerts to order forecast collaboration exceptions, such as commit mismatches, forecast deviations, and past due commitments.
- Interact with supply chain planners by way of social networking to understand forecast deviations from one cycle to another.
The following screenshot shows an example of inline editing on the Edit Order Forecast Details page in the Supplier Portal.
Edit Order Forecast Details Page
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Supplier users must have access to Oracle Supplier Portal Cloud to review forecasts and provide commits.
Collaborate with Contract Manufacturers on Production Status
Effective outsourcing projects each contract manufacturer as a virtual extension of your manufacturing capabilities, so you can manage costs, reduce supply risk, and meet your fulfillment goals. Close collaboration with contract manufacturers enables you to:
- Receive periodic progress updates from your contract manufacturing partners by way of the Supplier Portal. The updates include completions and component consumption, as well as lot and serial information on the consumed component.
- View contract manufacturer progress updates online.
- Automatically convert contract manufacturer updates into manufacturing transactions for visibility and costing.
The following screenshot shows the default search filters on the search page and the production report search result. The icons in the Status column indicate whether the submission of report data to Manufacturing was successful. You can resubmit the production reports with errors.
Production Reports Search Page
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Supplier Portal, Supply Chain Collaboration, and Supply Chain Orchestration all integrate to provide visibility to the procurement and manufacturing processes.
Key Resources
- Oracle SCM Cloud: Implementing Manufacturing and Supply Chain Materials Management, available on the Oracle Help Center.
Orchestrate Supply Chain Business Processes
As the complexity of collaboration increases, you need to automate processes and monitor exception conditions online. Supply Chain Collaboration provides a predefined process to send an order forecast to a supplier and receive a response. The process monitors whether the supplier responds within the expected forecast commitment cycle time, and raises an exception if not. The process can also automatically adjust to midcycle updates to the order forecast.
Steps to Enable
No steps are required to enable this feature.
Interoperate with Standards-Based B2B Messaging
Business to Business (B2B) messaging is a key component of collaboration relationships that can increase the quality, quantity, and frequency of information that can be exchanged. However, the differences in B2B standards, the technical capabilities of trading parties, and the large numbers of trading parties can make this costly to establish and maintain one partner at a time. To better manage B2B communications with large numbers of trading parties, Supply Chain Collaboration uses the Oracle Collaboration Messaging Framework, a next-generation B2B messaging platform that maps and routes standards-based messages directly to the network provider. Trading partners can continue to use their existing B2B messaging protocols to automatically connect to Oracle SCM Cloud through their network.
From the enterprise perspective, Collaboration Messaging Framework is tightly integrated with, and included as part of all Oracle SCM Cloud applications, making it easy for Supply Chain Collaboration customers to set up additional trading partner connections.
Implement B2B Messaging with Multiple Service Providers
Use Collaboration Messaging Framework to define suppliers as trading partners and select which service providers and B2B messages apply to them. To facilitate this, you can:
- Use a global, industry-standard XML format (OAGIS 10.1 – Open Applications Group Integration Specification) for all messages.
- Use predefined integration with B2B service providers to onboard entire communities of trading partners with minimal effort.
- Let trading partners continue to use their existing B2B processes (and existing B2B format, such as EDI) when they communicate.
Steps to Enable
No steps are required to enable this feature.
Integrate Procure-to-Pay B2B Messaging
Supply Chain Collaboration supports the procure-to-pay process by way of predefined integration between Collaboration Messaging Framework and Oracle Purchasing Cloud. The following table provides the supported B2B messages.
| Functional Name |
OAGIS B2B Message |
Other B2B Standards* |
|---|---|---|
| Outbound Purchase Order |
ProcessPurchaseOrder |
|
| Outbound Purchase Order Change |
ChangePurchaseOrder |
|
| Outbound Cancel Purchase Order |
CancelPurchaseOrder |
|
| Inbound ASN |
ProcessShipment |
|
| Inbound Invoice |
ProcessInvoice |
|
*Translation provided by third-party service providers.
Steps to Enable
No steps are required to enable this feature.
Integrate Order-to-Cash B2B Messaging
Supply Chain Collaboration supports the order-to-cash process by way of predefined integration between the Collaboration Messaging Framework and Oracle Order Management Cloud.
The following table provides the supported customer-facing B2B messages.
| Functional Name |
OAGIS B2B Message |
Other B2B Standards* |
|---|---|---|
| Inbound Order |
ProcessPurchaseOrder |
|
| Outbound Order Acknowledgement |
AcknowledgePurchaseOrder |
|
| Inbound Change Order |
ChangePurchaseOrder |
|
| Outbound Change Order Acknowledgment |
AcknowledgeChangePurchaseOrder |
|
| Inbound Cancel Order |
CancelPurchaseOrder |
|
| Outbound Cancel Order Acknowledgement |
AcknowledgeCancelPurchaseOrder |
|
| Outbound ASN |
ProcessShipment |
|
*Translation provided by third-party service providers.
Steps to Enable
No steps are required to enable this feature.
Integrate Planning Collaboration B2B Messaging
Supply Chain Collaboration supports the planning collaboration process by way of predefined integration between Collaboration Messaging Framework and Supply Chain Collaboration. The following table provides the supported B2B messages:
| Functional Name |
OAGIS B2B Message |
Other B2B Standards |
|---|---|---|
| Process Forecast |
ProcessPlanningSchedule |
|
| Acknowledge Commit |
AcknowledgePlanningSchedule |
|
*Translation provided by third-party service providers.
Steps to Enable
No steps are required to enable this feature.
APPENDIX A: FUNCTION SECURITY PRIVILEGES AND AGGREGATE PRIVILEGES
This release includes new roles and privileges that facilitate function security for new features. If you have created custom job roles, then you can add new privileges to those custom roles as needed.
Table A-1 Function Security Privileges for Supply Planning Collaboration
| Privilege Name and Code |
Job Role Name and Code |
|---|---|
| View Order Forecasts VCS_VIEW_ORDER_FORECAST |
Supply Chain Collaboration Planner ORA_VCS_SUPPLY_CHAIN_COLLABORATION_PLANNER |
| View Supply Chain Collaboration Work Area VCS_VIEW_SCC_SUPPLY_PLANNING_WORKAREA |
Supply Chain Collaboration Planner ORA_VCS_SUPPLY_CHAIN_COLLABORATION_PLANNER |
| Commit to Order Forecasts as Enterprise User VCS_COMMIT_ORDER_FORECAST_ENTERPRISE |
Supply Chain Collaboration Planner ORA_VCS_SUPPLY_CHAIN_COLLABORATION_PLANNER |
| Commit to Order Forecasts as Supplier VCS_COMMIT_ORDER_FORECAST_SUPPLIER |
Supplier Demand Planner ORA_POS_SUPPLIER_DEMAND_PLANNER |
| View Supply Chain Collaboration infolets as Suppliers VCS_VIEW_SCC_SUPPLY_PLANNING_REGION_AS_SUPPLIER |
Supplier Demand Planner ORA_POS_SUPPLIER_DEMAND_PLANNER |
| Schedule Order Forecast Decomposition VCS_SCHEDULE_ORDER_FORECAST_DECOMP |
Supply Chain Application Administrator ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR
|
| Manage Supply Planning Network Relationships VCS_MANAGE_SUPPLY_RELATIONSHIPS |
Supply Chain Application Administrator ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR |
| Manage Aggregation Schedules VCS_MANAGE_AGGREGATION_SCHEDULES |
Supply Chain Application Administrator ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR |
| Manage Collaboration Plans VCS_MANAGE_COLLAB_PLANS |
Supply Chain Application Administrator ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR |
| Purge Historical Collaboration Records VCS_PURGE_HISTORICAL_RECORDS |
Supply Chain Application Administrator ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR |
| View Order Forecasts by Web Service VCS_GET_ORDER_FORECAST_WEBSERVICE |
Web Services Application Identity (SCM) FUSION_APPS_SCM_SOA_APPID |
| Execute Order Forecast Orchestration Web Services VCS_EXECUTE_FORECAST_ORCHESTRATION_WEB_SERVICES |
Web Services Application Identity (SCM) FUSION_APPS_SCM_SOA_APPID |
| Commit to Order Forecasts by Web Service VCS_COMMIT_ORDER_FORECAST_WEBSERVICE |
Web Services Application Identity (SCM) FUSION_APPS_SCM_SOA_APPID |
| View Supply Chain Collaboration B2B Infolets VCS_VIEW_SCC_B2B_INFOLETS |
B2B Messaging Administration Duty ORA_CMK_B2B_MESG_ADMIN_DUTY |
Table A-2 Function Security Privileges for Contract Manufacturing Collaboration
| Privilege Name and Code |
Job Role Name and Code |
|---|---|
| View Contract Manufacturing Reports DOS_CMP_VIEW_RPTS |
Supplier Inventory Manager ORA_INV_SUPPLIER_INVENTORY_MANAGER |
| Upload Contract Manufacturing Reports DOS_CMP_UPLOAD_RPTS |
Supplier Inventory Manager ORA_INV_SUPPLIER_INVENTORY_MANAGER |
| View Contract Manufacturing Reports DOS_CMP_VIEW_RPTS |
Supply Chain Operations Manager ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER |
| Upload Contract Manufacturing Reports DOS_CMP_UPLOAD_RPTS |
Supply Chain Operations Manager ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER |
| Resubmit Contract Manufacturing Reports DOS_CMP_RESUBMIT_RPTS |
Supply Chain Operations Manager ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER |
---
Copyright © 2017, 2019, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only, and the contents hereof are subject to change without notice.This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
