Update 22B

Revision History

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

Date	Product	Feature	Notes
27 MAY 2022	Product Development & Product Hub Common	Replace Item Structure Components Using a Change Order	Updated document. Revised opt in and Tips and Considerations content.
27 MAY 2022	Product Development & Product Hub Common	Replace Item Structure Components Using a Web Service or Business Event	Updated document. Revised opt in content.
27 MAY 2022	Product Development	Freeze Columns in Item Structure Tables	Updated document. Revised description and Tips and Considerations content.
27 MAY 2022	Product Development & Product Hub Common	Analyze Substitute Component Data in OTBI	Updated document. Revised description.
09 MAY 2022	Product Hub	Selected Product Hub Bug Fixes in This Update	Updated document. Added two issues.
25 APR 2022	Product Development & Product Hub Common	Selected Product Development & Product Hub Common Bug Fixes in This Update	Updated document. Revised description of issue 33189023.
18 APR 2022	Product Development & Product Hub Common	Selected Product Development & Product Hub Common Bug Fixes in This Update	Updated document. Revised description of issue 33134165.
08 APR 2022	Product Development & Product Hub Common	Improve Change Workflow Resiliency	Updated document. Revised Role details.
18 MAR 2022			Created initial document.

Overview

IMPORTANT NOTE: If you are being updated directly from 21D to 22B you should review the content of both 22A and 22B sections to ensure you see all the changes included in the update.

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

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.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

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:

1. Click Navigator > My Enterprise > New Features.
2. 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.
3. 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.
4. 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:

1. Click Navigator > My Enterprise > Offerings.
2. On the Offerings page, select your offering, and then click Opt In Features.
3. On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
4. 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.

Feature Summary

Quality Management

Quality Management

View Origination Lot and Resultant Lot in Genealogy OTBI

Oracle Transactional Business Intelligence (OTBI) lets you create ad hoc reports using real-time transactional data from Oracle Cloud Inventory lot split, merge, and translate transactions to analyze your lot genealogy data. In this update, you can view additional lot details by adding the Origination Lot and Resultant Lot column to your genealogy reports in OTBI.

These new columns are now available in these Product Genealogy OTBI subject areas:

• Product Genealogy - Genealogy Instance Real Time
• Product Genealogy - Genealogy Instance Structures Real Time
• Product Genealogy - Genealogy Object Composition Real Time
• Product Genealogy - Genealogy Object Where Used Real Time
• Product Genealogy - Genealogy Transaction History Real Time

The new columns in the Product Genealogy OTBI subject areas give you additional reporting capability to help you quickly trace the genealogy of lot splits, merges, and translations and verify the details of the origination lot or resultant lot.

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

The lot split, merge, and translate transactions are already supported in the Inventory - Inventory Transactions Real Time subject area. You can create an OTBI report that combines data from this Inventory subject area and any Genealogy subject area using common dimensions such as Item and Lot. Refer to the documentation on cross-subject area joins for more information.

Key Resources

• Refer to the 21A Inventory Management What's New for Perform Lot Split, Merge, and Translate Using REST APIs and FBDI for more information about this feature.

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)

Use Long Text Attributes in Quality Reports for In-Depth Analysis

Add long text attributes into your quality reports to enable in-depth analysis of quality issues and quality actions. For example, you could add these fields to your reports to view quality issue descriptions, closure reasons, or resolution notes.

These attributes are Character Large Object (CLOB) fields configured using Application Composer. You can now find them under the Quality Issues and Quality Actions subject areas in Oracle Transactional Business Analytics.

Sample Analysis with Long Text Attributes in Quality Actions Subject Area

Include configured long text attributes to provide additional holistic analysis of quality issue and quality action objects.

Steps to Enable

To view these attributes, you must first add them to your reports from the relevant Custom Attributes folder under the subject area.

For quality action reports:

• Enterprise Quality Actions Real Time subject area > Quality Actions Custom Attributes

For quality issue reports:

• Enterprise Quality Issues Real Time subject area > Quality Issues Custom Attributes

Tips And Considerations

• Long text attributes enabled in quality issue and quality action objects using Application Composer are automatically visible in the respective subject areas.

• For faster loading of reports, limit the number of long text attributes in an analysis.

Key Resources

• For details on configuring long text fields, see the topic Long Text Fields in the Configuring Applications Using Application Composer guide under Applications Common, on the Oracle Help Center.

• For instructions on creating reports, refer to 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 can access this feature:
  • Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)

• Users who are assigned configured job roles that contain these privileges can access reports:
  • Transactional Analysis Duty (FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY)
  • Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY)
  • BI Consumer Role (BIConsumer)

Product Lifecycle Management

Innovation Management

Leverage a Unique Number Attribute for Ideas

You can now configure a number generation method for ideas, so that unique numbers are automatically assigned to the objects when you create them.

This unique number is displayed along with other object details such as the name and description for an idea in the General Information page, the Manage Ideas page, and in the notifications.

You can set up the numbering method to use a prefix and suffix to help classify and identify the type of object. For example : PROTO_1002_NAO.

Unique Number Generated for Idea

Ideas REST endpoints have been updated to include the unique number.

Import and export of setup data for the Product Requirements and Ideation Management functional area from the Setup and Maintenance work area now includes the sequence generation criteria defined for each product idea class.

Use automatically generated unique numbers to ensure an easily identifiable, consistent pattern of reference for your ideas.

Steps to Enable

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

• Offering: Product Management
• Functional Area: Product Requirements and Ideation Management
• Task: Manage Product Idea Classes

2. Open the idea class for which you want to configure number generation.
3. In the Number Generation Method field, select an option:

Inherited from Parent: Applies the same number generation method to all child classes of this parent class. This is the default setting.

Sequence-generated: Automatically generates values in a specified sequence, based on the increment setting. If you select this option, then enter the following criteria:

• Prefix: text that automatically appears before the number
• Suffix: text that automatically appears after the number
• Starting Number: the first number in the sequence (Default Value =1)
• Increment: Incremental difference between two numbers in the sequence (Default Value =1)
• Maximum Number of Attempts: the number of attempts the application must make to generate the next available unique number (Default Value =50)
• Description*: Description of the number generation method for that class. This is a mandatory field.

4. Save your changes.

Number Generation Tab in Idea Class Setup

Tips And Considerations

• For existing or old data, the Number attribute will be set to NULL. 
• Avoid duplicating the number generation configuration for different idea classes.

Key Resources

• Watch Replace Components and Add Reviewers Readiness Training.

• Refer to the Oracle SCM Cloud Using Innovation 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 can access this feature:
  • 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)
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

• To access the setup task, the following privilege is required:
  • ACA_SETUP_PRODUCT_INNOVATION_PRIV

• To create and manage ideas, the following privileges are required:
  • Create Product Idea (ACN_CREATE_PRODUCT_IDEA_PRIV)
  • Manage Product Idea (ACN_MANAGE_PRODUCT_IDEA_PRIV)

Selected Innovation Management Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Fusion Cloud Innovation Management works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

Create Proposal

Before this update, when you marked attributes as Optional in the current version of the proposal and Required in the new version, an error appeared and blocked the new version from being created. With this update, the issue is fixed.

Oracle reference: 33441378

Hide Actions Using Page Composer

When you attempt to hide the Manage Ideas quick action using Page Composer, an error message appeared on saving the changes. With this update, the issue is fixed.

Oracle reference:  33239391

Steps to Enable

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

Product Development

Publish Changes Without Contribution Folder Limitation

Publication files for change orders are now published to the FAImportExport Security Group root folder in Oracle WebCenter Content instead of the Contribution Folders location to avoid any limitation in the number of files that can be stored.

Additionally, you can now initiate change order publication using an Oracle Enterprise Scheduler Service (ESS) web service. For more details, see the support note referenced in the Key Resources section.

Business users who currently perform change publication from the user interface will see no change.

Facilitate automation of the change order publication process and provide a scalable way of sharing change order data without running into any folder limitations.

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

Tips And Considerations

• Integration users can continue to download the ZIP file using the GenericSoapPort SOAP service by passing the Document ID. If you have written any extensions to get the file specifying the folder path, you will need to modify your code. For details, see the support note referenced in the Key Resources section.

• You can retrieve the publication files from Oracle WebCenter Content programmatically, or by using the File Import and Export option under Tools in the Navigator.

Key Resources

• Watch Replace Components and Add Reviewers Readiness Training.

• Oracle Supply Chain Management Cloud: Using Product Development guide, available on the Oracle Help Center.

• Refer to support note: Doc ID 2846835.1 How To Invoke Change Order Publication Using SOAP Service.

• Refer to support note: Doc ID 1334471.1 Sample Soap Requests for Use in WebCenter Content (WCC/UCM) 11g Calls to the GenericSoapService (GenericSoapPort).

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.

• The following roles and privileges are required to publish change orders:
  • Publish Change Order (ACA_PUBLISH_CHANGE_ORDER_PRIV)
  • Attachments User (AttachmentsUser)
  • CRM Stage Write (CRMStageWrite)

• Users who are assigned the following predefined job roles are automatically able to publish change orders:
  • 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)
  • Supplier Product Design Engineer (ORA_ACA_SUPPLIER_PRODUCT_DESIGN_ENGINEER_JOB)

• The following roles and privileges are required to view change order publishing processes:
  • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
  • View Change Orders (ACA_VIEW_CHANGE_ORDERS_PRIV)
  • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)

• Users who are assigned the following predefined job role are automatically able to view the ESS logs:
  • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)

• Integration users who have the following predefined roles can retrieve the publication file from WebCenter Content (WCC/UCM) using the GET_FILE operation in UCM Web Service GenericSoapService (GenericSoapPort):
  • AttachmentsUser
  • AttachmentsAdmin

Freeze Columns in Item Structure Tables

You can now freeze a column in the item structure table and scroll through all the columns to its right, without losing context. This feature is available on the structure table for both items and change affected objects.

To freeze a column, select the column and click Freeze. All columns to the left of the frozen column are also frozen. For example, you can keep the item name column frozen and scroll right to view all its additional attributes.

Freeze Column on Item Structure Table

Freeze Column on Affected Object’s Structure Tab

Efficiently review a large amount of component data spread across multiple columns in the item structure without losing context.

Steps to Enable

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

Tips And Considerations

• You can select and freeze a single column or a group of columns. Note that you can only scroll through the columns to the right of the frozen columns.

• You can't freeze individual columns within an attribute group (for example, Component Details, Purchasing, and so on); you must select the complete attribute group. This is applicable on the structure view of commercial items and on the structure view of affected objects on changes..

Key Resources

• Watch Replace Components and Add Reviewers Readiness Training.
• Oracle Fusion Cloud SCM: Using Product Development 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 can 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 can access this feature:
  • Manage Item (EGP_MANAGE_ITEM_PRIV)
  • View Item (EGP_VIEW_ITEM_PRIV)
  • Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
  • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) and one of the following:
    • View Change Orders (ACA_VIEW_CHANGE_ORDERS_PRIV) OR
    • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)

Selected Product Development Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Fusion Cloud Product Development works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

Item and Document Classes Shown in Class List

In previous updates, after you opted in to the feature named Leverage Consistent Item Search Across Product Management, the Class list on the Manage Items and Manage Documents pages displayed only the default item and default document class. With this update, the issue is fixed.

Oracle reference: 33597756

Steps to Enable

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

Product Hub

Enhance Integrations Using Deletion Business Events

Enhance integrations using the new business events that are raised when an item and its related entities are deleted. You can subscribe to these events through Oracle Integration Cloud to orchestrate real-time integrations with other systems.

The deletedItemsEntities REST resource allows you to query the deleted entity objects that were deleted through the delete group UI or from import. The details include the primary identifier of the object and other secondary identifiers of the deleted entity.

Business events are raised every time an item or its related entity is deleted. The delete can be explicit or implicit. The payload consists of a primary identifier and other secondary identifiers of the deleted entity. The payload also consists of other relevant details. Integration with external systems can be done by listening to the delete business event with the payload or by using a combination of business events and fetching the details using the deletedItemsEntities REST resource.

The following table lists the entities and the corresponding delete events.

Entity	Event
Item	Item Bulk Delete Event [postItemBulkDelete]
Item Revision	Item Bulk Delete Event [postItemBulkDelete]
Item Revision	Item Bulk Delete Event [postItemBulkDelete]
Item Organization	Item Bulk Delete Event [postItemBulkDelete]
Item Supplier Association	Item Bulk Delete Event [postItemBulkDelete]
Item Category Assignment	Item Category Assignment Delete Event [postItemCategoryAssignmentDelete]
Related Item Relationship	Related Item Relationship Delete Event [postRelatedItemXRefDelete]
Trading Partner Item Relationship	Trading Partner Item Relationship Delete Event[postTradingPartnerItemXRefDelete]
GTIN Item Cross Reference Relationship	GTIN Item Cross Reference Relationship Delete Event [postGtinItemXRefDelete]
Item Cross Reference Relationship	Item Cross Reference Relationship Delete Event[postItemXRefDelete]
Source System Item Relationship	Source System Item Relationship Delete Event[postSourceSystemItemXRefDelete]
Item Level Multi-row Attribute	Item Level Multi Row EFF Delete Event [postItemMultiRowEFFDelete]
Item Revision Level Multi-row Attribute	Item Revision Level Multi Row EFF Delete Event [postItemRevisionMultiRowEFFDelete]
Item Supplier Level Multi-row Attribute	Item Supplier Level Multi Row EFF Delete Event [postItemSupplierMultiRowEFFDelete]
Single Row Attribute at all Levels	Item Bulk Delete Event [postItemBulkDelete]
Entities deleted via Import	Item Bulk Delete Event [postItemBulkDelete]

This feature benefits your business by allowing integrations to maintain external systems in sync, near real time when an item or its related entities are deleted.  

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 23A

Tips And Considerations

The following entities are supported for the delete business events:

• Item Deletion
• Item Revision Deletion
• Item Organization Assignment Deletion
• Item Supplier Association Deletion
• Item Category Assignment Deletion
• Item Relationship Deletion
• Item Trading Partner Relationship Deletion
• Item Multi-row Attribute Deletion at Item, Item Revision, Item Supplier Levels

Key Resources

• Watch Optimize Item Rules and Set Reciprocal Relationships Readiness Training.

• Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation, 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 Manager (ORA_EGP_PRODUCT_MANAGER_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature associated with the deletedItemsEntities REST resource:
  • Delete Bulk Record REST (EGP_BULK_DELETED_ENTITY_REST)

Update Additional Category Attributes Using Import Maps and Use Sorted Values in Smart Spreadsheets

You can reassign item category assignments using import maps and smart spreadsheets. You can also set the start and end dates of the item category assignments using import maps, smart spreadsheets, and the Supplier Products REST resource. Also, the list of values for the attributes in the smart spreadsheet are sorted.

The following attributes are available for mapping under the Item Categories node of the import map:

• Old Category Code
• Old Category
• Start Date
• End Date

The StartDate and EndDate attributes are also available in the categories child resource of the Supplier Products REST resource.

You can use the attributes in the following ways:

• Old Category Code and Old Category attributes to reassign the existing item category assignments to new ones.
• Start Date and End Date attributes to set the start date and end date of the item category assignments.

The following screenshot shows the four attributes in the Item Categories node of the import map.

Import Map Item Category Assignment Attributes

This feature ensures maintenance of the item category assignments and allows you to quickly update the data in the smart spreadsheets.

Steps to Enable

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

Tips And Considerations

• You can delete the end dates of the existing item category assignments through import by entering #NULL in the smart spreadsheet column that’s mapped to the End Date attribute under Item Categories node of the import map.

• You can’t save an import map if the External check box in the import map is selected and any of the Old Category Code or Old Category attributes are mapped.

• Attributes with more than 10000 values aren’t displayed as drop-down in the smart spreadsheet generated from the Create Import Map or Edit Import Map pages.

• The list of values in the smart spreadsheet for extensible flexfields with independent, dependent, or subset value sets are sorted based on the sort order defined in the value set setup. If the sort order is not defined, then the values are sorted alphabetically or in ascending order depending on the data type of the extensible flexfield.

• Extensible flexfields with non-translatable value sets are sorted based on the Value attribute of the value set value.

• Extensible flexfields with translatable value sets are sorted based on the Translated Value attribute of the value set value.

• Extensible flexfields with table-based value sets are sorted based on the Order By clause defined in the value set setup. If the Order By clause isn’t defined, then the values aren’t sorted in the smart spreadsheet.

• Operational attributes (except Lifecycle Phase, Related Item Type, and Cross Reference Type) with lookups are sorted based on the display sequence set in the Manage Standard Lookups task.
  • Lifecycle Phase attribute values are sorted based on the display sequence defined for them in the Manage Lifecycle Phases setup task.
  • Related Item Type attribute values are sorted based on the display sequence defined for them in the Manage Related Item Subtypes setup task.
  • Cross Reference Type attribute values are sorted based on the display sequence defined for them in the Manage Cross Reference Types setup task.
  • If the display sequence isn’t defined, then the values are sorted alphabetically or in ascending order depending on the data type of the attribute. The sorting is based on the Meaning attribute of the lookup values.

• Operational attributes that contain a list of values without associated lookups are sorted alphabetically or in ascending order depending on the data type of the attribute.

Key Resources

• Watch Optimize Item Rules and Set Reciprocal Relationships Readiness Training.

• Customer Connect Event, Importing Items using Import Maps.

• Refer to the following in the Oracle SCM Cloud Implementing Product Management guide, available on the Oracle Help Center:
  • Importing items using import maps section
  • Supplier products chapter

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)
  • 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 Batch (EGI_MANAGE_ITEM_BATCH)
  • Manage Item Import Map (EGI_MANAGE_ITEM_IMPORT_MAP)
  • Manage Product Upload (EGS_MANAGE_PRODUCT_UPLOAD_PRIV)

Identify Opportunities to Optimize Item Rules

Sometimes a few item rules that you’ve created may potentially cause performance issues when triggered. To generate a report of these rules, run a diagnostic test. You can review these rules and optimize the rule definition.

The following image shows the diagnostic test run for rules.

Diagnostic Test for Rules

The following image shows the diagnostic test results.

Diagnostic Test Results

This feature helps to identify opportunities to optimize the item rules.

Steps to Enable

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

Tips And Considerations

When you run into performance issues caused by rules, you can run the diagnostic test and identify the rules that may be the possible reason for sub-optimal performance. You can also proactively run the diagnostic test and identify opportunities to improve the rule definition.

Key Resources

• Watch Optimize Item Rules and Set Reciprocal Relationships Readiness Training.

• Refer to the Running Diagnostic Tests in the Oracle Applications Cloud Using Common Features 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 can access the feature:
  • Application Diagnostics Administrator (ORA_FND_DIAG_ADMINISTRATOR_JOB)
  • Application Diagnostics Advanced User (ORA_FND_DIAG_ADVANCED_USER_JOB)
  • Application Diagnostics Regular User (ORA_FND_DIAG_REGULAR_USER_JOB)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Access Application Diagnostic Dashboard (FND_DIAG_ACCESS_DASHBOARD_PRIV)
  • Search Application Diagnostic Test (FND_DIAG_SEARCH_TEST_PRIV)
  • Run Application Diagnostic Test (FND_DIAG_RUN_ONLINE_ONLY_PRIV)
  • View Application Diagnostic Run Status (FND_DIAG_VIEW_RUN_STATUS_PRIV)
  • View Application Diagnostic Test Report (FND_DIAG_VIEW_TEST_REPORT_PRIV)

Define Reciprocal Relationships for Superseded Items

You can now enable reciprocal for superseded item relationships. To support completely interchangeable items, specifically in service parts business, where demand of item A can be met by supply of item B and vice versa, you can create reciprocal superseded relationships. 

The following image shows the Reciprocal check box selected for the Superseded type of item relationship in the Create Related Item Relationship window.

Superseded Item Relationship with Reciprocal Selected

This feature provides more flexibility when setting up an item relationship that can be consumed appropriately by the business systems.

Watch a Demo.

Steps to Enable

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

Key Resources

• Watch Optimize Item Rules and Set Reciprocal Relationships Readiness Training

• Refer to the Manage Item Relationships section in the Oracle SCM Cloud Implementing Product 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 can access this feature:
  • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
  • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Manage Item (EGP_MANAGE_ITEM_PRIV)
  • Manage Item Relationship (EGP_MANAGE_ITEM_RELATIONSHIP_PRIV)

Replace Item Structure Components

You can now quickly replace a component in your item structure, copying over key data from the original component to the replacement component.

NOTE: A single opt-in feature governs access to the Replace action from the Product Information Management and Product Development work areas, and from the associated business event or SOAP service. Feature Name: Replace Item Structure Components

This section covers the Replace feature in the Product Information Management work area.

To replace a component, select the component in the item structure tab and click the Replace icon. Then use the item picker to search and select a replacement component.

The original component is marked as removed and the replacement component is marked as added in the following row. When you click Save, the redlines disappear and the original component is displayed in a new Replaces column for your reference.

Replacing Structure Components

What’s Copied Over

When you replace a component, item sequence, structure component attributes, substitutes, and reference designators are copied over from the original component to the replacement component.

Here are the attributes that are copied over:

Component Attributes

• Item Sequence - Read-only
• Quantity
• Yield
• Comments
• Start Date
• End Date
• Planning Percent
• Check ATP
• Required to Ship
• Required for Revenue
• Include on Shipping Documents
• Automatically Request Material
• Basis
• Enforce Integer Requirement
• Supply Type
• Component UOM

Substitute Components

• Item
• Description
• Primary UOM
• Quantity
• Inverse Quantity
• Priority
• Enforce Integer Requirement
• Descriptive flexfields

Reference Designators

• Reference Designator
• Description
• Descriptive flexfields

Start Date and End Date

• Upon replacement, the end date of the original component and the start date of the replacement component will match the date in the Date field on the toolbar. (This ‘context’ date allows you to see what the structure looks like at a given date.)

• If a replacement is to be effective only in the future, select a future date in the toolbar and then perform the Replace action. The replacement is visible in the structure when the date selected is after the start date of the replacement component.

Once you’ve replaced a component, you can save to production, or save to a change order and route it for approval.

Streamline your replacement process by performing replacements with a single action and keep track of which components were replaced.

Watch a Demo.

Steps to Enable

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

Offering: Product Management  No Longer Optional From: Update 22D

Tips And Considerations

• If a component has redlines, for example, the quantity is updated, the component can’t be replaced.

• Once a replacement is selected, neither the original nor the replacement component can be edited.

• The Replaces column is visible by default and retains the record of replaced components even when you enter future dates in the Date field. The original component is shown in the Replaces column until it’s replaced with another component.

• If the replacement component selected has a different UOM from the original component, a warning message is displayed and the quantity is reset to 1. Reference designators and substitute components aren’t copied over. The replacement component's UOM will show the item’s primary UOM.

• If the replacement component was defined as a substitute component of the original component, then it isn't copied to the substitute component table of the replacement component.

Key Resources

• Watch Replace Components and Add Reviewers Readiness Training

• Oracle Supply Chain Management 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:
  • Roles for the replace action
    • 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:
  • Functional privileges to view and edit item structures 
    • Manage Item (EGP_MANAGE_ITEM_PRIV)
  • Functional privileges to view and edit affected object structures
    • Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV) or
    • Manage Change Order (ACA_MANAGE_CHANGE_ORDERS_PRIV) and Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) 
  • Data privileges to view and edit item structures
    • View Item Basic
    • Maintain Item Basic
    • View Item Structure
    • Maintain Item Structure

Selected Product Hub Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Fusion Cloud Product Hub works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

Limit for the Number of Records in the Interface Tables

Before update 22B, a high volume of records in the interface table contributed to poor performing queries, data backup, data recovery, new index creation, and so on, thus affecting import performance. After you update to 22B, a warning message will indicate that you must purge the records based on the number of records in the interface table. If you continue to ignore this message, then after a threshold limit of six million records in any interface table, the import process displays an error message. You must purge the interface table data using one of these methods:

• The Purge Interface Table scheduled process (if you don't have an Oracle Product Management Cloud Service subscription)
• The Manage Item Batch page (if you have an Oracle Product Management Cloud Service subscription)
• The purgeBatchData operation in the Batch Maintenance REST resource

Oracle reference: 33652971

Limit for the Length of the Item Rule Expression

Before update 22B, there was a limit for the length of an item rule expression. After you update to 22B, this limit is decreased due to changes in the underlying technology. Therefore, rule expressions that were previously under the limit may now exceed it. If your rule expression exceeds 500 characters, it's likely to exceed the limit. You can run the Optimize Rules scheduled process to identify any rules that exceed the limit and take necessary action to minimize the length of the expressions of those rules.

Oracle reference: 34069427

View Actual User Name Using Requested By Attribute in Rules

Before update 22B, when you referenced the Requested By attribute in rules, it returned an internal identifier instead of the name of the user who had requested the change order. After you update to 22B, it returns the actual user name.

Oracle reference: 32899878

Automatically Generate Catalog Category Identifiers

Before update 22B, you were able to specify a value for the category identifier when creating a catalog category using the Item Categories REST resource or Catalog Categories SOAP web service. After you update to 22B, you aren't allowed to specify this value and the system generates it automatically.

Oracle reference: 32918558

Organizations in Change Propagation

Change orders were stuck during propagation when you specified the same organization for source and target. With this update, a validation message prevents you from duplicating source and target organizations in the change order.

Oracle reference: 33120741

Steps to Enable

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

Product Development & Product Hub Common

Ensure Uniqueness in Trading Partner Item Numbers

You can maintain unique trading partner item numbers and avoid duplicates. Trading partner items refer to customer items, competitor items, manufacturer part numbers, and supplier items. For example, for a manufacturer called National Technologies Inc, earlier you were able to create trading partner items with numbers such as CABLE123 and cable123. You can no longer create such duplicate trading partner items. The validation isn't case-sensitive and will consider CABLE123 and cable123 as duplicates. Similarly, you can’t create manufacturer parts with duplicate manufacturer part numbers in the Product Development work area.

The following image shows an existing trading partner item name called CABLE_C_123.

Existing Trading Partner Item Name in Product Hub

The following image shows the error message that appears when you try to create a trading partner item called cable_c_123.

Error Message When Creating Duplicate Customer Item

The following image shows the error message that appears when you try to create a duplicate manufacturer part number in Product Development work area.

Error Message When Creating Duplicate Manufacturer Part Number in Product Development

The enhanced validations benefit your business by ensuring unique trading partner item numbers.

Steps to Enable

If there are any duplicate trading partner items in your system, perform the following:

1. Run the Upgrade Product Management Data scheduled process with these parameters:

• Update Process: Analyze
• Functional Area: Trading Partner Items
• Feature: Ensure Uniqueness in Trading Partner Item Numbers

Submit the analysis job.

After the process is completed, view the logs for the duplicate trading partner item records.

2. You must take necessary actions to correct the duplicate numbers. You can delete one of the duplicate records or change one of the trading partner item numbers so that there are no duplicate records for trading partner item numbers.

3. Run the scheduled process Upgrade Product Management Data again with these parameters:

• Update Process: Execute
• Functional Area: Trading Partner Items
• Feature: Ensure Uniqueness in Trading Partner Item Numbers

Submit the analysis job.

If you don’t have any duplicate trading partner items created previously, you don’t have to perform any actions. The new validation to ensure unique trading partner items will be added automatically.

Tips And Considerations

To correct the duplicate trading partner item, set the Edit Trading Partner Item Number Allowed (ORA_EGP_TPI_UPDATEABLE) profile option to Yes and then change the trading partner item number.

Key Resources

• Watch Optimize Item Rules and Set Reciprocal Relationships Readiness Training

• Refer to the Create and Edit Trading Partner Items section in 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 can access this feature:
  • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
  • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)

• Users who are assigned a configured job role that contains this privilege can access this feature:
  • Manage Trading Partner Item (EGP_MANAGE_TRADING_PARTNER_ITEM_PRIV)

Enter Item Search Criteria and View Results More Efficiently

You can easily control the search criteria attributes that are used to search for items and display the search results. To add the search criteria attributes, the Add Fields action allows you to browse the list of attributes that you can use to search for items, select the required attributes from the Available Attributes list, and move them to the Selected Attributes list. After you click OK, the attributes are added to the Advanced Search region. You can also use the Find option to quickly search an attribute and add it to the Advanced Search region.

The Add Columns action provides a similar user experience and adds the selected attributes as columns in the search result. You can change the order of the attributes in the Selected Attributes list. The columns will be displayed in the same order in the search results.

The list of search attributes appears based on the product being used. In Product Development, you can control the visibility of the user-defined and operational attributes for the search attributes. Additional attribute groups are also filtered. The Available Attributes list only shows the extensible flexfield (EFF) attributes that are assigned to the Product Development page when creating or editing an item class.

In Product Hub, the search attributes appear for all the user-defined and operational attributes.

Select and Add Attributes Window in Product Hub

Select and Add Attributes Window in Product Development

Add Columns Window in Product Hub

Add Columns Window in Product Development

This feature allows you to be more efficient when searching and selecting items.

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

The steps to enable this feature in Product Hub and Product Development are different.

Product Hub

1. Enable the opt in for the Enter Item Search Criteria and View Results More Efficiently feature. You can enable this features in the Product Management offering within the Items functional area.
2. Perform deployment offline for the item extensible flexfield before using this feature the first time. In the Setup and Maintenance work area, go the Deploy Item Extensible Flexfields task:

• Offering: Product Management
• Functional Area: Items
• Task: Deploy Item Extensible Flexfields

3. Search and select the EGO_ITEM_EFF flexfield code.
4. From the Actions menu, select the Refresh and Deploy Offline option.

Product Development

Enable the opt in for both the Consistent Item Search feature and the Enter Item Search Criteria and View Results More Efficiently features. You can enable these features in the Product Management offering within the Items functional area. All the other steps are same as Product Hub provided in the preceding section.

Tips And Considerations

• You can save the selected fields and columns by creating a personal saved search. Saved searches can also be created for all users.

• In the Product Development work area, you can filter the Available Attributes list when adding fields and columns based on configurations that are setup. Operational attributes are displayed based on the configuration in the Manage Configuration page:

1. In the Product Development work area, click the Manage Configurations page.
2. Click the Items tab.
3. Expand Item Attributes Display Settings.
4. Select the operational attributes groups that must be visible as Available Attributes.
5. Click Save to save the configuration.

• User-defined attribute groups are displayed based on the attribute groups assigned to the Product Development page when creating or editing an item class:

1. In the Setup and Maintenance work area, go to Manage Item Classes:

• Offering: Product Management
• Functional Area: Items
• Task: Manage Item Classes

2. Search for the item class you want to configure and click the link to edit the item class.
3. Click the Pages and Attribute Groups tab. 
4. Click the Pages subtab.
5. In the table, select the row corresponding to the PD Page.
6. In the Attribute Groups: PD Page table, use the Select and Add icon to add user-defined attribute groups to the PD page. The selected attribute groups will be visible in the Add Fields and Add Columns display.

Key Resources

• Watch Optimize Item Rules and Set Reciprocal Relationships Readiness Training.
• Oracle SCM Cloud Implementing Product Management guide, available on the Oracle Help Center.
• Oracle SCM Cloud Implementing Product Development 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 can access this feature:
  • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
  • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)

Improve Change Workflow Resiliency

With this update, you can leverage several enhancements that help improve change workflow resiliency, performance, and error logging.

• Remove non-essential validations
  • Avoid running validations on extensible flexfield attributes that aren't redlined in a change order. Previously, before activating a change order line, the application would validate whether any disabled or end-dated value sets were assigned to these attributes and this could result in stuck changes. This validation is non-essential and has been removed.

• Retry unprocessed threads
  • Automatically retry unprocessed threads in case of Enterprise Scheduler Service (ESS) errors. Previously, if a change line was stuck due to an ESS error, and there were unprocessed change lines in the change order, the retry operation would cancel such unprocessed change lines. The job is now redesigned to continue processing the unprocessed change lines. For example, let’s say a change had 10 lines and change lines 1 and 2 were completed while change line 3 failed to complete. In this case, the job will now process lines 4 to 10 instead of canceling them.

• Enhance error logging for automatic cancellation
  • Trigger a message when a change order is automatically canceled due to threads that didn’t start. The CLOB field in the EGO_CHANGES_ERRORS table now logs details of change lines that were automatically canceled for this reason.  

This feature provides visibility into the details of change order validation errors directly in the implementation logs to allow faster debugging and issue resolution.  It also improves resiliency and performance by removing non-essential validations.

Steps to Enable

To enable enhanced error logging for automatic cancellation, you must enable the 22A feature Accelerate Error Debugging for Changes, and also perform the following steps:

1. In the Setup and Maintenance work area, go to the following task: Manage Administrator Profile Values. 
2. Search for the profile option code: ORA_EGO_CHANGE_DEBUG_MODE or profile option name: Enable Change Debugging.
3. For the profile level, set the profile value to Yes. The default is No. 

Key Resources

• Watch Replace Components and Add Reviewers Readiness Training.

• To enable enhanced error logging, refer to: What's New: 22A: Oracle Product Management Cloud: Accelerate Error Debugging for Changes.

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 the following predefined job role can view the ESS logs:
  • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)

• Users who are assigned the following predefined job role can view change order scheduling and activation processes:
  • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)

• Users who are assigned a configured job role that contains these privileges can view change order scheduling and activation processes:
  • View Change Orders (ACA_VIEW_CHANGE_ORDERS_PRIV)
  • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)

• Users who are assigned these privileges can access change objects and view scheduling and activation statuses:
  • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV)
  • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)

Analyze Substitute Component Data in OTBI

Leverage the new columns added to Product Management subject areas in Oracle Transactional Business Analytics (OTBI) to help improve your analysis of substitute components:

Subject areas:

• Product Management - Structures and Components
• Product Management - Where Used

Here are the new columns added to a Substitute Components folder in these two subject areas.

• Substitute Component Name
• Substitute Component Description
• Substitute Component Primary UOM
• Substitute Component Item Quantity
• Substitute Component Inverse Quantity
• Substitute Component Planning Priority
• Substitute Component Enforce Integer Requirement
• Additional Attributes (Descriptive Flexfields)

Analysis for Substitute Components in Structures and Components Subject Area

This feature improves traceability when analyzing item structures and components by enabling users to view substitute components and relevant details in a BI report.

Steps to Enable

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

Tips And Considerations

• To see the descriptive flexfields in OTBI, you must run the scheduled process Import Oracle Fusion Data Extensions for Transactional Business Intelligence.

• To populate data in the Structures and Components subject area and the Where Used subject areas, you must first run scheduled processes. For details, see the topic referenced in the Key Resources section. 

Key Resources

• Watch Replace Components and Add Reviewers Readiness Training.

• Refer to the following topic in the guide Creating and Administering Analytics and Reports for SCM, available on the Oracle Help Center.
  • Chapter: Subject Areas
  • Topic: Run Scheduled Process for Populating Subject Areas

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 can 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 can access this feature:
  • Transactional Analysis Duty (FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY)
  • Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY)
  • BI Consumer Role (BIConsumer)

Selected Product Development & Product Hub Common Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Fusion Cloud Product Development and Product Hub Common work. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

Advanced Search for Change Orders

In the advanced search for change orders, the Status field appeared twice; the same field name was used to indicate change status as well as change publication status. With this update, the field that shows publication status has been renamed to Publication Status.

Oracle reference:  33508686

Approvers List in Change Status Dialog Box

When you select an approver in the change status dialog box that includes more than 10 approvers, the dialog box scrolled automatically. With this update, the issue is fixed.

Oracle reference: 32724532

Component Quantity in Change Orders

When you edit and save the structure component quantity in a change order, the old value shown in the redline summary view was automatically rounded off after the second decimal place. For example, if you modified the quantity from 1.041567891 to 1.041567889:

• The new value would be shown as 1.041567889
• The old value would be rounded off to 1.042

With this update, the old quantity value in the redline summary view is also shown up to 10 decimal places.

Oracle reference: 33189023

Reference Designators on Changes

The Reference Designator side tab on a change order wasn’t being refreshed when using Query By Example to filter a structure. With this update, the issue is fixed.

Oracle reference: 33335123

New Item Revision Validation

The validation message that appears when you save new revision values on the change affected objects page didn't indicate which items had invalid values. The message now includes the item number to help you identify the item revision that needs correction.

Oracle reference: 33714381

Notification on Change Completion

If only one response was required on a user-defined approval and a role was added as an approver, the FYI notification on change completion was earlier sent only to the user who approved the change order. With this update, the FYI notification is sent to all members of the role.

Oracle reference: 33508957

Redlining of Reference Designators Deleted Using REST API

Prior to this update, if you used a REST API to delete a reference designator for a structure component on a change order, the reference designator was removed without being redlined. Redlines are now captured for all deleted reference designators, including those deleted using REST APIs.

Oracle reference:  33134165

Unprocessed Change Lines

When change lines were stuck due to errors on the server, the unprocessed lines were canceled by a retry job. With this update, the retry job attempts to reprocess the unprocessed lines, instead of canceling them.

Oracle reference: 33514318

Import Structure Changes Using FBDI

When you import item structure header changes using file-based data import (FBDI), the ItemBulkload event wasn’t being created. With this update, the issue is fixed.

Oracle reference: 32861838

Prebuilt OTBI Dashboards not Updated

Although the Portfolios work area wasn’t supported after update 21C, the Innovation Management Dashboard still showed portfolio-related tabs and pages.  Also, the Innovation Management and PLM Details dashboards were not updated to the Redwood style. Portfolio data is now removed from the Innovation Management dashboard and both dashboards are updated to the Redwood style.

Oracle reference:  33782028

Steps to Enable

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

Replace Item Structure Components

To enable the features in this section, you must opt in to the feature named Replace Item Structure Components.

Replace Item Structure Components Using a Web Service or Business Event

You can now replace item structure components programmatically using the following:

• Item Structure Version 2 SOAP Service
• Product Design Change Order Service
• Item Structure Component Create Event

NOTE: A single opt-in feature governs access to the Replace action from the Product Information Management and Product Development work areas, and from the associated business event or SOAP service. Feature Name: Replace Item Structure Components

Using Item Structure Version 2

To replace a component, use the updateStructure operation and specify the following parameters:

• ComponentSequenceId: Item sequence of the original component.

• ComponentItemNumber: Item Number of the original component. This is optional.

• EndDateTime: End date of the original component. This is optional if the component is effective on approval. For a future dated change order, this is the future effective date.

• ReplacedBy: Item number of the replacement component.

Here’s a sample payload request for the original component Keyboard V1 to be replaced by the replacement component, Keyboard V2.

Item Structure Version 2 - updateStructure Request

To find the original component (Replaces attribute), use the findStructure operation. This sample payload shows the original component Keyboard V1 that was replaced by the replacement component, Keyboard V2.

Item Structure Version 2 - findStructure Response

Using Product Design Change Order

Run the redlineItemStructure operation in ASYNC or ASYNC BULK modes, specifying the following parameters:

• ComponentItemNumber: Item Number of the original component
• ReplacedBy: Item number of the replacement component
• ACDType = DELETE

Here’s a sample payload:

Product Design Change Order - redlineItemStructure Request

To find the original component (Replaces attribute), use the findChangeObject operation.

Sample:

Product Design Change Order - findChangeObject Response

Using Item Structure Component Create Event

Retrieve the original component (ReplacedForComponent attribute) in the payload in addition to the replacement component using this business event.

In this response payload, you can see the original component’s item ID, Keyboard V1.

Item Structure Component Create Event Response

What’s Copied Over

When you replace a component, item sequence, structure component attributes, substitutes, and reference designators are copied over from the original component to the replacement component.

Here are the attributes that are copied over:

Component Attributes

• Item Sequence - Read-only
• Quantity
• Yield
• Comments
• Start Date
• End Date
• Planning Percent
• Check ATP
• Required to Ship
• Required for Revenue
• Include on Shipping Documents
• Automatically Request Material
• Basis
• Enforce Integer Requirement
• Supply Type
• Component UOM

Substitute Components

• Item
• Description
• Primary UOM
• Quantity
• Inverse Quantity
• Priority
• Enforce Integer Requirement
• Descriptive flexfields

Reference Designators

• Reference Designator
• Description
• Descriptive flexfields

Streamline your component replacement process by using web services or business events to programmatically replace components in item structures.

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

Tips And Considerations

If you want to use the Replace Item Structure Components Using a Change Order feature, then you must opt in to its parent feature: Replace Item Structure Components. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

Additional tips and considerations are:

• If a component has redlines, for example, the quantity is updated, then the component can't be replaced.

• You can’t replace a component that is already a replacement for another component in the same change order.

• If the replacement component is a substitute component of the original component, then it isn't copied to the substitute component table of the replacement component.

Key Resources

• Watch Replace Components and Add Reviewers Readiness Training.
• Oracle Supply Chain Management Cloud: REST API for Oracle Supply Chain Management Cloud 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 can access this feature:
  • Roles for the replace action
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB) or
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Functional privileges to view and edit item structures  
    • Manage Item (EGP_MANAGE_ITEM_PRIV)
  • Functional privileges to view and edit affected object structures
    • Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV) or
    • Manage Change Order (ACA_MANAGE_CHANGE_ORDERS_PRIV) and Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) 
  • Data privileges to view and edit item structures
    • View Item Basic
    • Maintain Item Basic
    • View Item Structure
    • Maintain Item Structure

Replace Item Structure Components Using a Change Order

A new Replace action enables you to replace structure components of engineering or commercial items from the change context. In the structure table of an affected object, you can now replace components with a single action and keep track of which components were replaced.

NOTE: A single opt-in feature governs access to the Replace action from the Product Information Management and Product Development work areas, and from the associated business event or SOAP service. Feature Name: Replace Item Structure Components

This section covers the Replace feature in the Product Development work area.

To replace a component from within the change order, navigate to Affected Objects > Structure, select the component and click the Replace icon.

The original component is marked as removed and the replacement component is marked as added in the following row. When you click Save, the original component is displayed in a new Replaces column for your reference.

What’s Copied Over

When you replace a component, item sequence, structure component attributes, substitutes, and reference designators are copied over from the original component to the replacement component.

Here are the attributes that are copied over:

Component Attributes

• Item Sequence - Read-only
• Quantity
• Yield
• Comments
• Start Date
• End Date
• Planning Percent
• Check ATP
• Required to Ship
• Required for Revenue
• Include on Shipping Documents
• Automatically Request Material
• Basis
• Enforce Integer Requirement
• Supply Type
• Component UOM

Substitute Components

• Item
• Description
• Primary UOM
• Quantity
• Inverse Quantity
• Priority
• Enforce Integer Requirement
• Descriptive flexfields

Reference Designators

• Reference Designator
• Description
• Descriptive flexfields

Start Date and End Date

The end date of the original component and the start date of the replacement component will be the same as the effective date of the affected object.

• If the affected object is effective on approval, this will be the date when the change order is moved to Scheduled status.
• If the affected object has a future effective date, this will be the same as the effective date.

New Replace Icon and Replaces Column in Change Context

The redline summary captures the replacement changes. Next to the added component, you can also see which component it replaces.

Redline Summary After Replace Action

Component replacement details are captured in the change order report as well.

Change Order Details Report

In the Change Order Details report:

• The new Replaces column appears in the Structure Changes table showing the original component that was replaced.
• The Change Action column shows the replacement component as Added and the original component as Disabled.
• Copied reference designators and substitute components are shown against the row marked Added.
• Change Action and Replaces attributes are shown in the Pending Component section.

Use this feature to quickly perform component replacements in a product structure with a single 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 22D

Tips And Considerations

If you want to use the Replace Item Structure Components Using a Change Order feature, then you must opt in to its parent feature: Replace Item Structure Components. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

Additional tips and considerations include:

• If a component has redlines, for example, the quantity is updated, then the component can't be replaced.

• You can’t replace a component that is already a replacement for another component in the same change order.

• If the replacement component selected has a different UOM from the original component, a warning message is displayed, and the quantity is reset to 1. Reference designators and substitute components aren’t copied over. The replacement component's UOM will show the item’s primary UOM.

• You can use the Undo Redlines action to revert the replacement action when the change order is in Open or Interim Approval status, provided you have the permission to perform the action. This permission is defined in the Additional Workflow Controls table in the change type setup.

• If you are replacing an item with a document, then the reference designators aren't copied to the replacement.

• If the replacement component is a substitute component of the original component, then it isn't copied to the substitute component table of the replacement component.

• In the Change Order Details report, replacement attributes are displayed regardless of whether you opt in for this feature or not. These attributes can't be hidden.

• If, prior to update 22B, you configured the Change Order Details report template, then the Replaces column won’t be included in the report after you opt in. You must configure your template to include this column.

Key Resources

• Watch Replace Components and Add Reviewers Readiness Training.
• Oracle Supply Chain Management Cloud: Using Product Development 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 for the replace action
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Functional privileges to view and edit affected object structures
    • Manage Change Order (ACA_MANAGE_CHANGE_ORDERS_PRIV) and Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) or
    • Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
  • Functional privileges to view and edit item structures 
    • Manage Item (EGP_MANAGE_ITEM_PRIV)
  • Data privileges to view and edit item structures
    • View Item Basic
    • Maintain Item Basic
    • View Item Structure
    • Maintain Item Structure

Product Lifecycle Management Common

Add Reviewers to Changes in Approval or Scheduled Status

You can now add reviewers to future statuses in the workflow when the object is in Approval or Scheduled status. Prior to this update, you could do this only for changes in Draft, Open, or Interim Approval status. This feature is supported in change orders, change requests, problem reports, and corrective actions.

Reviewer Added for Completed Status

Workflow participants can add and remove reviewers for future statuses based on their permissions for these actions in the Additional Workflow Controls table in change type setup.

NOTE: The reviewers you add will receive an FYI notification.  Your administrator can configure the layout, style, and content of the notification according to your business needs.

This feature benefits your business by enabling key stakeholders to be added as reviewers when a change is in Approval or Scheduled status, and notified accordingly.

Steps to Enable

To enable this feature you must opt-in to the feature: Add Reviewers to Change Workflows (ORA_ACA_ADD_REVIEWER)

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

To define who can add or remove participants for the change in Scheduled or Completed status, assign permissions for the following actions using the Additional Workflow Controls table in change type setup:

• Add Participants for Future Status
• Remove Participants for Future Status

Additional Workflow Controls for Scheduled Status

Tips And Considerations

• You can add reviewers only for change orders, change requests, problem reports, and corrective actions created in or after 22A.

• When an object is in an approval workflow, you can add or remove reviewers only for future statuses in the workflow. For example, if a change order is in Scheduled status, then you can’t add participants to review the change order while it’s in Scheduled status.

• A Claim button appears on the notification when multiple reviewers are added. If one of the reviewers claims the task, the others don't see any action buttons on the notification.

• The action names in the Additional Workflow Controls table for Add Approvers for Future Status and Remove Approvers for Future Status have been changed to Add Participants for Future Status and Remove Participants for Future Status.

Key Resources

• Watch Replace Components and Add Reviewers Readiness Training.
• Oracle Supply Chain Management Cloud: Using Product Development guide, available on the Oracle Help Center.
• Watch video: Modify Email Notification Template for Change Orders and New Item Requests.

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 can be added as reviewers because these roles contain the required privilege to view configured notifications for changes:
  • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
  • Supplier Product Design Engineer (ORA_ACA_SUPPLIER_PRODUCT_DESIGN_ENGINEER_JOB)
  • Supplier Quality Engineer (ORA_ENQ_SUPPLIER_QUALITY_ENGINEER_JOB)

• Users who are assigned configured job roles that contain these privileges can add and remove reviewers:
  • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV) or
  • Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)

• Users who are assigned configured job roles that contain these privileges can be added as reviewers:
  • For change orders:
    • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) and one of the following:
      • View Change Orders (ACA_VIEW_CHANGE_ORDERS_PRIV) 
      • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV) or
      • Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
  • For change requests:
    • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) and one of the following:
      • View Change Request (ACA_VIEW_CHANGE_REQUESTS_PRIV)
      • Manage Change Request (ACA_MANAGE_CHANGE_REQUESTS_PRIV) or
      • Manage Item Change Order (EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV)
  • For problem reports:
    • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) and one of the following:
      • View: View Problem Report (ACA_VIEW_PROBLEM_REPORTS_PRIV)
      • Manage: Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV)
  • For corrective and preventive actions:
    • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) and one of the following:
      • View: View Corrective Action (ACA_VIEW_CORRECTIVE_ACTIONS_PRIV)
      • Manage: Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV

• Users who are assigned any of these predefined job roles can configure the notification template:
• • BI Author Role (BIAuthor)
  • BI Publisher Data Model Developer (BIPDataModelDeveloper)

Use Separate REST Services for Change Orders, Change Requests, Problem Reports, and Corrective Actions

Use separate REST API resources to create, read, update, or delete the following objects:

• Change orders
• Change requests
• Problem reports
• Corrective actions

These REST API resources are secured with fine-grained access control. You must have View or Manage privilege on the object to access these resources.

Here are the object end points and the URLs for each REST API resource:

• Product Change Orders V2  
  •  /fscmRestApi/resources/latest/productChangeOrdersV2

• Product Change Requests       
  •  /fscmRestApi/resources/latest/productChangeRequests

• Quality Problem Reports    
  • /fscmRestApi/resources/latest/qualityProblemReports

• Quality Corrective and Preventive Actions    
  • /fscmRestApi/resources/latest/qualityCorrectiveAndPreventiveActions

Here’s a sample request to create a change order.

Create One Change Request

Additionally, you can use a new List Of Value (LOV) resource to get the list of values available for a lookup type. For example, the list of values defined for Change Reason.

List of Values for Change Reasons

Secure API-based actions and resources independently for each change object.

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.

If you're using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Tips And Considerations

• If you are currently using Product Change Orders REST API for integrating change requests, problem reports, and corrective and preventive actions, it’s recommended that you use the new distinct REST API resources that are available in this update since they are secured by their granular privileges.

• For future integrations using REST API, it's recommended that you use the Product Change Orders V2 service. To benefit from new and future enhancements, ensure that you migrate the current integrations using the Product Change Orders service to the Product Change Orders V2 service. There will be no further enhancements to the existing Product Change Orders service.

• When configuring the user interface using Application Composer, you can now use the LOV resources to get all the list of values available for a list attribute.

Key Resources

• Watch Replace Components and Add Reviewers Readiness Training.

• Oracle Supply Chain Management Cloud: REST API for Oracle Supply Chain Management Cloud guide, available 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 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:
  • View Privileges:
    • View Change Order (ACA_VIEW_CHANGE_ORDERS_PRIV)
    • View Change Request (ACA_VIEW_CHANGE_REQUESTS_PRIV)
    • View Problem Report (ACA_VIEW_PROBLEM_REPORTS_PRIV)
    • View Corrective Action (ACA_VIEW_CORRECTIVE_ACTIONS_PRIV)
  • Manage Privileges
  • Manage Change Order (ACA_MANAGE_CHANGE_ORDERS_PRIV)
  • Manage Change Request (ACA_MANAGE_CHANGE_REQUESTS_PRIV)
  • Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV)
  • Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)

• To provide granular View or Manage access for change orders, change requests, problem reports and corrective actions, you must provide the Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) privilege along with the object-specific View or Manage privilege.

• To access certain LOVs, you need the following additional privileges:
  • To access LOVForOrganization, LovUnitOfIssueValue, LovPrimaryUOMValue, LovSecondaryUomValue, and PackagingStringsPVO1:
    • ORA_RCS_SCM_COMMON_VIEW_WEB_SERVICE_DUTY
  • To access LovItemCatalogGroupValue and LovCurrentPhaseValue:
    • EGP_GET_ITEM_CLASS_REST_PRIV 
  • To access ItemNumberLOV:
    • EGP_VIEW_ITEM_PRIV

Common Technologies and User Experience

Approvals and Notifications

Employee Vacation and Delegation Rules Report

Use the Employee Vacation and Delegation Rules Report to view the vacation and delegation rules set by your employees in BPM Worklist. Administrators can use this report to review details of the rules defined by employees to delegate or reassign their workflow tasks. To submit the report and see the output, use the Scheduled Processes work area.

Submitting the Report in the Scheduled Processes Work Area

The report contains the following details:

Section	Content
Originator Employee Details	Information about the employee who has defined the vacation or delegation rule, such as the employee name, person number, position, job code, location and email ID.
Rule Details	Details of the rule defined by the employee. Includes the rule type (vacation or delegation), validity period, type of action(reassign or delegate) and the rule conditions based on which the workflow tasks will be reassigned or delegated.
Destination Employee Details	Information about the employee to whom the workflow tasks are reassigned or delegated. Includes the employee's name, person number, position, job code, location, email ID and the name and person number of the employee's manager.

Employee Vacation and Delegation Rules Report

This report helps you manage and troubleshoot approvals, for example for people who are out of office.

Steps to Enable

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

Tips And Considerations

If you don’t enter the date parameters while submitting the report, the report runs as if you had entered the first and last date of the current month.

Key Resources

• Review Employee Vacation and Delegation Rules (available April 1, 2022)

Role Information

• To run and view this report, you must have a role that contains both:
  • Run BPM Workflow Reports (FUN_RUN_BPM_WORKFLOW_REPORTS_PRIV) privilege
  • Run BPM Workflow Reports (FUN_RUN_BPM_WORKFLOW_REPORTS_PRIV_OBI) role

• Both are already granted to these predefined job roles:
  • Financial Application Administrator (ORA_FUN_FINANCIAL_APPLICATION_ADMINISTRATOR_JOB)
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)

Reporting and Analytics

Updates to Oracle Transactional Business Intelligence and New Documentation Library

As of Release 22A, Oracle Transactional Business Intelligence (OTBI) is updated from functionality available in Release 21D or earlier. If your update is from Release 21D to 22B, this new functionality is part of the update.

What's Notable and Different in Oracle Transactional Business Intelligence

There are some important one-time considerations when you prepare for Oracle to update OTBI from Release 21D to 22B or later. For other issues related to updates, carefully review Known Issues.

1. The OTBI catalog is placed in read-only mode three days before your update from Release 21D to 22A or later. During this three-day period, you can access the catalog, but changes you make aren’t retained. This one-time activity, which is required to ensure that the catalog is migrated in a consistent state prior to 22B update, won’t be repeated for the next Oracle Applications Cloud update.

When the catalog is in read-only mode, you can’t retain:

• Changes to artifacts such as Publisher objects, analyses, and agents (including artifacts that were edited)
• Modifications to objects in the catalog (such as renaming objects or changing their permissions)
• Modifications to the catalog structure (such as adding or deleting folders)

To retain your changes after update, it's recommended you archive changed content before the update and then unarchive after the update is complete.

2. Before you move the catalog content from stage to production environments using the Archive and Unarchive actions, prepare for Oracle to update both stage and production environments to OTBI. You can’t move catalog content from a Release 22B environment to a Release 21D environment. See Can’t Move Catalog Content from a 22A Environment to a 21D Environment.

OTBI is updated from functionality available in Oracle BI Enterprise Edition 11.1.1.9 to 12c.

Steps to Enable

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

Tips And Considerations

There's a new OTBI library, with a new set of OTBI guides for Oracle Cloud Applications. It's recommended that you refer to the library below, and not to the Oracle BI Enterprise Edition and Oracle Analytics Server Middleware libraries on Oracle Help Center.

Key Resources

For information about using, configuring, and administering OTBI, go to the OTBI library, a new set of OTBI guides for Oracle Cloud Applications.

• Get Started

• Guides

1. Use OTBI to explore and analyze data by building and sharing analyses and dashboards.

Creating Analyses and Dashboards in Oracle Transactional Business Intelligence

2. Model data and design pixel-perfect reports in Publisher.

Designing Pixel-Perfect Reports in Oracle Transactional Business Intelligence

3. View, publish, and manage pixel-perfect reports.

Using Oracle Analytics Publisher in Oracle Transactional Business Intelligence

4. Manage users and configure OTBI.

Administering Oracle Transactional Business Intelligence

5. Administer and configure Publisher for pixel-perfect reporting.

Administering Oracle Analytics Publisher in Oracle Transactional Business Intelligence

6. Review developer and integrator information, and known issues.

More...