Cloud Readiness / Oracle Fusion Cloud Product Lifecycle Management
What's New
Expand All


  1. Update 23A
  1. Revision History
  2. Overview
  3. Pre-Update and Post-Update Tasks
  4. Optional Uptake of New Features (Opt In)
  5. Feature Summary
  6. Quality Management
    1. Quality Management
        1. Use 8D Workflow for Corrective Actions
        2. Selected Quality Management Bug Fixes in This Update
  7. Product Lifecycle Management
    1. Product Development
        1. Manage and Secure Manufacturers Efficiently
        2. Selected Product Development Bug Fixes in This Update
    2. Product Hub
        1. Improved Selection of Categories Within a Hierarchy for Item Category Assignments
        2. Automate Item Import Using Oracle Integration Cloud
        3. Optimize Extraction of Item Extensible Flexfields for Business Intelligence
        4. Define Default Repair Transaction Code for an Asset Item
        5. Generate and Assign GTINs to Items Automatically Using Rules
        6. Compute Check Digit for GTINs Using Item Rules
        7. Support Kit Items on Transfer Orders
        8. Create UOM Conversion Data for All Items
        9. Use UOM Names in Packaging Strings
        10. Selected Product Hub Bug Fixes in This Update
    3. Product Development & Product Hub Common
        1. Autocomplete Changes Efficiently to Ensure Change Workflow Resiliency
        2. Analyze Where Items Are Used As Substitutes
        3. Use Enhanced REST Services to Manage Items and Changes
        4. Reinstate Obsolete Items to Earlier Lifecycle Phases
        5. Use Audit Reports to Govern User Activities on Attachments
        6. Selected Product Development and Product Hub Common Bug Fixes in This Update
    4. Product Lifecycle Management Common
        1. Notify Approvers upon Removal from Approvers List
        2. Associate Trading Partner References to a Change or Quality Workflow

Update 23A

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
20 OCT 2023 Product Development Manage and Secure Manufacturers Efficiently Updated document. Revised feature information.
12 APR 2023 Product Development and Product Hub Common Use Audit Reports to Govern User Activities on Attachments

Updated document. Added a feature that was backported in the March monthly maintenance pack.

27 FEB 2023 Product Development Selected Product Development Bug Fixes in This Update Updated document. Revised descriptions.
30 JAN 2023 Product Hub Selected Product Hub Bug Fixes in This Update Updated document. Revised description for Oracle reference 34302547.
30 JAN 2023 Product Development and Product Hub Common Analyze Where Items Are Used As Substitutes Updated document. Revised Tips and Considerations.
17 JAN 2023 Product Hub Selected Product Hub Bug Fixes in This Update Updated document. Added an entry.
10 JAN 2023 Product Hub Optimize Extraction of Item Extensible Flexfields for Business Intelligence Updated document. Revised Tips and Considerations section.
02 DEC 2022     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 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

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Quality Management

Quality Management

Use 8D Workflow for Corrective Actions

Selected Quality Management Bug Fixes in This Update

Product Lifecycle Management

Product Development

Manage and Secure Manufacturers Efficiently

Selected Product Development Bug Fixes in This Update

Product Hub

Improved Selection of Categories Within a Hierarchy for Item Category Assignments

Automate Item Import Using Oracle Integration Cloud

Optimize Extraction of Item Extensible Flexfields for Business Intelligence

Define Default Repair Transaction Code for an Asset Item

Generate and Assign GTINs to Items Automatically Using Rules

Compute Check Digit for GTINs Using Item Rules

Support Kit Items on Transfer Orders

Create UOM Conversion Data for All Items

Use UOM Names in Packaging Strings

Selected Product Hub Bug Fixes in This Update

Product Development & Product Hub Common

Autocomplete Changes Efficiently to Ensure Change Workflow Resiliency

Analyze Where Items Are Used As Substitutes

Use Enhanced REST Services to Manage Items and Changes

Reinstate Obsolete Items to Earlier Lifecycle Phases

Use Audit Reports to Govern User Activities on Attachments

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

Product Lifecycle Management Common

Notify Approvers upon Removal from Approvers List

Associate Trading Partner References to a Change or Quality Workflow

Quality Management

Quality Management

Use 8D Workflow for Corrective Actions

You can now use a predefined Corrective Action type, 8D Corrective Actions, based on the eight disciplines problem solving approach.

In the Create Corrective Action dialog box, you can now select 8D Corrective Actions from the Type drop-down list.

8D Corrective Actions Type in Create Dialog

Workflow of 8D Corrective Action Type

Use a structured, preconfigured workflow template based on the 8D methodology to define the quality problem, identify the root cause, and execute the corrective and preventative action (CAPA) necessary to prevent future recurrence of the quality problem.

Steps to Enable

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

Key Resources

  • Oracle Fusion Cloud SCM: Quality Management guide, available on the Oracle Help Center.

Access Requirements

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 must have the following privilege:
    • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV)
    • View Corrective Action (ACA_VIEW_CORRECTIVE_ACTIONS_PRIV)
    • Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)

Selected Quality Management Bug Fixes in This Update

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

Corrective Action Creation Date

The search results for corrective actions always showed the creation date in UTC, regardless of the preferences set up in the user's General Preferences: Regional Setting page.

With this fix, the search results show each action's creation date in the time zone that the user has specified.

Oracle reference: 34059377

Quality Issue Visibility

The visibility of a quality issue (in the Quality Management work area) was not being restricted to the users listed on its Security tab. Other users could find it by navigating to the Relationships tab of an associated quality action - Quality Action > Relationships tab > Quality Issue.

With this fix, only users who are listed on the Security tab of the quality issue have access to it.

Oracle reference: 29968220

Steps to Enable

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

Product Lifecycle Management

Product Development

Manage and Secure Manufacturers Efficiently

You can now filter your manufacturer search using location fields. Use the Add Fields button on the Manage Manufacturers page to include details such as Country, State, City, etc., in the search criteria. These attributes are also also added as columns in the default search results table.

Additionally, the Where Used tab on the manufacturer page now supports the Export to Excel action.

Manage Manufacturers Search Criteria with Location Attributes Included

Manufacturer Where Used Export

You can also control access to manufacturer parts using the new Manufacturer Security tab.

Manufacturer Security Tab

With these enhancements, you can:

  • Quickly search for manufacturers using their location as a criteria.
  • Easily share and analyze Manufacturer Where Used data by exporting it to Excel.

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 ManagementNo Longer Optional From: Update 23C

To use the Manage and Secure Manufacturers Efficiently feature, you must opt in to its parent feature: Update Manufacturer Management. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

If you opt in to Update Manufacturer Management and use granular privileges, then you must add the following data security policies to your role to have access to the manufacturer security tab:

  • 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.
  1. Search for the role. Click Actions > Edit Role.
  1. On the Edit Role page, click Data Security Policies.
  1. 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.
  1. Actions: Select all the actions.
  1. Click OK.
  1. Click Next.
  1. Save your changes.

Tips And Considerations

  • Grant modifications and updates to the Public setting for manufacturers in the Product Development work area and trading partners in the Product Information Management work area are automatically synced. Updates made to these settings form either work area are automatically reflected in the other.
  • Manufacturer parts inherit the grants added to the parent manufacturer, but the security tab will not be displayed on the manufacturer part.  Users can see these inherited grants and edit the trading partner item to add additional individual grants in the Trading Partner Item page in the Product Information Management work area.  These individual grants will apply to the manufacturer part and the item AML.

Key Resources

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

Access Requirements

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:
    • To view, create, and manage manufacturers:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
  • Users who are assigned a configured job role that contains these privileges can access this feature:
    • To access manufacturer data:
      • 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)
  • Users who are assigned configured roles also need to add a Data Security Policy.

Here’s how you create a new data security policy for a configured role:

  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. Click Create Data Security Policy.
    1. In the Create Data Security Policy, enter the following:
      1. Policy Name: <unique name>
      2. Data Resource: Search for and add the resource named HZ_PARTIES (Trading Community Party).
      3. Data Set: Select All values.
      4. Actions: Select all the actions.
      5. Click OK and click Next.
  5. 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.

Comparing Structures

When you used the Compare Structures feature, duplicate items sometimes appeared on the first item structure and for structures with components beyond the first level. The issue was intermittent. The comparison result was misaligned vertically (due to the duplicate items).

The intermittent issue related to duplicate items on the first item structure is fixed, which resolves the vertical misalignment issue.

Oracle reference: 33872118

Validation Rules Affecting Structure Page Display

When a validation rule related to structure creation failed, a corresponding error message appeared. After you closed the error message and the Create Structure window, the page didn't respond, so you had to refresh the page.

The issue is fixed. You don't need to refresh the page after you close the error message and Create Structure window.

Oracle reference: 33579185

Steps to Enable

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

Product Hub

Improved Selection of Categories Within a Hierarchy for Item Category Assignments

You can easily assign categories to items using the improved way of selecting categories within a hierarchy. When you type the name of the catalog or category you want to assign, it automatically matches the name with the available catalog and category names and displays them as suggestions. Category suggestion also includes the catalog name to help you know the catalog for the category.

When you select a category from the displayed suggestions, the catalog and category names are populated in the respective fields in the user interface.

If you select a catalog from the displayed suggestions, a window shows a list of categories and their paths within the hierarchy for the selected catalog. The hierarchy path allows you to identify the correct category based on the position of the category within the hierarchy. After you select a category from this list and click OK, the catalog and category names are populated in the respective fields in the user interface.

If the suggestions doesn’t show the required category, you can use the Search icon to select or search a catalog and display the categories for the selected catalog.

Enter a Catalog or Category Name to View the Suggestions

Enter a Catalog or Category Name to View the Suggestions

Select a Category From the Catalog Hierarchy

Select a Category From the Catalog Hierarchy

This feature provides easier visibility of the categories and helps to determine the correct category to assign to the item.

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 ManagementNo Longer Optional From: Update 23C

Tips And Considerations

When searching for categories within a catalog with a single level of hierarchy, the suggestions provide an easy way to find the category by typing all or part of the category name.

Duplicate category names are displayed in the suggestions along with the catalog name. Duplicate category names in catalogs with a multilevel hierarchy are displayed with their hierarchy path.

Key Resources

Access Requirements

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 these predefined job roles can access this feature:
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_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 Catalog (EGP_MANAGE_ITEM_CATALOG_PRIV

Automate Item Import Using Oracle Integration Cloud

You can use the new operations of the Item Batch Maintenance service to monitor and manage notifications for the import and publication jobs that are processed successfully or processed with errors. Also, a new business event indicates the import process has successfully processed different entity types in the batch.

Using these new operations and the event, you can develop a fully automated integration in conjunction with Oracle Integration Cloud to import items, including the seamless handling of import errors. Additionally, managing the publication process errors can also be automated.

Steps to Enable

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

Tips And Considerations

You can fetch details using the following operations in the Item Batch Maintenance service:

  • findItemImportErrors - Provides a list of errors for a given Request ID for the import process.
  • findItemImportBulkloadRecords - Provides a list of all entities that are successfully imported for a Request ID for the import process.
  • findPublicationJobErrors - Provides a list of errors for a given Publication Request ID for the publication process.

The Post Import Bulk Load business event is raised once after a successful import process for each entity type with the request ID.

Key Resources

  • Refer to the Item Batch Maintenance SOAP Web service in the Oracle Fusion Cloud SCM: SOAP Web Services for SCM guide, available on the Oracle Help Center.

Access Requirements

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned this predefined job roles can access this feature:
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
  • Users who are assigned configured job roles that contain this privilege can access this feature:
    • Manage Item Batches (EGI_MANAGE_ITEM_BATCH_PRIV)

Optimize Extraction of Item Extensible Flexfields for Business Intelligence

You can extract the extensible flexfield data for items, item revisions, and item supplier associations in bulk using the Business Intelligence Cloud Connector (BICC). BI view objects are available for each extensible flexfield context. You can use the respective view object and set up the data store for extraction. You can perform full extraction or incremental extraction of data.

The following image shows the BICC data store setup for extracting extensible flexfield data using BI view object.

BICC Console

BICC Console

This feature provides an alternate method to extract the product data in bulk and load it into the designated external storage areas. It may better suit your integration requirements to communicate with downstream systems.

Steps to Enable

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

Tips And Considerations

After making changes to the extensible flexfield’s metadata, you must deploy the extensible flexfields offline before extracting the data using BICC.

If you've secured the View access of the extensible flexfield context with a privilege, you must grant this privilege to the FUSION_APPS_OBIA_BIEE_APPID user by using the Manage Item Classes task in the Setup and Maintenance work area and then navigating to the Security tab on the Edit Item Class page. After granting this privilege, the extensible flexfield data can be extracted using BICC.

Key Resources

Access Requirements

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 configured job roles that contains this privilege can access this feature:
    • OBIA_EXTRACTTRANSFORMLOAD_RWD

Define Default Repair Transaction Code for an Asset Item

You can define and then set the default repair transaction codes that are used in warranty coverages, warranty contracts, work order resources, and material transactions of an asset item as a part of supplier warranty. 

In the Setup and Maintenance work area, go to the Manage Condition Event Codes task and define the repair transaction codes. The repair transaction codes must be of type Transaction Code (TXN_CODE). You can then set the default repair transaction code for an item as shown in the following screenshot.

Default Repair Transaction Code

Default Repair Transaction Code

This feature allows additional predefined information that helps to manage your operations and supplier warranty items. 

Watch a Demo.

Steps to Enable

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

Tips And Considerations

  • Attribute value can be set using the UI, import process, or SOAP service, or REST service.
  • In the Simplified Change Management interface, the Affected Objects redline view of commercialization change orders shows the Default Repair Transaction Code attribute.

Key Resources

Access Requirements

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned this predefined job role are automatically able to access this feature:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER)
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature.
    • Create Item Class Item Data (EGO_CREATE_ITEM_CLASS_ITEM_DATA)
    • View Item (EGP_VIEW_ITEM)
    • Maintain Item Asset Maintenance Group Data(EGO_MAINTAIN_ITEM_ASSET_MAINTENANCE_GROUP_DATA)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature in commercial change orders.
    • View Change Orders (ACA_VIEW_CHANGE_ORDERS_PRIV)
    • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)

Generate and Assign GTINs to Items Automatically Using Rules

You can automatically generate GTINs and create GTIN relationships using item rules. Assignment rules support a new function that creates GTIN relationships automatically. You can leverage the existing capabilities of item rules such as call a web service, automatically sequence function, fetch values from your own objects or item attributes, and so on to generate the GTIN, and then the assignment rule automatically creates the GTIN relationships.

The following image shows an assignment rule that generates and assigns GTIN to items.

GTIN Assignment Rule

GTIN Assignment Rule

This feature benefits your business by:

  • Increasing efficiency and decreasing manual GTIN relationship assignment.
  • Expanding the governance processes across your enterprise to include GTIN creation. 

Steps to Enable

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

Tips And Considerations

The syntax of the function for assigning GTIN is: 

assignGTIN (<GTIN String/Expression>, <UOM Code>, <Party Type>, <Registry ID>)

You can use a rule function that generates a GTIN as the first argument. You must then pass the UOM code as the second argument that will be used as the GTIN UOM. Party type and registry ID are optional arguments. You can pass these values to create party GTIN relationships.

This GTIN expression can be a concatenation of multiple values.

Key Resources

Access Requirements

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 Item Rule Set (EGO_MANAGE_ITEM_RULE_SET_PRIV)

Compute Check Digit for GTINs Using Item Rules

You can calculate the check digit for GTIN 8, GTIN 12, GTIN 13, or GTIN 14 using the new function in item rules. The syntax of the function is gtinCheckdigit( ). You can pass a 7, 11, 12, or 13-digit number. The function performs a mod 10 check digit calculation and returns the check digit.

The following screenshot shows a rule with the GTIN check digit function.

GTIN Check Digit Function

GTIN Check Digit Function

The capability to calculate the GTIN check digit benefits your business by giving you the ability to generate a GTIN for your product instead of relying on an external system to supply a GTIN.

Steps to Enable

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

Tips And Considerations

You can also pass an expression in the GTIN check digit function. This expression must return a 7, 11, 12, or 13-digit number.

Key Resources

Access Requirements

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 Item Rule Set (EGO_MANAGE_ITEM_RULE_SET_PRIV)

Support Kit Items on Transfer Orders

In many industries, companies need the flexibility to store individual components in their warehouses while providing employees the option to request those distinct components individually or to request them as a group of multiple components that represent a kit.

For instance, your maintenance facility performs scheduled preventative maintenance and immediate emergency repairs. Because scheduled maintenance is planned at specific intervals, your mechanics have specific sets of components they always order for the various maintenance milestones. Oftentimes these standard scheduled maintenance kits can have over 75 or 100 components. On the other hand, for emergency repairs, your mechanics need to order only the exact repair parts required to get the piece of equipment up and running properly. While some of these components are likely present in one of the scheduled maintenance kits, not all components of the kits are required. So ordering a kit for an emergency repair that only requires a few components isn't necessary.

To provide this flexibility when conducting internal transfers, you can now request pick-to-order kits on a transfer order instead of requesting each component individually. After defining the kit parent item and associating the component structure in Oracle Fusion Cloud Product Hub, you use the kit parent item name when requesting the transfer order. Upon creation, Oracle Fusion Cloud Inventory Management automatically explodes the kit components onto the transfer order so that picking, shipping, and receiving still occur at the component level.

This feature lets your employees more efficiently create an internal transfer for a standard set of components that are stocked individually, but often ordered together as a kit.

Watch a Demo.

Steps to Enable

Define kit items in the Product Information Management work area. The following are the required attribute settings for a kit item in the source organization.

  1. Define the kit item with these Inventory, SalesOrder Management, and Manufacturing item attribute settings.
  • Stocked = No
  • Transaction Enabled = No
  • Internally Transferable = Yes
  • Shippable = No
  • Transfer order enabled = Yes
  • Pick components = Yes

Example - Inventory Kit Item Attributes

  1. Create kit item structure.

An item structure is required for kit items. You must use the Primary item structure name when creating a new item structure for a kit item.

This example of a kit item structure shows the kit item and its shippable components.

Kit Item Structure

  1. Associate the kit item to the inventory organizations.

Kit Item Organization Association

Tips And Considerations

In order to assure that the kit component items are shipped together (in a kit), the shipment lines are automatically stamped with a shipment set number at the time of the transfer order creation. The business intention of the kit item is that full quantities of all kit components within the kit item, ship at the same time. But there are business conditions that require the shipment set to be broken. The Shipment Set Behavior shipping parameter controls the ability to break a shipment set. You can only ship less than the requested quantities for the kit components if the Shipment Set Behavior parameter is Information or Warning

Consider the settings of the Shipment Set Behavior parameter to determine the level of control you want when picking and shipping kit components.

  • When you choose Error as the Shipment Set Behavior, if any quantity changes are made to the shipment line, an error message displays at ship confirmation and the transaction stops. This is true for kit components as well as standard items.
  • When you choose Warning as the Shipment Set Behavior, if any quantity changes are made to the shipment line, a warning message displays at ship confirmation and you have a choice to continue or stop the transaction. This is true for kit components as well as standard items.
  • When you choose Information as the Shipment Set Behavior, if any quantity changes are made to the shipment line, the change is accepted and the transaction processes without issue. This is true for kit components as well as standard items.

Shipping Parameter - Shipment Set Behavior

Also consider enabling the Enforce shipment sets shipping parameter. With this parameter enabled, the system assures that all lines in a shipment set are picked together. This isn't a required setup, but it has proven beneficial to companies that want to keep the shipment set intact from picking through shipping.

Shipping Parameter - Enforce Shipment Sets

NOTE: Before update 23A, you couldn't set the Pick Component and Internally Transferable attribute values to Yes when the Shippable and Stocked attribute values were set to No for an item. After update 23A, you can set the attribute values accordingly so you can add your kit items to transfer orders.

Key Resources

Access Requirements

You have a couple of options for giving people access to this feature, depending on whether you're assigning them to 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:
    • Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
    • Shipping Manager (ORA_WSH_SHIPPING_MANAGER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Create Supply Request (DOS_CREATE_SUPPLY_REQUEST)
    • Manage Inventory Transfer Order (INV_MANAGE_INVENTORY_TRANSFER_ORDER)
    • Manage Shipments and Shipment Lines (WSH_MANAGE_SHIPMENT_AND_SHIPMENT_LINE)

Create UOM Conversion Data for All Items

Every item has a primary unit of measure, and may be ordered or fulfilled in units of measure other than the primary unit, so long as there are existing standard or item-specific conversions.  A standard conversion between units is applicable to all items, such as 1 Liter = 1000 Milliliters.  An item-specific conversion between units may introduce a relationship between two classes, such as Volume and Quantity.  Or, it may override a standard conversion to reflect the unique packaging of an item, such as 1 Box = 25 Each. The conversion for every item that has no item-specific data is limited to the same set of standard conversions associated with its primary unit of measure.  If an item has one or more item-specific conversions, it often defines additional units that the item may be transacted in, and may override the standard conversions. 

This set of unique conversion data for all items is now stored to better support analytics.

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 ManagementNo Longer Optional From: Update 23C

Use UOM Names in Packaging Strings

You may now choose to display the packaging string that is associated with an Item using the unit of measure names instead of the briefer short code for the unit of measure. For example, the packaging string EA 100 / BX 20 / CS might represent 100 of an item in a box, with 20 boxes in a case. By using the names, the packaging string might instead read Each 100 / Box 20 / Case. 

Unit of measure short codes are limited to three characters and might not be clear which unit of measure they represent.. You might prefer to show the packaging string using the more identifiable names of the participating units of measure.

Steps to Enable

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

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.

Item Template Availability in New Item Requests and Change Orders

Starting in update 22D, you could apply a template when assigning an item to a child organization (either an inventory organization or an item organization). You can now apply a template when assigning an item to a child organization (either an inventory organization or an item organization) during the definition step of a new item request, and also as part of a change order.

Oracle reference: 34302547

Updated Constraint Checks for the Manage Delete Groups Task 

Before update 23A, if you used the Manage Delete Groups task to submit a group of items for deletion, the task ran a series of constraint checks. One of those checks was to make sure that the items in the delete group aren't present in marketing objects. After you update to 23A, this specific check won't be performed. However, other constraint checks are still performed before the item is deleted.

Oracle reference: 34451131

Steps to Enable

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

Product Development & Product Hub Common

Autocomplete Changes Efficiently to Ensure Change Workflow Resiliency

Previously, you had to manually select the Autocomplete on Cancel check box in change order type setup to ensure that change orders move to completion when the last change line is canceled.

To make your change workflow more resilient, this is now the default setting and is applied to both new and in-progress change orders.

Default Setting is Autocomplete on Cancel

With this update, you can decrease the number of clicks involved in creating a change order type, and increase control over the final status of both new and in-progress change orders.

Steps to Enable

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

Tips And Considerations

  • For a change order to move to the completed status on the cancellation of the last change line, at least one change line should have moved to the completed status.
  • If all the change lines in a change order have moved to the canceled status, then on the cancellation of the last change line the change order would stay in canceled state.
  • Prior to this update, the Autocomplete on Cancel setting was applicable only to newly created change orders.

Key Resources

Access Requirements

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 work on change orders:
    • 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:
    • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) and 
    • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)

Analyze Where Items Are Used As Substitutes

You can now identify where an item is used as a substitute when using the where used query on the first level of the item structure. A new search filter Include Substitute Components and a new column Substitute For have been added to the item's Where Used report in the Product Development and Product Information Management work areas to help you view the components in which the item is marked as a substitute. You can also enable substitute component search by default using a new profile option.

Search Filters and Substitute for Column in Product Development UI

Search Filters and Substitute For Column in Product Information Management UI

When you generate the Where Used report in OTBI, you can choose to include substitute components across all levels. Here’s the list of subject areas and the corresponding attributes:

  • Product Management- Where Used Real Time
    • Component Substituted for
    • Component Used as Substitute
  • Where Used Quick Preview
    • Where Used Component Substituted for
    • Where Used Component Used as Substitute

Where Used Item Attributes in OTBI

Where Used Report in OTBI

Additionally, the change order details report is enhanced to include substitute component attributes and shows the affected objects in descending order of the sequence number.

Here are the substitute component attributes:

  • Primary UOM
  • Enforce Integer Requirement
  • Priority
  • Global descriptive flexfields

Substitute Component Attributes in Change Order Details Report

Get a more holistic view of where an item component was used as a substitute and which components it substituted. Your product engineers will now have the flexibility to review this and additional substitute information on an ad hoc basis through a UI search or through preconfigured reports.

Steps to Enable

To display the new substitute component attributes in the OTBI report and to enable the Include Substitute Components field in the UI by default, you must set the value of the profile option Include Substitutes in Item Where Used Data to Yes. Here’s how:

  1. In the Setup and Maintenance work area, use the Manage Administrator Profile Values task.
  2. In the Profile Display Name field, search for Include Substitutes in Item Where Used Data.
  3. In the Profile Value column, set the profile value to Yes.
  4. Save your changes.

Tips And Considerations

  • This feature is supported only for the first level structure in the UI and all levels in the OTBI report.

  • The Substitute For column in the UI is shown only if the Include Substitute Components search filter is selected.

  • When you select Include Substitute Components, the Where Used results are restricted to the master organization and primary structure in Product Development, and to the context item's organization in Product Information Management.

  • In Product Information Management, you can perform a search on primary, alternate, or all structures based on the search filters.

  • The change order details report doesn't display redlines for substitute components.   

Key Resources

Access Requirements

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) Or Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Supplier Product Design Engineer (ORA_ACA_SUPPLIER_PRODUCT_DESIGN_ENGINEER_JOB)
  • Users who are assigned a configured job role that contains these privileges can access this feature:
    • Functional privileges to view the where used report:
      • View Item (EGP_VIEW_ITEM_PRIV)
      • Manage Item (EGP_MANAGE_ITEM_PRIV)
    • Functional privileges for supplier portal users to view the where used report:
      • View Supplier Items (ACA_VIEW_SUPPLIER_ITEMS_PRIV)
    • Functional privileges to view the change order details report:
      • 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)
      • Generate Item Change Order Report (Generate Item Change Order Report)
    • Functional privileges for supplier portal users to view the change order details report:
      • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) and one of the following:
        • 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)
      • Generate Item Change Order Report (Generate Item Change Order Report)
      • BI Consumer
    • Data security privileges to view the where used report
      • View Item Basic
      • Maintain Item Basic
      • View Item Structure or Maintain Item Structure

Use Enhanced REST Services to Manage Items and Changes

The following REST APIs have been enhanced in this update:

  • Item Structures
  • Product Change Orders V2
  • Product Change Requests
  • Quality Problem Reports
  • Quality Corrective and Preventive Actions

Use the Item Structures expansion resource to expand the item structure and return all structure levels.

Use the change and quality resources to:

  • Change the workflow status from Open to Interim Approval, Approval, Hold, or Cancel.
  • Get Assigned By and Assigned Date attributes for a change task.

Here are some examples to illustrate these capabilities.

Expansion Results

Change Order Promoted from Open to Interim Approval

GET Operation Response Shows Change Task's Assigned By and Assigned Date

Create, update, and access more detailed functions for items, bills of material, and change workflows programmatically for easier integration with external systems and configured extensions.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

You can retrieve the expanded structure in one call using the Expand function. For example:  /itemStructures?q=ItemNumber={itemnumber}&expand=Expansion

Key Resources

Access Requirements

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)
  • Users who are assigned a configured job role that contains these privileges along with Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) can access this feature:
    • For change orders:
      • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV) 
    • For change requests:
      • Manage Change Request (ACA_MANAGE_CHANGE_REQUESTS_PRIV) 
    • For problem reports:
      • Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV)
    • For corrective and preventive actions:
      • Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)

Reinstate Obsolete Items to Earlier Lifecycle Phases

You can now change the item lifecycle phase from obsolete to an earlier one such as Design or Production. Change of lifecycle phase can be done on the:

  • item or the change order for a commercial item (in Product Information Management)
  • change order for an engineering item (in Product Development)

Select the New Lifecycle Phase on the Item Page for a Commercial Item

Select the New Lifecycle Phase on a Change Order for an Engineering Item

Change the Lifecycle Phase on the Item Page in Change Order Context

This feature makes your business process more flexible by allowing you to reinstate items that were previously obsoleted, either intentionally or by mistake.

Watch a Demo.

Steps to Enable

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

Tips And Considerations

You can’t reinstate the parent item in a structure if the child component is marked obsolete.

Key Resources

Access Requirements

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) 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 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)
    • Data privileges to view and edit item structures:
      • View Item Basic
      • Maintain Item Basic
      • View Item Structure

Use Audit Reports to Govern User Activities on Attachments

In Oracle Product Hub and Oracle Product Development, users can access attachments associated with business objects, such as Items and Structures, based on the access privileges. Users can download or check out the attachment. They can also check in a new version of the attachment or choose to cancel check out without checking in a new version.

With this feature, you can audit the user activities such as Attachment Check In, Attachment Checkout, Attachment Cancel Checkout, and Attachment Download on an attachment if the attachment business object (for example, Items Attachments) has been enabled for auditing using the Manage Audit Policy UI available in the Setup and Maintenance work area.

NOTE: Auditing the user activities on the attachment business object is in addition to auditing the existing attachment maintenance activities such as insert, update, and delete.

To access the Audit Reports, go to Navigator > Tools > Audit Reports. The following screenshot shows the various event types for the Item Attachments business object based on which you can generate an audit report.

Audit Reports

Audit Reports

This feature is enabled for the following business objects:

  • Item Attachments
  • Item Revision Attachments
  • Change Object Attachments
  • Structure Attachments
  • Catalog Attachments
  • Category Attachments

This feature is enabled for the following types of attachments:

  • Text
  • File
  • Repository File/Folder

This feature enhances governance and oversight by monitoring user activities on attachments.

Steps to Enable

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

Tips And Considerations

  • When an attachment is added, the audit report considers it as Insert event and Attachment Check-In event.

  • The events are audited only after a business object is enabled for audit.

  • Audit details for the user activities on the attachment are available only in the Audit Reports (Tools > Audit Reports). It isn’t available in the History tab on the Edit Items page.

Key Resources

Access Requirements

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

  • View Audit History (FND_VIEW_AUDIT_HISTORY_PRIV)

This privilege was available prior to this update.

Selected Product Development and Product Hub Common 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.

System Actions Displayed in OTBI Reports

In the change order history tab or new item request action log, the Author column displays System as the author of automatic actions performed as part of the workflow. With this update, the OTBI reports also display System as the author of such actions.

Oracle reference: 34360298

Retrieving Redlined Substitute Components Using SOAP

The following operations in the Product Design Change Order SOAP service were returning errors if the change order contained substitutes with redlines: findChangeObject and findChangeOrderRedline.

You can now use these operations to get substitute component information even when the substitute has redlined item attributes.

Oracle reference: 34176846

Opening Change Orders Added in Delete Groups

Previously, if you tried to open a change order that's part of a delete group, you'd get an error message. You’d face this issue in the Product Development work area and simplified Change Management interface.

This issue is now fixed.

Oracle reference: 30526067

Steps to Enable

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

Product Lifecycle Management Common

Notify Approvers upon Removal from Approvers List

You will now receive a new FYI notification if you're removed as an approver or reviewer in the current interim approval or approval workflow status. You can see the comments in the notification provided during removal action.

Removal Notification

If your role is designated as the workflow status participant, the Assignee field of the FYI notifications now displays your role name instead of your user name.

Completed Notification with Role in Assignee Field

This feature benefits your business by proactively notifying users upon their removal as an approver. These targeted notifications ensure that users don't waste time trying to approve workflows they don't need to, and other participants in the change workflow aren't inundated with notifications that don't pertain to them.

Steps to Enable

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

Tips And Considerations

  • The user name appears in the Assignee field for the removal notification instead of approval group name.
  • The removed users still receive the FYI notifications as they are part of approval groups.

Key Resources

Access Requirements

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)
    • Quality Engineer  (ORA_ENQ_QUALITY_ENGINEER_JOB)
  • Users who are assigned configured job roles must have the below privileges:
    • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV)
    • Modify Change Status (EGO_MODIFY_CHANGE_STATUS_PRIV)

Additionally, users require the following privileges:

  • For change orders:
    • View Change Order (ACA_VIEW_CHANGE_ORDERS_PRIV) 
    • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)
  • For change requests:
    • View Change Request (ACA_VIEW_CHANGE_REQUESTS_PRIV)
    • Manage Change Requests (ACA_MANAGE_CHANGE_REQUESTS_PRIV)
  • For problem reports:
    • View Problem Report (ACA_VIEW_PROBLEM_REPORTS_PRIV) 
    • Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV)
  • For corrective actions and preventive actions:
    • View Corrective Action (ACA_VIEW_CORRECTIVE_ACTIONS_PRIV)
    • Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)

Associate Trading Partner References to a Change or Quality Workflow

You can now optionally associate trading partner reference attributes like Customer, Supplier, Manufacturer, and Source to the problem reports, corrective actions, change orders, and change requests.

To include the attributes in the General Information tab for internal and supplier users, configure the attribute visibility in the setup of the predefined change type.

General Information Tab of Change Order for Internal User

General Information Tab of Change Order for Suppliers

FBDI import template ChangeOrderImportTemplate.xlsm now supports import of completed problem reports and corrective actions.

It also supports the import of the new attributes.

Change Order Import Template with New Attributes

This feature benefits your business by enabling you to:

  • Formally track the origination of a problem report, CAPA, or change workflow.
  • Provides the ability to associate a trading partner as a source of a problem report, CAPA, or change workflow.

Steps to Enable

  1. In the Setup and Maintenance work area, go to the following:
    • Offering: Product Management
    • Functional Area: Change Orders
    • Task: Manage Change Order Types
  1. Select the predefined change type for which you want to configure the trading partner reference attributes.
  1. Click Edit and click the Attributes tab.
  1. In the Header Attributes section, the attributes are listed for their visibility.
  1. In the Visibility column, select one of the following options for each of the attributes.
    • Blank: The attributes aren't visible to any user.
    • Internal: The attributes are visible for business users.
    • Internal and External: The attributes are visible for business users and supplier users.
  1. Click Save and Close.

NOTE: To retain the existing behavior, the default value is set to Blank.

Attribute Configuration for Predefined Change Type

Tips And Considerations

  • Change types that are created based on a predefined change type inherit the attribute visibility configuration of the parent change type.

  • Although the change type 8D Corrective Actions is predefined, the attribute visibility setting is read-only. The configuration is inherited from its parent change type, Corrective Action.

  • You can only import and export configurable attributes that are listed in the Attributes tab for the predefined change types.

  • You can display the attributes to suppliers only if they are exposed to the business user.

  • To enable users to edit the attributes, assign the Manage Change Header Attributes permission in Additional Workflow Controls.

  • The change objects that are in progress honor the attribute visibility configuration.

Key Resources

Access Requirements

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)
    • Quality Analyst (ORA_ENQ_QUALITY_ANALYST_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 a configured job role that contains these privileges can access this feature:
    • Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV)
    • Modify Change Status (EGO_MODIFY_CHANGE_STATUS_PRIV)

Additionally, internal users require the following privileges:

  • For change orders:
    • View Change Order (ACA_VIEW_CHANGE_ORDERS_PRIV)
    • Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)
  • For change requests:
    • View Change Request (ACA_VIEW_CHANGE_REQUESTS_PRIV)
    • Manage Change Requests (ACA_MANAGE_CHANGE_REQUESTS_PRIV)
  • For problem reports:
    • View Problem Report (ACA_VIEW_PROBLEM_REPORTS_PRIV)
    • Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV)
  • For corrective and preventive actions:
    • View Corrective Action (ACA_VIEW_CORRECTIVE_ACTIONS_PRIV)
    • Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)

Additionally, external users require the following privileges:

  • For change orders:
    • View Change Orders in Supplier Portal (ACA_VIEW_CHANGE_ORDER_SUPPLIER_PORTAL_PRIV)
    • Manage Change Orders in Supplier Portal (ACA_MANAGE_CHANGE_ORDERS_SUPPLIER_PORTAL_PRIV)
  • For change requests:
    • 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)
  • For problem reports:
    • View Problem Report in Supplier Portal (ACA_VIEW_PROBLEM_REPORT_SUPPLIER_PORTAL_PRIV)
    • Manage Supplier Problem Reports (ACA_MANAGE_SUPPLIER_PROBLEM_REPORTS_PRIV)
  • For corrective and preventive actions:
    • View Corrective Action in Supplier Portal (ACA_VIEW_CORRECTIVE_ACTION_SUPPLIER_PORTAL_PRIV)
    • Manage Supplier Corrective Actions (ACA_MANAGE_SUPPLIER_CORRECTIVE_ACTIONS_PRIV)