Update 20A

Revision History

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

Date	Feature	Notes
20 DEC 2019		Created initial document.

Overview

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

Security and New Features

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

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

Give Us Feedback

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

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users in a couple of ways:

Access the Opt In page from the New Features Work Area

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

or...  Access the Opt In page from the Setup and Maintenance Work Area

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

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

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.

Enable Trading Partners to Override Their Service Provider's Message Definition

You can override a service provider's message definition for your trading partners. This helps trading partners exchange different external message types or use their own message transformations.

For trading partners that use a predefined service provider, you can set up override message definitions that use the same messaging standard that the service provider uses, for example, if you want to use a different message transformation.

For trading partners associated with a user-defined service provider, you can set up any override message definitions for your trading partner. For example, you can set up cXML message definitions for a trading partner whose user-defined service provider is set up with OAGIS 10.1 message definitions.

Override message definitions must always be for a document set up for the service provider.

Steps to Enable

1. In the Collaboration Messaging Framework work area use the Manage Collaborations Message Definitions task to create a message definition for your trading partner that wants to exchange a message either with a different messaging standard, for example, cXML instead of OAG 7.2.1 or with a different message transformation than that of the user-defined service provider they are associated with.
2. Click Manage B2B Trading Partners.
3. Search for and select the trading partner that you want to use the new message definition for. Then click Actions > Edit.
4. On the Edit Trading Partner page, you will notice that the Delivery Methods tab is not displayed and the Outbound Collaboration Messages and Inbound Collaboration Messages tabs are blank. The Override service provider’s message definition check box is selected.

This indicates the trading partner is using all of the service provider’s messages, which are displayed on Edit Collaboration Messaging Service Provider’s page that you can reach using the Manage Collaboration Messaging Service Providers task.

5. On the Edit Trading Partner page, select the message definition that you want to use instead of the message definition of the service provider.

You can select different message definitions for any of the documents of your service provider. Message definitions selected on the Edit Trading Partner page override those of the service provider for the same document. In this example, a new message definition for Process PO is used for the trading partner. The rest of the messages exchanged for that trading partner will use the message definitions of the service provider's.

The delivery methods that are available for selection for the trading partner will be those of the associated service provider.

Tips And Considerations

You can add the Document Type column to the Outbound Collaboration Messages or Inbound Collaboration Messages tabs for additional information about the message definition. Click View and select the column you want. 

Key Resources

• Configuring and Managing B2B Messaging for Oracle Applications Cloud guide available on the Oracle Help Center

Role Information

To use this feature, you need these privileges or roles:

• Privilege Names and Codes:
  • Create External Partner (CMK_CREATE_EXTERNAL_PARTNER_PRIV)
  • Manage Associated External Partner (CMK_MANAGE_ASSOCIATED_EXTERNAL_PARTNER_PRIV)
  • Manage B2B Trading Partners (CMK_B2B_TRADING_PARTNERS_PRIV)

• Duty Role Names and Codes:
  • B2B Messaging Administration (ORA_CMK_B2B_MESG_ADMIN_DUTY)
  • Collaboration Messaging Setup (ORA_CMK_COLLAB_MESG_SETUP_DUTY)

• Job Role Name and Code:
  • B2B Administrator (ORA_CMK_B2B_ADMINISTRATOR_ABSTRACT)

Automatically Reprocess Outbound Error Messages

Enable automatic reprocessing of outbound collaboration messages that aren't processed successfully due to temporary resource issues.

Collaboration messages that don't get processed successfully due to errors such as resource issues are currently left unprocessed until you manually review and submit them for reprocessing. You can now automatically reprocess these outbound messages. You define the window of time during which the errors occurred to include in the automatic reprocessing and determine how often the application must attempt to reprocess the messages.

Steps to Enable

1. In the Setup and Maintenance work area, use the Manage Collaboration Messaging Configuration task in the Manufacturing and Supply Chain Materials Management offering.
2. In the General Setup tab, Automatic Message Reprocessing section, select the Enable Reprocessing check box.
3. Enter a value in the Reprocessing Window in hours to specify the past window of time to include the messages that encountered errors. The default value is 48 hours.
4. Enter a value in the Reprocessing Interval in minutes to define the interval at which the messages will be reprocessed. The default value is 120 minutes.
5. Click Save and Close.

Tips And Considerations

Automatic reprocessing of errors applies to outbound messages.

You can reprocess these types of outbound error messages automatically:

B2B Error: Oracle B2B was unable to deliver the message.

Application Service Invocation Failure: Collaboration Messaging Framework was unable to call the application service used to retrieve the outbound message payload.

External Service Invocation Failure: Collaboration Messaging Framework was unable to call the trading partner or service provider’s service.

Internal Service Issue: Collaboration Messaging Framework was unable to call an internal processing service.

Key Resources

• Configuring and Managing B2B Messaging for Oracle Applications Cloud guide available on the Oracle Help Center

Role Information

To use this feature, you need these privileges or roles:

• Privilege Names and Codes
  • Manage Collaboration Messaging Configuration (CMK_MANAGE_COLLAB_MESG_CONFIG_PRIV)

• Duty Role Names and Codes
  • B2B Messaging Administration (ORA_CMK_B2B_MESG_ADMIN_DUTY)
  • Collaboration Messaging Setup (ORA_CMK_COLLAB_MESG_SETUP_DUTY)

• Job Role Name and Code:
  • B2B Administrator  (ORA_CMK_B2B_ADMINISTRATOR_ABSTRACT)

Export B2B Trading Partner Information

Export trading partner information to a spreadsheet for easier analysis during setup.

From the Manage B2B Trading Partners page, you can use Actions > Export to Excel to download your trading partner information into a spreadsheet. You can then use this file to view or analyze your data.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Configuring and Managing B2B Messaging for Oracle Applications Cloud guide available on the Oracle Help Center

Role Information

To use this feature, you need this job role:

• Job Role Name and Code:
  • B2B Administrator (ORA_CMK_B2B_ADMINISTRATOR_ABSTRACT)

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.

View and Commit to Order Forecasts Using a Purchasing UOM

The unit of measure (UOM) used in planning applications may differ from the UOM used to purchase goods. In this update, you can set the UOM on a collaboration relationship to be used for all collaboration quantities. When you set the UOM on the collaboration relationship, all quantities including order forecasts, commits, open purchase orders, in-transit shipments, shipments in receiving, and purchase requisitions are converted and displayed in the specified collaboration UOM. The new UOM Definition Source attribute specifies the source where you set the UOM for a particular relationship.

Here are the options for UOM Definition Source:

• Published order forecast: Use this option to convert and display collaboration quantities in the UOM of the order forecast published to Oracle Supply Chain Collaboration Cloud. This is the default value for UOM Definition Source and accepts the UOM published by Oracle Supply Chain Planning Cloud. Alternatively, if you are importing order forecasts using a REST service or file-based data import, you can optionally provide a UOM. If a UOM is not provided, Supply Chain Collaboration will use the item's primary UOM set on the item record.

• Approved supplier list: Use this option to convert and display collaboration quantities in the purchasing UOM defined on the approved supplier list matching the item and supplier.

• Primary: Use this option to display collaboration quantities in the item's primary UOM. The item's primary UOM is defined on the item record.

• Other: Use this option to convert and display collaboration quantities in the user-defined UOM set on the collaboration relationship.

For collaboration plans using items and organizations sourced from an external planning source system, UOM Definition Source depends on Supply Planning to resolve the available UOMs, UOM conversions, item's primary UOM, and purchasing UOM.

For example, in this image, you are viewing a supply plan in Supply Chain Planning.  The planning UOM for item TS101150 is Each. For January 4, you have a purchase order quantity of 25, a shipment in receiving quantity of 20, and planned order quantity of 25.

Supply Chain Planning - Supply Plan

In this image, you are viewing the published order forecast in Supply Chain Collaboration. When the supply plan is published to include purchase orders in the order forecast, the published order forecast quantity is 50 Each. When the UOM Definition Source is set to Approved supplier list, the collaboration UOM for item TS101150 is LB. The UOM conversion exists as 1 Each = 50 LB, as a result, your quantities for January 4 are converted to LB.

Supply Chain Collaboration - Edit Order Forecast Details

Watch a Demo

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management  No Longer Optional From: Update 20C

After enabling this feature, you may optionally update the UOM Definition Source attribute for your relationships on the Manage Supply Collaboration Network page.

For example, in this image, you see the new UOM Definition Source attribute on the Edit Relationship page with Approved supplier list selected.

Manage Supply Collaboration Network - Edit Relationship

In this image, you see UOM Definition Source set to Other and UOM set to LB.

Manage Supply Collaboration Network - Edit Relationships

Key Resources

• Watch View and Commit to Order Forecasts Using a Purchasing UOM Readiness Training

Role Information

Access to View and Commit to Order Forecasts Using a Purchasing UOM is available through the shipped job roles and privileges. Use the existing Supply Chain Collaboration Planner role to collaborate on supply plans with a collaboration UOM on the Manage Order Forecasts and Commits page as an enterprise user in Supply Chain Collaboration. Use the existing Supplier Demand Planner role to collaborate on supply plans with a collaboration UOM on the Manage Order Forecasts and Commits page as a supplier contact in Oracle Supplier Portal Cloud.

To use this feature, you need these privileges or roles:

SUPPLY CHAIN COLLABORATION

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

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

SUPPLIER PORTAL

• Privilege Name and Code:
  • Commit to Order Forecasts as Supplier (VCS_COMMIT_ORDER_FORECAST_SUPPLIER)

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

Supply Chain Orchestration

Create Reports for Supply Requests and Supply Orders

Here are some of the benefits you can realize with this enhancement.

• Use reports and analytics to manage hundreds of sales orders and their corresponding supply orders.
• Identify critical sales orders that have issues with supply requests and supply orders.
• Efficiently manage supply orders that need your attention so they can reach completion.
• Allow your critical back-to-back sales orders to create supply orders.
• Reduce the time and effort needed to do a query in the Supply Orchestration work area.

Get details in each subject area of your report.

• Number of successful records for each request source.
• Number of error records for each request source.
• Number of errors for open sales orders. Include the requested delivery date for each order according to day, such as end of month, end of quarter, and so on.
• Number of errors for shipped or closed sales orders.

REPORT ON A WIDE RANGE OF DATA 

Here are just a few examples of the kind of data you report on.

• Count of supply requests in status Error sorted by year.
• Count of supply requests in status Success sorted by year.
• Errors for columns across subject areas.
• Supply lines that are in error for open sales orders.
• Closed supply orders for configured items sorted by year.
• All supply requests that are in status Success sorted by day.
• Closed and fulfilled supply orders with sales orders that are in Processing status.
• Transfer orders that are in error sorted by item.

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Assume you need a report that displays supply requests that are in an error status. You want the source, status, date, batch number, and operation.

Try it.

1. In the Navigator, click Reports and Analytics.
2. On the Reports and Analytics page, click Browse Catalogs. Oracle Transactional Business Intelligence opens in a new tab on your browser.
3. On the Catalog page, click New > Analysis.
4. In the Select Subject Area dialog, scroll down to locate the subject areas.

• Supply Chain Orchestration - Supply Order Real Time
• Supply Chain Orchestration - Supply Request Real Time

5. Click Supply Chain Orchestration - Supply Request Real Time.
6. Add columns to your report.

• On the Untitled page, in the Subject Areas area, expand Supply Chain Orchestration - Supply Request Real Time, expand Supply Request Details, then drag Request Source from the Subject Areas area and drop it onto the Selected Columns area.

• Repeat for other subject areas. Drag and drop so the Selected Columns area resembles this sequence.

  Request Source

  Request Status

  Request Creation Date

  Request Batch Number

  Request Supply Operation

• Click Save Analysis.

7. Modify a column. Assume you want the month, day, and year but not the time of day.

• Click the gear next to Request Creation Date, then click Column Properties.
• In the Column Properties dialog, click Date Format, then add a check mark to Override Default Date Format.
• Delete all the content in the Custom Date Format window except for M/d/yy, click OK, then click Save Analysis.

8. Add a filter.

• In the Save As dialog, name your report All Requests in Error Status, then click OK.
• In the Selected Columns area, click the gear next to Request Status, then click Filter.
• In the Filter dialog, set the value to Request Status is equal to Error.
• Make sure the Filter by Request Status Code contains a check mark, click OK, then click Save Analysis.

9. Click Results, wait for the result to finish building, then examine the results.

Tips And Considerations

GET A FULL PICTURE OF THE SUPPLY CHAIN

Here's an example of a run time report that follows a sales order from start to finish.

GET A FULL PICTURE OF THE SUPPLY CHAIN

Here's what this examples does.

• Get sales order data, such as the sales order number and item, from Order Management.
• Get supply order data, such as the supply order number and status, from Supply Orchestration.
• Get purchase order data, such as the purchase order number, from Purchasing.
• Get work order data, such as the work order number and status, from Inventory Management.

This example also illustrates how you can filter data to avoid a lot of unwanted empty output. Assume you want a full picture of the supply chain but are only interested in flows that include the sales order, supply order, purchase order, and work order. You don't want to display a lot of rows that don't have any purchase orders, work orders, and so on. You can filter the data. For example, add the Work Order Number subject area to the Selected Columns area, click the gear next to Work Order Number in the Selected Columns area, then click Filter. In the New Filter dialog, set Operator to Is Not Null. Repeat for each type of sales order.

ORGANIZE ACCORDING TO DATE 

Need to scan the status of supply orders according to source, organized by date, and drill down on date? Use the time subject areas to arrange your report according to time, such as by day, week, month, or year, including start dates and end dates.

• Time  - Supply Request Creation Date
• Time  - Supply Request Need by Date

Here's an example that organizes supply orders according to date.

FILTER AND MANIPULATE COLUMN DATA

Filter and manipulate column data to focus your report.

Details:

• Use the Sort action to sort data.

• Use the Filter action to filter data. Choose from a variety of operators, then choose a value. For the value, the dialog makes life simple. It filters the values you can choose according to subject area. For example, if the subject area is Supply Order Status, then choose one or more statuses.

• Use the Edit Formula action to create your own formula that filters results. Include functions, columns, variables, equations, and so on in your formula.

• Use column properties to change appearance, such as font, alignment, borders, headings, suppress repeating values, and so on.

• Use Sort Ascending or Sort Descending to sort report output according to column.

• The result might take minutes to build, depending on you set up the report and the volume of data you're reporting. If it takes too long, add filters or remove columns.

• Consider how each subject area you add to your report affects report output. For example, if your report includes Request Supply Operation, and Item Number, then the output might include more than one item number for each operation because the relationship between operation and item number is one to many. Other relationships between columns might result in a lot of rows in one column for only one row in another column. The good news is that you filter and sort to meet your specific requirements.

• Consider adding graphics to enhance the impact of your reports.

Key Resources

• Oracle SCM Cloud: Creating and Administering Analytics and Reports for SCM on Oracle Help Center.

• Guidelines for Creating Cross-Subject Area Analyses in Oracle Transactional BI (Doc ID 1567672.1) on My Oracle Support.

Role Information

To use this feature, the following role is required:

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

Select and Assign Item Catalogs to Configured Items

You use an item catalog to categorize each configured item into a meaningful group to help manage the item and to summarize data when you create a report. In previous updates, configure-to-order copied to each configured item only to the specific set of item catalogs necessary for downstream processing.

You can now add an item catalog to a supply orchestration lookup, then rely on the lookup for inclusion of the catalog in the copy action.

Steps to Enable

1. In the Setup and Maintenance work area, go to the task. 

• Offering: Manufacturing and Supply Chain Materials Management
• Functional Area: Supply Chain Orchestration
• Task: Manage Supply Orchestration Lookups

2. On the Manage Supply Orchestration Lookups page, search for lookup type ORA_CTO_CATALOG_COPY_REQUEST.

• In the Lookup Codes area, click Actions > New, then set values.

Attribute	Value
Lookup Code	Enter any value.
Enabled	Contains a check mark.
Start Date and End Date	Optional. Specify dates when the code is available.

For example.

Tips And Considerations

• Adding too many item catalogs to a configured item might affect performance at run time.

Key Resources

Use these resources on Oracle Help Center:

• Set Up Configure-to-Order chapter in Oracle SCM Cloud: Implementing Order Management 
• Define Catalogs chapter and Define Lookups section in Oracle SCM Cloud: Implementing Common Features for SCM 

Role Information

To use this feature, the following role is required:

• Job Role Name and Code: 
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Close Supply Orders for Internal Material Transfers

If an unexpected system downtime or unexpected technical error occurs, then Supply Chain Orchestration might not update the status for a supply order, and the supply order might be left in an open status even though fulfillment is done for the supply order. You can use the Close Supply Orders scheduled process to close these supply orders in back-to-back flows. In this update, you can now also close orders in transfer flows.

Assume you create and submit transfer order 86954 in the Inventory work area, and Supply Chain Orchestration creates supply order 300100184370687 to fulfill 86954. A week later you experience a power outage. You restore power then notice the status for all fulfillment lines in 86954 is Closed, but the status for 300100184370687 remains Open.

You notice a similar situation for 20 other sales orders. Use the Close Supply Orders scheduled process to fix the problem.

As an option, you can run the scheduled process in Report Only mode to create a report that lists the supply orders that are open and don't have any pending fulfillment actions, but not close them.  

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Assume you need a report of all open supply orders for requests you've received from Order Management, but the orders don't have any pending fulfillment actions.

Try it.

1. In the Navigator, click Scheduled Processes.
2. On the Overview page, click Schedule New Process.
3. In the Schedule New Process dialog, search for Close Supply Orders, set values, then click Submit.

   Attribute	Value
   Report Only	Add a check mark to create a report but don't close any orders.
   Supply Request Source	Required. Choose the source that sent the request to create supply to Supply Chain Orchestration. For example, choose. Oracle Fusion Supply Chain Orchestration to search only for requests that you create in the Supply Orchestration work area. Oracle Fusion Order Management to search only for requests that Order Management sent to Supply Chain Orchestration. For this example, choose Oracle Fusion Order Management.
   Supply Request Reference	Optional. Leave empty, or choose a value to search only for supply orders associated with a single sales order, purchase order, or work order. If you set Supply Request Source to. Order Management, then set Supply Request Reference to the sales order. Procurement, then set Supply Request Reference to the purchase order. Inventory Management, then set Supply Request Reference to the work order.
   Supply Request Batch Number	Optional. Leave empty, or choose a batch to narrow the search. This parameter identifies the import batch number on the interface table. If you specify it, then the scheduled process will process all supply orders in the import batch. For details about import, see File-Based Data Import for Oracle Supply Chain Management Cloud.
   Supply Type	Optional. Choose a flow to narrow the search. For example, choose Transfer to search only for supply orders that involve an internal material transfer.
   Item	Optional. Choose an item to search only for supply orders that contain the item. For example, choose the AS54888 Standard Deskktop to search only for supply orders that fulfill the AS54888.
   From Creation Date To Creation Date	Conditional. Enter values to narrow the search according to the date when Supply Orchestration created each supply order. Both dates must occur on or before the current date. The duration that the dates specify must not exceed 90 days. For example, you can specify January 1, 2019 to March 31, 2019, which includes a duration of 90 days, but you can't specify January 1, 2019 to April 1, 2019 because that duration includes 91 days. If you set Supply Request Reference or Supply Request Batch Number, then you don't need to set the dates.

4. On the Overview page, in the search results, click Refresh until the status for your process is Succeeded.
5. In the Log and Output area, next to Attachment, click the link inside the parentheses, such as (1 more. . .), then click the .txt file, such as 103648.txt.
6. Examine the report output.

Here's an example of your report.

The scheduled process processes supply orders differently depending on the flow.

• Internal material transfer. Process supply orders that are open only when the transfer order or purchase order for the transfer is closed or canceled. 

• Back-to-back. Process supply orders that are open only when the sales order line is shipped or canceled.

Key Resources

• Supply Chain Orchestration chapter in the Implementing Manufacturing and Supply Chain Materials Management book, available on Oracle Help Center.

Role Information

Here's the role you need to use this feature.

Job Attribute	Value
Job Role	Supply Chain Operations Manager
Code	ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB

View Supply Orders According to Requested Delivery Date

The number of supply orders that you manage can become large over time.  You can now filter them to improve performance on the Overview page of the Supply Orchestration work area and to help you find what you're looking for. Here are the predefined values you can set in the View by Requested Delivery Date attribute.

• All 
• Last 7 days
• Last 15 days
• Last 30 days
• Next 7 days
• Next 15 days
• Next 30 days

Overview Page

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management  No Longer Optional From: Update 20C

Tips And Considerations

USE A PREDEFINED FILTER 

Assume you must filter orders on the Overview page so it only displays orders where the Requested Delivery Date occurs during the last seven days, starting with today. For, example, if today is January 10, 2019, then display all orders that contain a Requested Delivery Date that occurs on January 4 through January 10.

1. Enable the View Supply Orders According to Requested Delivery Date opt-in feature.
2. Go to the Supply Orchestration work area.
3. On the Overview page, set the View by Requested Delivery Date attribute to Last 7 Days, then click Refresh.
4. Examine the results.

CREATE YOUR OWN FILTER 

You can add your own filters or modify filters that already exist for the View by Requested Delivery Date attribute. You use the Setup and Maintenance work area to add the filter to a lookup.

Assume you need to filter supply orders on the Overview page according to the last 45 days.

1. In the Setup and Maintenance work area, go to the task.

• Offering: Manufacturing and Supply Chain Materials Management
• Functional Area: Manage Supply Orchestration Lookups
• Task: Manage Supply Orchestration Lookups

2. On the Manage Supply Orchestration Lookups page, open the ORA_DOS_RDD_INTRVL lookup type for editing.
3. Click Actions > New, then set values.

Attribute	Value
Lookup Code	+ or - number where + (plus sign) indicates days into the future. This value is optional. You can leave it unsigned to indicate days into the future. - (negative sign) indicates days into the past. number is the number of days. For this example, enter -45.
Display Sequence	5
Enabled	Contains a check mark.
Start Date	Today's date.
End Date	Leave it empty.
Meaning	Last 45 Days
Description	Display supply orders where the requested delivery date occurs within the last 45 days.

4. Test. 

• Go to the Supply Orchestration work area.
• On the Overview page, verify that you can set View by Requested Delivery Date to Last 45 Days, and that the page correctly applies the filter.

TROUBLESHOOT 

Trouble	Shoot
The list of values in View by Requested Delivery Date doesn't display Last 45 Days.	Go to the Manage Supply Orchestration Lookups page and make sure you set a start date, and that the start date occurs on or before today. If you set an end date, then make sure it hasn't already occurred.
The Overview page doesn't display the View by Requested Delivery Date attribute.	Make sure you enable the View Supply Orders According to Requested Delivery Date opt-in feature.

Key Resources

See these books on Oracle Help Center under Oracle Supply Chain Management Cloud:

• Implementing Manufacturing and Supply Chain Materials Management
• Using Supply Chain Orchestration

Role Information

To use this feature, the following role is required:

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

Orchestrate and View Supply Requests from Replenishment Planning

Oracle Replenishment Planning Cloud maintains optimum inventory levels to meet customer service targets at the lowest inventory cost. Replenishment Planning releases supply recommendations, such as movement requests, transfer requests, and buy requests, with subinventory details to Oracle Supply Chain Orchestration Cloud. Supply Chain Orchestration receives, orchestrates, and tracks the supply creation process for movement requests, transfer orders, and purchase orders.

You can use the Supply Chain Orchestration work area to view statuses and updates for supply requests from Replenishment Planning in real time. You can limit the search to view only supply requests from Replenishment Planning, or you can include supply requests from other demand sources and get a complete supply picture.  You can search for and identify movement requests too.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Supply Chain Orchestration automatically groups large volumes of replenishment requests into smaller, more manageable batches to improve performance and to make sure the results are reliable.

The Supply Chain Orchestration Interface scheduled process processes 10,000 records in each batch, by default. You can reduce the value in the Batch Size parameter in the Process Details dialog to improve performance.

Key Resources

• Oracle Replenishment Planning Cloud readiness training for update 20A.
• Oracle SCM Cloud: Implementing Manufacturing and Supply Chain Materials Management, available on the Oracle Help Center.

Role Information

To use this feature, the following role is required:

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

Orchestrate and View Supply Requests That Include Project Data

• Receive and orchestrate transfer requests across organizations that include project data from Oracle Self Service Procurement Cloud

• Receive and orchestrate transfer requests within an organization or across organizations that include project data from the Supply Requests REST API.

• Receive and orchestrate purchase requests for outside processing that includes project data from Oracle Manufacturing Cloud.

You can use the project number and task number to search for supply requests that include project data on various pages in the Supply Orchestration work area, such as the Manage Supply Request Exceptions page.

You can view the full set of project data on each supply line, such as Project Number, Task Number, Expenditure Item Date,  Expenditure Type, Expenditure Organization, Contract Number, and Funding Source.

View them on the Supply Order Details page and the Manage Supply Lines page. For example.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• You can receive transfer requests of both inventory and expense destination type that include project data from Self Service Procurement and the Supply Request REST API.

• You can capture project data only for transfer requests when you use the Supply Request REST API.

• You can capture only the project number and task number, or you can capture the full set of project data when you use the Supply Request REST API. If you capture only the project number and task number, or only part of the full set of project data, then Supply Chain Orchestration keeps the values you capture and gets default values for the project attributes you don't capture.

• If validation fails for the project cost transaction, or if a setup or technical error occurs, then you can manually correct the error and use the Supply Orchestration work area to resubmit the supply request. For example, if the expenditure type isn't active during the expenditure item date, then use the Manage Expenditure Types page to validate the expenditure type date. Resubmit the supply request so orchestration can successfully process the transfer request for the project.

Key Resources

See these books on Oracle Help Center under Oracle Supply Chain Management Cloud.

• Implementing Manufacturing and Supply Chain Materials Management
• Using Supply Chain Orchestration

See these presentations.

• Transfer Project Specific Inventory 20A readiness training
• Execute Project Specific Manufacturing 20A readiness training

Role Information

Here's the role you need to use this feature.

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