Update 23D

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	Module	Feature	Notes
11 JAN 2024	Product Development and Product Hub Common	Use Import Tools to Delete Item Structure Data	Updated document. Revised Tips and Considerations section.
13 DEC 2023	Product Lifecycle Management Common	Use Extensible Flexfields on Changes, Problem Reports, and Corrective Actions	Updated document. Updated Tips and Considerations section.
07 DEC 2023	Product Development	Selected Product Development Bug Fixes in This Update	Updated document. Added a bug fix.
01 DEC 2023	Product Development and Product Hub Common	Efficiently Manage Multiple Values for Item Attributes	Updated document. Added a feature that was backported in the November monthly update of 23D.
02 NOV 2023	IMPORTANT Actions and Considerations		Updated document. Updated the details about the changes in a feature name and supported functionality.
25 OCT 2023	IMPORTANT Actions and Considerations		Updated document. Added details about changes in a feature name and supported functionality.
17 OCT 2023	Product Hub	Efficiently Search for Documents Using the Item Object Identifier	Updated document. Moved feature from Product Development and Product Hub Common to Product Hub.
04 OCT 2023	Product Lifecycle Management Common	Use Extensible Flexfields on Changes, Problem Reports, and Corrective Actions	Updated document. Revised Access Requirements section.
26 SEP 2023	Product Development and Product Hub Common	Selected Product Development & Product Hub Bug Fixes in This Update	Updated document. Added a bug fix.
14 SEP 2023	Product Development and Product Hub Common	Use Import Tools to Delete Item Structure Data	Updated document. Revised Key Resources content.
14 SEP 2023	Product Lifecycle Management Common	Retain Copied Data on Clipboard	Updated document. Revised feature description.
01 SEP 2023			Created initial document.

Overview

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 Fusion Cloud SCM: 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 Configure Offerings.

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

Product Lifecycle Management

Product Development

Create Manufacturer Parts Using Save As

You can use the new Save As feature to create a new manufacturer part from an existing manufacturer part. You can choose to copy over the original manufacturer part's attachments, descriptive flexfields and security settings to the new manufacturer part. The Save As feature includes a new standard field, Created From.

Save As Action on Manufacturer Part

Save As Dialog: Select What Data to Copy Over

New Created From Field Shows Source Manufacturer Part

This feature helps you do the following:

• Speed up the definition of manufacturer parts by copying existing data.
• Choose what specific business data you want to copy over to the new manufacturer part.
• Ensure complete traceability of the original manufacturer part from which it was copied or created.

Steps to Enable

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

Tips And Considerations

• You must have the Manage Manufacturer Part privilege to use the Save As feature. If you don’t have that privilege, the Save As option is grayed out.

• If the source manufacturer part is private, then you must have the Maintain grant privilege to use the Save As feature.

• In the Save As dialog box, if you change the manufacturer from the source manufacturer, the Security check box is grayed out and manufacturer part instance grants aren’t copied to the new manufacturer part.

• The Supplier Portal doesn’t provide the Save As option or display the Created From field on manufacturer parts.

Key Resources

• Oracle Fusion Cloud SCM Using Product Development Guide, available on the Oracle Help Center.

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

• Manage Trading Partner Item (EGP_MANAGE_TRADING_PARTNER_ITEM_PRIV) or
• Manage Trading Partner Item Reference (EGP_MANAGE_TRADING_PARTNER_ITEM_REFERENCE_PRIV)
• View Trading Partner Item (EGP_VIEW_TRADING_PARTNER_ITEM_PRIV)

These privileges were available prior to this update.

If you opt in to the Extend Manufacturer Data with Application Composer feature and use granular privileges, then you must add the following data security policies to your role to have access to the Security tab on the Manufacturer Part page:

• EGP_TRADING_PARTNER_ITEMS
• EGP_PRIVATE_TRADING_PARTNERS

The procedure for adding a data security policy is the same for both EGP_TRADING_PARTNER_ITEMS and EGP_PRIVATE_TRADING_PARTNERS, except for the change in the value of the attribute Parameter1.

Here’s how you create the data security policies:

1. Sign in to Security Console.
2. Search for the role. Click Actions > Edit Role.
3. On the Edit Role page, click Data Security Policies.
4. In the Create Data Security Policy dialog box, enter the following:
   1. In the Policy Name field, enter the data security policy name.
   2. Data Resource: Search for and add the resource named Application Object (FND_OBJECTS).
   3. Data Set: Select by instance set.
   4. Condition Name: Select For Business Object Application Object specified by the Grant parameter PARAMETER1 for a specific grant for Table FND_OBJECTS.
   5. Enter a value for Parameter1 based on the data security policy:
      • For TRADING PARTNER ITEMS, enter EGP_TRADING_PARTNER_ITEMS.
      • For PRIVATE TRADING PARTNERS, enter EGP_PRIVATE_TRADING_PARTNERS.
5. Actions: Select all the actions.
6. Click OK.
7. Click Next.
8. Save your changes.

Selected Product Development Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle 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.

Missing AML Redlines

Redlines were not being captured correctly on change orders because date attribute values were not synchronized. This has been fixed, and the redlines are now captured correctly.

To update start date values for approved manufacturer lists (AMLs), run the Upgrade Product Management Data scheduled process with the following settings:

• Upgrade Process: Execution
• Functional Area: Item Relationships
• Feature: Update start dates on AML and display redlines
• Commit size: 10

If you want to see which AMLs need to be fixed, you can run the same scheduled process with the upgrade process set as Analysis instead of Execution.

Oracle reference: 35541838

Deleting Structure Components

Prior to this fix, you could delete a component from a structure created in the Product Information Management work area by opening the structure in the Product Development work area. Now the Delete button is disabled in the Product Development work area for such structures. If you want to delete a component from a structure, you must do it in the work area where the structure was created.

Oracle reference: 35902086

Steps to Enable

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

Product Hub

Efficiently Search for Documents Using the Item Object Identifier

A document is a type of item and can be identified based on the item class of the item. The document item class is configured in the Product Development work area. When searching for items in the Product Information Management work area, both items and documents are displayed in the search results. You can use the item object identifier to filter and identify document items in the search results.

Item Object Type Identifier Search Results

This feature helps to increase productivity by efficiently searching for a combination of documents and other items using a single query and easily identifying the documents from the search results.

Steps to Enable

Run the Upgrade Product Management Data scheduled process with the following options:

• Upgrade Process: Execution
• Functional Area: Item Attribute
• Feature: Item Object Types

Upgrade Product Management Data Scheduled Process

NOTE: Make sure to add the Item Object Type attribute to the index and views to enable the filter chip in the Product Management Search.

Tips And Considerations

• The Upgrade Product Management Data process has to update all the items. If there are enormous number of items, expect a delay in the completion of this process.

• Schedule to run the process on a weekend.

• Running the process in Analysis mode isn’t supported.

• Item Object Type attribute is hidden by default for items viewed in the Product Information Management work area.

• You can’t set the attribute value using the UI, import process, SOAP service, or REST service. It’s automatically set based on the item class of the item. Once set, you can’t modify the attribute value.

Key Resources

• Refer to the Items and Documents chapter in the Oracle Fusion Cloud SCM: Implementing Product Management guide, available on the Oracle Help Center.

Access Requirements

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Create Item Class Item Data (EGO_CREATE_ITEM_CLASS_ITEM_DATA)
• Manage Item (EGP_MANAGE_ITEM_PRIV)

These privileges were available prior to this update.

Selected Product Hub Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle 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.

Last Updated Date for New Item Requests Completed Before 22D

The last updated date couldn't be tracked on new item requests that were completed prior to the 22D update. With this fix, the Definition table captures the last updated date value in the Completed On column for such new item requests.

Oracle reference: 35284688

Editing Component Entities for a Past Date

Previously, you were allowed to edit component entities such as descriptive flexfields, substitutes, and reference designators for a past date by entering the date in the Date field (on the Edit Item Structure page).

With this fix, you can’t edit component entities for a past date.

Oracle reference: 35173177

Steps to Enable

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

Product Development & Product Hub Common

Use Import Tools to Delete Item Structure Data

Use the Delete transaction type in item structure import maps and FBDI templates to delete structure entities you don't want in the item structure. Use the All components batch option in the item structure import file to achieve dynamic synchronization of the item structure.

Additionally, the change order import process now updates the new revision of affected items automatically on an engineering change order.

Delete Structure Entities

In the import file for engineering and commercial items, set the transaction type as Delete for specific structure entities such as structure components, substitute components, and reference designators.

Then set the Update option to Changed components only for the item structure.

Changed Components Batch Option

Input File for Deletion of Component

Input File for Deletion of Reference Designator

You can also delete structure entities by selecting the transaction type as Delete in FBDI import.

Update All Components Dynamically

Use the Item Structure batch option All components to dynamically update the item structure. The import considers the data provided in the import file as the source of truth and updates the structure of the item accordingly.

All Components Batch Option

Automatically Update New Revision of Affected Items on Change Orders

The item import has been enhanced to populate the new revision of the affected item automatically on engineering change orders as it does on the user interface.

With this feature, you can:

• Automate changes to your structure by enabling deletion of components through the import process.
• Improve ingestion of changes from your CAD BOMs by enabling deletion of reference designators.
• Eliminate manual intervention by updating the revision on change orders during item import.

Steps to Enable

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

Tips And Considerations

• To remove any structure data using All components batch option, exclude the details of the entity such as component, reference designator or substitute component from the import file.

• The All components batch option only supports the synchronization of structure entities like components, substitutes, and reference designators. It doesn’t support the synchronization of AMLs.

• The revision number isn’t incremented automatically on the affected item of an engineering change order if:

  • The affected item is part of another change order which is in scheduled status.

  • The change in revision number doesn't follow a standard pattern, or it's not obvious what the next revision should be. For example, the initial revision number is .001, or Z.

• The Delete transaction type and the Replace function aren’t supported for the All components batch option in structure import.

• If there are errors when using the All components batch option the complete transaction isn’t rolled back. The changes without errors are imported and the changes that caused errors are captured in the error log.

• The import will error out if you try to delete the component which has been added or redlined on the same change order. You can use the UI or webservice to delete the component in this case. Note that this issue has been fixed in Update 24A.

• If the import file includes a Delete component transaction type and an End Date value, the application will use the end date to complete the import.

• The following existing validations will be applicable for the All components batch option and the Delete component transaction type:

  • You must route the structure changes through a change order if the parent item is a released engineering item or if it’s already assigned to a change order.

  • If you want to merge the structure changes on to the existing affected item, the effective dates must match or they must be set to effective on approval.

Key Resources

• Refer to the Item Batch Structure Options topic in Oracle Fusion Cloud SCM: Using Product Master Data Management, available on the Oracle Help Center.

Access Requirements

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Functional privilege to import items:
  • Manage File Import and Export (FND_MANAGE_FILE_IMPORT_AND_EXPORT_PRIV)

• Functional privilege 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

These privileges were available prior to this update.

Selected Product Development & Product Hub Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Product Development and Oracle Product Hub 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.

Mass Updates for Component UOM

Prior to this update, you couldn't edit the UOM on structure components during mass uploads, so you had to manually edit the UOM after upload.

You can now add or update the component UOM using import tools and web services.

Oracle reference: 29024968

Character Limit for Descriptive Flexfield Attributes

Prior to this fix, the character limit was 150 characters for descriptive flexfield attributes corresponding to table columns 26 through 30. 

Now the limit has been extended to 4000 characters.

Oracle reference: 35377991

Missing Title on Request Info Notification

Prior to this fix, when an approver sent a request for information on a change order, the title on the bell notification wasn’t displayed for the change analyst. This issue occurred on Request Info notifications configured using BPM Worklist.

With this fix, the title Information Requested appears in the bell notification for the change analyst.

Oracle reference:34583696, 35288949

Created From Attribute Missing in OTBI

The Created From attribute was not available in Oracle Transactional Business Intelligence (OTBI) subject areas for items and trading partner items.

With this fix, the attribute has been made available in these subject areas.

Oracle reference: 35685214

View Affected Object Number on Redline Summary

The redline summary view of a change order's affected objects didn't show the selected object's number. This made it difficult to identify which redlines you were viewing if you had a long list of affected objects and the context of the selected object was not visible within the page view.

With this fix, the redline summary view includes the affected object number in the header area so that you can easily identify the object for which you're viewing redlines.

Oracle reference: 35380130

Steps to Enable

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

Efficiently Manage Multiple Values for Item Attributes

When populating the values for an extensible flexfield attribute using Oracle Product Hub and Oracle Product Development UIs, you can assign multiple values to one UI field itself. This negates the need for adding one row each for the attribute value. To avail this feature, the attribute should have been configured with the new display type called Multiple Select List of Values (referred to as multiselect enabled attribute).

In the UI, when you navigate to a multiselect enabled attribute and click the drop-down list, the values of the associated value set will be displayed as a List Of Values (LOV) of check boxes. From the LOV, you can choose multiple values applicable to the item by selecting the check box. When you navigate out of the field, all the values you've selected will be displayed in the field as a concatenated string using semi-colon as the delimiter. Similarly, in the edit mode,  if you navigate back to the field and click the drop-down list, the concatenated values will be displayed as an LOV of check boxes with a tick mark for the selected values.

Additionally, the UI also lists All as an entry in the LOV. If you select All, then all the values in the drop-down list will be autoselected and the field will display the value All instead of the concatenated list of selected values.

This feature has been enabled in the following UIs.

List of Impacted UIs

Work Area	UI Name	Additional Information
Product Information Management	Edit Items page
Product Information Management	Edit Affected Object Details page	Edit Commercialization Change Order and select Affected Object
Product Development	Edit Items page
Product Development	Edit Affected Object Details page	Edit Change Order and select Affected Object

Other than the preceding UIs, there's no change in how the data is populated or accessed (example, item import, item rules, and web services) or reported (example, publications and BI reports). For example, in the UI, even if you've assigned four values (example, Forest Green, Ocean Blue, Wine Red, and Warm Yellow as colors) for the multiselect enabled attribute in a single row or field, for the purpose of all other functionalities, it's considered as four rows (one row for each color) of the multirow attribute group.

Product Information Management - Edit Items Page Rendering Multiselect Enabled Attribute

The Product Development Edit Items page also supports multiselect extensible flexfields that have been added to the Product Development page.

Product Development - Edit Items Page Rendering Multiselect Enabled Attribute

You can redline multiselect enabled attributes on change orders. Values that were deselected are displayed in red text with a strikethrough. Values that are newly selected are displayed in green text.

Redlining Multiselect Enabled Attribute on Change Order Affected Object Details Page

This feature improves:

• Efficiency and user experience: Select multiple values at a time with a few clicks.
• User experience with better usability: View multiple values in a single field or row.

Steps to Enable

1. In the Setup and Maintenance work area, go to the Manage Item Attribute Groups and Attributes task.

2. Configure a new attribute group with the following key configurations:

• Translatable: Not selected.
• Behavior: Select Multiple Rows.
• Context Usage: Select Item.

NOTE: The multiselect enabled attribute must be the first attribute in the attribute group. Regardless of its enabled status, there can be only one multiselect enabled attribute in the attribute group.

When creating an attribute, specify the following:

• Data Type: Select Character.
• Display Type: Select Multiple Select List of Values.
• Unique Key: Select this check box.

The associated value set must have the following configuration:

• Validation Type: Select Independent.
• Value Data Type: Select  Character.
• Value Subtype: Select Text or Translated Text.

Manage Item Attribute Groups and Attributes - Edit Attribute Page

Tips And Considerations

• You can't modify an attribute of an existing attribute group to leverage this feature, even if the attribute group isn't associated with any item class.

• If an attribute group contains multiple attributes including the multiselect enabled attribute, the attribute group will be rendered as a set of fields similar to a single row attribute group. In such cases, the data will be stored similar to a multirow attribute group with the values of the attributes other than the multiselect attribute repeated across all the rows.

• The attribute group with multiselect enabled attributes can't be accessed via Product Hub's Supplier Portal UIs. However, the same attribute groups can be populated by the suppliers using the REST services and smart spreadsheets.

• In an attribute group with multiselect-enabled attribute, any non-multiselect enabled attribute that's marked as Required will be considered as Required only if the multiselect enabled attribute has at least one value populated. This means, in the UI, if all the values of a multiselect enabled attribute is deleted or removed, then when saving the changes, the value in all other attributes in the attribute group will be deleted.

• After you configure a new attribute group and assign it to an item class, you must perform the Deploy Item Extensible Flexfield task.

Key Resources

• Refer to the Configure Extensible Flexfields or User Defined Attributes section in the Oracle Fusion Cloud SCM: Implementing Product Management guide, available on the Oracle Help Center.

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

• For items:
  • View Item (EGP_VIEW_ITEM_PRIV)
  • Edit Item (EGP_MANAGE_ITEM_PRIV)

• To redline multiselect item flexfields on change orders, you need the preceding privileges along with the following privileges:
  • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORKFLOW_OBJECTS_PRIV) and one of the following:
    • View Change Order (ACA_VIEW_CHANGE_ORDERS_PRIV)
    • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)

These privileges were available prior to this update.

Product Lifecycle Management Common

Retain Copied Data on Clipboard

The clipboard functionality is enhanced in the following ways:

• The contents of the clipboard are now retained when you sign out of the application and sign back in.

• Items in the clipboard are sorted by the date they were added, newest to oldest, and limited to 500 items.

• You can select one or more items from the clipboard and use the Paste icon or drag and drop function to add them to the target locations, such as the Affected Items tab, Item Structure tab, or Relationships tab.

• The selections are deselected when you:
  • Add more items to the clipboard
  • Sign out and sign back in

Contents Copied to Clipboard

This feature improves productivity by providing quick access to items selected in a previous session. It eliminates the need for business users to search and add the items to the clipboard again when they start a new session.

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 24B

Tips And Considerations

You can no longer copy and paste directly from the source location to the target location.  For example, you can't copy items from search results or structures and paste these directly to the Affected Items tab or Item Structure tab. You must copy the items to the clipboard, then select them from the clipboard and paste to the target location.

Key Resources

• Refer to the Oracle Fusion Cloud SCM Using Product Development guide, available on the Oracle Help Center.

Access Requirements

Users who are assigned a configured job role that contains this privilege can access this feature:

• Access Clipboard (ACA_ACCESS_CLIPBOARD_PRIV)

Use Extensible Flexfields on Changes, Problem Reports, and Corrective Actions

Similar to items, you can now add extensible flexfields at the header level to change orders, change requests, problem reports and corrective actions. Unlike global descriptive flexfields that are added to all change types at all levels, you can choose to add extensible flexfields at the following levels:

• All Change Types - this is at the top level of change types and includes predefined as well as copied change types. Extensible flexfields added at this level are inherited by predefined and copied change types.

• Predefined change types  - this is the second level of change types. Extensible flexfields added at this level are inherited to change types copied from the predefined change types (Engineering Change Order, Commercialization Change Order, Change Order without Revision Control, Change Request, Deviation Request, Problem Report, and Corrective Action).

• Change types copied from predefined ones - this is at the third level. Extensible flexfields added at this level aren't inherited.

The extensible flexfields are available on:

• Manage Pages on Change Orders, Change Requests, Problem Reports and Corrective Actions
• Create and Edit Pages on Change Orders, Change Requests, Problem Reports and Corrective Actions
• Change Order Details Report
• OTBI Reports
• Change Audit Report
• REST APIs
• SOAP Services
• Number Assignment and Validation Rules

Manage Pages on Change Orders, Change Requests, Problem Reports and Corrective Actions

• You now have new Manage Change Orders, Manage Change Requests, Manage Problem Reports and Manage Corrective Actions pages for searching.
  • The default search filter is set to  All Change Types.
  • You can include extensible flexfields both in search criteria and search results.
• 

Select and Add Extensibe Flexfields in Search Criteria

Create and Edit Pages on Change Orders, Change Requests, Problem Reports and Corrective Actions

• When you create changes:
  • The create dialog box shows the required extensible flexfields as well as the ones configured in number assignment rules. The sequence of flexfields is as per the setup.
  • When using Save As or Duplicate, select the Additional Information option to copy over extensible flexfields.

• When you edit changes:
  • The extensible flexfields appear on the General Information tab after the descriptive flexfields.

Note that the Manage Change Header Attributes action in the Additional Workflow Controls table for the change type must be set to All or Additional Information to edit extensible flexfields. Otherwise, they are read-only.

         

Editing Change Header Extensible Flexfields

Change Order Details Report

• The report now includes extensible flexfields in the Change Order Information section.

• 

  Change Order Details Report with Multi-row Change Extensible Flexfields

OTBI Reports

• OTBI includes extensible flexfields under the following Product Management subject areas:
  • Change Order Real Time
  • Change Order Approvals Real Time

          

OTBI Change Order Real Time Report with Extensible Flexfields

Change Audit Report

• You can now track extensible flexfields in the audit report if they’re configured in Product Hub Audit Policy. 

REST APIs

• Integration users can now include change extensible flexfields when creating or updating a change.

• Following REST APIs are enhanced to support extensible flexfields:
  • Product Change Orders V2
  • Product Change Requests
  • Quality Problem Reports
  • Quality Corrective and Preventive Actions

         

Update Change Extensible Flexfields Using REST APIs

SOAP Services

• The following Product Design Change Order Services are enhanced to support extensible flexfields:
  • createOrUpdateChangeObject(Sync and Async)
  • getChangeOrder(Sync and Async)
  • findChangeObject(Sync and Async)
  • findChangeOrderRedline (Sync and Async)

            

Update Change Extensible Flexfields Using SOAP Web Services

Number Assignment and Validation Rules

• Assignment rule for number generation:
  • You can now use extensible flexfields in an assignment rule for generating change numbers. The extensible flexfields used in the rule also appear as required fields in the Create Change and the Save As dialog boxes.

           

Extensible Flexfields Used in the Rule for Generating Change Number

• Entry and exit criteria:
  • You can now use extensible flexfields in the validation rules for entry and exit criteria.

             

Extensible Flexfields Used in the Rule for Entry Criteria

This feature benefits your business by the following:

• Capture richer descriptive attributes to aid the timely and accurate implementation of workflows for changes, problem reports, and corrective actions.

• Leverage configured attributes for intelligent change numbering and help users quickly find their change workflows.

• Expand or add validation criteria for accurate change definition and execution.

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 24B

Configuring and editing extensible flexfields

• Manage Extensible Flexfields task has a new flexfield code EGO_CHANGE_EFF to add extensible flexfields to the change type header.
  • Please refer to the Overview of Flexfields topic in the Implementing Common Features for SCM Guide listed in Key Resources for details on defining and deploying extensible flexfields.

• You can migrate the extensible flexfields to different environments using the Export and Import features in Functional Setup Manager.

 

View the Extensible Flexfields for the Selected Change Type

• Once you opt in to this feature, the Manage Change Order Types lists the change types in a hierarchy.

• When you edit a change type, you can view the extensible flexfields on the Attributes tab. The Inherited column shows where the flexfields are inherited. The Associated Category column shows the change type for which the flexfields are defined.

 

Attributes Tab Showing Flexfields for the Change Type

Tips And Considerations

Setup

• You can only add alphanumeric characters and underscores in the Internal Name field on the change type. (You can’t use hyphens when you create a new change type.)

• It’s recommended to use the Manage Extensible Flexfields task to add or remove extensible flexfields.

• You can't set extensible flexfields as required if changes are in progress for the change type.
  • When you get the error message, you must cancel out of the page.

• The Associated Category column on the Pages tab (of the Edit Extensible Flexfield task) shows All Change Types even when you select a predefined or copied change type. Use the Associated Contexts tab to see the correct category.

• You can use XML format to export and import both value sets and extensible flexfields at the same time. If using CSV format, you must export and import value sets first and you can then export and import the extensible flexfields.

• If you opt in to this feature, deploy extensible flexfields and opt out of this feature, the flexfields aren’t available on the Create, Manage and Edit pages for change orders, change requests, problem reports, and corrective actions, but the flexfields will be available on REST API, SOAP services, and import.

• Extensible flexfields are inherited down the hierarchy of change types. If you add them at the first (or top level), they are automatically inherited at the second and third levels of the hierarchy. If you add them only to the second level, they are automatically inherited to the third level. So you can't manually add them at two different levels. For example, if you add the flexfields to the predefined Engineering Change Order change type which is at the second level, you can't also add the same to All Change Types which is at the first level. You'd have to delete them from the second level and then include them at the first level so that they are automatically inherited to the second level.

• When you duplicate a change type that's copied from a predefined change type, the extensible flexfields added on the source change type will not be copied over to the new change type.

• Data security isn't available on change extensible flexfields.

• If you want flexfields to appear as search criteria by default, select the Indexed option on the Edit Segment page.

Create and Edit Pages On Change Orders, Change Requests, Problem Reports And Corrective Actions

• If you haven’t opted in to the feature Use Simplified Change Management Interface, but have opted in to this feature, you won't be able to see extensible flexfields in the Product Information Management work area.

• You can’t create changes using All Change Types. It’s used to indicate the hierarchy of change types and the inheritance of extensible flexfields across change types.

Manage Change Pages on Change Orders, Change Requests, Problem Reports and Corrective Actions

• Quality users will now see new Manage Problem Report and Manage Corrective Action pages that are similar to Manage Change Orders.

• Saved searches created:
  • Prior to the opt-in of this feature are no longer available and must be recreated.
  • For specific change types are only available when that specific change type is selected in the type drop-down list.

• The Application Default saved search will replace the current default search and any other saved searches that you’ve created. This saved search is run by default when you select a change type.

• When you search for changes at a predefined change type level (Engineering Change Order, Commercialization Change Order, Change Order without Revision Control, Change Request, Deviation Request, Problem Report, and Corrective Action), the search results also include changes at the third level. 
  • Additionally, when you search for the predefined change type Change Requests, the search results also include Deviation Requests.

• In the Product Development work area, the Manage Change Requests page:
  • No longer supports the following: Updated By, Last Update Date, Approver, Approver Action, Approver Action Date, and context-sensitive descriptive flexfields. These fields aren’t visible in the search results table.
  • No longer includes the Change Completeness icon in the search results.
  • No longer includes is blank and is not blank operators in the search criteria for the Name and Number. This is to ensure good performance.

• Selection of multiple rows on the Manage Change pages:
  • Supported only for the Generate Report action on Manage Change Orders pages in the Product Information Management work area, Manage Change Requests in the Product Development work area and Manage Problem Reports and Manage Corrective Actions in the Quality Management work area.
  • Supported for both Generate Report and Publish actions on the Manage Change Orders page in the Product Development work area.

OTBI

For extensible flexfields to be available in OTBI, here’s want you need to do:

• Edit the context and select the BI Enabled option in Business Intelligence.
• Run the scheduled process Import Oracle Fusion Data Extensions for Transactional Business Intelligence.

REST APIs, SOAP Services and Import

When you import or create items on a change using REST APIs or SOAP services, the required extensible flexfields must have a default value to successfully create the change order.

Change Order Details Report

• If the column width in a multi-row table exceeds the page width, the content is truncated in the PDF format. It’s recommended to use the HTML format in such cases.

• If the extensible flexfields are added in the Associated Contexts tab and not on the Pages tab of the Edit Extensible flexfields page, they appear in the report only if they have a default value.

Number Assignment and Validation Rules

• The following attributes aren’t supported in number assignment rules: Approval Date, Assigned To, Change ID, Created By, Creation Date, Need by Date, Reason, and Requested by.

• Multi-row extensible flexfields aren’t supported in number generation rules.

• Groovy scripts aren’t supported for creating validations and assignment rules on changes using extensible flexfields. It’s recommended to use item rules.

Key Resources

• Refer to the Overview of Flexfields topic in the Implementing Common Features for SCM Guide, available on the Oracle Help Center.

• Oracle Fusion Cloud SCM Implementing Product Management Guide, available on the Oracle Help Center.

• Oracle Fusion Cloud SCM Using Product Development guide, available on the Oracle Help Center.

• Oracle Fusion Cloud SCM Using Product Master Data Management Guide, available on the Oracle Help Center.

• Refer to the Overview of Setup Data Export and Import topic in the Using Functional Setup Manager Guide, available on the Oracle Help Center.

• How to update or redline Item EFF Attributes using SOAP Web Services

Access Requirements

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Manage Change Attribute Groups and Attributes
  • Manage Item Change Order Type (EGO_MANAGE_ITEM_CHANGE_ORDER_TYPE_PRIV)

• Manage Extensible Flexfields
  • Manage Application Extensible Flexfield (FND_APP_MANAGE_EXTENSIBLE_FLEXFIELD_PRIV)

• Access Change Extensible Flexfields
  • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) and one of the following:
    • Change order access:
      • View Change Order (ACA_VIEW_CHANGE_ORDERS_PRIV)
      • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)
    • Change request access:
      • View Change Request (ACA_VIEW_CHANGE_REQUESTS_PRIV)
      • Manage Change Requests (ACA_MANAGE_CHANGE_REQUESTS_PRIV)
    • Problem report access:
      • View Problem Report (ACA_VIEW_PROBLEM_REPORTS_PRIV)
      • Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV)
    • Corrective action access:
      • View Corrective Actions (ACA_VIEW_CORRECTIVE_ACTIONS_PRIV)
      • Manage Corrective Actions (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)

• Access Change Extensible Flexfields in Supplier Portal
  • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) and one of the following:
    • Change order access:
      • View Change Order in Supplier Portal (ACA_VIEW_CHANGE_ORDER_SUPPLIER_PORTAL_PRIV)
      • Manage Change Orders in Supplier Portal (ACA_MANAGE_CHANGE_ORDERS_SUPPLIER_PORTAL_PRIV)
    • Change request access:
      • View Change Request in Supplier Portal (ACA_VIEW_CHANGE_REQUEST_SUPPLIER_PORTAL_PRIV)
      • Manage Change Requests in Supplier Portal (ACA_MANAGE_CHANGE_REQUESTS_SUPPLIER_PORTAL_PRIV)
    • Problem report access:
      • View Problem Report in Supplier Portal (ACA_VIEW_PROBLEM_REPORT_SUPPLIER_PORTAL_PRIV)
      • Manage Supplier Problem Reports (ACA_MANAGE_SUPPLIER_PROBLEM_REPORTS_PRIV)
    • Corrective action access:
      • View Corrective Action in Supplier Portal (ACA_VIEW_CORRECTIVE_ACTION_SUPPLIER_PORTAL_PRIV)
      • Manage Supplier Corrective Action (ACA_MANAGE_SUPPLIER_CORRECTIVE_ACTIONS_PRIV)

• Audit access:
  • Manage Product Audit Trail Reports (EGI_MANAGE_PROD_AUDIT_REPORTS_PRIV)

• Import access:
  • Import Item (EGP_IMPORT_ITEM_PRIV)
  • Manage Item Import Map (EGI_MANAGE_ITEM_IMPORT_MAP_PRIV)

These privileges were available prior to this update.

IMPORTANT Actions and Considerations

Replaced and Removed Features

From time to time, Oracle replaces existing Cloud service features with new features, or removes existing features. Replaced features may be put on a path to removal. As a best practice, you should use the newer version of a replaced feature as soon as the newer version is available.

This section identifies the features in this Cloud service that have been replaced or will be removed.

Module	Removed Feature	Target Removal	Replacement Feature	Replaced In	Additional Information
Product Hub	Items REST service	24C	Items Version 2 REST service	18C	No additional enhancements have been made to the Items REST service since update 19A. Items Version 2 provides broader functionality, and you should move to it at your earliest convenience. For details about the Items Version 2 REST service, see REST API for Oracle Fusion Cloud SCM on the Oracle Help Center.
Product Development	Create a Child Object for a Configured Change Order	23D	None	NA	Starting in update 23D, you won't be able to create child objects for configured change orders. Instead of creating a child object, you can create a 1:M (one-to-many) relationship for your configured change order in the Relationships node in Application Composer. If you've created child objects for configured change orders prior to 23D, you can continue to use those child objects. However, if you do so, then you can create only one change order per item when you import items. To learn how to create relationships, see the Object Relationships topic in Oracle Fusion Cloud: Configuring Applications Using Application Composer.

Changes to Feature Name and Supported Functionality

The feature Extend Manufacturer Data with Application Composer (ORA_ACA_MFR_ADDL_INFO) has been renamed to Update Manufacturer Management and the ability to extend manufacturer objects using Application Composer has been disabled. You can continue to use the Manufacturer REST resource and Oracle Transactional Business Intelligence (OTBI) reports for manufacturers.

After you update to 23D, your users won’t see the Create Manufacturer and Manage Manufacturers tasks in the Product Development work area until you edit a configured role that you’ve assigned to those users. Assign the following privileges to the configured roles of any users who need access to the Create Manufacturer and Manage Manufacturers tasks:

• Create Manufacturer (EGP_CREATE_MANUFACTURER_PRIV)
  • Users with Create Manufacturer privilege should also be given Manage Manufacturer privilege (EGP_MANAGE_MANUFACTURER_PRIV)

• View Manufacturer (EGP_VIEW_MANUFACTURER_PRIV)

• Manage Manufacturer (EGP_MANAGE_MANUFACTURER_PRIV)

In addition, verify that your configured roles for manufacturer access have the HZ_PARTIES data security policy. Here’s how you create and assign the required data security policy for a configured role:

1. In the Security Console work area, search for and select the configured role you want to edit.
2. Click Actions > Edit Role.
3. On the Edit Role page, click Data Security Policies.
4. Click Create Data Security Policy.
   • In the Create Data Security Policy section, enter the following:
     1. Data Resource: Search for and add the resource named HZ_PARTIES (Trading Community Party).
     2. Data Set: Select All values.
     3. Actions: Select all the actions.
     4. Policy Name: <name>
     5. Click OK and click Next.
5. Save your changes.

For details of the Update Manufacturer Management feature, see:

• Update Manufacturer Management
• Configure Manufacturer Search