Update 22A

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 DEC 2021			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 SCM Cloud: Performing Your Quarterly Update (doc ID 2337485.1) on My Oracle Support.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions using the following privileges:

• Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
• Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

1. Click Navigator > My Enterprise > New Features.
2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
4. Click the icon in the Enabled column and complete the steps to enable the feature.

In some cases, you might want to opt in to a feature that's not listed in the New Features work area. Here's how to opt in:

1. Click Navigator > My Enterprise > Offerings.
2. On the Offerings page, select your offering, and then click Opt In Features.
3. On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
4. On the Edit Features page, complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Offering Configuration.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Quality Management

Quality Management

Use Actual Names to Search for Users in Quality Management

You can now search for users by first name, last name, and email in addition to the user name in the Quality Management work area.

You can also configure how users should be shown on quality issues, quality actions, problem reports, and corrective actions. A new profile option (ORA_EGP_NAME_DISPLAY_MODE) lets you choose your preferred display format from the following options:

• User Name - This is the default setting. (Example: Andrea.Fisher)
• Email (Example andrea.fisher@abc.com)
• Name : First Name Last Name (Example: Andrea Fisher)

Users are shown in the selected format on the objects and tabs listed below:

• Quality issues and quality actions
  • General Information
  • Comments
  • Affected Objects
  • Workflow
  • Security
  • History
  • Send Object dialog
  • Manage <object> pages
  • Graphical Navigator
  • Related Objects

• Problem reports and corrective actions
  • General Information
  • Tasks
  • Workflow
  • Security
  • Relationships
  • History
  • Manage <object> pages
  • Send Object dialog

Basic Search Screen

User Displayed As Per Profile Value Setting

This feature makes it easier for you to search for users, and provides the flexibility to choose how users are displayed on the interface.

Steps to Enable

1. In the Setup and Maintenance work area, go to the following task: Manage Administrator Profile Values
2. Search for the profile option: ORA_EGP_NAME_DISPLAY_MODE
3. Select your preferred user display format; options are User Name, Email, and Name

Name display Value setup screen

Tips And Considerations

• After you update to 22A, the user display format in the  Workflow Approvers table and the Send Object dialog will be reset to User Name, which is the default setting now. If you want to revert to the previous setting, you can change the profile value to Name.

• If a user doesn't have Email and First Name Last Name configured, then User Name is displayed.

• Your saved searches will work correctly if the operator used on a user attribute is Equals or Not Equals. If not, you must modify the saved search.

• You can configure the Name format by updating the Display Name setting using the Manage Person Name Formats task in Setup and Maintenance.

• The default setting for user display format is applied on all pages and tabs except the Attachments tab. The Attachments tab will show the User Name irrespective of profile value selection.

Key Resources

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

Role And Privileges

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

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Quality Analyst (ORA_ENQ_QUALITY_ANALYST_JOB)
  • Quality Engineer (ORA_ENQ_QUALITY_ENGINEER_JOB)

• To set up this feature, here's what you need:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
  • Setup Product Quality (ENQ_SETUP_PRODUCT_QUALITY_PRIV)

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

    • View Quality Issue (ENQ_VIEW_QUALITY_ISSUE_PRIV)

    • Manage Quality Issue (ENQ_MANAGE_QUALITY_ISSUE_PRIV)

  • Quality Action:

    • Manage Quality Action (ENQ_MANAGE_QUALITY_ACTION_PRIV)

    • View Quality Action (ENQ_VIEW_QUALITY_ACTION_PRIV)

  • Problem Report:

    • View Problem Report (ACA_VIEW_PROBLEM_REPORTS_PRIV)

    • Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV)

  • Corrective Action:

    • View Corrective Action (ACA_VIEW_CORRECTIVE_ACTIONS_PRIV)

    • Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)

Create an Inspection Plan for a Quality Inspection Management Functional Area Catalog

Today you can perform an inline inspection at receiving and during work in process using an item category-based inspection plan that aligns to a Procurement, Inventory, or Planning functional catalog. Since these functional catalogs may already be in use, they may not align to the way you inspect a category of items. You can now define a Quality Inspection functional catalog and its associated categories as the basis for creating inspection plans. You can create an inspection plan for the Quality Inspection functional catalog and a specific item category, so that the plan applies to inline and adhoc inspection of all items under this combination regardless of whether the inspection type is receiving, work in process, or inventory.

Create an Inspection Plan Using a Quality Specific Catalog

With Quality Inspection Management functional area catalogs, you can now align the way you group items with the way you inspect them.

Watch a Demo.

Steps to Enable

To set up a quality inspection management functional area catalog:

1. From the Setup and Maintenance work area, select the Manufacturing and Supply Chain Materials Management offering.
2. Select the Catalogs functional area.
3. Select the Manage Functional Area Catalogs task.
4. You can either create a new catalog by clicking Create or you can assign an existing catalog. 
5. Select the catalog to use and click Assign to assign the catalog to the Quality Inspection Management functional area.

You can now go to the Product Information Management work area and assign a category value for that catalog for each applicable item.

Tips And Considerations

• You can create multiple categories under the quality inspection-specific functional catalog to further differentiate types or levels of inspection.

• During inline inspection, an inspection plan defined for the Quality Inspection Management functional area takes precedence over plans for other functional areas and the same inspection criteria.

Key Resources

• Watch Create an Inspection Plan for a Quality Inspection Management Functional Area Catalog Readiness Training

Role And Privileges

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

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Edit Inspection Plans (QA_EDIT_INSPECTION_PLANS)

Enter Inspection Results by Editing All Rows

When entering inspection results, today you have to select a row multiple times inside the results table on the Inspection Details page in order to start data entry. And the inspection result lookup occasionally requires a browser refresh to continue with the correct result selection. Now you can directly enter results by clicking once inside the table and continuing to enter the remaining results.

Inspection results entry is quicker and more efficient now that you can click once inside the table and continue editing all rows in the table.

Steps to Enable

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

Role And Privileges

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

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Quality Engineer (ORA_QA_QUALITY_ENGINEER_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Edit Inspection Results (QA_EDIT_INSPECTION_RESULTS)

Manufacturing

Manufacturing

Resequence Work Order Operations During Execution

Production operations are executed in a prespecified sequence as defined by a work definition. However, certain operations require a specialist operator, or specific material, or specified resource to be used to ensure quality of the product.

Due to shop floor exigencies, an operator or material or resource may not be available at the given time thereby holding up the manufacturing process. To ensure the production is on schedule and meets customer demand, certain production operations can be performed ahead of this operation and continue production. When the specialist operator or material or resource is available, you can return to this previous operation and complete the operation.

Let’s take an example with a work order having operations 10, 20, 30 40, and 50.

Until this update, a work order always enforced completion of operations in a linear and sequential manner. As an operator, you had to complete operations 10, then 20, 30, 40, and 50 in this sequence only.

With this update, as a production operator, you can now resequence operations during execution. For example, you can complete operation 10 first, then 40, then 30, then 20, and then finally 50. However, you have to complete all the operations before completing the work order.

Here are the capabilities supported in this feature:

• Identify resequenceable operations in work definition
• Create and edit work orders with resequenceable operations
• Execute resequenceable operations
• Schedule work orders with resequenced operations
• Cost work orders with resequenced operations

Each of these capabilities are modeled and supported by appropriate REST services. This services-oriented structure is leveraged throughout this capability.

Identify Resequenceable Operations inWork Definition

Work definition operations are identified as count point or automatically transact. In addition to these two options, a new option was added for operations, the Allow Resequencing option.  To enable an operation to be resequenced during execution, in addition to identifying the operation as count point, you now also have to enable the Allow resequencing option.

It’s required to have the first operation and last operation as count point only. When an operation is identified as count point only, you have to execute that operation before you can execute a resequenceable operation. 

Work Definition: Edit Operation

You can define any number of resequenceable operations provided they are between two count point operations.

You can also identify a serial tracked manufacturing operation as a resequenceable operation. However, the serial start operation has to be a count point operation.

In the example, where a work definition has operations 10, 20, 30 , 40, and 50, only operations 20, 30, and 40 can be identified as resequenceable operations. This means that you have to execute operation 10 first. After that you can execute operations 20, 30, and 40 in any sequence. Only after completing 20, 30, and 40 in any sequence, you will be able to complete operation 50.

A supplier operation can’t be identified as a resequenceable operation.

In a process manufacturing work definition, a resequenceable operation can’t have outputs assigned.

You can’t add automatically transact or an optional operation between two resequenceable operations.

A contract manufacturing organization cannot have resequenceable operations.

Create and Edit Work Orders with Resequenceable Operations

On creation of a work order using a work definition having resequenceable operations, the Allow resequencing option is carried to the work order.

Until the work order is released, the Allow resequencing option can be updated or you can add resequenceable operations.

When the work order is released, in addition to the existing operation sequence, a new execution sequence is stamped for each operation. At the time of release, the execution sequence is the same order as the operation sequence. However, when you perform resequence action in the dispatch list, the execution sequence of the operations will change.

Edit Work Order: Operations Tab

As the work order progresses during execution, work order rescheduling would consider the execution sequence for the schedule than the operation sequence. The work order operation dates, material requirement dates, and resource dates would be based on execution sequence.

Execute Resequenceable Operations

Upon completion of the first count point operation, you will now be able to view all the resequenceable operations in the dispatch list.  The resequenceable operations are identified with a visual indicator in the dispatch list.

You can choose to execute any of the resequenceable operations. When you choose an operation for execution, the execution sequence now gets updated based on the actual sequence that is executed. The work order operation gets rescheduled automatically to align with the execution sequence. 

Review Dispatch List : Resequence Action

You can also complete partial quantities for a resequenceable operation. When you execute an operation, the execution sequence gets fixed and the balance quantities will need to progress only in the same execution sequence.  However, you can reverse the entire quantity for an operation and progress with a different traversal path of operations.

Performing push material transactions, manual resource transaction, picking materials, material reservation for an operation doesn't alter the execution sequence.

You can perform all actions for a resequenceable operation like quick complete, detailed complete, quality inspection, reject, scrap, serialized manufacturing actions.

When you complete all the resequenceable operations, you will be able to progress to the next immediate count point operation.

Schedule Work Orders with Resequenced Operations

Production Scheduling adheres to the execution sequence number for released work orders with resequenced operations. All other work orders will be scheduled based on the operation sequence.

Cost Work Orders with Resequenced Operations

The cost processor will use the execution sequence to calculate the accumulated WIP for each operation if the work order has resequenced operations. In the following example, let's see how the accumulated work in process balances are calculated and used.

Operation	Input Costs	Total costs at operation
10	100	100
20	150	250
30	50	300
40	25	325
50	75	400

Let's say that the operator has changed the sequence to 10->40->30->20->50. When the information gets interfaced to costing, the cost processor will calculate the work in process balances as below:

Operation	Input Costs	Work in Process Balance
10	100	100
40	25	125
30	50	175
20	150	325
50	75	400

The accumulated work in process balances are used in Actual and Perpetual Average cost methods to calculate the cost of scrap, output costs in case of process manufacturing work orders and for the provisional completion method "At accumulated work in process balances". So, if a unit of scrap is reported in the operation 20, it would be scrapped using the WIP balance of $325 when the operations are resequenced versus $250 if there were no resequencing.

The Review Work Order Costs UI has been changed to display the execution sequence followed by the work order.

Review Work Order Costs Page Showing the Execution Sequence

File-Based Data Import (FBDI) Changes:

You can define resequenceable operations using FBDI. A new column, Allow Resequencing, has been introduced to the following spreadsheets: Work Definition Import, Process Work Definition Import, Work Order Import, and Process Work Order Import. Use the latest template after upgrade to 22A.

You can't resequence operations using the Operation Transaction spreadsheet.

REST API Changes:

You can define resequenceable operations using REST services. A new attribute ResequenceFlag has been introduced at the operation level to the following services: Work Definition Requests, Work Definitions, Work Orders, and Process Work Orders. You can resequence the next operation to be executed using a custom action ResequenceAsNextOperation, which is part of the Work orders and Process Work Orders services. You can specify the Execution Sequence as an optional parameter in REST services of Production Scheduling.

Resequencing work order operations during execution helps adhere to production schedule and customer delivery schedule overcoming the shop floor exigencies.

Watch a Demo.

Steps to Enable

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

Offering: Manufacturing and Supply Chain Materials Management  No Longer Optional From: Update 22D

Key Resources

• Watch Resequence Work Order Operations During Execution Readiness Training

Role And Privileges

• Users who are assigned any of these predefined job roles can access this feature:
  • Manufacturing Engineer (ORA_WIS_MANUFACTURING_ENGINEER_JOB)
  • Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB)
  • Production Operator (ORA_WIE_PRODUCTION_OPERATOR_JOB)

Create Work Order Reports with Resequenced Operations, Supplier Operation Requisitions, and Shipping Details Using OTBI

Create OTBI reports for work orders using new and modified attributes for resequencing operations, requisitions for supplier operations, and shipping details in outside processing and direct item procurement. The following attributes are available in these subject areas and folders:

Subject Areas: All

• Work Order > Resequencing Enabled
• Work Order Operations > Allow Resequencing
• Work Order Operations > Execution Sequence

Subject Areas: Work Order Performance Real Time, Material Usage Real Time, Actual Production Real Time, Production Exceptions Real Time

• Work Order Operations > Supplier Operation > Requisition Number
• Work Order Operations > Supplier Operation > Requisition Line
• Work Order Operations > Supplier Operation > Requisition Line Quantity
• Work Order Operations > Supplier Operation > PO Quantity
• Work Order Operations > Supplier Operation > UOM

Subject Areas: Purchased Item Real Time

• Purchase Order > UOM
• Purchased Item Usage > Purchase Order Quantity

If you have already enabled the 21D feature Purchase Items That Are Priced in Their Secondary UOM feature, then two new fields for Shipping Quantity and Shipping UOM are available in the Procurement data model. The intent of introducing these new fields is to translate the existing Quantity and UOM fields on a purchase order as the Pricing Quantity and UOM and further distinguish it from the Shipping Quantity and UOM. The existing PO Quantity and UOM attributes in the Manufacturing OTBI subject areas for Outside Processing and Direct Item Procurement has now been modified to point to the new data model fields. Existing OTBI reports with these fields may display incorrect data that can be rectified by removing and adding them back.

You can now build robust work order reports to analyze resequenceable work order operations, requisition details for supplier operations, and shipping details in outside processing and direct item procurement.

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

For additional considerations, please refer to the 21D Procurement feature: Generate Reports on Purchase Orders for Items Priced in Their Secondary UOM Using OTBI.

Role And Privileges

• Users who are assigned any of these predefined job roles can access this feature:
  • Production Supervisor (ORA_WIE_PRODUCTION_SUPERVISOR_JOB

Enforce Gapless Numbering for Manufacturing and Maintenance Work Orders

Based on the Enforce Gapless Numbering for Work Orders profile option settings, you have an option to create manufacturing and maintenance work order numbers with or without gaps.

Use this profile option to improve performance during mass creation of manufacturing and maintenance work orders.

Steps to Enable

To enable the Enforce Gapless Numbering for Work Orders profile option, perform the following steps.

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

• Offering: Manufacturing and Supply Chain Materials Management
• Functional Area: Manufacturing Master Data
• Task: Manage Administrator Profile Values

2. In the Profile Option Code field, query for the option Enforce Gapless Numbering for Work Orders (code: ORA_WIE_ENFORCE_GAPLESS_NUMBERING).

Profile option values are:

Yes - Gapless numbers are always enforced; there won’t be any gaps in work order numbers generated even in case of orderless transactions.

No - Work order numbers are not guaranteed to be gapless. Though they may still be in all likelihood gapless, there may be situations in which certain generated work orders could be discarded.

Tips And Considerations

The profile value can be set up only at site level.

Role And Privileges

• To set up this feature, here's what you need.

• • Predefined job role name and code:
    • Application Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)