Oracle Product Management Cloud
What's New
  1. AUGUST MAINTENANCE PACK FOR 19C
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Product Development & Product Hub Common Features
        1. Fast Track the Creation of Your New Item Requests
  1. Update 19C
  1. Revision History
  2. Overview
  3. Optional Uptake of New Features (Opt In)
  4. Feature Summary
    1. Product Development
        1. Add Attachments to Manufacturers in Your Approved Manufacturers List
        2. Improve User Productivity with New Clipboard Functionality
        3. Manage Tasks for Engineering Change Requests
        4. Match Order of Components in OTBI Structure Reports and User Interface
        5. Use Rules to Autogenerate Fields During Item Creation
        6. View Comma-Separated Reference Designators in Structures and Components Subject Area
        7. Check Component Quantity Against Number of Reference Designators
        8. Secure Item Relationship Creation with Object Privileges
        9. Exclude Extended Flexfield Attributes to Speed Up Item Search
        10. Track and Manage Change Order Tasks with OTBI
        11. View the Approved Manufacturers List by Parent Revision in Structures and Components Subject Area
        12. Improve Report Usability with Last Scheduled Process Dates
        13. View Components for a Pending Revision of an Item Structure
    2. Product Development & Product Hub Common Features
        1. Capture Change History for Cover Page Attribute Changes and Action Details
        2. Copy Data When Creating a Change Order from a Change Order or Change Request
        3. Import Item Revisions and Historical Change Orders Using File-Based Data Import (FBDI)
        4. Move Canceled, Rejected, or Failed Change Lines to a New Change Order
        5. Detect Revision Conflicts for Proper Sequencing of Change Orders
        6. Select First Level or All Levels for Your Bills of Material Comparison
        7. Use Item Import Template to Import Revision-Specific Approved Manufacturers List
    3. Product Hub
        1. Configure the Publication Payload Size
        2. Leverage Improved Error Messaging to Trace Publication Errors
        3. Mark New Item Requests Complete
        4. Disseminate Item Data Changes to External Systems Through the New Item Request Business Events
      1. Integrate and Extend Product Hub Using REST Services
        1. Manage Items Using a REST Service
        2. Manage Product Uploads Using a REST Service
        3. Manage New Item Request Attachments Using REST Services
        4. Manage Status Changes for New Item Requests Using REST Services
    4. Quality Management
        1. Navigate Directly to Quality Issues and Actions from Approval Notifications
        2. Categorize Attachments on Quality Issues or Quality Actions
        3. Improve Usability and Security of the Relationship Rule Editor
        4. Enhance Analytics with Additional Attributes in Quality Issues and Actions Real Time Subject Areas

August Maintenance Pack for 19C

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 Feature Notes
30 AUG 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

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.

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.


Customer Action Required = You MUST take action 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*

Customer Action Required

Product Development & Product Hub Common Features

Fast Track the Creation of Your New Item Requests

Product Development & Product Hub Common Features

Fast Track the Creation of Your New Item Requests

The classic new item request process requires you to enter the new item request name, number, and additional details across multiple windows. With this update, you can have new item request number, name, and description values filled in automatically as described here.

If the number generation method is rule-generated or sequence-generated:

  • Number is automatically generated
  • Name = Item number
  • Description = Item description

If the number generation method is user-defined:

  • Number and name = Item number
  • Description = Item description

In addition to the Submit button on the item page, you now see a Quick Submit button. Use this action to bypass multiple pages, minimize the number of clicks, and thus fast track the new item request process.

New Item Request Quick Submit

New Item Request Created in Open Status on Quick Submit

Steps to Enable

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

Tips And Considerations

You can still use the classic process and click Submit, if you prefer that. The Quick Submit button is enabled only for single item creation, not multiple item creation.

Also, users with the Application Implementation Consultant role can hide the Quick Submit button using Page Composer, if desired.

Role Information

Job Role Name and Code:

  • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)   
  • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)

Update 19C

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 Feature Notes
02 AUG 2019 Manage Items Using a REST Service Updated document. Edited feature description.
24 JUN 2019

Use Item Import Template to Import Revision-Specific Approved Manufacturers List

Updated document. Edited feature description.
21 JUN 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

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.

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 in a couple of ways:

Access the Opt In page from the New Features Work Area

  1. Click the Navigator, and then click New Features (under the My Enterprise heading)
  2. On the New Features page, select the offering that includes new features you’d like to review
  3. Click Go to Opt In for any feature you want to opt in
  4. On the Edit Features page, select the Enable option for the feature, and then click Done

or...  Access the Opt In page from the Setup and Maintenance Work Area

  1. Click the Navigator, and then click Setup and Maintenance
  2. On the Setup page, select your offering, and then click Change Feature Opt In
  3. On the Opt In page, click the Edit Features icon for any area that includes features you want to opt in
  4. On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close
  5. Click Done.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may auto enable 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 auto 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.


Customer Action Required = You MUST take action 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*

Customer Action Required

Product Development

Add Attachments to Manufacturers in Your Approved Manufacturers List

Improve User Productivity with New Clipboard Functionality

Manage Tasks for Engineering Change Requests

Match Order of Components in OTBI Structure Reports and User Interface

Use Rules to Autogenerate Fields During Item Creation

View Comma-Separated Reference Designators in Structures and Components Subject Area

Check Component Quantity Against Number of Reference Designators

Secure Item Relationship Creation with Object Privileges

Exclude Extended Flexfield Attributes to Speed Up Item Search

Track and Manage Change Order Tasks with OTBI

View the Approved Manufacturers List by Parent Revision in Structures and Components Subject Area

Improve Report Usability with Last Scheduled Process Dates

View Components for a Pending Revision of an Item Structure

Product Development & Product Hub Common Features

Capture Change History for Cover Page Attribute Changes and Action Details

Copy Data When Creating a Change Order from a Change Order or Change Request

Import Item Revisions and Historical Change Orders Using File-Based Data Import (FBDI)

Move Canceled, Rejected, or Failed Change Lines to a New Change Order

Detect Revision Conflicts for Proper Sequencing of Change Orders

Select First Level or All Levels for Your Bills of Material Comparison

Use Item Import Template to Import Revision-Specific Approved Manufacturers List

Product Hub

Configure the Publication Payload Size

Leverage Improved Error Messaging to Trace Publication Errors

Mark New Item Requests Complete

Disseminate Item Data Changes to External Systems Through the New Item Request Business Events

Integrate and Extend Product Hub Using REST Services

Manage Items Using a REST Service

Manage Product Uploads Using a REST Service

Manage New Item Request Attachments Using REST Services

Manage Status Changes for New Item Requests Using REST Services

Quality Management

Navigate Directly to Quality Issues and Actions from Approval Notifications

Categorize Attachments on Quality Issues or Quality Actions

Improve Usability and Security of the Relationship Rule Editor

Enhance Analytics with Additional Attributes in Quality Issues and Actions Real Time Subject Areas

Product Development

Add Attachments to Manufacturers in Your Approved Manufacturers List

Use the Attachments tab in the Manufacturer Details page to add attachments related to the manufacturer.  You can attach any file type, see the description and revisions of the file, and perform controlled check in and check out of that file.

Manufacturer Attachments Tab

Steps to Enable

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

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

Improve User Productivity with New Clipboard Functionality

Use the clipboard to create an item structure from scratch. You can drag and drop the first level of the structure directly from the clipboard and then continue adding child components to the subassembly either from the clipboard or from the search results.

With this update, you will also notice different icons for items and documents on the clipboard for enhanced clarity.

Drag and Drop from Clipboard to Item Structure Table

Structure Header is Automatically Created

Steps to Enable

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

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

Manage Tasks for Engineering Change Requests

Create, assign, read, and update tasks for engineering change requests directly in the user interface or through a REST service.  Within the user interface, the same columns that are available for engineering change orders are now available for change requests. You can add, update, or delete tasks while the change request is in Draft or Open status. A notification is sent to the assignee when the change request is saved.

Tasks Tab on Change Request

Steps to Enable

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

Tips And Considerations

Here's how change request tasks work. You'll notice that validations for tasks are similar for change requests and change orders.

  • Sequence is mandatory and must be unique for each change request. By default, it is in increments of 10.
  • Name is mandatory and must be unique.
  • Description is optional.
  • The Required option can only be set to Yes if the Complete Before Status is Open, Interim Approval, or Approval.
  • Assigned To is not required, but if it is entered, the selected user must exist in the system. The user can be created in HCM or directly in the Security Console. The assignee can be an internal or external employee.
  • Start-by Status is optional.
  • Complete Before Status defaults to Completed.
  • Need-by date is optional
  • Task Status defaults to Open. It can be updated up until the Complete Before Status so that the task can be marked completed. If Required is set to Yes, then the current change request status must be between Start By Status and Complete Before Status.

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

Match Order of Components in OTBI Structure Reports and User Interface

Eliminate the need to verify the content of structure reports you create in Oracle Transactional Business Intelligence (OTBI) against the user interface. The structure reports you create in Oracle Transactional Business Intelligence (OTBI) using the Structures and Components subject area now display data in the same order as in the user interface, allowing users to be much more efficient when working with the data.

Structure Display in the User Interface

Structure Display in OTBI

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports.  For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Tips And Considerations

Ensure that the Level column is set to sort in Ascending order.

Role Information

  • Job Role Name and Code:
    • Transactional Analysis Duty (FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY)
    • Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY)
    • BI Consumer Role (BIConsumer)

Use Rules to Autogenerate Fields During Item Creation

Set up rules to autogenerate item name, description, and extended flex fields, to improve efficiency and reduce errors while creating new items from the user interface.

If you set up a rule to fill in the Item Name and Description fields automatically in the Create Item dialog based on attribute values, the associated extended flexfield attributes also appear in the dialog.

Create Item Dialog with Rule Generated Attributes

Steps to Enable

First, set up a rule and then configure the attributes to autogenerate. Here's how you define a rule in the Setup and Maintenance work area.

  1. Navigate to the Manage Item Rule Sets task.
  2. Create an assignment rule for the association type Item class and use the item class name for Association Name.
  3. Define the result type either as Item Number or Item Description, depending on the purpose of the rule.

The sample rule shown here concatenates two extended flexfield attributes and uses the resulting text as the value for the item description.

Sample Rule for Item Description Attribute

Now, associate the rule to the item class you want to configure:

  1. Navigate to the Manage Item Classes task.
  2. Search for and open the item class you want to configure.
  3. On the Item Management tab, select the Rule Generated option for Number Generation and Description Generation and select the associated rule set.

Set Up Item Class to Use Rule Generated Number and Description

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

View Comma-Separated Reference Designators in Structures and Components Subject Area

You need clear visibility to item details when looking through bills of material.  Key details include reference designators.  There can be many reference designators for an item and reviewing multiple lines of an item structure can be very cumbersome and inefficient.  

With this update, you can see comma-separated reference designators in your Oracle Transactional Business Intelligence (OTBI) item structure and component reports.   A new column in the report shows you all of the reference designators for a particular component in the item structure. You'll find it easier to review all reference designators for each component instead of one reference designator per row of the structure.

OTBI Report with Reference Designators in Comma-Separated Format

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports.  For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Tips And Considerations

If the existing Reference Designator column has been used in an analysis, the same is converted to a comma-separated format automatically. Review any current analyses that contain the Reference Designator column after upgrade to 19C.

Role Information

  • Job Role Name and Code:
    • Transactional Analysis Duty (BI_TRANSACTION_ANALYSIS_GENERIC_DUTY)
    • Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY)
    • BI Consumer Role (BIConsumer)

Check Component Quantity Against Number of Reference Designators

You often need to create structures with items that contain multiple reference designators. In such cases, it's easy to miss a reference designator call-out from your engineering team.

Provide an automatic check to ensure that the number of reference designators matches the item component quantity. This check becomes active when you create the first reference designator for an item component. If the reference designator list is empty, there is no check for consistency. 

If there is an inconsistency, you can manually modify the quantity or the number of reference designators. Or you can allow the application to adjust the quantity automatically when you close the Reference Designator dialog.  You can thus reduce the chance for errors in your item structure and eliminate the need to rework the bills of material.

Reference Designator Dialog Shows Quantity and Quantity Related Option

Steps to Enable

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

Tips And Considerations

In Product Development, this feature is enabled by default. To disable it, deselect the Quantity Related option in the Reference Designator dialog.

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

Secure Item Relationship Creation with Object Privileges

Secure items from unauthorized access in multiple ways. You can have security defined at the item class level, or at the item level using the Team tab. Additional data security can be applied as well. For instance, you can restrict access to items based on specific item attribute values.

With this update, you can also restrict item relationship creation from the Relationship tab of an item, a change order, or a change request. If the current user does not have access to the item due to functional security or data security, then the system hides the related item record in the relationships table.

Steps to Enable

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

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

Exclude Extended Flexfield Attributes to Speed Up Item Search

Speed up your item search significantly by excluding extended flexfields from the search results. With this update, the Manage Items search result list doesn't include extended flexfield attributes by default. The attributes are only included if you add at least one extended flexfield attribute to the search criteria. Include extended flexfield attributes in the search criteria only if you really need to.

Item Search Excludes Extended Flexfield Attributes Unless Added as Search Criteria

Steps to Enable

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

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

Track and Manage Change Order Tasks with OTBI

When there are a large number of change orders that are being actively worked on, it's hard to keep track of the required tasks that must be completed to make progress on the change order. 

Set up Oracle Transactional Business Intelligence (OTBI ) Analyses and Alerts to inform task owners of their pending tasks, or send a consolidated list of open tasks to change order assignees. You can also send alerts based on the Need-by date. Make sure your change management stakeholders are always aware of what is needed from them to help prioritize activities.

Use these analyses and alerts to ensure a controlled and predictable change management process that meets your cycle time needs and improves overall efficiency.  

OTBI Analysis Shows Open Tasks on Open Change Orders

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports.  For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Role Information

  • Job Role Name and Code:
    • Transactional Analysis Duty (FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY)
    • Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY)
    • BI Consumer Role (BIConsumer)

View the Approved Manufacturers List by Parent Revision in Structures and Components Subject Area

View Approved Manufacturers List (AML) details by the parent item revision in Structures and Components subject area.  To see AML information, select the parent item number and a revision.  You can now review the AML details for that parent item and all of its children based upon the selected revision.

OTBI Analysis Shows AML for Revision C of the Parent Item 

OTBI Analysis Shows AML for Revision D of the Parent Item

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports.  For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Role Information

  • Job Role and Duty:
    • Transactional Analysis Duty (FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY)
    • Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY)
    • BI Consumer Role (BIConsumer)

Improve Report Usability with Last Scheduled Process Dates

When you create analyses of items and structures using the Structures and Components subject area, it's essential that you work with current or fresh data. This subject area is populated on demand using a scheduled process or the Publish for Analysis action within the item page or the item search page.

Now you can see the last refresh date, that is, the date a scheduled process for a specific item was last run, and determine whether you need another scheduled process run to refresh the item data. So you can always be sure you're using the latest item information in your reports and analytics.

OTBI Analysis Shows Last Refresh Date and Time

Steps to Enable

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

Role Information

  • Job Role Name and Code:
    • Transactional Analysis Duty (FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY)
    • Product Transaction Analysis Duty (FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY)
    • BI Consumer Role (BIConsumer)

View Components for a Pending Revision of an Item Structure

Use the Structures and Components subject area in Oracle Transactional Business Intelligence (OTBI) to view a report of the components for a pending item revision. Select a pending revision to see the parent item and all its child components for that revision.

You can take advantage of the improved visibility to plan the upcoming revision of your item better.

In the following example, Revision D is the pending revision of an item in Product Development.

Pending Revision in Product Development

Here you can see the same revision and its components in the analysis created using the Structures and Components subject area.

Pending Revision in OTBI

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports.  For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Role Information

  • Job Role Name and Code:
    • Transactional Analysis Duty FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY
    • Product Transaction Analysis Duty FBI_PRODUCT_TRANSACTION_ANALYSIS_DUTY
    • BI Consumer Role BIConsumer

Product Development & Product Hub Common Features

Capture Change History for Cover Page Attribute Changes and Action Details

To meet compliance standards, most industries require that you maintain your change history. With this update, you can capture the details of change cover page attributes, affected objects, tasks, relationships and attachments. You can see who made the changes and when, and compare the new values against the old values. You can also export this information to Microsoft Excel for further analysis.  

Use the View Item Audit Trail action from the Actions menu in Product Development to view change history. Or go to Navigator > Tools > Audit Reports.

History Data

Steps to Enable

You must first configure the information that you want to track. 

In the Setup and Maintenance work area:

  • Search for and open the task Manage Audit Policies
  • Click Configure Business Object Attributes.
  • Choose your product, Product Hub.
  • Scroll down the list of business objects to locate Change Objects
  • Configure the attributes you want to track.

Configure Audit Policy for Change Order History Tracking

Tips And Considerations

In the View Item Audit Trail dialog, you can search for your change object by change number.  Filter by product Product Hub and business object Change Objects. Enter the change number in the Description field for quick results.

NOTE: You can't use the Description field to find descriptive flexfields.

Key Resources

Watch Change Order History and BOM Comparison Readiness Training

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

Copy Data When Creating a Change Order from a Change Order or Change Request

Create new change orders from existing change orders and change requests to prevent data errors and improve efficiency. To copy data over to the new object, simply select the information you want to copy, and you won't have to worry about missing out important details pertinent for your change, or entering the wrong data.

When you copy a change order to create another change type, such as an engineering change order, non-revision controlled change order, or commercialization change order, you can now include the descriptive flexfields of a change order.

Here's what you can copy over from a change order:

  • descriptive flexfields
  • attachments 
  • affected objects
  • relationships*

* For engineering and non-revision controlled change orders only.

And here's what you can copy over from a change request:

  • affected objects
  • descriptive flexfields of affected objects
  • attachments
  • relationships

Using Save As to Copy Another Change Order

Steps to Enable

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

Tips And Considerations

You can only copy relationships of change orders created in Product Development.

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

Import Item Revisions and Historical Change Orders Using File-Based Data Import (FBDI)

Your business may require historical change order information from your previous on-premise solution to be maintained in Oracle Product Lifecycle Management Cloud. You want this information linked to specific revisions of your items.  

Use the Import Change Orders file-based data import (FBDI) template to import historic change order data and link those change orders to an existing item revision chain.  You can do the data migration in a single phase, meaning both item revision data and corresponding change orders are imported together. Or, you can first import the item revision data only, and later import the historic change order data.  You can now import this historic change data even if new change orders have been created in the user interface since the item was first imported.

If you have this information in your Oracle Product Lifecycle Management Cloud, you can get a complete history of your items in just a few clicks and eliminate the need to maintain old on-premise or other archive solutions.

Steps to Enable

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

Key Resources

You can find the Import Change Orders FBDI template in the Product Management chapter of the File-Based Data Import for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role Information

  • To use this feature, you need:
    • EGO_MANAGE_ITEM_CHANGE_ORDER_PRIV  - used to secure the jobs and services related to importing change orders.
  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
    • Application Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB) - used to access the Schedule Processes task, to run the Import Change Orders job.

Move Canceled, Rejected, or Failed Change Lines to a New Change Order

Move change lines from an existing change order to a new change order when the change lines are in Draft, Open, Canceled, or Rejected status, or have failed for any reason. The redline information is retained, so you don't need to redline again. You also see a record of the move in the History tabs of the source and target change orders.

Move Change Lines

Move Canceled Line to New Change Order

History of the Move Captured in Both Source and Target Change Orders

Steps to Enable

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

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

To move a canceled change line of a change order that is in Approval, Scheduled or Completed status, you must have the EGO_RESCHEDULE_ITEM_CHANGE_ORDER_PRIV privilege. 

Detect Revision Conflicts for Proper Sequencing of Change Orders

See improved consolidation of redline information when you use the Resolve Revision Conflicts feature that was introduced in an earlier update.

If you have parallel changes going on for the same affected object, you can detect whether the source revision on top of which the modification is defined is still the valid one. When you promote the change order, the application checks revisions and shows an error message if the revision is not the latest. You can then use the Resolve Revision Conflicts action to update to the appropriate source revision. Proper recalculation of the delta of redlines based on the new source revision is crucial here.

With this update, you can also consolidate redline information for the following objects:

  • Item attributes (including descriptive flexfields)
  • Item-level extended flexfields
  • Item revision-level attachments
  • Item structure components
  • Approved Manufacturers List (AML)
  • Organization associations (for Product Hub)

Steps to Enable

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

Tips And Considerations

NOTE: Consolidation of item revision-level extended flexfields is not supported.

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

Select First Level or All Levels for Your Bills of Material Comparison

You often need to compare bills of material for items and structures that you are evaluating for a change or other business requirement.  Most times, you want to compare only the first level of that structure to make decisions for your next steps.

Use view filters in the Product Information Management work area to compare bills of material either by the first level of the structures or by all levels. If you compare by first level only, you get a faster response time and it's an easier comparison to traverse.

You can also filter your bills of material comparison by the first level of structures in the Product Development work area, so you don't need to switch to the Product Information Management work area.

To compare structures in Product Development, go to the Structure tab of an item and select Actions > Compare Structures.  Likewise, in Product Information Management, go to the Structures tab of an item and select Actions > Compare.

BOM Comparison Results

In the Product Development work area, you can choose to compare the structure based on the selected item revisions or by specifying an effective date. If you choose Revision in the Compare By field, then the effective date becomes read-only and shows a default value. 

The application calculates the default value of the effective date as follows:

  • For a past effective revision - end date of that revision.
  • For a current effective revision - current date.
  • For a future or pending revision - start date of that revision.

Compare by Revision 

Here's how you define which attributes to consider in the structure comparison.

Define List of Attributes for Comparison

Watch a Demo

Steps to Enable

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

Key Resources

Watch Change Order History and BOM Comparison Readiness Training

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Design Engineer (ORA_ACD_PRODUCT_DESIGN_ENGINEER_JOB)
    • Product Design Manager (ORA_ACD_PRODUCT_DESIGN_MANAGER_JOB)

Use Item Import Template to Import Revision-Specific Approved Manufacturers List

It's critical that the information you import to Oracle Product Lifecycle Management Cloud is accurate, because it's the basis for all of your subsequent lifecycle management activities. In this update, you can import the approved manufacturers list for each revision of an item, and then use Oracle Transactional Business Intelligence (OTBI) to view the approved manufacturers list by item revision in the Structures and Component subject area.

To import items, download the Item Import template from the File-Based Data Import for Oracle Supply Chain Management Cloud guide, and follow the steps included in the template. For an item, you can bring in the revisions using the EGP_ITEMS_REVISIONS_INTERFACE tab of the item import template. To ensure that the approved manufacturers list shows up against a specific revision of the item, make sure that the Start Date Active date entered for the approved manufacturers list on the EGP_ITEM_RELATIONSHIPS_INTF tab matches the Effectivity date for that revision on the EGP_ITEMS_REVISIONS_INTERFACE tab. The Start Date Active date must be in YYYY/MM/DD HH:MM:SS.mm format.

After importing the item revisions with the approved manufacturers list, you can view the list by parent revision in the Structures and Component subject area of Oracle Transactional Business Intelligence (OTBI). You can easily change the view to see and compare different revisions.

OTBI Report Parent Revision C

OTBI Report Parent Revision D

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Tips And Considerations

When you import items where the approved manufacturers list start and end dates are different for different revisions, use different batches to complete the import successfully.  

Only the first instance of the approved manufacturers list is considered in one import batch, so the list is shown only in revision A of the item.  To create the relationship between the item and the approved manufacturers list in revision B, import it in a separate batch.

This update supports approved manufacturers lists that have no end date, but only a start date.

Key Resources

For details about the Item Import template, refer to the File-Based Data Import for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role Information

  • Job Role Name and Code:
    • ORA_EGI_PRODUCT_DATA_STEWARD_JOB
    • FND_MANAGE_SCHEDULED_PROCESSES_PRIV 

Product Hub

Configure the Publication Payload Size

With this enhancement, you can control of the size of the publication payload to match the systems and processes requirements. The default publication payload size is 500 MB for all publication payloads. The value is in MB. You can use the EGI_PUBLICATION_ITEMS_PER_PAYLOAD profile option to set a new value less than 500 MB to reduce the size of all publication payloads.

To change the payload size, use the Manage Advanced Item Profile Options (EGI_PUBLICATION_ITEMS_PER_PAYLOAD) task in the Setup and Maintenance work area:

  • Offering: Product Management
  • Functional Area: Items

This feature was also made available in a monthly update of 19C.

Publication Payload Sizing Profile

Steps to Enable

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

Tips And Considerations

Review the requirements for the systems or processes that will use the published data to determine requirements for the payload size. 

No actions are required because the default setting is for the maximum file size.

Key Resources

  • Oracle Fusion Product Hub Publication Process White Paper (Doc ID 1933240.1)

Role Information

  • Privileges Name and Code:
    • Publish Item (EGI_PUBLISH_ITEM_PRIV)
    • Publish Catalog (EGI_PUBLISH_CATALOG_PRIV)
    • Publish Item Class (EGI_PUBLISH_ITEMCLASS_PRIV)
    • Publish Trading Partner Item (EGI_VIEW_TRADING_PARTNER_ITEM_PRIV)
  • Job Role Name and Code:
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
    • Product Manager (ORA_PRODUCT_MANAGER_JOB)

Leverage Improved Error Messaging to Trace Publication Errors

The publication job log have improved error messages. You can use these messages to easily trace the publication errors and fix them. The publication job log now contains additional information regarding the error including the item number, rule name, and any error message that you have configured for the rule definition.

NOTE: This feature was also available in a monthly update of 19B.

Here is a sample of the publication job log:

Steps to Enable

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

Tips And Considerations

Create rules to display clearly defined error messages.

Key Resources

  • Oracle Fusion Product Hub Publication Process White Paper (Doc ID 1933240.1)

Role Information

  • Privilege Name and Code:
    • Publish Item (EGI_PUBLISH_ITEM_PRIV)
    • Publish Catalog (EGI_PUBLISH_CATALOG_PRIV)
    • Publish Item Class (EGI_PUBLISH_ITEMCLASS_PRIV)
    • Publish Trading Partner Item (EGI_VIEW_TRADING_PARTNER_ITEM_PRIV)
  • Job Role Name and Code:
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
    • Product Manager (ORA_PRODUCT_MANAGER_JOB)

Mark New Item Requests Complete

Mark your new item requests complete directly from the New Item Request Definition page with a new Mark Complete button.  You can now follow a more streamlined process and avoid unnecessary navigation. You have the flexibility to update the line item task status in the New Item Request notification page or after you've made updates to the item in the New Item Request definition page. You'll notice that the Done button in the Definition notification has also been renamed to Mark Complete.

Mark Complete Button on the New Item Request Definition Page

Mark Complete Button on the Definition Notification

Steps to Enable

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

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)

Disseminate Item Data Changes to External Systems Through the New Item Request Business Events

Use business events to notify external systems of new item request status changes.  You can subscribe to these business events with Oracle Integration Cloud.  Your integration specialists can then connect to any available web service or other available resources in Oracle Integration Cloud and perform event-driven actions driven by new item request status changes. 

Business events are generated for the following new item request status changes: Open, Definition, Approval, Scheduled, and Completed.

Here are the available events:

Business Event ID Description

SCM_EGO_NEW_ITEM_REQUEST_CHANGE_STATUS_OPEN

New Item Request Opened

SCM_EGO_NEW_ITEM_REQUEST_CHANGE_STATUS_DEFINITION

New Item Request Status Changed To Definition

SCM_EGO_NEW_ITEM_REQUEST_CHANGE_STATUS_APPROVAL

New Item Request Status Changed To Approval

SCM_EGO_NEW_ITEM_REQUEST_CHANGE_STATUS_SCHEDULED

New Item Request Scheduled

SCM_EGO_NEW_ITEM_REQUEST_CHANGE_STATUS_COMPLETED

New Item Request Completed

Business Events for New Item Request Status Changes

Steps to Enable

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

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)

Integrate and Extend Product Hub Using REST Services

Manage Items Using a REST Service

You can use the Items Version 2 REST service to find, create, and manage items and item-related data. This REST service replaces the existing Items REST service, which has been deprecated.

With this service, you can:

  • Create item
  • Create item revision
  • Specify values for item, and revision attributes that include standard operational attributes and user-defined attributes
  • Create supplier association
  • Create and manage attachments
  • Assign items to catalog categories
  • Search for items

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Role Information

  • Privilege Name and Code:
    • Create Item Class Item Data (EGO_CREATE_ITEM_CLASS_ITEM_DATA)
    • Manage Item (EGP_MANAGE_ITEM)
  • Job Role Name and Code
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)

Manage Product Uploads Using a REST Service

You can now use the Product Uploads REST service to upload product data from multiple source systems into the Oracle Product Hub Cloud staging tables. You can also add the product data to an item batch and import it into Product Hub using this service.

With this service, you can:

  • Create a product upload
  • Upload the product data using data files and import map
  • Add the product data to an item batch for importing it into Product Hub
  • Retrieve the product upload details for previously uploaded product data

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 > REST API) .  If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

  • You cannot upload product attachments using this service.
  • If the spoke system is set to On Data Load, then, when you upload the product data, this service will also create an item batch and add the product data to that batch for importing it into Product Hub.
  • If the spoke system is set to Manual, then uploading the product data using this service will not create an item batch. To add the product data to an item batch for such spoke systems, you can create an item batch using the Item Batch Maintenance service. When the batch gets created, note the batch id, and then specify the batch id in the PROCESS action parameter of the Product Uploads service.

Role Information

  • Privilege Name and Code:
    • Manage Product Upload (EGS_MANAGE_PRODUCT_UPLOAD_PRIV)
  • Job Role Name and Code:
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)
    • Supplier Product Administrator (ORA_EGS_SUPPLIER_PRODUCT_ADMINISTRATOR_JOB)

Manage New Item Request Attachments Using REST Services

Use the Attachments REST web service to post, get, patch, and delete your new item request attachments.  If the new item request is in draft or open status, you can now programmatically post, update, or delete its attachments.

The Attachments REST service is a child service of the New Item Requests root service. With this service, you can:

  • Attach URLs, files, text, and repository files or folders to your new item requests. 
  • Use parameters in the request payload to identify the URLs, files, text, and repository files or folders that will be attached, add a title to the attachment, and also add a description.

URL and File Attachment Using REST API

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 > REST API) .  If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

Attachments can be added to only one attachment category, Miscellaneous, with the categoryName MISC.

Example:

{

"DatatypeCode" : "FILE",

"FileName": "file1.jpg",

"Title":"file1_titile",

"CategoryName" : "MISC",

"FileContents" : "<Base64 encoded file content>"

}

Key Resources

Refer to the following documentation, available on the Oracle Help Center:

  • REST API for Oracle Supply Chain Management Cloud

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)

Manage Status Changes for New Item Requests Using REST Services

Use the New Item Requests REST web service to submit new item requests from Draft to Open status and from Open to Definition status.  

To programmatically automate the movement of a new item request from one status to another:

  • Use the POST method to call the new item request into your session.
  • Apply the changeStatus command in the request payload.
  • Supply the next status name as the toStatusName property.

New Item Request Status Change Using REST API

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 > REST API) .  If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

Example:

{

"name" : "changeStatus",

"parameters" :   [

{ "nirNumber" : "LY_NIR_1037" },

{ "orgCode" : "V1"},

{ "toStatusName" : "Open" }

]

}

Key Resources

Refer to the following documentation, available on the Oracle Help Center:

  • REST API for Oracle Supply Chain Management Cloud

Role Information

  • Job Role Name and Code:
    • Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)
    • Product Data Steward (ORA_EGI_PRODUCT_DATA_STEWARD_JOB)

Quality Management

Navigate Directly to Quality Issues and Actions from Approval Notifications

You use the quality management workflow as a vehicle to mobilize designated resources and track progress. To facilitate communication, designated approvers receive workflow approval notifications for quality issues or actions that need immediate review and approval.

With this update, you can directly navigate to the quality issue or quality action from the object hyperlink in approval notifications, improving responsiveness and efficiency of quality problem resolution.

Approval Notification

Object Hyperlink in Approval Notification

Steps to Enable

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

Key Resources

Watch Attachment Categories and Notifications Back Links Readiness Training

Role Information

  • Job Role Name and Code:
    • Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)

Categorize Attachments on Quality Issues or Quality Actions

You gather a lot of data during quality management processes as teams work in parallel to define and ultimately resolve quality-related problems. To keep this data organized and provide easy access to individual artifacts as needed, you can categorize attachments. You can also restrict access by attachment category to keep the artifacts secure.  

When you add an attachment to an issue or action, you can select the appropriate category to indicate the kind of attachment being added.  When you use the Save As action to create a new issue or action, attachment category details are carried over to the new issue or action along with the attachments.

Specify Attachment Category 

Watch a Demo

Steps to Enable

To enable this feature, assign additional attachment categories for quality issues and quality actions.

In the Setup and Maintenance work area:

  1. Open the task Manage Attachment Entities.
  2. Search for the entity ENQ_ACTION (Quality Actions) or ENQ_ISSUE (Quality Issues).
  3. Select the entity to see the attachment categories assigned to that specific entity.
  4. Add the additional attachment categories that should be made available for selection when you create attachments.

Manage Attachment Entities

Key Resources

Watch Attachment Categories and Notifications Back Links Readiness Training

Role Information

You must have an administrator role to manage attachment categories and assign them to the issue or action attachment entities.

  • Job Role Name and Code:
    • Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)

Improve Usability and Security of the Relationship Rule Editor

Addressing quality-related events can be a complicated, often intertwined process with multiple dependencies across the various stages or steps from definition to resolution. Not unlike project planning, coordinating the various data gathering and decision processes can be an overwhelming, time consuming, and labor intensive activity.

Use the improved relationships rule editor to define and automatically manage the relationships across quality issues, quality actions, and change orders. You can define rules to change the status of one object when the status of a related object is changed to a specific value. For example, you can define that the status of a quality action is set to Closed once the related change order is set to Closed.

With these improvements, you can clearly see which status is set for each object.

Define Relationships Rule

In addition, the Rule Editor is more secure and prevents unauthorized use with the following improvements:

  • You need Manage privilege on the source objects to set rules for those objects. You cannot open the Rule Editor without this.
  • You can create a rule only if both related objects have a workflow assigned. 

Enhanced Security for Setting Relationship Rules

Steps to Enable

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

Key Resources

Watch Attachment Categories and Notifications Back Links Readiness Training

Role Information

  • Job Role Name and Code:
    • Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)

Enhance Analytics with Additional Attributes in Quality Issues and Actions Real Time Subject Areas

Improve analysis and reporting insights for quality issues and quality actions in Oracle Transactional Business Intelligence (OTBI) with additional attributes for date, text and number.

Quality Issues and Quality Actions Subject Areas with Extended Attributes

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Key Resources

Watch Attachment Categories and Notifications Back Links Readiness Training

Role Information

  • Job Role Name and Code:
    • Quality Issues and Actions Transaction Analysis Duty (FBI_QUALITY_ISSUES_ACTIONS_TRANSACTION_ANALYSIS_DUTY)
    • BI Consumer Role (BIConsumer)