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 |
|---|---|---|---|
| 07 JAN 2022 | Product Recall Management | Product Recall Management | Updated document. Revised feature description. |
| 05 MAR 2021 | Product Hub | Manage Item Import Data Using Transaction Type in Import Maps or Supplier Products REST Service | Updated document. Revised feature description. |
| 11 FEB 2021 | Product Hub | Copy and Paste Items Using Clipboards | Updated document. Revised feature description. |
| 05 FEB 2021 | Quality Management | Assign Organizations to Quality Actions | Updated document. Revised role information. |
| 05 OCT 2020 | Product Recall Management | Product Recall Management | Updated document. Replaced screenshots. |
| 29 SEP 2020 | Product Hub | Manage Item Relationships Using a REST Service | Updated document. Revised feature description. |
| 29 SEP 2020 | Innovation Management | Manage Proposal Teams Using REST Services, Manage Product Concepts Using REST Services | Updated document. Revised feature descriptions. |
| 29 SEP 2020 | Quality Management | Use REST Services to Manage Approvers for Future Approval Statuses | Updated document. Revised feature description. |
| 18 SEP 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.
Pre-Update and Post-Update Tasks
Depending on the features you're using in your Cloud applications, you may be required to perform certain steps immediately before or after your quarterly update. For details of these pre-update and post-update steps and the product areas that are affected, refer to Oracle SCM Cloud: Performing Your Quarterly Update (doc ID 2337485.1) on My Oracle Support.
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.
Link to SCM Application Pages Using Deep Links
In this update, Oracle Supply Chain Management Cloud delivers new deep links that provide easy navigation directly to application pages without using the menu structure. You can use these links in a variety of ways, such as in business intelligence reports and third-party application pages.
New deep links introduced in this update are listed by product:
- Manufacturing
- Work Order (WIE_WORK_ORDER,EDIT)
- Exception (WIE_PRODUCTION_EXCEPTION,EDIT)
- Work Definition (WIS_WORK_DEFINITION,EDIT)
- Edit Resource (WIS_RESOURCE,EDIT)
- Supply Chain Collaboration
- Manage Supply Collaboration Network (COLLABORATION_RELATIONSHIP,EDIT)
- Supply Chain Financial Orchestration
- Monitor Financial Orchestration Execution (FOS_MONITOR_UI,NONE)
- Supply Chain Orchestration
- Supply Order Details (SUPPLY_ORDER,NONE)
- Supply Order Details (SUPPLY_ORDER,VIEW)
- Configurator
- Workspace (CONFIGURATOR,WORKSPACE)
- Overview (CONFIGURATOR,OVERVIEW)
- Overview (CONFIGURATOR,NONE)
- Maintenance
- Customer Asset (ORA_CSE_ASSET,EDIT)
- Edit Work Order (ORA_MNT_WORK_ORDER,EDIT)
- Manage Maintenance Work Orders (ORA_MNT_WORK_ORDER,NONE)
- Work Order (ORA_MNT_WORK_ORDER,VIEW)
- Order Management
- Manage Orders (SALES_ORDER,VIEW)
- Manage Orders (SALES_ORDER,FULFILLMENT_VIEW)
- Manage Orders (SALES_ORDER,NONE)
- Manage Orders (SALES_ORDER,CREATE)
- Product Hub
- Item (PIM_ITEM,EDIT)
- Items (ITEMS,EDIT)
- Manage Items (PIM_ITEM,NONE)
- Collaboration Messaging Framework
- Collaboration Message: {MESSAGEGUID} (B2B_MESSAGE_TRANSACTIONS,VIEW)
- Channel Revenue Management
- Manage Supplier Claims (SUPPLIER_CLAIM,NONE)
- Supplier Claim (SUPPLIER_CLAIM,EDIT)
- Quality Inspection Management
- View Inspection Results (INSPECTION_EVENTS,VIEW)
- View Inspection Plan (INSPECTION_PLANS,VIEW)
- Supply Chain Planning
- Manage Sourcing Rules (SOURCING_RULES,NONE)
- Edit Sourcing Rule (SOURCING_RULES,EDIT)
- Manage Assignment Sets (SOURCING_ASSIGNMENTS,NONE)
- Edit Assignment Set (SOURCING_ASSIGNMENTS,EDIT)
- Manage ATP Rules (ATP_RULES,NONE)
- Edit ATP Rule (ATP_RULES,EDIT)
- Manage Planning Allocation Rules (ATP_ALLOCATION_RULES,NONE)
- Edit Allocation Rule (ATP_ALLOCATION_RULES,EDIT)
- Receiving
- Receive Items (SSP_RCV_PO,NONE)
- Fiscal Document Capture
- Fiscal Document (INBOUND_FISCAL_DOCUMENT,VIEW)
- Cost Management
- Review Work Order Costs (WORK_ORDER_COST, VIEW)
- Review maintenance work order costs(MNT_WORK_ORDER_COST,VIEW)
- Review Item Costs (ITEM_COSTS,VIEW)
- Review Cost Accounting Distributions (COST_ACCOUNTING_DISTRIBUTIONS, VIEW)
- Receipt Accounting Distributions (RECEIPT_ACCTG_DISTRIBUTIONS,VIEW)
When you add deep links to reports or third-party application pages, users can simply click those links to go directly to the application pages they need to use, without any additional clicks or navigation. When a user clicks a deep link, that user's security assignment is honored; that is, users can access application pages only if they're assigned a job role that allows them access.
Steps to Enable
You can find all of the available deep links in the Deep Links work area. Some deep links, such as those assigned the NONE action, are ready to use as is. Other deep links, such as those assigned the EDIT action, require you to edit the link details before you can add the deep link to a report or third-party application page. Refer to the documentation listed in the Key Resources section for details and instructions.
Key Resources
For details about how to work with deep links, refer to these books on the Oracle Help Center:
- Oracle Applications Cloud: Configuring and Extending Applications
- Oracle SCM Cloud: Implementing Common Features for SCM
Role Information
You have a couple of options for giving people access to the Deep Links work area, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access the Deep Links work area:
- Application Developer (FND_APPLICATION_DEVELOPER_JOB)
- Application Implementation Administrator (ORA_ASM_APPLICATION_IMPLEMENTATION_ABSTRACT)
- Application Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)
- Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)
- Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
Users who are assigned configured job roles that contain this privilege are able to access the Deep Links work area:
- View Administration Link (FND_VIEW_ADMIN_LINK_PRIV)
If you're using deep links specifically for reports, here are the privileges you need:
- For Business Intelligence Publisher:
- BI Author Role (BIAuthor)
- BI Consumer Role (BIConsumer)
- BI Administrator (BIAdministrator)
- For Oracle Transactional Business Intelligence (OTBI):
- BI Author Role (BIAuthor)
- BI Consumer Role (BIConsumer)
Terminate Approval Workflows in Innovation Management
Use a Terminate Workflow action to stop the approval workflow of a concept, proposal, portfolio scenario, or requirements specification that was already submitted for approval. The object returns to Draft status and you can resubmit it again for approval.
New Terminate Workflow Action
Terminate Workflow Dialog Requests Comment
Termination Logged in Approval History
Termination Withdrawn Notification
You can now correct or change approvers as required and resubmit the approval workflow. A record of the approval workflow termination is logged in Approval History.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Only the user who submitted the object for approval is allowed to terminate the approval workflow.
Role Information
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB) or
- Product Portfolio Manager (ORA_ACE_PRODUCT_PORTFOLIO_MANAGER_JOB)
Use Attachment Categories for Innovation Management Objects
Choose an attachment category when you add attachments to concepts, requirements, proposals, ideas, and portfolios. You can set up multiple attachment categories in the Setup and Maintenance work area to organize object attachments.
Attachment Category Dropdown
Assigning Categories to Attachment Entities
Categorization helps you clearly identify the relevant attachments for a specific process step. It’s also a prerequisite if you want to secure attachments based on category.
Steps to Enable
To assign Attachment Categories to Attachment Entities for the Innovation Management objects, go to the Setup and Maintenance work area, search for the setup task "Manage Attachment Entities". Search for respective attachment entity like ACN_IDEA for Ideas. Add or remove categories in the sub-table "Attachment Categories".
Tips And Considerations
The attachment categories can be set for the entities as follows:
| Attachment Entity | IM Object |
|---|---|
| ACN_REQUIREMENT |
Requirement Specifications |
| ACN_REQUIREMENT_LINE |
Requirement Lines |
| ACN_IDEA |
Ideas |
| ACE_PORTFOLIO |
Product Portfolio |
| ACD_PROPOSAL |
Product Proposal |
| ACD_COMPONENT |
Concept and Concept Component |
Role Information
Users who are assigned any of these predefined job roles are automatically able to access this feature, depending on the object type:
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB) or
- Product Portfolio Manager (ORA_ACE_PRODUCT_PORTFOLIO_MANAGER_JOB)
Leverage Improved Notifications in PLM and Quality Management
Select roles in addition to users when you use the Send action to send objects for review. You can expand a role to display the list of its members, and then further refine the list to include only the users you want to notify. The remaining roles automatically expand to show members when you send the notification.
A new Sent By field in the notification helps you identify the user who sent the notification.
Enhanced Send Dialog to Add and Expand User Roles
With this update, you can easily notify large groups of stakeholders or approvers and ensure faster cross-functional collaboration.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB) or
- Product Portfolio Manager (ORA_ACE_PRODUCT_PORTFOLIO_MANAGER_JOB) or
- Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB) or
- Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)
Integrate and Extend Innovation Management Using REST Services
Manage Proposal Teams Using REST Services
Use the Product Proposals REST resource to add or remove teams for your proposals in Innovation Management.
SAMPLE CALL
curl -H "Content-Type: application/vnd.oracle.adf.resourceitem+json"-u user:pwd -X POST-d '{"UserName" : "product_manager"}' "https://server/fscmRestApi/resources/latest/productProposals/300100185184414/child/Team"
Watch a Demo
You can add a team to a proposal programmatically from an external client, from Application Composer (using groovy scripting), or during legacy data import.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Key Resources
Role Information
Users who are assigned any of these predefined job roles are automatically able to access this feature:
-
Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
Manage Product Concepts Using REST Services
Use the Product Concepts REST resource to add, update, or delete concepts, attachments, and concept structures.
New APIs enable you to add the following to the concept structure:
- concept components
- sub-concepts
- items
A new structure attribute called Level depicts the position of a structure line item within the structure.
New Attribute Called Level in Concept Structure
SAMPLE CALL
curl -H "Content-Type: application/vnd.oracle.adf.resourceitem+json"-u user:pwd -X POST -d@payload "https://server:port/fscmRestApi/resources/latest/productConcepts“
SAMPLE PAYLOAD
{
"Name" : "Concept 7005",
"Description" : “Conceptual Design for Project 7005",
"ConceptStructure" : [ {"ParentLevel" : "1", "ToType" : "COMPONENT", "Name":“C1"},
{"ParentLevel" : "1.1", "ToType" : "COMPONENT", "Name":"comp 1.1.1"},
{"ParentLevel" : "1.1", "ToType" : "COMPONENT", "Name":"comp 1.1.2"},
{"ParentLevel" : "1.1", "ToType" : "SUB_CONCEPT", "Name":“R12x Flying Bike"}, {"ParentLevel " : "1", "ToType" : "ITEM", "Item_Name" : “AS45111" }]
}
With this REST service update, you can create and manage concepts and concept structures with greater flexibility from an external client, or from Application Composer (using groovy scripting), or during legacy data import. You can also extend the ability to initiate concept structures from engineering, customer or legacy data, and eliminate the need for manual data entry.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Role Information
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
Use Optimized Payloads for Change Orders and New Item Requests
Optimize the payload size for change orders and new item requests by including only the data affected by rule based approval criteria. If the rule includes evaluations of particular attributes, the payload transfers only the relevant attributes referred to in the rules to the back-end workflow engine for processing.
With this update, rule based approvals are more efficient because only relevant change line payload information is sent to the workflow engine for processing. You can ensure reliable processing of affected objects, change lines, and new item request lines for rule based approvals.
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: Product Management No Longer Optional From: Update 21B
Tips And Considerations
This feature has no impact on the UI.
Role Information
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Manage New Item Request (EGO_MANAGE_NEW_ITEM_REQUEST_PRIV)
- Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
Improve Configuration Options for Item Reports
Use an item's extended attributes as parameters for OTBI reports launched from the item page. You can group reports by context, and also launch reports from the Manage Items page.
View Reports
In the Configured Reports dialog launched from the View Reports action on the item page, you can filter reports by context.
Filter Reports by Tab Context
Search Results
You can easily find the reports you need to accomplish your tasks without having to search through a large number of reports.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
Roles
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
- Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
- Supplier Product Design Engineer (ORA_ACA_SUPPLIER_PRODUCT_DESIGN_ENGINEER_JOB)
- Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
Privileges
- To access the setup task, you must have ACA_SETUP_PRODUCT_INNOVATION_PRIV. Note that the following role has this privilege: Supply Chain Application Administrator: ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB
-
To launch a report from an object that you already have access to, you must have the View Product Management Reports (ACA_VIEW_PRODUCT_MANAGEMENT_REPORTS_PRIV) privilege.
NOTE: In 20C, you can perform this action only from the item page in the Product Development work area.
Undo Redlines for AML on Change Affected Objects
Use the Undo Redlines action to clear AML-related redlines on the affected objects of a change order. You can multiselect rows to undo redlines quickly. An icon indicates which redlines will be undone and the Undo action is completed upon saving the change order.
New Undo Redlines Action and Icon
Icon on Row Shows Which AML Redlines Will Be Undone
Watch a Demo
Multiselect provides a more efficient way to back out AML redlines. The clear indication of which AML rows will have redlines undone allows the user the opportunity to change their mind before performing the save action.
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: Product Management No Longer Optional From: Update 21A
Tips And Considerations
When you opt in to use this feature, you must opt in to the feature named: Undo Structure Redlines for Change Affected Objects. Opting in to the Undo Structure Redlines for Change Affected Objects feature also enables the feature described here. If you previously opted in to the Undo Structure Redlines for Change Affected Objects feature, then this feature is automatically enabled.
Key Resources
Role Information
You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB) or
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- View Item Change Order (EGO_VIEW_ITEM_CHANGE_ORDER_PRIV)
- Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
Restrict Access to Change Web Services
Ensure that only users with requisite privileges can access and execute change web services.
Users can use following privileges to perform the following actions on change orders: GET, FIND, GET Approvers, Manage and Create:
- EGO_VIEW_ITEM_CHANGE_ORDER_PRIV
- EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV
- EGO_CREATE_ITEM_CHANGE_ORDER_PRIV
User can use following privileges to perform the Describe action and Mange on new item requests in REST services:
- EGO_VIEW_NEW_ITEM_REQUEST_PRIV
- EGO_MANAGE_NEW_ITEM_REQUEST_PRIV
These privileges can be used instead of the following existing privileges:
- EGP_MANAGE_ITEM_MANUFACTURER_PRIV
- EGP_MODIFY_TRADING_PARTNER_PRIV
You now have granular controls to restrict actions in change web services.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Tips And Considerations
The existing roles and privileges are still valid, so you have time to familiarize yourself with the new privileges.
Key Resources
Role Information
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- EGO_VIEW_ITEM_CHANGE_ORDER_PRIV
- EGP_MODIFY_TRADING_PARTNER_PRIV
- EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV
- EGO_CREATE_ITEM_CHANGE_ORDER_PRIV
- EGO_VIEW_NEW_ITEM_REQUEST_PRIV
Default Additional Controls Settings for Changes in Progress
If you delete a workflow status from the change type configuration while there are pending change orders for the type, it can result in improper actions. To prevent this, application default values are now applied for all actions in the Additional Workflow Controls table for the deleted status.
You can also define supplier actions for the change type in the new Portal Users column added to this table.
New Portal User Column in Additional Workflow Controls Table
Change order workflows can still move forward with default controls if a status is deleted for a change type that has pending change orders. A change administrator can also control what suppliers can do for each change type at the status level.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Although this feature enables you to circumvent accidental deletion of a status, it is not recommended to do so. As a best practice, ensure that the change type doesn't have any pending change orders before you delete a status.
Key Resources
Role Information
You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB) or
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
Leverage Extended Character Length for Item Revision Code
Previously, the revision number for items and documents in Product Development had a 3-character limit. Now the supported length is up to 18 characters, the same as it is in Product Hub.
The Revision list on items and documents reflects this extra length. Also, when you define a new revision in the change order affected object page, you can manually specify a revision number with up to 18 characters.
Long Revision Number in Item Page
Watch a Demo
With the enhanced length, you can use more meaningful revision identifiers, for example, you could have a revision called Draft. It’s also easier to take over data from legacy systems, since the revision number can be taken over without the need for truncation.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The item revision bump-up mechanism continues to support only up to 3 characters.
Key Resources
Role Information
You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- View Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV) or Manage Item Change Order (EGO_VIEW_ITEM_CHANGE_ORDER_PRIV)
- View Item (EGP_VIEW_ITEM_PRIV) or Manage Item (EGP_MANAGE_ITEM_PRIV)
Get Additional Insights Into Structures and Changes Using OTBI
View remaining approvers for rejected change orders using new columns in the Change Order-Approvals subject area.
Activity Type, Response and Rejection Details in Change Order-Approvals Subject Area
Sample Analysis with Activity Type and Response
Sample Analysis with Rejection Details
Select the Latest Revision indicator on structure reports to retrieve the structure for the latest item revision. This flag has been added to Item Revisions and Structures and Components subject areas.
Latest Revision Flag in Structures and Components Subject Area
Sample Analysis with Latest Revision Flag
A new attribute Change Order Status Version 2, added in the Change Order Real Time and Change Order Approvals subject areas, provides the accurate status of the change order when in the Draft, Hold, and Canceled statuses.
Change Order Status Version 2 in Change Order and Change Order Approvals Subject Areas
Sample Analysis with Change Status Version 2
Watch a Demo
With this update, you can improve the change order cycle time by analyzing the open change orders for approvers who are yet to sign off based on response. You can analyze the most relevant structures and items by filtering analyses based on the latest revision. Additionally, you can minimize delays in the change order process by identifying and acting on change orders in the Draft, Canceled, and Hold statuses.
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).
Key Resources
Role Information
You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Transactional Analysis Duty (FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY) or
- Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY) or
- BI Consumer Role (BIConsumer)
View Reference Designators for Affected Objects in Side Panel
Select a component of an affected object on a change order to view and edit details of its reference designators in a side panel.
.
Reference Designator Side Panel View for Structure Component
Use the side panel view to quickly view and edit each component's reference designators without losing context.
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: Product Management No Longer Optional From: Update 21B
Role Information
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- EGP_MANAGE_ITEM
- EGO_MANAGE_ITEM_CHANGE_ORDER
Import and Export Additional Configurations for Change Types
The ability to export and import change type configurations accelerates the implementation timeline for your cloud environments. With this update, you can also import and export additional change type configuration such as propagation rules, entry and exit criteria, and creator settings. If there are any errors or warnings related to the import or export, you can find them in the same page for easy reference.
Creators Setup in Change Type
Save time and ensure data is consistent when you migrate change type setup between your Development and Production environments.
Steps to Enable
Set up the implementation project and configuration package for the task Manage Change Order Types in the Setup and Maintenance work area to run the import and export of change types.
Key Resources
Role Information
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Application Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)
Filter Change Statuses by Change Type
Use the Type and Status filters in the My Changes panel to view change orders of a particular type and status. In the Type list, you can select one or more change types to filter your search, or select All to view results for all change types.
My Changes Panel with Type Filter
In the Status list, you can see the statuses that are used in the workflows of the selected change types. Draft, Cancel, and On Hold statuses are always included. You can use multi-select here as well.
Results appear in alphabetical order for both type and status.
If you click a hyperlink in the My Changes infotile on the landing page, then the respective statuses in the Open, Pending Approval, or Approved category are preselected.
My Changes Panel with Status Filters
Previously, you could only select one or all change types in the My Changes panel. The new filters with multi-select capability help you quickly find the exact change types that you’re interested in. Now that change type names and status names created by your organization are visible in the filters, you’ll see improved usability and reduced training effort.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB) or
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- View Item Change Order (EGO_VIEW_ITEM_CHANGE_ORDER_PRIV)
- Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
Search for Manufacturers by Registry ID
Use the familiar Registry ID in advanced search to easily search for manufacturers while creating manufacturer parts. You can use the Add Fields option to add Registry ID as a search field.
Use Registry ID Advanced Search
Use the Registry ID to identify the manufacturer in the following:
- Create Manufacturer Part dialog
- Item Structure tab > AML panel
- Change order without revision control > Affected Objects > Item AML tab > Select and Add dialog
- Engineering change order > Affected Objects > Item AML tab > Select and Add dialog
Select Registry ID
Watch a Demo
When a manufacturer has multiple locations identified, these can be differentiated using the Registry ID. Instead of searching by manufacturer name, you can now search by Registry ID to speed up the search.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- View_Item (EGP_VIEW_ITEM_PRIV) or Manage_Item (EGP_MANAGE_ITEM_PRIV)
- View_Trading_Partner (EGP_VIEW_TRADING_PARTNER_PRIV) or Manage_Trading_Partner (EGP_MANAGE_TRADING_PARTNER_PRIV)
- Manage Item Change Orders (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
Other Product Development Changes in This Update
This section includes details about additional changes in this update that can change the way Oracle Product Development Cloud works.
Improve Next Revision Calculation for Engineering Change Orders
The method to calculate the next higher item revision number in an engineering change order has been modified. Instead of considering only the past, current effective, or future effective (change order is scheduled) revisions, the new procedure considers all revisions (past, current effective, future effective, and pending) when searching for the highest existing revision number. Instead of retrieving the item revision with the furthest future effectivity date, the system now retrieves the item revision that was created most recently.
Here’s how this impacts application behavior: the item revision identified as the base revision for new revision calculation might change because the application now evaluates the creation date of the item revision instead of the effective date. In case the calculated item revision is already used, the application does not blank out the item revision number, but continues to increment the new item revision number until it finds an unused number, so the user does not have to enter a number manually.
The algorithm to calculate the next higher revision number continues to support up to 3 characters for revision numbers.
Bug reference: 30886890
Govern Cyclic Relationships for Related Items Through Setup
Now you can use the Manage Related Item Types task to specify whether you want to disallow cyclic relationships for a relationship type.
By default, cyclic relationships are allowed. So, when you try to create a relationship between two items, you might form a loop with other existing relationships. For example, consider a scenario in which there are existing relationships: Item A has a superseded relationship with Item B and Item B has a superseded relationship Item C. A user may create a new superseded relationship between Item C and Item A, that would form a loop; this could be undesirable. Using this new user interface, you can specify whether cyclic relationships should be prevented for a relationship type. Using this setup, users can be prevented from creating relationships that could form a loop.
To govern cyclic relationships, use the Manage Related Item Types task in the Setup and Maintenance work area:
- Offering: Product Management
- Functional Area: Items
- Task: Manage Related Item Types
Setup to Govern Cyclic Relationships for Related Item Types
This user interface gives users a quick and easy way to view and control whether a relationship type can have cyclic item relationships.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Cyclic relationships are allowed by default until you explicitly set the Allow Cyclic Relationship for a relationship type to No.
- This feature prevents cyclic relationships from being created after the setup change shown. You must query any existing cyclic relationships created before the setup change and fix those.
Key Resources
- Watch Item Management, Data Consolidation and Analytics Readiness Training
- What's New information about cyclic relationship check using a REST resource in Oracle Product Lifecycle Management Cloud for 20C.
- Refer to the Oracle SCM Cloud Using Product Master Data Management guide, available on the Oracle Help Center.
Role Information
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Manage Related Item Types (EGP_MANAGE_RELATED_ITEM_TYPE_PRIV)
Save Products Without Required Values for Extensible Flexfields
Supplier Product Administrators can now save products in draft status without entering values for all required extensible flexfields. They can then submit the products once the values for all required extensible flexfields have been provided.
Save Products In Draft Status Without Values For All Required Extensible Flexfields
Supplier Product Administrators have improved flexibility, because they can enrich their product data incrementally without losing their work even if all of the required attribute values have not been entered.
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: Product Management No Longer Optional From: Update 21B
Tips And Considerations
- Products cannot be saved without providing values for the following attributes: Category, Product Name, Description, and Primary Unit of Measure.
- For multi-row extensible flexfield rows, a value needs to be provided for the unique row identifier attributes.
- Values for all required extensible flexfields need to be provided before submitting the products.
- All required extensible flexfield values need to be provided if the products are being created using Product Uploads.
Key Resources
- Watch Item Management, Data Consolidation and Analytics Readiness Training
- See the chapter on supplier products in the Oracle SCM Cloud Using Product Master Data Management guide, on the Oracle Help Center.
Role Information
You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.Users who are assigned this predefined job role are automatically able to access this feature:
- Supplier Product Administrator (ORA_EGS_SUPPLIER_PRODUCT_ADMINISTRATOR_JOB)
Users who are assigned configured job roles that contain this privilege are able to access this feature:
- Manage Product Upload (EGS_MANAGE_PRODUCT_UPLOAD_PRIV)
Item search has a new feature to enhance searching for sets of items. You can now use the new search operator In to search for a list of comma- separated items in the Advanced Search region of the Manage Items page. You can use standard copy and paste operations to enter the string of items, then initiate a search and see the results for all items in the list that are searchable.
Search with Multiple Items Using the In Operator
The panel drawer item search has also been enhanced to support multiple item search. You can copy and paste a set of items into the Multiple Items window and select the Search action. The list of items is then formatted and added to the item field in the Advance Search region of the Manage Items page, the In Operator is selected, and the search is performed.
The item field on the Manage Items page is limited to 1,000 characters when using the In operator.
Your product data steward is more efficient by being able to search for multiple specific item numbers at one time. This allows your users to quickly access all relevant information at one time.
Steps to Enable
A forced deployment of extensible flexfields must be performed prior to using this feature.
Tips And Considerations
- The Search with Multiple Items and Copy and Paste Items Using Clipboard features both require a forced deployment of extensible flexfields, so you should consider using both features and performing a single deployment.
- You can copy and paste from external sources including documents, spreadsheets and reports.
- The Multiple Item Search in the task panel drawer automatically formats the list of items by adding comma separators when you elect to search.
Key Resources
- Watch Item Management, Data Consolidation and Analytics Readiness Training
- See the chapter on Search in the Oracle SCM Cloud Using Product Master Data Management guide on the Oracle Help Center.
Role Information
Search requires both functional security and data security when items are in a private state. Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
Users who are given these functional privileges can search items:
- View Item (EGP_VIEW_ITEM_PRIV)
- Manage Item (EGP_MANAGE_ITEM_PRIV)
In the case of private items, users who given these data privileges can search for items:
- View Item Basic (EGO_VIEW_ITEM_BASIC_DATA)
Include Additional Related Item Attributes in OTBI Reports
You can now create OTBI reports by including additional attributes of target item of the relationship. These attributes include operational and user-defined attributes of the item.
Related item relationship is a relationship between two items. With this enhancement, you can include the attributes of both of the items in the relationship in the same report.
Screenshot of Report Showing FROM Item and TO Item Attributes
Gain improved business insight by building reports which show more information on item relationships.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Watch Item Management, Data Consolidation and Analytics Readiness Training
- See the Creating and Administering Analytics and Reports for SCM guide, available on the Oracle Help Center.
Role Information
Users who are assigned any of these predefined duty roles are automatically able to access this feature:
- Transactional Analysis Duty (FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY)
- Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY)
- BI Consumer Role (BIConsumer)
Copy and Paste Items Using Clipboards
The clipboard is a powerful new virtual scratch pad available in the panel drawer of the Product Information Management work area. You can use the clipboard to maintain a collection of items to be added to change orders and item structures as needed later.
The Manage Items page has been enhanced to support the new clipboard by adding a new Copy icon to the Search Results table. From the search results, you can multi-select your candidate items and click the Copy icon to add them to the clipboard. Note that you can incrementally add items to your collection by performing iterative searches.
Manage Items Page
The Manage Change Orders page has been enhanced to support the new clipboard by adding a Copy icon and a Paste icon. You can copy affected items from change order lines into the clipboard by clicking the Copy icon, and then optionally multi-select items from the clipboard and use the drag-and-drop operation to add them to a change order’s list of affected items. However, in any clipboard-enabled page, if you want to paste just the most recent set of items you have copied into the clipboard, then you can simply click the Paste icon without any need to navigate to the clipboard.
Manage Change Orders Page
The Manage Item Structure page has also been enhanced to support the new clipboard by adding a Copy icon and a Paste icon. You can copy items from item structures into the clipboard by clicking the Copy icon, and then optionally multi-select items from the clipboard and use the drag-and-drop operation to add them to another item structure. However, in any clipboard-enabled page, if you want to paste just the most recent set of items you have copied into the clipboard, then you can simply click the Paste icon without any need to navigate to the clipboard.
Watch a Demo
By leveraging complex search functionalities to build your collection of items in the clipboard and then add them as structure components and change order lines without performing duplicate manual entries, you can enjoy improved efficiencies. Your ability to perform your tasks by clicking copy and paste icons and using intuitive drag-and-drop capabilities improves your user experience.
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: Product Management No Longer Optional From: Update 21B
After you opt in, perform the Refresh and Deploy Offline step, as detailed in the topic on deploying item flexfields in the Implementing Product Management guide, available on the Oracle Help Center.
Tips And Considerations
Optionally, you can paste items into the Manage Change Orders and Manage Structures pages from your Favorites collection and the Recent Items collection on the clipboard. Refer to the Access Favorites and Recent Items feature in Oracle Product Lifecycle Management Cloud - Update 20B for instructions to enable this capability.
Key Resources
- Refer to the Access Favorites and Recent Items feature in Oracle Product Lifecycle Management Cloud - Update 20B.
- The "Refresh & deploy offline" step, as detailed in the Flexfield Deployment section of the whitepaper Extensible Flexfield Setup, available on My Oracle Support at User Defined Attribute Groups and Attributes (Extensible Flexfields-EFFs) Setup White Paper (Doc ID 1992317.1).
- Refer to the Oracle SCM Cloud Using Product Master Data Management guide, available on the Oracle Help Center.
Role Information
You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned this predefined job role are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
Users who are assigned configured job roles that contain this privilege are able to access this feature:
- Access Clipboard (ACA_ACCESS_CLIPBOARD_PRIV)
Match Potential Duplicates Across Item Classes
Decrease your chances of erroneously creating duplicate items by identifying potential duplicates across item classes that share the same data quality matching attributes. The duplicate item check is now more robust.
Data Quality check now ensures that items across the item classes are used for matching if they have the same set of matching attribute values, irrespective of the position of the item class in the item class taxonomy.
Increase your enterprise accuracy by decreasing chances of erroneously having duplicate items in your Product Information Management work area. The duplicate item check is now more robust by match-checking inherited attributes.
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: Product Management No Longer Optional From: Update 21B
Tips And Considerations
- The matching attributes inherit down the item class hierarchy.
- The matching attributes present in the item class drive the identification of the potential duplicates. Therefore, if any new matching attribute are added to a child item class, then any items belonging to such child item classes will not be shown as potential duplicates.
Key Resources
- Watch Item Management, Data Consolidation and Analytics Readiness Training
- Customer Connect session: Improve product data quality using Product Hub
- Oracle SCM Cloud Using Product Master Data Management guide, available on the Oracle Help Center.
Role Information
Users who are assigned this predefined job role are automatically able to access this feature:
- Product Manager (ORA_EGP_PRODUCT_MANAGER)
Users who are assigned configured job roles that contain any of these privileges are able to access this feature:
- Create Item Class Item Data (EGO_CREATE_ITEM_CLASS_ITEM_DATA)
- Check Item Data Quality (EGI_CHECK_ITEM_DATA_QUALITY)
Use Import Maps to Import Common Structures, and Reference Designators and Substitute Components with Start Dates
You can now import common structures using import maps. You can now also import reference designators and substitutes with start dates using import maps.
To import common structures using import maps, you need to map the Common Structure Item and Common Organization attributes in the Master Data region of import maps. The data file column mapping to the Common Structure Item attribute must contain the source item number from which the common structure is to be created. The data file column mapping to the Common Organization attribute must contain the organization of the source item from which the common structure is to be created.
Import Map Common Structure Item Attribute
You can now use import maps as a single method for importing items and related entities, which improves the efficiency of the item import process making you more productive.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Only the first-level common structure can be created through import.
- The start dates specified for the components will be set as the start dates for the component reference designators and substitutes.
- If multiple reference designators are being imported using import maps, then, in the data file, the component start date needs to be specified for every row of the reference designators.
- If multiple substitutes are being imported using import maps, then, in the data file, the component start date needs to be specified for every row of the substitutes.
- If the same component is being imported with different effectivity dates, then the component start date specified in the data file corresponding to the reference designator will be set as the reference designator start date.
- If the same component is being imported with different effectivity dates, then the component start date specified in the data file corresponding to the substitute will be set as the substitute start date.
Key Resources
- Watch Item Management, Data Consolidation and Analytics Readiness Training
- Customer Connect Event, Importing Items using Import Maps
- See topic on importing items using import maps in the Oracle SCM Cloud Using Product Master Data Management guide on the Oracle Help Center.
Role Information
You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.Users who are assigned this predefined job role are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Manage Item Import Map (EGI_MANAGE_ITEM_IMPORT_MAP)
- Manage Item Batch (EGI_MANAGE_ITEM_BATCH)
Manage Item Import Data Using Transaction Type in Import Maps or Supplier Products REST Service
You can now import item data using import maps by specifying values for the Transaction Type attribute to create, update, or sync a row of item data. You can also delete certain item entities using the Transaction Type attribute. Only those item entities that can be deleted through file-based data import (FBDI) are supported for deletion through import maps as well. Supplier Product Administrators can now also specify values for the Transaction Type attribute using the Supplier Products REST service. Smart Spreadsheets also now support the Transaction Type attribute.
Import Map Transaction Type Attribute
The Transaction Type attribute allows your product data steward to have more control over whether an item or its child entities are created, updated, or deleted.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- If data is uploaded directly to an item batch using import maps in Oracle Product Hub Cloud, then the valid values for Transaction Type attribute are: CREATE, UPDATE, SYNC, and DELETE. Note that the DELETE Transaction Type is only supported for item entities that can be deleted through FBDI.
- If data is uploaded using product uploads in Oracle Product Hub Portal Cloud, then the valid values for Transaction Type attribute are: SYNC and DELETE. If the value for the Transaction Type attribute is specified as CREATE or UPDATE, then it's converted to SYNC during the data file upload process.
- If the Transaction Type attribute is not mapped, or it's mapped but has no value provided in the data file, then the SYNC transaction type is inserted by import maps in the interface tables.
- For translatable extensible flexfields, the Transaction Type attribute is displayed twice, once per installed language, in import maps for mapping.
- The Transaction Type attribute is available only for the following product entities in Supplier Products REST: extensible flexfields, relationships, and categories.
- If data is uploaded using the Supplier Products REST in Oracle Product Hub Portal Cloud, then the valid values for Transaction Type attribute are: SYNC and DELETE. If the value for Transaction Type attribute is specified as CREATE or UPDATE, then the service call errors out.
- If single-row extensible flexfield data is uploaded using the Supplier Products REST in Oracle Product Hub Portal Cloud, then the valid value for the Transaction Type attribute is SYNC. If the value for the Transaction Type attribute is specified as CREATE, UPDATE, or DELETE, then the service call errors out.
Key Resources
- Watch Item Management, Data Consolidation and Analytics Readiness Training
- Refer to the Oracle SCM Cloud Using Product Master Data Management guide, available on the Oracle Help Center.
Role Information
You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
- Supplier Product Administrator (ORA_EGS_SUPPLIER_PRODUCT_ADMINISTRATOR_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Manage Item Import Map (EGI_MANAGE_ITEM_IMPORT_MAP)
- Manage Item Batch (EGI_MANAGE_ITEM_BATCH)
- Manage Product Upload (EGS_MANAGE_PRODUCT_UPLOAD_PRIV)
Quickly Analyze Validation Errors for New Item Requests
View item activation status and access log files directly from the new item request page to address validation errors. Two new columns in the Items table provide a clear indication of activation status and a link to the scheduled process.
The activation ID is hyperlinked for 72 hours and you can click the link to access the log file. If you want to access it after the 72-hour period, you can copy the ID and search for the log file using the Manage Scheduled Processes task.
New Columns in Items Table for New Item Requests
Access to Log File
Speed up your new product introduction. If the new item request scheduled process fails, your users can now directly access validation errors and fix them without having to wait for an administrator.
Steps to Enable
Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.
Key Resources
Role Information
You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB) or
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Manage New Item Request (EGO_MANAGE_NEW_ITEM_REQUEST_PRIV)
Additionally, users require the following data security policies to access the log file (for change orders and new item requests):
- Grant ESS Requests Output View (ESS_REQUEST_OUTPUT_READ)
- Grant ESS Requests View (ESS_REQUEST_READ)
Use Contextual Actions to Access Affected Item Details
View and access details of affected objects for a commercialization change order with a new contextual details icon.
In the Affected Objects table, each item appears with a new triangle icon to indicate that additional information is available. An information dialog appears on hover, and you can click it to bring up a panel with details such as item name, class name, description, status code, revision code, and primary UOM. You can also drill down using the hyperlinks to access affected object specifications, structures, attachments, relationships, an associations in a dynamic tab.
Contextual Information Displayed for Affected Objects of Commercialization Change Orders
This update improves productivity because you can navigate to affected object details in fewer clicks, without losing the change context.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- View Item Change Order (EGO_VIEW_ITEM_CHANGE_ORDER_PRIV)
- Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
- View Item (EGP_VIEW_ITEM_PRIV)
Add Packaging Strings to Items
Many of your items may have non-standard quantity conversions specific to the items themselves, driven by their packaging UOM hierarchies. Some examples of non-standard conversions could be: the count of items going into bags, the count of bags going into cartons, or the count of cartons going into a case. For example, the item Gloves GL-47M might have a packaging string Ea 120/BG 20/CTN 12/C12 to represent its packaging information that: one hundred and twenty gloves go into a Bag, 20 Bags go into a Carton, and twelve Cartons go into a Case.
With this update, you can optionally assign a packaging string for an item using the new operational attribute Packaging String in the Unit of Measure region of the Edit Items page. You can assign a packaging string for an item by choosing one from an existing collection available in the list for the Packaging String field. If a suitable packaging string isn't available in the existing collection, then you can quickly augment the collection by building a new packaging string in real time using the Define Packaging String wizard.
Packaging String Attribute on Edit Items Page
You can open the Define Packaging String wizard by clicking the + icon of the Packaging String field. The wizard guides you through a three-step process by which you can design your own packaging UOM hierarchy along with its conversion multipliers. With these inputs, the wizard constructs a new reusable packaging string and creates new UOMs such as 'Box of 18' for your future use.
Define Packaging String Wizard
Watch a Demo
NOTE: The Packaging String attribute, like any other operational attribute, can be leveraged in Product Hub functionalities such as new item requests, change orders, item rules, and item batches.
With the addition of this new attribute, you will be able to enjoy improved productivity by leveraging the ‘Define packaging String’ wizard and also by reusing the packaging string.
By having the packaging string as a ready reference, your users can gain operational improvements by quickly computing quantity conversions while viewing item attributes.
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: Product Management
Tips And Considerations
When you opt in to use this feature, you must opt in to the feature named: Create Packaging Strings for Items. Opting in to the Create Packaging Strings for Items feature also enables the Add Packaging Strings to Items feature.
New Features Work Area
Additional tips:
-
The Packaging String attribute is controlled at the master organization level only, which means that, by inheritance, the packaging string of an item is the same at the master organization and all of the child organizations that the item is assigned to. You can't change the control of the Packaging String attribute to the child organization level.
Key Resources
- Watch Add Packaging String to Items Readiness Training
- Watch the Add Packaging String to Items Demo
- Refer to the Oracle SCM Cloud Using Product Master Data Management guide, available on the Oracle Help Center.
Role Information
You have several options for providing users with access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned this predefined job role are automatically able to access this feature:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Manage Unit of Measure (INV_MANAGE_UNIT_OF_MEASURE_PRIV)
- Manage Units of Measure and Standard Conversions (INV_MANAGE_UOM_AND_STD_CONV_PRIV)
Integrate and Extend Product Hub Using REST Services
Manage Item Relationships Using a REST Service
You can now create and manage item relationships using the following REST resources:
- Trading Partner Item Relationships
- Related Item Relationships
- GTIN Relationships
- Cross-Reference Relationships
Using REST services, you can create, update, delete, and search for these item relationships.
You can build enhanced integrations and extensions by using REST resources to maintain item relationships.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Key Resources
Role Information
Users who are assigned this predefined job role are automatically able to access this feature:
- ORA_EGI_PRODUCT_DATA_STEWARD_JOB
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- EGI_GET_ITEM_REL_REST: For GET on Related item relationships, GTIN relationships and Cross-reference relationships.
- EGI_MANAGE_ITEM_REL_REST: For GET, POST, PATCH and DELETE on Related item relationships, GTIN relationships and Cross-reference relationships.
- EGI_GET_TPI_REL_REST: For GET on Trading partner Item relationships REST API.
- EGI_MANAGE_TPI_REL_REST: For GET, POST, PATCH and DELETE on Related item relationships, GTIN relationships and Cross-reference relationships.
Manage Trading Partner Items Using a REST Service
You can now create, update, delete and search for trading partner items using the trading partner items REST service.
The term trading partner items refers to:
- Customer Items
- Competitor items
- Manufacturer Part Numbers
- Supplier Items
You can now build integrations and extensions by using trading partner items REST service to maintain trading partner items.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Tips And Considerations
You can use the existing Manage Trading Partner Items task to manage the public flag for trading partner and also grant view, maintain and administer accesses to trading partner items.
Role Information
Users who are assigned this predefined job role are automatically able to access this feature:
- ORA_EGI_PRODUCT_DATA_STEWARD_JOB
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- EGI_GET_TPI_REST: For GET on Trading Partner Items.
- EGI_MANAGE_TPI_REST: For GET, POST, PATCH and DELETE on Trading Partner Items.
Other Product Hub Changes in This Update
This section includes details about additional changes in this update that can change the way Oracle Product Hub Cloud works.
Item Extensible Attributes Inline Search Display Type
After updating to 20D, you can configure item extensible attributes with the display type of Inline Search with no issues in page loading or performance. When you view these attributes on the Edit Items page of the Product Information Management work area, you'll see a suggested list of values as you start typing an attribute value. This is a useful way to find the right value when a long list of values associated with the attribute is available.
Bug reference: 30785646
Product Development & Product Hub Common Features
Securely generate and access OTBI analysis reports for structures and structure-related data. When you create an OTBI analysis using the Structures and Components Real Time and Where Used Real Time subject areas, the results will omit values for secured attributes of the items, based on the access you have been granted to view those items. Some examples of the secured attributes in Structures and Components Real Time subject area are Parent Item Name, Component Item Name, Lifecycle Phase, Immediate Parent Item Name, Component Trading Partner Name and Component Trading Partner Item Number.
The following example illustrates the use of grants in the Structures and Components Real Time subject area:
Sample Analysis Run by User With Grants to All The Component Items
Sample Analysis Run by User Without Grants to One The Component Items
The following screenshots show the attributes in the Structures and Components subject area which are secured. When secured attributes are added to an analysis, the data will be blank if the user does not have grants to the corresponding component items.
Secured Item Attributes in the Structures and Components Subject Area
Secured Trading Partner Item Attributes in the Structures and Components Subject Area
The examples of secured attributes in the Where Used Real Time subject area are Where Used Item Name, Trading Partner Name, and Trading Partner Item Number. When secured attributes are added to an analysis, the data will be blank if the user does not have grants to the corresponding component items.
Secured Attributes in the Where Used Subject Area
The reports in the following subject areas previously displayed items only if you were granted access to view those items:
- Item Revisions Real Time
- Receivables - Customer Account Site Tax Profile Real Time (Item Description attribute)
- Receivables - Customer Tax Profile Real Time (Item Description)
These reports have been enhanced to also display items that belong to public item classes.
Now your data steward can save time. No additional security configuration is needed to secure the generating or viewing of your reports for your structures or structure-related data. You can share structures easily with suppliers, because security setup data from the Product Information Management work area is carried over when viewing or generating reports for your structure or structure-related data.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
-
When there is a need to share structure content with suppliers or users with limited grants, it's s best to share an analysis rather than provide access to the subject area.You can use filters to exclude the component rows with blank values, thus creating an analysis with the item components that the user has access to.The analysis can be shared with the supplier by creating a custom role and providing permissions on the analysis to this role.
- Existing OTBI analyses in the subject areas described here might return different results based on the item data security configuration because they will no longer display items to which the user does have have view access.
Key Resources
Role Information
Users who are assigned any of these predefined duty roles are automatically able to access this feature:
- Transactional Analysis Duty (FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY)
- Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY)
- BI Consumer Role (BIConsumer)
Other Product Development & Product Hub Common Changes in This Update
This section includes details about additional changes in this update that can change the way Oracle Product Development Cloud and Oracle Product Hub Cloud work.
Check Approve Item Change Order Privilege at Role Level
Previously, the application didn’t validate whether a role assigned as an approver had the Approve Item Change Order privilege before submitting the change order for approval. Any role added as an approver would be automatically expanded to show its members, and you had to manually remove users who did not have the privilege.
Now, when a role is assigned in the approvers panel of a change order, and the change is submitted for approval, the application checks whether the Approve Item Change Order privilege (EGO_APPROVE_ITEM_CHANGE_ORDER_PRIV) is assigned to the role (directly or through role inheritance). If it isn’t, an error is shown and the role is not expanded to show its members.
Make sure any role that you add as an approver, or a parent role, has the Approve Item Change Order privilege assigned.
Bug reference: 31317526
Record Application Actions in Change History
The following new entries are now created in the action log of a change if the change is automatically approved or rejected by the application.
- Automatically approved by an approver
- Automatically rejected by an approver
The action is logged on behalf of the user who submitted the change for approval. When you review change history later on, you can clearly identify which actions were automatically triggered by approval rules and which actions were performed manually by users.
Bug reference: 30973737
Ensure Change Assignee is an Active User
When you promote or demote a change to the next status, an additional check validates whether the assignee is an active user. This check is performed for each status up to Approval status. If the assignee is not an active user, the promotion does not proceed. Demotion will proceed, and an entry is in the action log.During manual or automatic promotion to Open status, if the application detects that the original change requestor is an inactive user, the change is not promoted.
During demotion, if the assignee is found to be an inactive user and Skip Request Comment is disabled, the Request for Comment notification is not sent. A corresponding entry is created in the action log. In this case, the user must choose an active user as the assignee and then promote the change manually.
Bug reference: 30731857
Leverage Additional Configuration Options
In this update, you have three new profile options to improve application performance. You can use the task Manage Administrator Profile Values in the Setup and Maintenance work area to configure these options.
- Minimum Time Between Effective Dates of Change Orders for an Item (EGO_MIN_TIME_GAP_BTWN_CO).
This new profile option enables you to define the minimum time gap in minutes between two parallel changes for an item. Earlier, a fixed time gap of 30 minutes restricted parallel processes to prevent locks. Now, depending on the complexity of changes to implement and the overall performance of your system, you can set the appropriate value for the profile option.
Additionally, the application considers only item changes for master organizations as a parallel process, not that of child organizations. In rare cases where the application still runs into a lock scenario, the change order is not automatically demoted but remains in its current state, and you can try to promote it manually later.
Bug reference: 31151092
- Zip Size limit for Publication (EGI_PUBLICATION_SIZE_OF_ZIP_FILE)
This profile option enables you to define the maximum size of the Zip files that are generated when you download item attachments or change order attachments. If the exported data is larger than what can be contained in a single Zip file, the process creates multiple Zip files.
NOTE: After downloading the set of Zip files, make sure that all the Zip files are extracted into the same root folder, and that the directory structure is created completely with all files available in their respective folders.
Bug reference: 30957467
- Default Display Mode for Item Extensible Flexfield Attributes (ACA_ITEM_EFF_DISPLAY)
This profile option enables you to define the behavior of extended flexfield attribute groups when you open the item page in Product Development.You can configure the display with the following values:
- Expand All - Expand all attribute groups.
- Expand All Groups with Required Attributes - Expand multi-row attribute groups and single row attribute groups that have at least one mandatory attribute.
- Expand Single-Row Groups with Required Attributes - Expand only single row attribute groups that have at least one mandatory attribute.
- Collapse All - Collapse all attribute groups.
Bug reference: 30827049
Product Recall Management is an end-to-end integrated solution that lets you capture product recalls from different sources and supports real-time remediation of recalled goods by reviewing inventory and expense purchases, aligning resources to quarantine the goods, and taking the appropriate disposal action. This solution is designed to primarily support the business processes pertaining to recall management in the healthcare industry.
The Product Recall Management solution includes these features:
- Capture and manage recall notices from different sources including regulatory authority and manufacturer
- Locate recalled parts based on on-hand inventory balance and historical purchases
- Assign tasks and align resources to quarantine and dispose the affected goods through notification of identified stakeholders
- Monitor disposition details against the tasks and bring the recall notice to closure
MANAGE RECALL NOTICES
Capture recall notices issued by different sources such as regulatory authority, manufacturer or supplier. You can create recall notices through the user interface or integrate regulatory authority data with your ERP through REST API or File Based Data Import offered by Product Recall Management and perform bulk import of recalled parts. Resolve duplicates, if any, when recall notices are captured from different sources for the same set of recalled parts.
A recall notice primarily includes the type of recall whether it is safety, advisory or voluntary, potential risk involved and the classification of recall based on severity, recall reason, recalling firm details, replacement type and recall instructions. Recalled parts are captured using the manufacturer part number along with National Drug Code (NDC), manufacturer lot and serial numbers.
The below screenshot shows the content of a recall notice.
Watch a Demo
LOCATE RECALLED PARTS
Recall Management takes you through a guided workflow by publishing the notice, once it is captured and any duplicated identified and resolved. This is followed by locating the recalled parts in the supply chain with different traceability statuses listed below. When the item is lot or serial controlled in Oracle Inventory Management, the recalled parts are traced by the lot or serial captured in the recall notice. But when the item is modelled as a plain item in Inventory, the recalled parts are traced by the recall period agreed between the buying organization and the recalling firm.
- Recalled parts that are in transit or available as a scheduled supply or lying in receiving dock before getting shelved in the warehouse will be traced as INBOUND
- Recalled parts that exists in perpetual inventory will be identified based on stock availability and shown as IN STOCK
- Recalled parts that are issued to PAR locations will be identified based on transaction history and shown as PAR with an estimated quantity
- Recalled parts that are issued to expense locations as well gets identified based on transaction history and traced as EXPENSE with an estimated quantity
The below screenshot illustrates how to locate the recalled parts captured in a recall notice.
ASSIGN TASKS AND NOTIFY STAKEHOLDERS
On locating the recalled parts, a pre-defined set of tasks gets assigned to the recall line based on traceability status and the replacement type captured in the recall notice. These tasks include delivering the recalled parts to quarantine location, performing recall count in the locations where the recalled parts reside, disposal of recalled parts from quarantine location or performing a device correction. Recall Management provides you with multiple options to view the locations where the recalled parts are identified and the various tasks assigned to different departments or organisations.
These screenshots illustrates the feature of reviewing the trace details and the task assignments.
Configure rules in BPM according to your business needs to notify the users responsible for different departments to carry out the tasks assigned. When a recalled part is traced in an expense location, the requester of that part by default gets the notification about the recall and the corresponding action to be taken.
Watch a Demo
MONITOR DISPOSITION DETAILS AND CLOSURE OF RECALL NOTICE
Product Recall Management provides a seamless integration with Oracle Inventory and partner solutions like RFSmart to perform a recall count in the identified locations using hand-held device and enables movement of affected goods to quarantine location. The count quantity reported will be captured against the count tasks assigned in different departments. You can also leverage the Inventory Count REST services to integrate with any custom built or third-party applications to report the recall count.
When the recall count is performed and the affected goods are quarantined, perform a disposal action as instructed in the recall notice. You can create a Return Order document and perform a Supplier Return with or without referencing the purchase order or receipt through which the material was originally received. You can also perform a scrap disposal against the Return Order without any reference to purchase order or receipt. When you specify the recall notice number during this Supplier Return or Scrap Disposal, the disposition task assigned to the recall line automatically gets closed after ensuring that the count quantity reported from different locations have been disposed. When all the tasks get completed, recall line gets automatically closed resulting in closure of recall notice. Review the complete history about the recall notice along with the traceability details, task progression details and disposition details as a reference at any point of time.
These screenshots illustrate these features.
Watch a Demo
- Have visibility and tighter control over the recall process for your goods.
- Extensive traceability of recalled parts across oracle cloud supply chain applications including non-quantity tracked expense items and inbound goods not yet received.
- Ensure timely and efficient compliance of regulations and general business practices for product recall.
- Improved accountability through flexible business rules driven notifications to stakeholders.
- Scalable, integration friendly architecture that enables seamless integration with partners like Rfsmart.
- Centralised and advanced monitoring of processing and closure of recall notices.
- Extremely flexible configuration, with the ability to model any type of product recall.
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: Product Management
Product Recall Management is a new, optional functional area in update 20D. You can use the New Features work area or the Offerings work area to opt in to this new functional area in the Product Management offering.
After you opt in, you must perform additional steps described below to enable product recall management.
- Define the recall classification lookup codes used to categorize the recall notice based on severity of the impact the recalled product creates on consumers
Navigation: Set up and Maintenance > Select Product Management offering > Select Product Recall Management functional area > Select the task Manage Product Recall Lookups
- Define the following recall parameters:
- Recall Notice Document Number Sequencing - This parameter enables user to specify the starting number for internal recall notice generation for each business unit.
- Item Validation Organization - Select an item master organization for each business unit where the recalled item categories, recalled manufacturer part number and the item relationships are defined.
- Product Traceability Grouping - This parameter indicates at which below listed entities level the product traceability details should be grouped and the task assignment should happen.
- Inventory Organization
- Location
- Subinventory
- Recall Subinventory and Stock Locator – Set up a default non reservable subinventory and stock locator for each inventory organization to quarantine the recalled parts.
Navigation: Set up and Maintenance > Select Product Management offering > Select Product Recall Management functional area > Select the task ‘Manage Product Recall Parameters’
- Define the regulatory authorities for each business unit, from whom the recall notices will be captured.
Navigation: Set up and Maintenance > Select Product Management offering > Select Product Recall Management functional area > Select the task ‘Manage Regulatory Authority for Product Recall’
Tips And Considerations
When you are using description-based items without any item number defined in the Product Information Management work area, you must have a blanket purchase agreement for those items with the manufacturer and manufacturer part number stored in it so that recall notices can be created for those type of items.
Key Resources
Role Information
The Product Recall Manager job role is seeded for 20D.
| Privilege Name and Code | Job Role Name and Code |
|---|---|
| Recall Management Console Inquiry ENQ_MGMT_CONSOLE_INQUIRY |
Product Recall Manager ORA_ENQ_PRODUCT_RECALL_MANAGER |
| Manage Product Recall Notices ENQ_MANAGE_PRODUCT_RECALL_NOTICES |
Product Recall Manager ORA_ENQ_PRODUCT_RECALL_MANAGER |
| View Product Recall Notices ENQ_VIEW_PRODUCT_RECALL_NOTICES |
Product Recall Manager ORA_ENQ_PRODUCT_RECALL_MANAGER |
| Manage Recall Task Status ENQ_MANAGE_RECALL_TASK_STATUS |
Product Recall Manager ORA_ENQ_PRODUCT_RECALL_MANAGER |
| Import Product Recall Notices ENQ_IMPORT_PRODUCT_RECALL_NOTICES |
Product Recall Manager ORA_ENQ_PRODUCT_RECALL_MANAGER |
| Manage Regulatory Authority for Product Recall ENQ_MANAGE_REGULATORY_AUTHORITY_FOR_ PRODUCT_RECALL |
Supply Chain Application Administrator ORA_RCS_SUPPLY_CHAIN_APPLICATION_ ADMINISTRATOR |
| Manage Product Recall Parameters ENQ_MANAGE_PRODUCT_RECALL_PARAMETERS |
Supply Chain Application Administrator ORA_RCS_SUPPLY_CHAIN_APPLICATION_ ADMINISTRATOR |
Considerations for Data Security:
The following data security function should be entered for your user-defined roles in the security console for the Manage Product Recall Data privileges.
- From Data Security Policies > Create Data Security Policy:
- Policy Name: Grant on Product Recall Notices
- Database Resource: Business Unit
- Dataset: Select by Instance Set
- Condition Name: Access the Business Units for which the user is explicitly authorized
- Actions: Maintain Recall notice
Assign Organizations to Quality Actions
When you add an organization to a quality action, it defines the primary location where that quality action must be executed or resolved. With this update, you can assign a specific organization to a quality action when you create the action, or any time prior to workflow approval.
New Organization Attribute in Create Dialog
New Organization Attribute in Search
Users have the ability to filter quality actions by organization in searches and restrict visibility of the quality action to only the users from the assigned organization.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Existing quality actions aren't automatically assigned to organizations during the update.
Key Resources
Role Information
Users who are assigned this predefined job role are automatically able to access this feature:
- Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
Note that users who need to create or access quality actions for an inventory organization must also be assigned to that organization. You can use the Manage Data Access for Users task in the Setup and Maintenance work area to assign users to organizations.
If you are using your own configured job roles to access quality actions, make sure that these job roles are assigned to the right data security policies in the Security Console, specifically: Grant on Inventory Organization.
The following data security function should be entered for your user-defined roles in the Security Console for the Quality Actions Data privileges:
- Policy Name: Grant on Inventory Organization
- Database Resource: Inventory Organization
- Dataset: Select by Instance Set
- Condition Name: Access the inventory organization parameter for table INV_ORG_PARAMETERS for the inventory organizations in which they can operate.
- Actions: Manage Quality Organization
Enable Suppliers to Create and Manage Problem Reports and Corrective Actions
Enable suppliers to create and manage problem reports and corrective actions from the Quality section of the Supplier Portal. Suppliers can initiate a problem report to report a problem or raise corrective action when a problem is reported and submit it to internal users. Internal users can initiate problem reports or corrective actions and share them with suppliers for further collaboration.
Quality Section in Supplier Portal Tasks Pane
Manage Problem Reports in Supplier Portal
Manage Corrective Actions in Supplier Portal
Leveraging Oracle's Supplier Portal Cloud, quality engineers in your supplier organizations can create and respond to quality problem reports using a secure, integrated work area, and engage in collaboration to take quick corrective action.
Centralized visibility and streamlined, standardized collaboration improves the completeness and timeliness of response to quality events. You can also improve product quality by eliminating communication gaps and promoting close collaboration with suppliers on problem reports and corrective actions.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- You can control the access and actions available to suppliers during object type setup. A Portal Users column is now available in the Additional Workflow Controls table for this purpose.
- Make sure you define the approvers and the default assignee for the problem report or corrective action type during the object type setup.
Key Resources
Role Information
You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Supplier Quality Engineer(ORA_ENQ_SUPPLIER_QUALITY_ENGINEER_JOB)
The supplier quality engineer must be assigned a data security policy with the following seeded condition to have access to the item change.
-
Seeded condition "Access the item change for table EGO_ENGINEERING_CHANGES_B for the item changes they created".
Users who are assigned configured job roles that contain all these privileges are able to access this feature:
- Access Supplier Portal Overview (POS_ACCESS_SUPPLIER_PORTAL_OVERVIEW_PRIV)
- Manage Supplier Problem Reports (ACA_MANAGE_SUPPLIER_PROBLEM_REPORTS_PRIV)
- Manage Supplier Corrective Actions (ACA_MANAGE_SUPPLIER_CORRECTIVE_ACTIONS_PRIV)
- Create Change Order(EGO_CREATE_CHANGE_ORDER_PRIV)
- View Item Change Order (EGO_VIEW_ITEM_CHANGE_ORDER_PRIV)
- Approve Item Change Order (EGO_APPROVE_ITEM_CHANGE_ORDER_PRIV)
- Modify Change Status (EGO_MODIFY_CHANGE_STATUS_PRIV)
The user with above privileges must be assigned data security policy with the following seeded condition to have access to the item change.
- Seeded condition "Access the item change for table EGO_ENGINEERING_CHANGES_B for the item changes they created".
Use REST Services to Manage Approvers for Future Approval Statuses
Add or remove approvers in quality management workflows using a REST API. You can now add or remove approvers for future approval statuses using the Workflow Approvers child resource in either the Quality Issues REST resource or the Quality Actions REST resource. The issue or action must not be in Draft status nor in Approval status.
SAMPLE CALL
curl -H "Content-Type: application/vnd.oracle.adf.resourceitem+json"-u user:pwd -X POST -d@payload "https://server:port/fscmRestApi/resources/latest/qualityIssues/123456789/child/workflowApprovers “
SAMPLE PAYLOAD
{"AssigneeType":"Role|User", "AssigneeName":“quality_analyst", "WorkflowStatusCode":"ORA_APPROVAL", "ActivityType":"Approval|Optional"}
Watch a Demo
You can now programmatically set or update approvers from external clients or from Application Composer groovy scripts. Improve productivity by eliminating the manual step of searching and adding users as approvers.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Key Resources
Role Information
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB) or
- Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)
Enforce Sampling Inspection Based on Acceptable Quality Limit
Most industries can use an acceptance sampling based on zero defects or a fixed percentage of the total quantity received. If you work in an industry that has a higher probability of rejection during acceptance sampling, this may not work. You require an objective way of controlling the quality of purchased materials based on varying quantities received, and even accepting defects within a tolerance limit.
Now you can define inspection levels with acceptance sampling based on different acceptable quality limits and apply them to mandatory receiving inspection plans that accommodate varying lot sizes. This type of sampling plan provides built-in, statistical quality control standards for determining the sample size based on the lot size. The acceptable quality limit is the percentage of the sample that can be rejected while still accepting the sample. For example, if the quantity received should contain no more than 2.5% of rejected material, then you enter the acceptable quality limit as 2.5.
When defining an inspection level, you can select the following information as part of an acceptable quality limit sampling plan:
- Sampling Standard: Single sampling plan for Normal, Tightened, or Reduced inspection
- Level: General Inspection Levels I, II, and III and Special Inspection Levels S1, S2, S3, and S4
- Acceptable Quality Limit: 0.065 to 1000
Acceptable Quality Level Sampling Inspection Level Definition
During the inline receiving inspection process, the quantity received is used to determine the number of units to be inspected and the number of accepted versus rejected units required to accept or reject the lot. In this scenario, the inspection lot is represented as the receipt line quantity instead of an inventory lot.
For example, if you receive 20 each for quality inspection, have a single sampling plan for normal inspection with general inspection level II, and have an acceptable quality limit of 2.5, the sample size is 5 each. The number of rejected units must be equal to or less than the acceptance number of zero to accept the receipt line quantity. If the rejected units are equal to or greater than the rejection number of one, the receipt line quantity is rejected.
Inspection with Acceptable Quality Level Sampling
Watch a Demo
To reduce the cost of an incoming inspection, you and your suppliers can agree on an acceptable quality limit that is appropriate for the criticality of the material being received. With acceptable quality limit-based sampling, you can enforce a standards-driven sampling scheme that reduces your risk of receiving unacceptable materials and encourages suppliers to achieve quality levels better than the process averages.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)
- Receiving Agent (ORA_RCV_RECEIVING_AGENT)
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Edit Inspection Results (QA_EDIT_INSPECTION_RESULTS)
Notify Users About Assignment Changes for Quality Issues and Quality Actions
Automatically send a notification to the assignee when you add an assignee to a newly created quality issue or action or the assignee is changed. The assignee receives an FYI notification and optionally an FYI notification email.
Sample Notification
Assignees to quality issues and quality actions get immediate notification of issues and actions that have been assigned to them, thus eliminating delays and improving time to response.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB) or
- Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)
Search Inspections Based on Lot Number or Date Range
With this update, you can use the new lot number search filter to quickly find inspection results for an item and lot. You can also search for inspections using the new date range filter, rather than being limited to searching for a specific date and time.
Inspections Search
These new search filters provide better accuracy and efficiency for searching inspection records.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Lot number is not shown by default on the Search Inspection page. You must add the search filter and search result column for Lot to search and view inspections by lot number.
- The search filters for From Inspection Date and To Inspection Date reflect the server time zone in Coordinated Universal Time (UTC).
Role Information
You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.
Users who are assigned any of these predefined job roles are automatically able to access this feature:
- Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)
- Receiving Agent (ORA_RCV_RECEIVING_AGENT)
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
- Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Edit Inspection Results (QA_EDIT_INSPECTION_RESULTS)
- View Inspection Results (QA_VIEW_INSPECTION_RESULTS)
Other Quality Management Changes in This Update
This section includes details about additional changes in this update that can change the way Oracle Quality Management Cloud works.
Create a Receiving Inspection Plan for all Purchase Order Suppliers of an Item or Item Category
After updating to 20D, you can define a Receiving inspection plan that's applicable to all suppliers without specifically adding inspection criteria records for each supplier. This allows you to create an inspection criterion for a document type of Purchase Order, while leaving the Supplier field blank. The unique combination of item or item category and inspection criterion is validated during inspection plan approval and is used to select the appropriate inspection plan during inline receiving inspection.
Bug reference: 27754623
IMPORTANT Actions and Considerations
Product Hub: Usage of Defaulting Control for Items with Dual UOM
If you use dual units of measure in contract manufacturing or outside processing items, you must avoid setting the value of the Defaulting Control attribute to No Default. In an approaching update, the No Default value won't be allowed for contract manufacturing or outside processing items. This attribute is set on the Overview tab of the Create Item or Edit Item pages in the Product Information Management work area.