Cloud Readiness / Oracle Supply Chain Collaboration and Visibility Cloud
New Feature Summary
  1. Update 19B
  1. Revision History
  2. Overview
    1. Collaboration Messaging Framework
        1. Use B2B Location Codes to Identify Ship-To and Bill-To Locations for Order-to-Cash Messaging
        2. Migrate Trading Partner Configurations from Oracle B2B Gateway to Oracle Cloud Collaboration Messaging Framework
        3. Specify an Alternate Delivery Method for Sending Large Messages
        4. Use a Web Service to Exchange Messages with Oracle Supplier Network
      1. Integrate and Extend Collaboration Messaging Framework Using REST Services
        1. Query B2B Service Providers Using a REST Service
        2. Query B2B Application Partners Using a REST Service
    2. Supply Chain Collaboration
      1. Buy-Side, Vendor-Managed Inventory
        1. Update the VMI Network Using Spreadsheet Uploads
        2. Review and Resolve Failed Replenishment Requests
    3. Supply Chain Orchestration
        1. Use the Supply Request REST Service to Request a Buy Supply in Addition to a Transfer Supply

Update 19B

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
17 APR 2019 Query B2B Application Partners Using a REST Service Updated document. Edited feature name and description.
17 APR 2019 Query B2B Service Providers Using a REST Service Updated document. Edited feature name and description.
08 MAR 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

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.

Use B2B Location Codes to Identify Ship-To and Bill-To Locations for Order-to-Cash Messaging

Assign B2B location codes to ship-to and bill-to location addresses of customers set up in Oracle SCM Cloud. You can use B2B location codes instead of bill-to and ship-to address details to exchange B2B messages with trading partners.

Migrate Trading Partner Configurations from Oracle B2B Gateway to Oracle Cloud Collaboration Messaging Framework

Migrate Oracle B2B setup data to Oracle Collaboration Messaging Framework Cloud if you implemented procure-to-pay B2B using B2B Gateway instead of Collaboration Messaging Framework.  This enables Oracle Cloud applications to use Collaboration Messaging Framework for all B2B messaging.

Specify an Alternate Delivery Method for Sending Large Messages

Specify a maximum message size for a delivery method as well as an alternate delivery method to be used if the message exceeds the maximum size.

Use a Web Service to Exchange Messages with Oracle Supplier Network

Use a web service instead of HTTP POST to set up B2B message exchange with Oracle Supplier Network.  You need to update message delivery setup in both Collaboration Messaging Framework and Oracle Supplier Network to use the Collaboration Message V2 web service.

Integrate and Extend Collaboration Messaging Framework Using REST Services

Query B2B Service Providers Using a REST Service

Use the B2B Service Providers public REST API to query B2B service providers. 

Query B2B Application Partners Using a REST Service

Use a public REST API to query B2B application partner details. You can use the B2B Trading Partners API to find the trading partners associated with a supplier site, customer, or customer account, and the collaboration documents that are enabled for messaging with each partner.

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.

Buy-Side, Vendor-Managed Inventory

Vendor-Managed Inventory (VMI) is a family of business models in which a buyer provides inventory and consumption information about a product to the supplier. Based on the agreement between the buyer and supplier, the supplier is responsible for maintaining the inventory thresholds close to or at the buyer's facility. This process streamlines inventory management by delegating replenishment calculations and execution of the process to suppliers.

Oracle Supply Chain Collaboration Cloud enables both partners to monitor inventory performance, receive exception alerts, and collaborate to resolve replenishment issues. Both pay-on-use and pay-on-receipt are supported.

This model ensures that both the enterprise and the supplier come together to provide better service to the customer. In addition, the enterprise’s planning and ordering cost will reduce as the responsibility will shift to the supplier while the overall service level will increase by providing the right product at the right facility. The supplier benefits by having visibility into the enterprise’s demand and stock levels. Further, the supplier will be able to incorporate promotions into the inventory plan more easily.

Update the VMI Network Using Spreadsheet Uploads

Update the vendor-managed inventory network by using file-based data import to create vendor-managed inventory relationships.

Review and Resolve Failed Replenishment Requests

Review the reasons for replenishment request failure, so analysts can resolve the data configuration issues and re-create the request.

Supply Chain Orchestration

Use the Supply Request REST Service to Request a Buy Supply in Addition to a Transfer Supply

Use a public REST API to make a supply request for a Buy supply type in addition to the Transfer supply type. If you don’t specify the supply type while requesting the supply, the REST service uses the Oracle Global Order Promising Cloud sourcing rules to determine whether the supply type is a Buy or Transfer.