TABLE OF CONTENTS DOCUMENT HISTORY

Transcription

1

2 TABLE OF CONTENTS DOCUMENT HISTORY 4 UPDATE 17D 4 Revision History 4 Overview 4 Optional Uptake of New Features (Opt In) 5 Update Tasks 5 Feature Summary 6 Supply Chain Collaboration 7 Streamline Collaboration Relationship Creation 7 Automate Actions for Past-Due Supplier Commitments 8 Manage Collaboration Relationship Candidates Using a REST API 8 View Purchase Orders and Shipments 9 Collaboration Messaging Framework 11 Search and Manage All B2B Messages From a Single Page 11 Use New B2B Protocol Options for Exchanging B2B Messages 12 Send B2B Messages Using 15 Send Invoice Rejection Notifications to Suppliers 17 UPDATE 17C 18 Revision History 18 Overview 19 Optional Uptake of New Features (Opt In) 19 Update Tasks 19 Release Feature Summary 19 Supply Chain Collaboration 21 Manage the Collaboration Process More Efficiently 21 Control Access to Trading Partner Data 21 Manage Functional Privileges by Roles 23 Edit Order Forecasts 23 Perform Order Forecast Commit Waterfall Analysis 25 Provide Planners with Visibility to Item Attributes 28 Adjust the Exception Start Date 28 View Collaboration Plans Across Multiple Tiers 29 Collaboration Messaging Framework 31 Exchange New B2B Messages with Your Trading Partners 31 Send Invoices to Customers 31 Receive Message Confirmation Messages 34 Enhance B2B Message Processing 37 Import B2B Trading Partners 37 Embed Attachments in Outbound Messages 40 Configure Message Maps 42 Supply Chain Orchestration 45 Public Service to Expose Complete Structure of Configured Item 45 UPDATE 17B 45 Revision History 45 Overview 46 Optional Uptake of New Features (Opt In) 46 2

3 Update Tasks 46 Release Feature Summary 46 Supply Chain Collaboration 47 Collaborate with Trading Partners on a Common Platform 48 Create and Manage Your Supply Collaboration Network 48 Review Status and Take Action Through Graphical Infolet-Based Views 49 Collaborate with Suppliers on Order Forecast Commitments 51 Collaborate with Contract Manufacturers on Production Status 52 Orchestrate Your Supply Chain 53 Orchestrate Supply Chain Business Processes 53 Interoperate with Standards-Based B2B Messaging 53 Implement B2B Messaging with Multiple Service Providers 53 Integrate Procure-to-Pay B2B Messaging 54 Integrate Order-to-Cash B2B Messaging 54 Integrate Planning Collaboration B2B Messaging 55 APPENDIX A: FUNCTION SECURITY PRIVILEGES AND AGGREGATE PRIVILEGES 56 3

4 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 02 FEB 2018 Update 17D Revised update 17D. 02 FEB 2018 Update 17C Revised update 17C. 02 FEB 2018 Update 17B Revised 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 02 FEB 2018 View Purchase Orders and Shipments Updated document. Revised screenshots. 20 OCT 2017 Created initial document. OVERVIEW This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you. SECURITY AND NEW FEATURES The Role section of each feature 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. 4

5 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. 5. Click Done. UPDATE TASKS 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. 5

6 FEATURE SUMMARY 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 Supply Chain Collaboration Streamline Collaboration Relationship Creation Automate Actions for Past-Due Supplier Commitments Manage Collaboration Relationship Candidates Using a REST API View Purchase Orders and Shipments Collaboration Messaging Framework Search and Manage All B2B Messages From a Single Page Use New B2B Protocol Options for Exchanging B2B Messages Send B2B Messages Using Send Invoice Rejection Notifications to Suppliers 6

7 SUPPLY CHAIN COLLABORATION 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 7

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

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

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

11 Publish Order Forecast Scheduled Process: Publish Order Details 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. 11

12 Manage Collaboration Messaging History 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 and AS2, in addition to SOAP web services. This feature expands the number of protocols available for exchanging B2B messages. You can now use HTTP and AS2 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 leverages Oracle SOA Cloud Service 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. (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. 12

13 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 Cloud Service 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. 13

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

15 Oracle B2B Trading Partner Agreements KEY RESOURCES Oracle Fusion Middleware User's Guide for Oracle B2B, Release , available on the Oracle Help Center. SEND B2B MESSAGES USING Send the same OAGIS XML B2B message used in system-to-system automation as an 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 . By providing an option for 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 attachments. In addition to the XML attachment, the subject and body of the can be configured to meet your unique requirements. (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 as Delivery Method Type. If a B2B Service Provider is not used, specify a new delivery method with as Delivery Method Type for the trading partner. Select Attach XML Message to send the XML message as the attachment. If Attach XML Message is not selected, the information sent is what you set up and configure for the body. 15

16 Collaboration Messaging Service Provider: Delivery Methods Collaboration Messaging Service Provider: Outbound Messages TIPS AND CONSIDERATIONS ID USED TO SEND B2B MESSAGES The IDs may exist or are derived from a number of sources. The sources include: 1. Oracle Cloud product: Products such as Payables, Receivables, Purchasing, or Order Management may already define an address for customers or suppliers. 2. 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 ID where the message should be sent. 3. Delivery method ID: When creating the delivery method in Oracle Collaboration Messaging Framework, you can define an ID. Collaboration Messaging Framework processes these sources in sequence to determine which ID to use to send the B2B message. When Collaboration Messaging Framework finds a valid ID, it will use that ID without proceeding to other options. 16

17 USER-DEFINED SUBJECT AND BODY To define a user-defined subject or body, you can use the Configure Message Maps feature. You can map attributes from the B2B message to the body using the new attributes in the Oracle predefined XSLT file. The information is formatted as a table in the body, where the column titles are userdefined. 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 s 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. (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. 17

18 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 address is taken from the original invoice message. VENDOR ADDRESS If the original invoice message does not contain a vendor address, rejection messages are not initiated. 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 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. 18

19 OVERVIEW This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you. SECURITY & 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. UPDATE TASKS 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. 19

20 RELEASE FEATURE SUMMARY Action Required to Enable Feature Feature Automatically Available End User Action Required Administrator Action Required Oracle Service Request Required Supply Chain Collaboration Manage the Collaboration Process More Efficiently Control Access to Trading Partner Data Manage Functional Privileges by Roles Edit Order Forecasts Perform Order Forecast Commit Waterfall Analysis Provide Planners with Visibility to Item Attributes Adjust the Exception Start Date View Collaboration Plans Across Multiple Tiers Collaboration Messaging Framework Exchange New B2B Messages with Your Trading Partners Send Invoices to Customers Receive Message Confirmation Messages Enhance B2B Message Processing Import B2B Trading Partners Embed Attachments in Outbound Messages Configure Message Maps Supply Chain Orchestration Public Service to Expose Complete Structure of Configured Item 20

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

22 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 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: 1. In the Setup and Maintenance work area, select the Manufacturing and Supply Chain Materials Management offering. 2. 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. 3. On the Manage Supply Chain Collaboration Settings page, set Enable data access security to Yes. 4. 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. 5. 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. 22

23 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. No steps are required to enable this feature. EDIT ORDER FORECASTS 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. 23

24 Edit Current Forecast - Inline Editing Forecasts are published to suppliers using the new publish action available from the actions menu. 24

25 Publish Action 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. 25

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

27 The following screenshot shows the Order Forecast Waterfall by Relationship report. Waterfall by Relationship Report The following screenshot shows the Waterfall chart. Waterfall Chart 27

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

29 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, Manage Order Forecasts and Commits Search Criteria 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 29

30 The following screenshot shows two order forecasts participating in a multi-tiered relationship: 1. The order forecast sent to supplier B for the AI-1TB item that is used within the AI-1TB-Assembly item. 2. 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 No steps are required to enable this feature. TIPS AND CONSIDERATIONS To model a multi-tiered relationship between a contract manufacturer and a supplier: 1. Setup contract manufacturers (Ship-to Supplier Sites) as organizations associated with a supplier site in Oracle Supply Chain Planning Supply Network Model. 2. Define a relationship in Supply Chain Collaboration by defining the ship-to as the contract manufacturer organization. 3. 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. 30

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

32 (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. 32

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

34 To setup a customer account collaboration to generate and send electronic invoices: 1. Select the Customer Account to receive electronic invoices. Manage Customer Account Collaboration Configuration 2. Perform the steps to setup a Collaboration Messaging Framework trading partner. 3. 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. 34

35 PROCESSING The confirmation messages are processed as follows: 1. 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. 2. 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. 3. 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. (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. 35

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

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

38 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. 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 (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. 38