TABLE OF CONTENTS DOCUMENT HISTORY 4

Similar documents
Transcription:

TABLE OF CONTENTS DOCUMENT HISTORY 4 UPDATE 17D 4 Revision History 4 Overview 4 Supply Chain Collaboration 5 Manage Collaboration Process More Efficiently 5 Streamline Collaboration Relationship Creation 5 Automate Actions for Past-Due Supplier Commitments 5 Manage Collaboration Relationship Candidates Using a REST API 5 View Purchase Orders and Shipments 5 Collaboration Messaging Framework 6 Enhanced B2B Message Processing 6 Search and Manage All B2B Messages From a Single Page 6 Use New B2B Protocol Options for Exchanging B2B Messages 6 Send B2B Messages Using Email 6 Exchange New B2B Messages With Your Trading Partners 6 Send Invoice Rejection Notifications to Suppliers 6 UPDATE 17C 7 Revision History 7 Overview 7 Supply Chain Collaboration 7 Manage the Collaboration Process More Efficiently 8 Control Access to Trading Partner Data 8 Manage Functional Privileges by Roles 8 Edit Order Forecasts 8 Perform Order Forecast Commit Waterfall Analysis 9 Provide Planners with Visibility to Item Attributes 9 Adjust the Exception Start Date 9 View Collaboration Plans Across Multiple Tiers 9 Collaboration Messaging Framework 10 Exchange New B2B Messages With Your Trading Partners 10 Send Invoices to Customers 10 Receive Message Confirmation Messages 10 Enhance B2B Message Processing 10 Import B2B Trading Partners 11 Embed Attachments in Outbound Messages 11 Configure Message Maps 11 Supply Chain Orchestration 11 Public Service to Expose Complete Structure of Configured Item 12 UPDATE 17B 12 Revision History 12 Overview 12 Supply Chain Collaboration 13 Collaborate with Trading Partners on a Common Platform 13 Create and Manage Your Supply Collaboration Network 13 Review Status and Take Action Through Graphical Infolet-Based Views 14 Collaborate with Suppliers on Order Forecast Commitments 14 2

Collaborate with Contract Manufacturers on Production Status 15 Orchestrate Your Supply Chain 15 Orchestrate Supply Chain Business Processes 15 Interoperate with Standards-Based B2B Messaging 15 Implement B2B Messaging with Multiple Service Providers 16 Integrate Procure-to-Pay B2B Messaging 16 Integrate Order-to-Cash B2B Messaging 16 Integrate Planning Collaboration B2B Messaging 17 3

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 06 OCT 2017 Update 17D New features delivered in update 17D. 11 AUG 2017 Update 17C New features delivered in update 17C. 07 APR 2017 Update 17B New features delivered in update 17B. UPDATE 17D 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 06 OCT 2017 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. 4

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, standardsbased 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 COLLABORATION PROCESS MORE EFFICIENTLY In an effort to streamline the end-to-end collaboration process and provide a better understanding of the collaboration results, the following enhancements are available. 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 navigating to different pages. AUTOMATE ACTIONS FOR PAST-DUE SUPPLIER COMMITMENTS Allow an administrator to define the action that occurs when suppliers are past the due date on their contractually obligated commitment. MANAGE COLLABORATION RELATIONSHIP CANDIDATES USING A REST API Allow an administrator to use a public REST API to view and manage collaboration relationship candidates received from planning that are not currently collaborated on. VIEW PURCHASE ORDERS AND SHIPMENTS Allow both suppliers and enterprise planners to derive and view the total commitment from purchase orders, shipments in receiving, and the in-transit shipments for an item in the given time bucket. 5

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 nextgeneration 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. ENHANCED B2B MESSAGE PROCESSING In addition to sending and receiving B2B messages, many value-add features are available that can improve efficiency, lower costs, and expand the scope of collaboration with your trading partners. These features include enhancements to message delivery options. 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. USE NEW B2B PROTOCOL OPTIONS FOR EXCHANGING B2B MESSAGES Send and receive B2B messages using standard HTTP, AS2, SFTP, in addition to SOAP web services. SEND B2B MESSAGES USING EMAIL Send the same OAGIS XML B2B message used in system-to-system automation as an email attachment to your trading partners. EXCHANGE NEW B2B MESSAGES WITH YOUR TRADING PARTNERS Delivery of pre-built, pre-integrated B2B messages is a key benefit of using Collaboration Messaging Framework. Prioritization and availability of these B2B messages are driven by use cases for strategic business process such as order-to-cash and procure-to-pay. New messages are added with every update, resulting in a robust library of B2B messages. Each pre-built B2B message can be implemented out-of-the-box with no additional integration or development work required, so expanding the number of B2B messages exchanged with trading partners is extremely fast and efficient. 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. 6

UPDATE 17C 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 11 AUG 2017 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. 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 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. This document details Release 11.13.17.08.00 enhancements. 7

MANAGE THE COLLABORATION PROCESS MORE EFFICIENTLY Delivery of pre-built, pre-integrated B2B messages is a key benefit of using Collaboration Messaging Framework. Prioritization and availability of these B2B messages are driven by use cases for strategic business processes such as order-to-cash and procure-to-pay and new messages are added with every release, resulting in a robust library of B2B messages. Each pre-built B2B message is ready-to-use with no additional integration or development work required so expanding the number of B2B messages exchanged with trading partners is extremely fast and efficient. 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. MANAGE FUNCTIONAL PRIVILEGES BY ROLES Users with different roles require different privileges. A small number of administrative users can manage access for the 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 with the 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 don t have access to the admin functions. EDIT ORDER FORECASTS Sometimes a collaboration planner needs to adjust the order forecasts in a plan, either due to sensitivity about some of the numbers, or for negotiation purposes, before sharing it with a supplier. 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. 8

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. 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. 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. 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. 9

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 Collaboration Messaging Framework, a nextgeneration 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. 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 Delivery of pre-built, pre-integrated B2B messages is a key benefit of using Collaboration Messaging Framework. Prioritization and availability of these B2B messages are driven by use cases for strategic business processes such as Order-to-Cash and Procure-to-Pay and new messages are added with every release, resulting in a robust library of B2B messages. Each pre-built B2B message is ready-to-use with no additional integration or development work required so expanding the number of B2B messages exchanged with trading partners is extremely fast and efficient. SEND INVOICES TO CUSTOMERS 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. 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 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. ENHANCE B2B MESSAGE PROCESSING In addition to sending and receiving B2B messages, there are many value-add features that can improve efficiency, lower costs, and expand the scope of collaboration with your trading partners. These features include enhancements to message payload or content and configuration capabilities. 10

IMPORT B2B TRADING PARTNERS 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 prebuilt 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. 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. CONFIGURE MESSAGE MAPS 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. 11

SUPPLY CHAIN ORCHESTRATION This release adds capability in the area of Configured Items supply creation and fulfillment. 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. UPDATE 17B 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 07 APR 2017 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. 12

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 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, standardsbased 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. 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. 13

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. 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. 14

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. 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. ORCHESTRATE YOUR SUPPLY CHAIN 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. 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. 15

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. 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 EDI ANSI ASC X12 850 EDI UN/EDIFACT ORDERS Outbound Purchase Order Change Outbound Cancel Purchase Order Inbound ASN ChangePurchaseOrder CancelPurchaseOrder ProcessShipment EDI ANSI ASC X12 860 EDI UN/EDIFACT ORDCHG EDI ANSI ASC X12 856 EDI UN/EDIFACT DESADV Inbound Invoice ProcessInvoice EDI ANSI ASC X12 810 EDI UN/EDIFACT INVOIC *Translation provided by third-party service providers. 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. 16

Functional Name OAGIS B2B Message Other B2B Standards* Inbound Order ProcessPurchaseOrder EDI ANSI ASC X12 850 EDI UN /EDIFACT ORDERS Outbound Order Acknowledgement AcknowledgePurchaseOrder EDI ANSI ASC X12 855 EDI UN /EDIFACT ORDRSP Inbound Change Order ChangePurchaseOrder EDI ANSI ASC X12 860 EDI UN /EDIFACT ORDCHG Outbound Change Order Acknowledgment Inbound Cancel Order Outbound Cancel Order Acknowledgement Outbound ASN AcknowledgeChangePurchaseOrder CancelPurchaseOrder AcknowledgeCancelPurchaseOrder ProcessShipment EDI ANSI ASC X12 865 EDI ANSI ASC X12 856 EDI UN /EDIFACT DESADV *Translation provided by third-party service providers. 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: 17

Functional Name OAGIS B2B Message Other B2B Standards Process Forecast ProcessPlanningSchedule EDI ANSI ASC X12 830 Acknowledge Commit AcknowledgePlanningSchedule EDI ANSI ASC X12 830 *Translation provided by third-party service providers. --- 18

Copyright 2017, 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 ortransmitted 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. 19