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	Product	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

Maintenance

Maintenance

Resequence Work Order Operations During Execution

Before this update, maintenance operations had to be executed in a prespecified sequence, as defined in the work order. Practically, maintenance operations may need to be executed out of the sequence to overcome operational constraints and make the asset operational at the earliest.

With this update, you can perform certain operations in a sequence different from the sequence defined in the work order. Let’s consider a work order with operations 10, 20, 30, 40, and 50 sequenced in that order. Now, your technician has the option to complete operation 30 before operation 20.

Note that you can change the sequence of operation completion only if the operations are defined as resequenceable operations.

Here's what you can do with this feature:

• Create and edit work definitions with resequenceable operations
• Create and edit work orders with resequenceable operations
• Execute resequenceable operations
• Schedule work orders with resequenceable operations
• Cost work orders with resequenceable operations

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

Create and Edit Work Definition with Resequenceable Operations

In addition to the Count Point and Automatically Transact check boxes, we have a new Allow Resequencing check box for operations. Select the Allow Resequencing check box to be able to resequence the operation later. Note that only a count point operation can be enabled as a resequenceable operation.

As always, it’s required to have the first operation and last operation as count point only operations in a work order.

Create Maintenance Work Definition UI

Here are a few business rules for an operation to be set as resequenceable:

• You can define any number of resequenceable operations if they are between two count point operations.
• A supplier operation can’t be identified as a resequenceable operation.
• You can’t add an autotransact or an optional operation between two resequenceable operations.

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 operation 10 should be executed first, and operations 20, 30, and 40 can be executed in any sequence. Operation 50 can be completed only after completing all the prior operations till operation 40.

Create and Edit Work Orders with Resequenceable Operations

When a work order is created using a work definition with resequenceable operations, the operations are transferred to the work order with the Allow Resequencing check box selected. However, in the work order, you can add new resequenceable operations or update the Allow Resequencing check box of an operation until the work order is released.

When the work order is released, all operations are arranged in the new execution sequence and ascending numeric values are assigned automatically to each operation. The value of the execution sequence is updated automatically when the operation is completed out of the defined sequence.

Edit Work Order: Operations Tab

After the execution sequence is assigned to work order operations, the work order scheduling gets based on the execution sequence of the operations. This means the work order operation dates, material requirement dates, and resource dates get based on the execution sequence.

Execute Resequenceable Operations

If a count point operation is followed by a set of resequenceable operations, then when the count point operation gets completed, you can view all the resequenceable operations in the dispatch list. This lets you complete the resequenceable operations in any order. The resequenceable operations are identified with a visual indicator in the dispatch list.

When you change the sequence of operation completion by clicking the resequenceable icon, the execution sequence gets updated automatically. At the same time, the work order operation gets rescheduled automatically based on the revised execution sequence. 

Review Maintenance Dispatch List: Resequence Action

When operations are completed in a certain order, then the execution sequence is set in the order of actual completion. After this, you can only reverse the operation completion based on the order execution sequence in the operation.

Performing push material transactions, manual resource transaction, picking materials, and material reservation for an operation doesn't alter the execution sequence. As usual, you can perform all actions for a resequenceable operation like quick complete, detailed complete, and enter quality inspection.

After completing all the resequenceable operations displayed in the dispatch list, the next immediate count point operation is displayed and can be completed.

Schedule Work Orders with Resequenceable Operations

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

Cost Work Orders with Resequenceable Operations

Maintenance work order cost calculation is not affected by the change in order of operation completion. However, the Maintenance Work Order Costs UI now also displays the execution sequence.

Maintenance Work Order Costs Page Showing the Execution Sequence

File-Based Data Import (FBDI) Changes:

You can define resequenceable operations using FBDI. The Allow Resequencing column is added to these spreadsheets: Work Definition Import and 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. The ResequenceFlag attribute has been introduced at the operation level to these services: Work Definitions, Work Orders. You can resequence the next operation to be executed using a configured action, ResequenceAsNextOperation, which is part of the 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 to continue the maintenance activity by overcoming the shop floor exigencies and make the asset operational at the earliest.

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

Role Information

• Users who are assigned any of these predefined job roles will be able to access this feature automatically:
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)
  • Maintenance Technician (ORA_MNT_MAINTENANCE_TECHNICIAN_JOB)

Integrate and Extend Maintenance Using REST Services

Fetch Asset Group Details Using REST API

Fetch asset group details for an asset using REST API. The response now includes not only the standard fields, but also the fields you define using Application Composer. The response details can be made available to third-party applications. Additionally, you can edit the standard and user-defined fields using the Asset Groups REST API.

The Asset Group object is extended using Application Composer. This helps you create your own fields for use in the application pages as well as the Asset Groups REST API.

First, you create and enter a sandbox that's enabled for Application Composer in a test environment. You then navigate to Application Composer, and for the Application field, select ERP and SCM Cloud, and select Asset Group as the Standard Object:

Asset Group Standard Object

These are the different types of fields that you can define:

Types of Fields

Next, you can add the fields to the Create and Edit Asset Group pages. You must duplicate the pages to edit and add these fields:

Adding Field to Pages

Then the pages and fields can be verified in the application pages in the sandbox. When verified, the sandbox can be published.

Verify New Fields

Finally, when the sandbox is published, the newly defined fields will be available in the Asset Groups REST API:

REST GET Response

Retrieving asset group details using a REST API allow integration of these details in third-party applications. Additionally, the extensibility for the asset groups gives you flexibility to use your own fields to further define and manage an asset group definition.

Steps to Enable

Leverage Application Composer to expose and adjust page layout and attributes. To learn more about extending your application using Application Composer, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.

Tips And Considerations

• Defining your own fields should include adding them to both the Create and Edit Asset Group pages.

• Additionally, users must have the Custom Objects Administration (ORA_CRM_EXTN_ROLE) role in order to view and interact with the fields you created in Application Composer.  For more details, refer to the Using Maintenance guide, and the Maintenance chapter in Implementing Manufacturing and Supply Chain Materials Management guide.

Role Information

• Predefined job role name and code:
  • Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)
  • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)

• Privileges:
  • Custom Objects Administration (ORA_CRM_EXTN_ROLE)
  • Manage Customer Assets (CSI_MANAGE_CUSTOMER_ASSETS_PRIV)
  • Manage Maintainable Assets (MNT_MANAGE_MAINTAINABLE_ASSETS_PRIV)
  • Manage Maintenance Work Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)
  • Manage Maintenance Work Order Operations (MNT_MANAGE_MAINTENANCE_WORK_ORDER_OPERATIONS_PRIV)

Track Asset Failures Using REST API

Standardizing the identification and capture of asset failures, causes, and resolutions enables organizations to measure and analyze asset reliability and availability, as well as maintenance effectiveness and efficiency. Failure data provides the foundation necessary to determine asset-specific maintenance strategies and optimize maintenance programs, as well as to support reliability tools like root cause analysis, failure modes and effects analysis, probability plotting and statistical modelling. Failure history data is required for gleaning insight from machine learning predictions and recommendations.

A number of new REST APIs provide robust support for asset failure tracking and analysis. These include:

• Asset Failure Events
• Failure Instances
• Failure Root Causes (child resource of Failure Instances)
• Asset Diagnostic Symptoms
• Maintenance Recommendations
• Asset Failure Sets
• Condition Event Codes

This set of APIs provides the foundation for developing user modules for failure tracking, history, and analysis.

The failure event represents the specific span of time during which an asset is not functioning appropriately, and whether that functional failure results in asset downtime. The failure instance represents a specific combination of failure, cause, resolution and failed part. A single failure event may have multiple failure instances; for example, if more than one part fails. A failure event can also have one or more root causes, representing causal factors that led to the immediate and observable cause of failure, such as improper design, inappropriate processes or insufficient training.

Symptoms are observations or diagnostic information related to anomalous asset behavior that may precede or co-occur with a failure event. Symptoms are often reported by asset end-users or IoT-enabled assets and result in an inspection, but may or may not result in a failure record; however, the symptom information is vital for predicting future failures when similar symptoms entail. Recommendations provide context-specific guidance to users regarding the most likely cause of a specific failure, most probable best fix for a failure, and/or the failed part that most likely caused the failure. These recommendations are expected to generally come from machine learning analysis of historical failure events, failure instances, symptoms and other data.

Failure sets define the rules around how failure data is captured and under which conditions a technician is required to capture failure data on a work order. Condition event codes provide standardized codification of failure codes, cause codes, resolution codes, diagnostic codes, etc. Condition event codes and a page to manage them existed previously, but now businesses can setup their codes using REST APIs.

This set of APIs supports flows where a maintenance technician, supervisor, reliability engineer or even an IoT-enabled asset needs to enter, edit, review or analyze failure data.

Failure tracking and analysis is fundamental to increasing asset reliability, reducing unplanned downtime, and reducing maintenance costs.

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.

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

Tips And Considerations

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

Key Resources

Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation, available on the Oracle Help Center.

Role Information

• Privilege Name and Code:        
  • Manage Condition Event Codes (MNT_MANAGE_FAILURE_CONDITION_EVENT_CODE_BY_SERVICE)       
  • Get Condition Event Codes (MNT_GET_FAILURE_CONDITION_EVENT_CODE_BY_SERVICE)       
  • Manage Failure Sets (MNT_MANAGE_FAILURE_SET_BY_SERVICE)       
  • Get Failure Sets (MNT_GET_FAILURE_SET_BY_SERVICE)       
  • Manage Failure Events (MNT_MANAGE_FAILURE_EVENT_BY_SERVICE)       
  • Get Failure Events (MNT_GET_FAILURE_EVENT_BY_SERVICE)       
  • Get Failure Event Instances (MNT_GET_FAILURE_EVENT_INSTANCE_BY_SERVICE)       
  • Manage Symptoms (MNT_MANAGE_FAILURE_SYMPTOM_BY_SERVICE)       
  • Get Symptoms (MNT_GET_FAILURE_SET_SYMPTOM_BY_SERVICE)

• Job Role Name and Code:       
  • Maintenance Management Web Service Duty

Manage the Relationship Between an Installed Base Asset and a Fixed Asset Using REST API

Create a relationship between the installed base asset and fixed asset using a REST service.

Here's what you can do with this update:

• Create the relationship between installed base and fixed assets
• Update the relationship of installed base and fixed assets
• Get the relationship details of installed base and fixed assets

Use the fixedAssetAssociations REST resource, a child to the existing InstalledBaseAssets resource.

Manage your asset details easily using the Installed Base REST API.

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.

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.

Tips And Considerations

Here are the requirements for successful creation or update of the relationships using the REST service:

• Users must have the Associate Fixed Assets (MNT_ASSET_FIXEDASSET_ASSOCIATE) privilege.
• Inventory organisation parameters must have the value for the new Fixed Asset Corporate Book attribute.

Just like the UI, the valid fixed asset types are CIP and Capitalized.

Key Resources

• Refer to the release documentation of Connect Your Installed Base Assets and Fixed Assets
• Refer to the REST APIs for Oracle SCM Cloud documentation available on the Oracle Help Center.

Role Information

• Users who are assigned any of these predefined job roles will be able to access this feature automatically:
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)
  • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)

• Users who are assigned configured job roles that contain one or more of these service privileges will be able to access this feature:
  • Manage Enterprise Assets by Service (CSE_MANAGE_ENTERPRISE_ASSETS_BY_SERVICE_PRIV)
  • Get Enterprise Assets by Service (CSE_GET_ENTERPRISE_ASSETS_BY_SERVICE_PRIV)
  • Manage Customer Assets by Service (CSI_MANAGE_CUSTOMER_ASSETS_BY_SERVICE_PRIV)
  • Get Customer Assets by Service (CSI_GET_CUSTOMER_ASSETS_BY_SERVICE_PRIV)

• Users who are assigned configured job roles that contain the one of the duty roles will be able to access this feature:
  • Maintenance Management Web Service (ORA_MNT_MAINTENANCE_SERVICE_DUTY)
  • Installed Base Web Service (ORA_CSI_INSTALLED_BASE_WEB_SERVICE_DUTY)

Service Logistics

Bill Multiple Parties for Field Service

Service Logistics now provides the ability to invoice multiple parties through individual debrief lines using the debrief header. Previously, the charges for Field Service and Depot Repair Work Orders were charged only to the Bill to Customer at the debrief header level. The Customer, Account and Bill-to Address attributes are now available for update at the debrief line level.  When a different Customer, Account and/or Bill to Address details are added to a debrief line, a matching sales order line is created to facilitate invoice processing for the newly added customer details.

New Bill to Details Field Added to Charges Tab

New fields have been added to the Charges tab for field service and depot repair work orders to allow billing based on debrief line level attributes. The Customer, Account, and Bill-to Address that are available at the debrief header are now also available for update at the line level.

Add New Bill-to Address Columns to Charges Tab

Bill to Details Context Menu

Debrief charge lines are priced based on the bill-to details at the line level. Any additions or changes to the charge lines can affect the total line amount and pricing information is re-calculated after any updates to ensure the correct amount is used for invoicing. 

The bill-to charges at the debrief line level provide the ability to invoice multiple parties for a single Field Service work order and Depot Repair work order for different items such as labor and other service expenses.

Steps to Enable

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

Role Information

• Users who are assigned any of these predefined job roles can access this feature:
  • Field Service Administrator (ORA_RCL_FIELD_SERVICE_ADMINISTRATORS)
  • Field Service Technician Duty (ORA_RCL_FIELD_SERVICE_TECHNICIAN_DUTY)
  • Depot Manager (ORA_RCL_DEPOT_REPAIR_MANAGER_JOB)

Retrieve Payment Terms Directly from Customer Account

You can now create the sales orders for field service work orders and depot repair work orders based on the payment terms defined at the customer master level. Previously, you set up pre-transformation rules to provide the default payment terms used when creating a sales order. Pre-transformation rules are now optional, and payment terms defined at the customer master level default when creating a sales order. 

Default Payment Terms for Order Charge Lines Come Directly from Customer Account Setup

By retrieving payment terms directly from the Customer Account, you minimize the number of additional setup steps.  

Steps to Enable

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

Role Information

• Users who are assigned any of these predefined job roles can access this feature: 
  • Field Service Administrator (ORA_RCL_FIELD_SERVICE_ADMINISTRATORS)
  • Field Service Technician Duty (ORA_RCL_FIELD_SERVICE_TECHNICIAN_DUTY)
  • Depot Manager (ORA_RCL_DEPOT_REPAIR_MANAGER_JOB)

Ship Field Service Parts to Field Warehouse Locations

You can now ship parts needed for field service work orders to a field stocking location.  This shipping option adds to existing capabilities to ship to customer and field service technician locations.

Using the Add Part UI and the Create Part Requirements UI Header region, you can now create work order part requirements/orders with field stocking location ship-to addresses.  This enables field service technicians to pick up parts at the district office stockroom, a drop box, or other field stocking location instead of having the parts delivered to the customer site or the technician’s home.  This feature is available when ordering parts for B2B Service work orders and when ordering parts for third party objects (when the destination organization is provided).

In addition, when parts are ordered before a field technician is assigned to the work order, the Add Part UI now defaults the destination organization from the work order's work area.  Work area is assigned by integration between B2B Service and Oracle Field Service Cloud.

Field Service Work Order Add Part UI

Create Part Requirements Header Region

The ability to ship work order parts to field stocking locations increases the flexibility of your parts supply chain and reduces shrinkage and lost parts. 

Defaulting the part requirement/order destination inventory organization from the work order's work area reduces errors and manual effort when coordinating the scheduling of part orders and field technicians.

Steps to Enable

Assign default destination inventory organizations to work areas in the tag column of the Service Logistics Work Area Lookup (ORA_RCL_WORK_AREA).   These default destination organizations are used when creating part requirements before a field technician has been assigned to the B2B Service work order.

Work Area Lookup

Role Information

Users who are assigned either of these predefined job roles can access this feature:

• Field Service Administrator (ORA_RCL_FIELD_SERVICE_ADMINISTRATOR)
• Field Service Technician Duty (ORA_RCL_FIELD_SERVICE_TECHNICIAN_DUTY)

Post Charges in the Background to Support High Volume Invoicing

Oracle Service Logistics Cloud now provides the ability to post charges in the background so you can update the next work order immediately. Prior to this feature, you had to wait for the charges to post before updating the next work order. A new Post Charges and Close button initiates a background job to post charges and then close the Depot Repair Workbench or the Manage Charges and Estimates page. 

New Post Charges and Close button

By posting charges in the background, you can now process a higher volume of work order updates and invoicing. 

Steps to Enable

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

Role Information

• Users who are assigned any of these predefined job roles can access this feature:
  • Field Service Administrator (ORA_RCL_FIELD_SERVICE_ADMINISTRATOR)
  • Field Service Technician Duty (ORA_RCL_FIELD_SERVICE_TECHNICIAN_DUTY)
  • Depot Repair Manager (ORA_RCL_DEPOT_REPAIR_MANAGER_JOB)