This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Product | Feature | Notes |
---|---|---|---|
19 JUN 2020 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Security and New Features
The Role section of each feature 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. For details about how to compare your configured job roles to predefined job roles and add security artifacts to your configured job roles, see the Security Console and Roles and Role Assignments chapters in the Oracle SCM Cloud: Securing SCM guide on the Oracle Help Center.
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 by stepping through the following instructions using the following privileges:
- Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
- Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)
Here’s how you opt in to new features:
- Click Navigator > My Enterprise > New Features.
- On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
- On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
- Click the icon in the Enabled column and complete the steps to enable the feature.
In some cases, you might want to opt in to a feature that's not listed in the New Features work area. Here's how to opt in:
- Click Navigator > My Enterprise > Offerings.
- On the Offerings page, select your offering, and then click Opt In Features.
- On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
- On the Edit Features page, complete the steps to enable the feature.
For more information and detailed instructions on opting in to new features for your offering, see Offering Configuration.
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.
Column Definitions:
Features Delivered Enabled
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Action is Needed BEFORE Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
---|---|---|---|---|---|---|
Feature |
Report |
UI or |
UI or |
|
||
Migrate Trading Partners from One B2B Service Provider to Another |
||||||
Create an Oracle Business Network Account from Collaboration Messaging |
||||||
Synchronize Supply Data Collected from External Organizations with Oracle Supply Planning Cloud |
||||||
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.
Migrate Trading Partners from One B2B Service Provider to Another
Migrate your trading partners when you switch to another B2B service provider, such as from the Oracle Supplier Network to the Oracle Business Network service provider.
In order to migrate your trading partners, you run a scheduled process, Migrate Trading Partners from One Service Provider to Another. This process updates all the old service provider’s references with the new service provider for all associated trading partners.
To migrate trading partners from the Oracle Supplier Network to Oracle Business Network, you need to have an Oracle Business Network account and have your Oracle Business Network service provider configured.
Migrate Trading Partners from One Service Provider to Another
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Check if the documents supported by the service provider you are migrating your trading partners to are the same as the documents supported by the service provider you are migrating from. If they aren’t, update your setup, otherwise, the migration won't be performed.
Key Resources
- Oracle Supply Chain Management Cloud: Configuring and Managing B2B Messaging guide available on the Oracle Help Center.
Role Information
To use this feature, you need these roles or privileges:
- Privilege Name and Code:
- Create Collaboration Messaging Setup Data File (CMK_OSN_B2B_MIGRATION_SCHEDULER_PRIV)
- Duty Role Names and Codes:
- B2B Messaging Administration (ORA_CMK_B2B_MESG_ADMIN_DUTY)
- Collaboration Messaging Manager (ORA_CMK_COLLAB_MESG_MANAGER_DUTY)
- Job Role Name and Code:
- B2B Administrator (ORA_CMK_B2B_ADMINISTRATOR_ABSTRACT)
Create an Oracle Business Network Account from Collaboration Messaging
Oracle Business Network is an open community for Oracle customers to exchange business documents with their trading partners.
You can create an Oracle Business Network account from Collaboration Messaging.
Use the Manage Collaboration Messaging Service Providers task to search for the predefined Oracle Business Network service provider and select Actions > Edit.
On the Edit Collaboration Messaging Service Provider page, select Create Account, which is available from the Account Setup drop-down list.
Enter the required details and click Submit. Your Oracle Business Network account will be set up on the Oracle Business Network. After you create your account, you can set up your suppliers for exchanging B2B messages using the Manage Supplier B2B Configuration task.
Create Account
Once you have an Oracle Business Network account, you can connect to that account from any of your environments. Use the Create Connection option available from the Account Setup drop-down list on the Edit Collaboration Messaging Service Provider page
Create Connection
You can then manage your connections to the Oracle Business Network using the Manage Connections option available from the Account Setup drop-down list on the Edit Collaboration Messaging Service Provider page.
Manage Connections
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
If you already have an Oracle Business Network account, you can connect to it from your current environment using the Create Connection option. Use the Manage Collaboration Messaging Service Providers task to select the Oracle Business Network service provider. The Create Connection option is available from the Account Setup drop-down list on the Edit Collaboration Messaging Service Provider page.
Key Resources
- Oracle Supply Chain Management Cloud: Configuring and Managing B2B Messaging available on the Oracle Help Center.
Role Information
To use this feature, you need these roles or privileges:
- Privilege Name and Code:
- Manage Service Provider (CMK_MANAGE_SERVICE_PROVIDER_PRIV)
- Duty Role Name and Code:
- B2B Messaging Administration (ORA_CMK_B2B_MESG_ADMIN_DUTY)
- Collaboration Messaging Setup (ORA_CMK_COLLAB_MESG_SETUP_DUTY)
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.
Synchronize Supply Data Collected from External Organizations with Oracle Supply Planning Cloud
When you have better external supply visibility, you can reduce the need to carry just-in-case inventory along with reducing the risk and cost across the supply chain. Many enterprises are enhancing their strategic relationships with suppliers to get increased access to their upstream supply status.
With this update, you can enable your external manufacturers to use Oracle Supply Chain Collaboration Cloud to digitally synchronize their end item and component on-hand balances, purchase order details, work order demands, work order supplies, and work order resources with Oracle Supply Planning Cloud. This change will enhance your end-to-end supply visibility while ensuring that you and your trading partners can now react quickly to any upstream supply chain disruptions.
You can use these existing file-based data import templates to upload data to Supply Planning.
- Supply Chain Planning Purchase Order Requisitions
- Supply Chain Planning Supply On Hand
- Supply Chain Planning Work Order Component Demands
- Supply Chain Planning Work Order Operation Resources
- Supply Chain Planning Work Order Supplies
On the Upload Supply Data page, you can initiate a supply data request as an external manufacturer user in Oracle Supplier Portal Cloud or as an enterprise user in Supply Chain Collaboration.
Upload Supply Data - File Upload
You can monitor the status of the request from the unprocessed status to the collection complete status and track any errors that occur during file loading, processing, or collections.
Upload Supply Data
Alternatively, you can create and monitor supply data requests using the Collaboration Supply Data Uploads REST resource to set up a system-to-system integration point.
Collaboration Supply Data Uploads REST Resource
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 21A
Tips And Considerations
By default, every supply data upload request will initiate the Supply Planning collections scheduled process. You may want to change this setting so you can run collections on a separate schedule. To change the setting, use the Collaboration Parameters REST resource to update the value for ORA_VCS_CM_INITIATE_SUPPLY_DATA_ESS_JOB to N. Then, collect supply data by running the Collect Pending Supply Data for Externally Managed Organizations scheduled process. The supply data requests will be grouped by source system and collection type.
Key Resources
Role Information
Access to the Synchronize Supply Data Collected from External Organizations with Supply Planning feature is available through the shipped job roles and privileges. Use the existing Supply Chain Application Administrator role to view and create supply data requests as an administrator on the Upload Supply Data page as an enterprise user in Supply Chain Collaboration. Use the existing Supplier Demand Planner role to view and create supply data requests on the Upload Supply Data page in Supplier Portal as a supplier contact in Supplier Portal.
To use this feature, you need these privileges or roles:
SUPPLY CHAIN COLLABORATION
- Privilege Name and Code:
- Manage Supply Data for Externally Managed Organizations as Enterprise User (VCS_MANAGE_SUPPLY_EXTERNAL_DATA_ENTERPRISE)
- Job Role Name and Code:
- Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_DUTY)
SUPPLIER PORTAL
- Privilege Name and Code:
- Manage Supply Data for Externally Managed Organizations as Supplier User (VCS_MANAGE_SUPPLY_EXTERNAL_DATA_SUPPLIER)
- Job Role Name and Code:
- Supplier Demand Planner (ORA_POS_SUPPLIER_DEMAND_PLANNER)
Manage Monthly Planning Cycles
The frequency of planning cycles to collaborate with your trading partners depends on the types of products you collaborate on and their associated lead times. If the lead time is longer, it is more effective to collaborate in a longer planning cycle. With this update, your suppliers can now manage planning cycles at a monthly level. In a monthly planning cycle, you can either pick the relative day of the month (example, first Monday, third Friday, or last Thursday) or a date in the month (example, 15 or 20) on which the collaboration plan is published to your suppliers.
You can also use REST API to manage these planning cycles.
On the Manage Collaboration Plans page, the enterprise user can view the new frequency, frequency duration, start day ordinal, start day, and start day attributes.
Manage Collaboration Plans
When creating or editing a weekly collaboration plan, enterprise users can define the Duration value and Start Day with a value of Monday to Sunday.
Create Collaboration Plan: Weekly Frequency
When creating or editing a monthly collaboration plan, enterprise users can define the Duration value and Start Date with a value of 1 to 28.
Create Collaboration Plan: Monthly Frequency and Start Date
And when creating or editing a monthly collaboration plan, enterprise users can define the Duration value and Start Day with a start day ordinal of First, Second, Third, Fourth, or Last and start day with a value of the name of the day (Monday to Sunday).
Create Collaboration Plan: Monthly Frequency and Start Day
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
To use this feature, you need these privileges or roles:
- Privilege Name and Code: Manage Collaboration Plans (VCS_MANAGE_COLLAB_PLANS)
- Job Role Name and Code: Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR)
Secure Data in the Supply Orchestration Work Area
You can now use predefined conditions to create your own data security policies and job roles to limit data access for each group of your users. The predefined Supply Chain Operations Manager job role doesn’t have any data access restrictions. It allows you to monitor all transactions for supply orders. Use this new feature to restrict this access.
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
- Add a global policy to the role where you need full access. The policy is Grant on Supply Order for ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB. This policy comes as enabled on the predefined role, by default.
- Create your own role for your new data security policy.
- Use a predefined condition when you create your policy or use your own condition.
- Create the user and assign the role to the user.
- If the predefined condition includes an organization attribute, then bind the user and role to the organization.
- If the predefined condition includes a business unit attribute, then bind the user and role to the business unit.
- Run the Import User and Role Application Security Data scheduled process each time you finish a set up. This process uses your changes to update security data.
Tips And Considerations
- Use a predefined condition, where possible.
- It is strongly recommended that you use a predefined condition for a security policy that restricts an organization or business unit because Oracle optimizes predefined conditions to improve performance.
- If you use more than one organization or more than one business unit, then use a single data security policy. To do this, add a separate binding record for each organization and another separate binding record for each business unit when you use the Manage Data Access for Users task in the Setup and Maintenance work area.
- Don’t use the in operator when you create your own condition. The in operator requires more time to finish a query.
- Limit the number of data security policies that you add to each role. Each new policy becomes another OR statement in the query and affects performance.
Key Resources
- Supply Chain Orchestration white papers (Doc ID 2257314.1 on Oracle Support)
Role Information
- You can copy the predefined Supply Chain Operations Manager job role.
- You must use the security manager role or the implementation consultant role when you do your setup.