This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
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 |
|---|---|---|---|
| 01 FEB 2022 | Product Development | Launch Change Order Reports Directly from Product Development | Updated document. Corrected a Key Resources link. |
| 27 APR 2021 | Product Development and Product Hub Common Features | Control Role Expansion for Group Approvals | Updated document. Revised feature details. |
| 27 APR 2021 | Product Hub | Configure New Item Request and Change Order Approval Notifications Using BI Publisher | Updated document. Revised feature details. |
| 18 MAR 2021 | Product Development | Accelerate Searches for Affected Objects and Structure Components | Updated document. Changed the opt-in expiration. |
| 18 DEC 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.
Manage Concept and Proposal Relationships Using REST Services
Use REST APIs to add or remove relationships for your concepts and proposals in Innovation Management.
Sample Request:
curl -u user:pwd -X GET https://server/fscmRestApi/resources/latest/productProposals/<proposal id>/child/Relationships
Sample Response:
{
"items" : [ {
"RelationshipId" : 300100218408537,
"RelationshipType" : "ORA_FULFILLS",
"CreatedBy" : "PLM_AUTO",
"CreationDate" : "2020-09-21T09:22:46+00:00",
"LastUpdateDate" : "2020-09-21T09:22:54.011+00:00",
"LastUpdatedBy" : "PLM_AUTO",
"DestObjType" : "IDEA",
"DestObjId" : 300100031871533,
"SrcObjType" : "PROPOSAL",
"SrcObjId" : 300100218408478,
"Name" : "Flying Bike",
"Description" : null,
"Status" : "Accepted",
Watch a Demo
Set proposal and concept relationships from an external client, from Application Composer (using Groovy scripting), or through legacy data import using a REST service.
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
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 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)
Accelerate Searches for Affected Objects and Structure Components
Accelerate your change definition process with faster searches. You can now use advanced search and keyword search to find the affected objects you want to add to a change order, and the component items you want to add to a structure.
Use this feature to add affected objects to:
- Engineering change orders
- Engineering change requests (including change requests on Supplier Portal)
- Change orders without revision control
- Commercialization change orders
- Problem reports
- Corrective actions
And components to:
- Structures in redline view
- Structures of a preliminary item
You can also search for an item using its extended flexfield attributes.
Search for Affected Objects
Search for Items in Structure View
Keep the user experience consistent across the application when adding items to structures and affected objects to change orders. In addition, refine your search using item attributes (including extended flexfields) as search parameters.
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 21C
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)
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
- Product Design Manager (ORA_ACD_PRODUCT DESIGN_MANAGER_JOB)
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
Launch Change Order Reports Directly from Product Development
Launch OTBI reports for a change order directly from the Product Development work area.
With this update, you can use the Actions menu on the change order to view and launch preconfigured reports. Click Actions > View Reports.
Launch Configured Reports from the Change Order
Select Configured OTBI Report
Context values of standard attributes are passed dynamically to reports.
Change Order Dashboard in OTBI
Watch a Demo
Easily access reports for your change orders directly from the object page Actions menu.
Steps to Enable
You must map the report settings in Oracle Transactional Business Intelligence (OTBI) to the report settings in the Setup and Maintenance work area. The configuration procedure is similar for changes and items. For changes, you must choose the Change business object and appropriate report context when setting up the report path and parameters.
Here are the high-level configuration tasks to enable this feature:
In Oracle Transactional Business Intelligence:
- Create the report and select report filters.
- Create dashboard prompts for the report.
- Create a dashboard for the report.
In the Setup and Maintenance work area:
- Configure the report path and parameters. Choose Change as the business object and set the appropriate context for the report, for example, Affected Objects.
- Map the parameters to the folder and column settings in OTBI.
- Validate your configuration.
Key Resources
-
Watch Direct Reports and History Tracking Readiness Training
- For more details on configuring Product Management reports, see the following:
Role Information
Users who are assigned configured job roles that contain this privilege are able to access this feature:
- View Product Management Reports (ACA_VIEW_PRODUCT_MANAGEMENT_REPORTS_PRIV)
Gain Additional Insights Into Pending Revisions
Analyze AML and attachments for pending item revisions using the Structures and Components Subject Area in OTBI.
The Structures and Components Subject area helps you identify the correct AML and attachments for a pending revision at the parent level, taking into account all the AML and attachment changes occurring in the change order associated with the revision.
Sample Analysis with Pending AML
Sample Analysis with Pending Attachments
Gain insight and take early action by understanding the changes to AML and attachments on the structure.
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).
Tips And Considerations
Only AML and attachment changes on the parent item assembly are shown.
AML and attachments for child components are based on the revision of the components associated with the parent item. If child components have AML and attachment changes resulting from other change orders, they are not shown.
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)
- Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY)
- BI Consumer Role (BIConsumer)
Leave Revision Blank During Change Order Creation
Engineering change orders require the new revision number to be specified for any affected object. A revision bump-up mechanism calculates the new revision number automatically. But in some cases the bump-up mechanism can't determine the new revision. If this happens when you create a new change order using Save As or when you assign an item using Assign to Change Order, the process fails to complete.
With this update, you can perform the Save As and Assign to Change Order actions with a new blank revision, so that the process completes successfully. You can then define the new revision number manually.
The application ensures that a new revision is defined for all affected objects in an engineering change order before submitting the change order for approval.
Blank Revision Number Field in an Engineering Change Order
Ensure that the change creation and definition process completes successfully even if users leave the revision field blank. This translates to more efficient processing of data, and less user training effort.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
As long as the new revision is blank, the application will not allow you to see or edit the revision-level attachments for the affected object in the change order context.
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)
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
- Product Design Manager (ORA_ACD_PRODUCT DESIGN_MANAGER_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)
Export and Import Item Classes and Child Entities
Use enhanced export and import content to support migration of item class data. The additional child entities provided include: attachment categories, descriptive flexfields, number/description generation content, new item request workflow definition details, change order type, transactional attributes, item class lifecycle phase, and import formats.
The export and import of item classes supports both XML and CSV formats.
The steps to export item class content in CSV format are:
-
In the Setup and Maintenance work area, use the Manage Item Classes task:
- Offering: Product Management
- Functional Area: Items
- Task: Manage Item Classes
-
In the row for the Manage Item Classes task, use the Actions control to select Export to CSV File > Create New.
-
A CSV file will be created for all item classes. Use the Export to CSV File > View All action to view the export results.
The item class export using XML format uses a different set of steps:
- In the task panel of the Setup and Maintenance work area, select the Manage Implementation Projects task.
- Create a new implementation project then select and add only the Manage Item Classes task. Close this task.
- In the task panel, select Manage Configuration Packages.
- Create a new configuration package using the implementation project that you created.
- Submit the configuration package to initiate the export.
- At the bottom of the Manage Configuration Packages page, monitor the export process and view the export results.
Improve your pod-to-pod migration efficiency and accuracy by utilizing the improved Export and Import Item Classes feature. This feature speeds up the process of creating item classes while also eliminating manual migration configuration errors.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
-
Setup Migration Best Practice, Customer Connect Session: https://cloudcustomerconnect.oracle.com/posts/f5824ff03f
- Refer to the Oracle SCM Cloud Using Product Master Data Management guide, available on the Oracle Help Center.
Role Information
- Privilege Name and Code:
- Manage Item Classes (EGP_MANAGE_ITEM_CLASS_PRIV)
- Job Role Name and Code:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
- Product Hub Administration Duty (ORA_EGI_PRODUCT_HUB_ADMINISTRATION_DUTY)
Improve integration capabilities by including the Request ID and Object Version Number attributes in the publication payload for items, catalogs and trading partner items. The Request ID value is updated when content is imported through the item batch infrastructure and is published as part of the publication payload allowing the items published to be filtered by this value.
The Object Version Number value is used by integration to indicate if the object is newly created or updated. A value of '1' indicates the object was created and each time the object is updated the value increases by '1'.
Streamline syndication with your integrated systems by being able to quickly identify items imported together. Also, speed up updates to downstream systems by being able to quickly identify only those items with deltas.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Publication Customer Connect Session: https://cloudcustomerconnect.oracle.com/posts/be58f99309
- Refer to the Oracle SCM Cloud Using Product Master Data Management guide, available on the Oracle Help Center.
Role Information
- Privilege Name and Code:
- Publish Item (EGI_PUBLISH_ITEM_PRIV)
- Publish Item Class (EGI_PUBLISH_ITEMCLASS_PRIV)
- Publish Catalog (EGI_PUBLISH_CATALOG_PRIV)
- Manage Trading Partner Item (EGP_TRADING_PARTNER_ITEM_PRIV)
- Job Role Name and Code:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
Check for Item Match Upon Item Update
Previously data quality checks were performed only at the time of item creation. Any potential duplicates were identified and shown to the user when new items were created. Now, whenever an item is updated, the data quality matching check runs, displays matching items, and prevents possible item duplicates. The duplicates are identified based on matching attributes or trading partner items associated with the item.
Edit Item Data Quality Check for Potential Duplicate
In the edit item UI flow, potential duplicates are shown in the familiar Data Quality pop-up. Based on the matching attributes or trading partner items being updated, the matching region shows all the similar duplicate items that have the same values. This matching display allows you to decrease the chances of creating duplicate items.
In the import flow, potential duplicates are shown in the data quality subtab of the In-progress tab of the batches page, which allows the data steward to select one of the items and allows the steward to update entity values based on import data.
Increase your enterprise accuracy by decreasing chances of erroneously creating duplicate items on update in your Product Information Management work area. This matching check eliminates loopholes that could allow duplicate items to be created. The duplicate item check is now more robust by match-checking when an item is updated.
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
- The opt in is a permanent opt in.
- The profile Allow New Item Creation When a Item Match is Found is used, in addition to the opt in, to determine whether potential duplicates are shown to the user and what actions can be performed by the user.
- During import, select one of the matching items to allow the import to update the attribute values of the matched item instead of changing the item provided in the import.
Key Resources
- Customer Connect session: Improve product data quality using Product Hub
- Watch Item Management, Data Consolidation and Analytics Readiness Training
- 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)
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD)
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)
Update and Delete Attachments Through Import
You can now use import maps, FBDI, and the Item Batch Maintenance SOAP service to delete existing attachments of items, item revisions, trading partner items, and use FBDI to delete catalogs and category attachments.
You can now also update the attachment file and category of existing attachments through import using import maps, FBDI, and the Item Batch Maintenance SOAP service.
To delete an existing attachment through import, the Transaction Type attribute should be DELETE, and to update an existing attachment through import, the Transaction Type attribute should be set to UPDATE or SYNC.
To update or delete a File, URL, or Repository File/Folder type attachment, the existing attachment will be identified during import using a combination of attachment category and file/URL/text attributes. If multiple attachments are found with this combination, then the attachment title will be used to identify the existing attachment to update or delete. If the inclusion of the attachment title still doesn't uniquely identify the existing attachment, then the import process will fail.
To update or delete a Text type attachment, the existing attachment will be identified during import using a combination of attachment category and title attributes. If multiple attachments are found using this combination, then import process will fail.
You can use the New Attachment Category, New File URL Text, and New Title attributes to update the attachment category, file/URL/text, or title of existing attachments through import.
For File and Repository File/Folder type attachments, to upload new files to existing attachments, you need to provide the new files to the import process by zipping them in a zip file.
The following screen capture illustrates this feature and its benefits.
Import Map New Attachment Attributes
Watch a Demo
This feature allows your business to more easily maintain (update and delete) an attachment or an attachment category through various import formats; this in turn allows your business to choose the format that best fits its requirements.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- The following new attributes are now added in the EGP_ITEM_ATTACHMENTS_INTF sheet of items FBDI and in the Attachments sheet of catalog FBDI to update attachment category, file, and title of existing attachments: New Attachment Category, New File URL Text, and New Title.
- The Transaction Type column on the EGP_ITEM_ATTACHMENTS_INTF sheet of items FBDI and the Attachments sheet of catalog FBDI, now supports the DELETE value to delete existing attachments through import.
- The following new attributes are now added under the Attachment node of import map’s master data region to update attachment category, file, and title of existing attachments: New Category, New File Name, and New Title.
- You cannot save an import map as external if any one of these attachment attributes are mapped: New Category, New File Name, and New Title.
- In import map smart spreadsheets, the Transaction Type attribute for attachments now supports the DELETE value.
- The following new attributes are now added to the Attachment interface of Item Batch Maintenance SOAP service to update attachment category, file, and title of existing attachments: NewAttachmentCategoryName, NewFileUrlText, and NewTitle.
- If no existing attachments are found during import using the given combination of attachment category and file/URL for File, URL, or Repository File/Folder type attachments, then the import process will fail.
- If no existing attachments are found during import using the given combination of attachment category and title for Text type attachments, then import process will fail.
- For the SYNC transaction type, the attachment will be updated if it exists, or will be created if it does not exist.
- If the attachment category of an existing attachment is changed to another attachment category with the Primary attribute set to Yes through import, and a primary attachment already exists for that attachment category on the item, then the attachment being imported will get set as the primary attachment after successful import. The Primary attribute of the existing attachment will be unchecked after successful import.
Key Resources
- Watch the Import Item Attachments Demo
- Refer to Import Item Attachments in the Oracle SCM Cloud Using Product Master Data Management guide on the Oracle Help Center
- Customer Connect Event, Importing Items using Import Maps
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)
- 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 Batch (EGI_MANAGE_ITEM_BATCH)
- Manage Item Import Map (EGI_MANAGE_ITEM_IMPORT_MAP)
Use Import Map Smart Spreadsheets on Macs
You can now use import map smart spreadsheets to generate data files and import items on Macs.
The following screen capture illustrates this feature and its benefits.
Import Map Spreadsheet On Mac
This feature gives more flexibility to your business by allowing the use of smart spreadsheets on both Mac and Windows operating systems.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- The data file generated from the smart spreadsheet is saved to the same folder in which the smart spreadsheet resides.
- If more than 256 attributes are mapped in the import map, you need to save the smart spreadsheet as a macro-enabled workbook before using it.
- Smart spreadsheets on Macs do not write some multi-byte characters of certain languages in the generated data file. You need to enter those multi-byte characters in the generated data file by editing it.
Key Resources
- Customer Connect Event, Importing Items using Import Maps
- Refer to Import 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 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:
- Manage Item Import Map (EGI_MANAGE_ITEM_IMPORT_MAP)
- Manage Item Batch (EGI_MANAGE_ITEM_BATCH)
Search UOM by Class Description
When creating items and selecting a unit of measure, you can now search for the UOM by UOM class description also. When the UOM class is a cryptic, short code, searching the UOM based on the UOM class description helps increase productivity and reduce errors.
Unit of Measure Class Description
Improve your business's efficiency by speeding up the search process. If you don't know a UOM code, you can now search using the UOM description instead of having to look up a code before being able to use it in the search criteria.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The unit of measure class description will be visible across all locations where the unit of measure item attribute is available.
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
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)
Integrate with External REST Services Using Rules
You can now invoke REST services from within item rules to query data from other sources.
You will first register the REST web service using Application Composer. Then, you can use the InvokeRestGet( ) function in rules to call REST services and perform a GET operation. A value returned by the service can be used for assignment or validation of an item attribute value.
Rule to invoke REST service
This feature extends your business's reach for creating accurate and current data by allowing your business to use business objects external to Oracle Product Hub Cloud when assigning or validating attribute values.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
When you register a REST service using Application Composer, you can register the URL with tokens or without tokens.
- If you have registered the endpoint URL without tokens, you can use the function InvokeRestGet( )
The syntax is InvokeRestGet(rest_service_name, map_of_query_parameters, return_value_expression)
- If you have registered the service URL with tokens, then you can use the function InvokeRestGetWithTokens( )
The syntax is InvokeRestGetWithTokens(rest_service_name, token_value1, token_value2, ... , token_value_n, return_value_expression)
Key Resources
- Watch Item Rules Readiness Training
- Refer to the chapter on Product Rules in the Oracle SCM Cloud Implementing Product Management guide, available on the Oracle Help Center.
- Refer to the chapter on Quick Start in the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.
- Refer to the solution playbook Access PaaS data from a cloud application using web services, available on the Oracle Help Center, for details on how to invoke a RESTful web service.
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 the privilege Manage Item Rule Set (EGO_MANAGE_ITEM_RULE_SET_PRIV) are automatically able to access this feature.
Update Your Configured Object Data Using Rules
You can now update your configured object values using item rules.
Using the new function updateCustomObjectValues() in rules, you can query your configured object data row, and then update the row.
Your Configured Object Data
Rule Showing the Function to Update Your Configured Object Value
This feature can decrease the workload for your entire enterprise. Now you can lessen the maintenance needed to external business objects outside of Oracle Product Hub Cloud by using item rules defined in the Product Information Management work area to update your external business objects, thereby keeping them accurate and current.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
You can optionally use the function to return a value from your configured object after update. The returned value can further be used for assignment or validation.
The syntax for the new function is:
updateCustomObjectValues( Custom Object Name, toMap(Custom Object Query Attribute, Value), toMap(Custom Object Attribute1 to update, Value1, Custom Object Attribute2 to update, Value2,.......,Custom Object AttributeN to update, ValueN), Custom Object Return Attribute)
The Custom Object Return Attribute is optional; it can be used to query the value from your configured object attribute.
Key Resources
- Watch Item Rules Readiness Training
- Product Rules chapter in the Oracle SCM Cloud Implementing Product 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 the privilege Manage Item Rule Set (EGO_MANAGE_ITEM_RULE_SET_PRIV) are automatically able to access this feature.
Report Item Catalogs and Category Hierarchies Using OTBI
You can now build OTBI reports on item catalog category hierarchy data more effectively.
Using the new BI subject area Item Catalog Category Hierarchy, you can create reports by including multiple levels of category hierarchy.
You can have a 360 degree view of item catalog category hierarchy data by creating reports with items and item attributes, the catalogs and categories to which the items are assigned to and their respective category hierarchies. You can also generate reports with different views of catalog setup such as list of item categories of a catalog.
BI Report Showing Item Catalog Category Hierarchy
Reporting item catalog and category hierarchies using OTBI gives your users additional methods in which to view your business' catalog category hierarchy. A configurable and more reader-friendly format in which to view the catalog and category hierarchy could lead to easier detection of inefficiencies or errors in your business.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
After making changes to existing catalog setup, you need to run the scheduled process Refresh Product Hub Snapshots before creating or viewing OTBI reports on catalog hierarchy.
Key Resources
- Watch Analytics, Setup and Web Services Readiness Training
- Refer to 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)
Users who are assigned the privilege Refresh Material View (EGI_REFRESH_MTL_VIEW_PRIV) are able to run the scheduled job that refreshes the snapshots of Product Hub.
Release Claim on New Item Request Definition Tasks
Use a new Release Claim action to release a claimed task. If you have claimed a new item request definition task that requires a response only from one user, you can release this claim so that it can be claimed by another user with the same role.
You can also release all your claims simultaneously with a Release All Claims action.
Release Claim to One Task or All Tasks
Make your business processes flexible enough to tackle the times when a task can't be completed by the original claimer due to unforeseen situations. The claim on the task can now be released so that it can be claimed and completed by another user.
Steps to Enable
You don't need to do anything to enable this feature.
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 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)
Configure New Item Request and Change Order Approval Notifications Using BI Publisher
Design and configure approval notifications for new item requests and change orders using Business Intelligence Publisher.
Configure the layout, style, and content of the predefined notification template according to your needs, taking into account your corporate identity design. You can also configure additional attributes such as new item requests/change order descriptive flexfields as per your requirement. After you save your changes, you can set this template as your default notification template.
The following screenshots show sample approval notification templates and notifications for new item requests and change orders.
Sample New Item Request Approval Notification Template with Added Attributes
Sample New Item Request Approval Notification
Sample Change Order Approval Notification Template
Sample Change Order Approval Notification
Expose attributes relevant for your business in approval notifications to help assignees make informed approval decisions for new item requests and change orders. You can also tailor the look and feel of your notifications to reflect your brand identity and enhance the 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 22D
For details about using Business Intelligence Publisher to configure notifications, see the Reports Modification chapter in the Creating and Administering Analytics and Reports for SCM guide, available on the Oracle Help Center.
When you create your new BI Publisher template, make sure you save it in the appropriate folder in BI Publisher.
Tips And Considerations
- If your business process requires a signature policy or disallows approval comments as configured in the BPM Worklist, it is recommended that you don't opt in to this feature.
- In update 21A, you can add attachments through the change order and new item request BIP notifications, but it is recommended that this feature not be used.
Key Resources
- Watch Direct Reports and History Tracking Readiness Training
- Reports Modification chapter in the Creating and Administering Analytics and Reports for SCM 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:
- Roles to view the configured notification for new item requests
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB) or
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
- Roles to view the configured notification for changes
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
- Roles to configure the notification template
- BI Author Role (BIAuthor)
- BI Publisher Data Model Developer(BIPDataModelDeveloper)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Privileges to view the configured notification for changes
- Approve Item Change Order (EGO_APPROVE_ITEM_CHANGE_ORDER_PRIV)
- Privileges to view the configured notification for new item requests
- Manage item (EGP_MANAGE_ITEM_PRIV)
- Manage New Item Request (EGO_MANAGE_NEW_ITEM_REQUEST_PRIV)
Integrate and Extend Product Hub Using REST Services
Query Item Classes and Lifecycle Phase Using a REST Service
Use the new Item Classes REST API to get the basic details of an item class. Use the associated Lifecycle Phases child REST resource to fetch all the lifecycle phases associated with the item class.
The basic details of the item class consist of: Item Class Name, Internal Name of the Item Class, Enabled Flag, Parent Item Class Name, Parent Item Class Description, Item creation Allowed flag, and Public or Private flag.
The Lifecycle Phases child REST API fetches the details: Phase Code, Phase Name, Phase Sequence, Start Date, Phase Type, End Date, and Associated Item Class.
Simplify your enterprise integrations by being able to programmatically retrieve item class details and the lifecycle phases associated with it. This allows your business to be more efficient by programmatically retrieving taxonomy details.
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
- REST API for Oracle Supply Chain Management Cloud guide available on the Oracle Help Center.
Role Information
Users who are assigned this predefined job role are automatically able to access this feature:
- EGP_VIEW_ITEM_CLASS
Manage Spoke System Item Relationships Using a REST Service
You can build enhanced integrations and extensions by using REST resources to manage spoke system item relationships.
Using the Spoke System Item Relationships REST API, you can create, update, delete, and search for spoke system item relationships.
Using a REST resource allows your business to be more efficient by automating the creation and maintenance of spoke system 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
- Watch Analytics, Setup and Web Services Readiness Training
- Refer to the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.
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 Spoke system item relationships.
- EGI_MANAGE_ITEM_REL_REST: For GET, POST, PATCH and DELETE on Spoke System item relationships.
Secure Items and Trading Partner Items Using a REST Service
Enable data security for items and trading partner items using the Secure an Object action of the Product Management Data Securities REST API. The new action supports changing the security state of items and trading partner items from public to private by specifying the Object Name, the name of the user or role, and the value for the Public flag. You can also change the security state of a group of trading partner items, using the new Secure an Object action by specifying the Object Name, the name of the user or role, the Trading Partner Name, the Trading Partner Item Type and the value for the Public flag.
This enhancement to the Product Management Data Securities REST API allows programs to be created that manage data security for items and trading partner items. The program now can change the data security state of items and trading partner items to private and to grant additional users or roles access to these objects.
This feature allows your business data to be made more secure, efficiently and programmatically.
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
- Data Security Customer Connect Session: https://cloudcustomerconnect.oracle.com/posts/afa20d9656
-
Refer to the REST API for Oracle Supply Chain Management Cloud documentation available on the Oracle Help Center.
Role Information
- Privilege Name and Code:
- Manage Product Management Data Security (EGO_MGT_PRODUCT_MGT_DATA_SECURITY_PRIV)
- Job Role Name and Code:
- Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
Product Development & Product Hub Common Features
Control Role Expansion for Group Approvals
Reduce the clutter in the Approvers table for a change order's approval status when you add roles that have a long list of members.
If only one response is required on behalf of a role or only one response is required per status, the role is no longer expanded to show its members. All members of the role receive approval notifications, and you can track who signed off on behalf of the role. The assignee field in the notification will not be expanded to show all its members.
If the approver is a role and Response Required From is set to All, the role will continue to be expanded to show all its members. It's still recommended to limit the number of members in a role to less than 50.
Group Role Expansion
You don't need to scroll through a long list to find out who took action on behalf of a role.
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 21C
Tips And Considerations
- IMPACT ON ONGOING APPROVAL WORKFLOWS
If you want to prevent role expansion in change orders that are currently in interim approval or approval status, you must terminate the approval workflow and restart approvals. You would also need to do this for ongoing approval workflows if you opt in for this feature and then decide to opt out later.
- IMPACT ON NOTIFICATIONS
Notifications are sent based on the configured response requirement:
- Response Required From = All: notifications are sent only to approvers added directly, not approvers inherited from the role hierarchy.
- Response Required From = One: notifications are sent to approvers added directly, as well as approvers inherited from the role hierarchy.
- One Response per Status - if the approver belongs to multiple roles, a single notification is sent to the first role in the list.
- If role is added as Optional Approval, it will continue to be expanded.
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) 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)
Enforce Additional Constraints for Deletion of Items and Changes
Delete constraints define rules to prevent accidental deletion of important data. Delete constraints are applied in the context of a Delete Group, which is used to manage the deletion of various object types. You can now validate item and change deletions against an expanded set of constraints.
Deletion is prohibited if the item:
- is used in another structure
- is an affected object of any change type or new item request
- is a Style item referring to SKU items
- is used as a substitute component
- is an affected object of a quality issue or quality action
- has a relationship defined in Product Development
The Check Constraint feature in the delete group runs the checks and reports whether these delete constraints are violated.
Delete Group
You can click the Details icon to review error messages related to the deletion.
Item Deletion Errors
Watch a Demo
Delete groups together with delete constraints restrict which users are allowed to delete data, and prevent the deletion of data which is still in use. This is a key feature to ensure data quality.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- If you delete a master organization item, the application automatically attempts to delete the associated child organization items. The item structure, attachment assignments, and team assignments are also deleted.
- An Item cannot be deleted, if it is an affected object in any change type, even if the respective change is pending or completed.
- Delete constraints apply for change orders, change requests and new item requests as well. You can only delete a change or new item request if it's in Draft or Canceled status. Also, you can't delete change orders and change requests if they have relationships defined in Product Development.
- When you delete a change order, its affected objects, workflow instance data, attachment assignments, team assignments, and security records are also deleted.
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 Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
- Product Design Manager (ORA_ACD_PRODUCT DESIGN_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)
- Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
- Manage Item (EGP_MANAGE_ITEM_PRIV)
- Manage Item Delete Group (EGP_MANAGE_ITEM_DELETE_GROUP_PRIV)
Improve Change Order History Tracking
Improve tracking of change order approval and rejection history with proper handling of approver comments. Comments can be defined as optional or mandatory in the approval task setup, depending on the regulatory requirements for your business.
If approval comments are mandated, comments entered by approvers are recorded in the approvers panel and in the action log. You can also see the comments in the approval task details accessed from the worklist. If an approver enters more than one comment in the approval task dialog, only the most recent comment is shown in the approver panel and in the action log associated with the approval task entry. You can see the full set of comments when you open the approval task details.
If approval comments are disallowed, no comments are shown in the approvers panel or the action log.
Approval Comment in Approvers Panel
Approval Comments in Action Log
Approval Comments in Approval Task Details
Watch a Demo
Streamline the change order approval process by preventing unnecessary comments from being captured in your change order. Ensure compliance with regulatory requirements regarding comment entry as part of approval or rejection.
Steps to Enable
You don't need to do anything to enable this feature.
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 Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
- Product Design Manager (ORA_ACD_PRODUCT DESIGN_MANAGER_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)
- Approve Item Change Order (EGO_APPROVE_ITEM_CHANGE_ORDER_PRIV)
Optimize Change Order Propagation
Configure propagation rules on commercialization change orders to replicate item structure modifications. For instance, you can propagate changes from the master organization item to one or more child organization items.
You can configure the application to automatically propagate changes or perform the propagation manually. If automatic propagation is activated, the propagation is triggered automatically when the source change order reaches Scheduled status. This creates a duplicate change order with the same item structure modifications in the target organization.
Enable Propagation Option in a Change Order
The action log tracks which change order was used as a source for propagation and which change order was created by propagation.
Propagation Details in Change Order Action Log
Leverage propagation to quickly replicate structure modifications from one item to another, ensure consistency between items in different organizations, and ensure product data quality.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Propagation of change orders is available for commercialization change orders created using the Simplified Change Management Interface. Propagation rules are configured during change order type setup.
When using this feature, note the following:
- You can trigger propagation if the source change order is in Scheduled status. The target change order will be created in Open status.
- The propagation is supported for items in definition organizations only (source and target).
- If the effective date of an affected object is set as Effective on Approval, you must enable automatic propagation.
- When propagating an item structure, make sure that the component items are already available in the target organization.
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 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 Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
Expand Item and Change Capabilities
You can now use the Get Master Org REST API to retrieve master organization details such as the Master Org ID. Also, you can create relationships between multiple change orders on a commercialization change order in the Product Information Management work area.
RETRIEVE MASTER ORG DETAILS
Sample Response Payload
Get Request Sample:
https://hostname/fscmRestApi/resources/11.13.18.05/productDevelopmentConfigurations
ADD RELATIONSHIPS ON COMMERCIALIZATION CHANGE ORDERS
In the Relationships tab of the commercialization change order, you can set relationships with the following change order types:
- Engineering change order
- Change order without revision control
- Commercialization change order
The Relationships tab of the commercialization change order also displays relationships that are already set up from the Product Development and Innovation Management work areas.
Add Relationship in Commercialization Change Order
Retrieve and update item and change information programmatically to increase business efficiency.
- Retrieve master organization details - Enable integration users to filter items by master organization.
- Add relationships on commercialization change orders - Leverage relationships to group change orders that are split due to a large number of affected objects. Also, enable users to navigate directly to related objects.
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:
- Get Master Org Details : Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
- Add Relationship To Commercial Change Order : Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
Display Date and Time Based on User Time Zone
Enable users to see the date and time based on their time zone preference across date fields on Product Hub commercialization change orders and the Product Development work area.
Date and time attributes appear in the user's preferred time zone for:
- Product Hub commercialization change orders viewed in the Simplified Change Management Interface
- All Product Development change order tabs with date and time attributes
- Product Development item tabs: General Information, Structures, and Changes
- Quality issues and quality actions: General Information tab
- Manufacturer and manufacturer parts: Search results table
Time Stamp and Time Zone on Change Order Workflow Tab
Time Stamp on Change Order Affected Objects Tab
Time Stamp on Item Structure Tab
:
Time Stamp on Manufacturers and Manufacturer Parts Search Results
Provide a consistent view of date and time attributes across change orders, items, quality issues and actions, manufacturers, manufacturer parts and their attachments.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The Changed On field in the change order shows the name of the time zone (for instance, PST) next to the date. Other date fields don't show the name, but the date and time is shown in the user's time zone.
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)
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
- Product Design Manager (ORA_ACD_PRODUCT DESIGN_MANAGER_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)
- Manage Item (EGP_MANAGE_ITEM_PRIV)
- Manage Trading Partner Item Reference (EGP_MANAGE_TRADING_PARTNER_ITEM_REFERENCE_PRIV)
Use an Enhanced View for Where Used Data
View item class and lifecycle phase columns in the Where Used table. You can view this information for the first level, top level, or all structure levels. You can also filter item class and lifecycle phase data using Query By Example.
Item Class and Lifecycle Phase Columns in Where Used Report
With this update, you can do the following:
- Quickly access item class and lifecycle phase information.
- Easily identify items that may be impacted.
- Enjoy a consistent user experience across Product Development and Product Information Management work areas for actions such as Export to Excel, Copy to Clipboard, Freeze, and Wrap.
Search Results Table with Additional Actions and Columns
Steps to Enable
You don't need to do anything to enable this feature.
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:
For the Product Development work area:
- Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB) or
- Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
For the Product Information Management work area:
- 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:
For the Product Development work area:
- Manage Item (EGP_MANAGE_ITEM_PRIV)
For the Product Information Management work area:
- Access Clipboard (ACA_ACCESS_CLIPBOARD_PRIV)
Enforce Sampling Inspection for a Work in Process Plan in Manufacturing
Today you can enforce the inspection of 100% of the consecutive units produced while completing a manufacturing work order operation. After the inspection is done, you can report on the operation quantity completed, rejected, or scrapped based on the number of units with accepted or rejected inspection results, respectively. However, once a manufacturer has produced a number of units with consistent good quality, they may not be able to test every product due to high volume production or the cost and cycle time of inspection.
With this feature, you can now select representative samples out of a discrete or process manufacturing work order operation quantity to determine the quality of a nonserialized work in process (WIP). WIP sampling is supported through the Review Dispatch List page and the Inspection Results REST services.
When defining an inspection level, you can specify sampling based on a percentage of the quantity produced, a fixed count of samples, or based on the statistical standards for Acceptance Quality Limit (AQL). In percentage-based sampling, any inspection failure can reject the entire quantity being completed at that operation. In AQL inspection, the system statistically determines the number of samples from the quantity produced and the maximum number of rejected units allowed in order to qualify for acceptance. You can associate a sampling-enabled inspection level with a mandatory WIP inspection plan to enforce inline WIP sampling.
Defining a Work In Process Inspection Plan with User Defined Inspection Level
During the inline WIP inspection process, you can complete the full or partial work order quantity at an operation using the Quick Complete or Complete with Details flows on the Review Dispatch List page. The quantity being completed at the operation is used to determine the number of samples based on the inspection level required by the WIP inspection plan. Then you can select this number of units at random for sampling and inspection to proceed with the operation transaction.
Inline Work In Process Inspection with Sampling
After results are entered for the required samples, the inspection is accepted or rejected based on either acceptance sampling logic for percentage-based and fixed count sampling or AQL standards and is applied to the entire quantity produced at the operation. If an initial sample failure is reported in percentage-based or fixed count sampling, you can also increase to 100% inspection to inspect the rest of the quantity. Saving the inspection results also drives the corresponding operation transactions for completed and rejected quantities. With the appropriate privilege, you can move the rejected quantity to scrap for disposal.
Watch a Demo
WIP sampling combined with flexible WIP inspection levels help manufacturers reduce the cost and scope of inspection to reach reliable conclusions about their product quality.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- WIP sampling can also be used with fixed count sampling. Refer to the Perform Sampling Inspection with a Fixed Count Inspection Level feature for more information.
- For discrete manufacturing work orders, inline WIP sampling can apply to work in process at an intermediate operation or the product at the last operation. The accepted quantity from inspection matches the product completion quantity at the last operation.
- For process manufacturing work orders, inline WIP sampling can apply to work in process at any operation, where the inspection quantity is considered representative of the batch quantity being completed at the operation. Ad hoc WIP inspection is recommended for inspecting the primary product, co-product, or by-product in process manufacturing.
- Similar to the existing inline WIP inspection process, WIP sampling is enforced prior to product or output completion when a lot number is assigned.
- The Inspect All feature increases percentage-based and fixed sampling to 100% inspection and does not apply to AQL sampling inspection.
- Inline WIP sampling does not apply to serial-controlled items or serial-tracked operations.
- Ad hoc WIP inspection allows the number of samples to be specified, so WIP inspection levels do not apply.
- The rejection rate of WIP inspections displayed in the Work Execution and Quality Management overview page infolet is based on the number of samples rejected out of the total samples and is unaffected by WIP sampling.
- You can analyze sampling-based WIP inspections in OTBI to help determine when you can manually switch inspection levels based on the historical detection of defects.
Key Resources
- Watch Enforce Sampling Inspection for a Work in Process Plan in Manufacturing Readiness Training
- Using Quality Management guide on the Oracle Help Center.
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)
- Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_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)
Perform Sampling Inspection with a Fixed Count Inspection Level
As an alternative to sampling based on a percentage sampling size or Acceptable Quality Limit, some companies need the flexibility to define a sample count that doesn't change based on quantities being received or produced. For example, a large work order only requires two samples for lab analysis and destructive testing purposes. Now you can define an inspection level based on a fixed count of samples and apply it to a mandatory receiving or work in process inspection plan. This type of sampling plan specifies the sampling size as a fixed count regardless of the receipt line quantity or work order quantity.
Fixed Count Inspection Level
During the inline inspection process, you take the predefined number of samples and test them based on acceptance sampling, which rejects the inspection quantity as soon as one defect is found with a rejected result. If the inspection results are inconclusive, you can also choose to increase the sampling size to 100% inspection of the remaining quantity being received or produced to further separate accepted and rejected quantities.
Sampling Inspection with a Fixed Count Inspection Level
Watch a Demo
With fixed count sampling, you can enforce the proper sampling size and procedure for your business, thereby reducing the costs associated with more samples and minimizing disruptions to operations.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Fixed count sampling can also be used with work in process sampling. Refer to the Enforce Sampling Inspection for a Work in Process Plan in Manufacturing feature for more information.
- Ad hoc inventory and work in process inspection allows the number of samples to be specified, so sampling-enabled inspection levels do not apply.
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)
- Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)
- Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_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)
Add Relationships Between Problem Reports and Corrective Actions
Create bi-directional relationships between Problem Reports and Corrective Actions from the Relationships tab of these objects. You can also use the Relationships tab of other objects in Product Development, Innovation Management, and Quality Management to add Problem Reports and Corrective Actions as related objects.
When you add a relationship, you can use simple search or advanced search to find the Problem Report or Corrective Action that you want.
Add Problem Report and Corrective Action from Relationships Tab
Organization details provided in the search results help you identify the correct object.
Search for Problem Reports
Relationships you create are listed along with its organization in the Relationships table.
Relationship Table for Problem Report Shows Corrective Action and Related Problem Report
Relationship Table for Change Order Shows Corrective Action and Related Problem Report
Relate objects to group similar product issues, identify patterns, and get a complete picture of impacted objects to ensure proper resolution.
Steps to Enable
You don't need to do anything to enable this feature.
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:
- Quality Analyst Job Role (ORA_ENQ_QUALITY_ANALYST_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV) or Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)
- Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
Additionally, you need to create a data policy with the following condition:
- Access the item change for table EGO_ENGINEERING_CHANGES_B for the item changes they have access to.
Cancel Workflows for Quality Issues and Actions
Cancel workflows for quality issues or actions that are created by accident or are no longer relevant. Use the Cancel action on an object to close its workflow and remove it from the infolets on the Overview page.
New Cancel Action in Actions Menu
Confirmation Dialog for Cancel Action
Cancellation Recorded in Quality Action Workflow Summary
Cancel workflows that were created in error, or are no longer required, so that you can keep your focus on relevant quality issues and actions.
Steps to Enable
Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.
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:
- Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
- Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)
Users who are assigned configured job roles that contain these privileges are able to access this feature:
- ENQ_CANCEL_QUALITY_ISSUE (for quality issues)
- ENQ_CANCEL_QUALITY_ACTION (for quality actions)
View Audit Details and Comments for Quality Issues and Actions in Side Panel
Use the side panel view on a quality issue or action to view audit details. You can see details for the object attributes that are configured for inclusion in the audit. Comments now appear in a side panel, instead of a dialog.
History Side Tab
Comments Side Panel
Watch a Demo
HISTORY SIDE PANEL
Gain instant access to audit details for a specific issue or action without having to navigate to the audit reports. You can easily track when it was created, updated, or deleted.
COMMENTS SIDE PANEL
Collaborate quickly and effectively to facilitate important quality processes. Use the Comments side panel to communicate issue details, share possible root cause and resolution, and clarify tasks. The side panel shows you a consolidated, uncluttered view of all the user comments for a quality issue or quality action.
Steps to Enable
You must enable auditing of quality issues and actions to see audit log entries in the History side panel.
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:
- Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
- Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)
Control Quality Object Creation with New Privilege
Use two different privileges to control who can create a quality object, and who can edit it. A new Create privilege lets you create, but not edit, quality objects. The Manage privilege lets you create and also edit quality objects.
Create Quality Issue Dialog
Enable non-quality personnel from other functional groups like production, development, or field service to create and view a quality issue or action. If you assign these users only the Create privilege, they can't edit or manage the object after creation.
Steps to Enable
Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.
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:
- Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
- Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)
All other roles, who can only create and not manage issues and actions, must be assigned the following new CREATE privileges:
- ENQ_CREATE_QUALITY_ISSUE
- ENQ_CREATE_QUALITY_ACTION
View Inventory Lot Split, Lot Merge, and Lot Translation in Genealogy
When dealing with goods that are under lot control, there are numerous events that might require you to break, combine, or transform some or all of the goods in a specific lot. For example, a weather event causes damage to your warehouse and spoils only a portion of a lot. The damaged portion of the lot is still usable for some, but not all, of your manufacturing processes. Thus, you need to split this quantity from the original lot and assign new lot numbers to ensure your goods are designated properly for future use. Similarly, maybe you regularly combine multiple lots into a single vat before use in downstream processes. When you merge all of these lots into a single vat, you assign a new and unique lot number. Finally, in some industries, a chemical reaction process might require that you change the assigned lot number of an item when the process is complete. For example, let’s say you complete a work order for item 123 into lot A. After two weeks, the reaction process is complete, and the lot should change to lot B. This change indicates that the item is ready for the next step. The item itself hasn’t changed, and the additional overhead of a work order just to change the lot number isn’t desired. Additionally, you need the lot history retained. In these scenarios, a work order isn’t required. Now you can perform lot splits, merges, and translations within Oracle Inventory Management Cloud using REST APIs or file-based data import (FBDI).
For historical traceability, you can track the lot genealogy data from the lot splits, merges, and translations and view these lot genealogy records through the Review Product Genealogy page. In genealogy details, the parent-child genealogy relationships for a specific lot are displayed visually using directional arrows and new filters for lot composition and lot where used, so you can trace forwards and backwards between the source lot and resultant lots. In the transaction history, you can filter the timeline for these inventory transactions by type and click through to review the lot split, merge, or translate transaction details.
Genealogy Details - Lot Split
Genealogy Timeline - Lot Split
The new split, merge, or translate lots feature lets you change lots dynamically and track its genealogy, without the additional overhead of creating a work order or performing extraneous inventory transactions.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Refer to the Perform Lot Split, Merge, and Translate Using REST APIs and FBDI feature under Inventory Management for more information.
- You cannot use the Product Genealogy REST APIs and FBDI to import lot genealogy data resulting from inventory lot split, merge, and translate transactions.
- You can view lot split, merge, and translate transactions in the Inventory Transactions Real Time subject area, but not the Product Genealogy subject areas in Oracle Transactional Business Intelligence.
Role Information
To use this feature, the following privileges or roles are required:
- Privilege Name and Code:
- Get Product Genealogy by Service (CSE_GET_PRODUCT_GENEALOGY_BY_SERVICE_PRIV)
- Manage Product Genealogy by Service (CSE_MANAGE_PRODUCT_GENEALOGY_BY_SERVICE_PRIV)
- Job Role Name and Code:
- Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)