Expand All


  1. Update 24A
  1. Revision History
  2. Overview
  3. Pre-Update and Post-Update Tasks
  4. Optional Uptake of New Features (Opt In)
  5. Feature Summary
  6. Maintenance
    1. Maintenance
        1. Enhance Maintenance Management and Installed Base OTBI Subject Areas for Key Sales Order Attributes for Assets
        2. Create Asset Meters Using a Scheduled Process
        3. Define the Validation Organization for Customer Assets
        4. Create Work Orders for Assets on the Asset Information Management Page
        5. Create Failure Sets in Setup and Maintenance
        6. Associate Work Order Operation to a Failure Instance
        7. Remove Items that aren't Asset Tracked Using a Maintenance Work Order
        8. Add Attachments to Maintenance Work Orders Using a REST Service
        9. Manage Task Flows on the Maintenance Management Landing Page
        10. Manage Maintenance Programs Across Organizations Using File-Based Data Import and REST API
        11. Manage Maintenance Forecast for an Asset Using a REST Service
        12. Manage Preventative Maintenance For Assets Across Organizations
        13. Manage Supplier Warranty Claims and Entitlements
        14. Manage Maintenance Forecast Across Organizations
    2. Service Logistics
        1. Consider the Supplier Warranty When Routing Returns
        2. Calculate Estimated Sales Tax
        3. Update the Create Expense UI Fields to Quantity and Unit of Measure
        4. Perform Mass Updates on Part Requirement Lines
        5. Use Smart Search to Search For and View Part Requirements

Update 24A

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
02 FEB 2024   Add Attachments to Maintenance Work Orders Using a REST Service Updated document. Revised feature information.
01 DEC 2023     Created initial document.

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Pre-Update and Post-Update Tasks

Depending on the features you're using in your Cloud applications, you may be required to perform certain steps immediately before or after your quarterly update. For details of these pre-update and post-update steps and the product areas that are affected, refer to Oracle Fusion Cloud SCM: Performing Your Quarterly Update (doc ID 2337485.1) on My Oracle Support.

Optional Uptake of New Features (Opt In)

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

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

Here’s how you opt in to new features:

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

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

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

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

Opt In Expiration

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

Feature Summary

Column Definitions:

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

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

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

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

Ready for Use by End Users
(Feature Delivered Enabled)

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

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

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

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Maintenance

Maintenance

Enhance Maintenance Management and Installed Base OTBI Subject Areas for Key Sales Order Attributes for Assets

Create Asset Meters Using a Scheduled Process

Define the Validation Organization for Customer Assets

Create Work Orders for Assets on the Asset Information Management Page

Create Failure Sets in Setup and Maintenance

Associate Work Order Operation to a Failure Instance

Remove Items that aren't Asset Tracked Using a Maintenance Work Order

Add Attachments to Maintenance Work Orders Using a REST Service

Manage Task Flows on the Maintenance Management Landing Page

Manage Maintenance Programs Across Organizations Using File-Based Data Import and REST API

Manage Maintenance Forecast for an Asset Using a REST Service

Manage Preventative Maintenance For Assets Across Organizations

Manage Supplier Warranty Claims and Entitlements

Manage Maintenance Forecast Across Organizations

Service Logistics

Consider the Supplier Warranty When Routing Returns

Calculate Estimated Sales Tax

Update the Create Expense UI Fields to Quantity and Unit of Measure

Perform Mass Updates on Part Requirement Lines

Use Smart Search to Search For and View Part Requirements

Maintenance

Maintenance

Enhance Maintenance Management and Installed Base OTBI Subject Areas for Key Sales Order Attributes for Assets

Oracle Transactional Business Intelligence (OTBI) offers you real-time, self-service reporting directly from Oracle Fusion Cloud Maintenance. The following table lists the updates available to the OTBI subject areas and dimension folders in this update:

Subject Area

Update by Dimension Folder

Installed Base - Customer Asset Real Time

The reference subject area is updated with the following attributes:

  • Customer Asset Details : This folder is updated to include these attributes
    • Customer Purchase Date
    • In Service Date
    • Installed Date
    • Registration Date

Installed Base - Customer Asset History Real Time

The reference subject area is updated with the following attributes:

  • Customer Asset Details : This folder is updated to include these attributes
    • Customer Purchase Date
    • In Service Date
    • Installed Date
    • Registration Date

Using OTBI, you can make better decisions based on real-time transactional information. With this update, you can use these enhanced subject areas to generate the reports and queries that you want, when you want them.

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).

Leverage new subject areas 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).

Access Requirements

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

  • Manage Customer Assets (CSI_MANAGE_CUSTOMER_ASSETS_PRIV)
  • Manage Maintainable Assets (MNT_MANAGE_MAINTAINABLE_ASSETS_PRIV)

These privileges were available prior to this update.

Create Asset Meters Using a Scheduled Process

Asset meters are created automatically when new assets are created if the applicable asset item has an associated meter template. If an asset was created, but the applicable item didn't have an associated meter template, a meter won't be created when the asset was created. This caused a problem if users wanted to create meters for new assets automatically but forgot to associate the meter templates to the item before creating the assets. In this situation, each asset’s meters would need to be manually created in the user interface because there was no way to add meters to existing assets automatically.

With this update, you can utilize a scheduled process to add meters to existing assets automatically. You can now use the Perform a Mass Association of Meter Templates scheduled process to programmatically perform bulk associations of meter templates or templates to assets.

The scheduled process can be submitted from the following two pages:

  • Scheduled Processes 
  • Meter Template page

Submitting Job Process from Scheduled Processes Page

The job is accessible through the Scheduled Processes. You can perform the Perform Mass Association of Meter Templates job with or without the meter template parameter (optional).

Scheduled Process

Scheduled Process

Submitting Job Process from Meter Template Page

You can also perform a mass association of meter templates by selecting the Schedule Mass Asset Update from the applicable tab of the meter template page in the context of an Item.

Meter Template Add Applicable Tab

Meter Template Add Applicable Tab

You can quickly and easily add new meters to existing assets.

Steps to Enable

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

Tips And Considerations

  • It's recommended that when defining the meter template essentials, the Record Meters at Work Order Completion field be selected as required if you want to be able to record meter readings in the Maintenance Dispatch List during work order completion.
  • The Default Master Organization for Maintenance Management parameter can be defined using your main master organization. The value can then be used for defaulting in the Manage Meter Templates.
    • See 23D Readiness content for Manage Additional Asset Maintenance Parameters

Access Requirements

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

  • Mass Association of Meter Templates (MNT_MASS_ASSOCIATION_METER_TEMPLATES)

This privilege is new in this update.

Define the Validation Organization for Customer Assets

You now need to define a validation organization to create or update customer assets. The organization can be an item or inventory organization.

This new parameter will replace the existing setup in the Manage Order Management Parameters. If not defined, you won't be able to create or update customer assets.

Steps to Enable

In Manage Asset Maintenance Parameters work area, define the validation organization for customer assets, which can be an item or inventory organization. The value is used as the item validation organization to validate the properties of the item associated with the customer asset being created or updated. If this value isn't defined, you will receive an error during an asset creation.

If you are an existing customer, then during your 24A update process, the value in the Manage Order Management Parameters will be migrated to the Manage Asset Maintenance Parameters page.  After the update, ensure to set the value correctly by an administrator. If you are a new customer, after the 24A update process, you will need to set this value if you wish to create or update customer assets.

Manage Asset Maintenance Parameters

Manage Asset Maintenance Parameters

Access Requirements

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

  • Manage Asset Maintenance Parameters (MNT_MANAGE_ASSET_MAINTENANCE_PARAMETERS)

This privilege was available prior to this update.

Create Work Orders for Assets on the Asset Information Management Page

You can now create and manage maintenance work orders from the Asset Information Management page.

A new Actions column is provided on the Asset Information Management page, with two action buttons, including View Details and More Actions.

The New Actions Column is the Last Column with Two Action Buttons: View Details, and More Actions

The New Actions Column is the Last Column with Two Action Buttons: View Details, and More Actions

The View Details action button opens the side drawer where you can see the Asset Groups and Additional Information:

Side Drawer with Groups and Additional Information

Side Drawer with Groups and Additional Information

Clicking on the More Actions represented by the three ellipses ". . . opens a dialog box that allows you to select Create Maintenance Work Order, Manage Maintenance Work Order, or View Asset 360.

More Actions Dialog box with Three Action Options: Create Maintenance Work Order, Manage Maintenance Work Order, or View Asset 360

More Actions Dialog box with Three Action Options: Create Maintenance Work Order, Manage Maintenance Work Order, or View Asset 360

If you select Create Maintenance Work Order, you will be prompted to enter the following work order details:

  • Generate maintenance work orders from a condition event (this is an optional selection)
    • If you selected the above option, you are required to enter a Condition Event
  • Work Order Description
  • Work Definition
  • Type and Subtype (both are required fields and can be derived from data entered in the above fields)
  • Priority 
  • Start Date (this date can be edited)

New Maintenance Work Order Dialog Box

New Maintenance Work Order Dialog Box

You can quickly and easily find your assets and create a maintenance work order, or manage your asset's maintenance work orders.

Steps to Enable

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

Tips And Considerations

You can create a maintenance work order and manually report a condition event code, replicating a system-generated code from a third-party asset monitoring system.

Key Resources

  • Check out the Implementation Guide content for How You Use Smart Search to Search For and View Assets in the New Assets UI under Oracle Fusion Cloud Maintenance.
  • Check out the User Guide content for How to Manage Condition Event Codes

Access Requirements

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

  • Manage Maintenance Work Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)
  • Manage Maintenance Work Orders ( MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)
  • View Maintenance Work Orders ( MNT_VIEW_MAINTENANCE_WORK_ORDERS_PRIV)

These privileges were available prior to this update.

Create Failure Sets in Setup and Maintenance

Capturing asset failures, causes, and resolutions helps organizations measure and analyze asset reliability and availability, which also helps assess maintenance effectiveness and efficiency. This update allows functional administrators to control and manage the definition of failure sets centrally in the Setup and Maintenance Manager rather than from the Manage Task Flows on the Maintenance Management Landing page.

Setup and Maintenance

Setup and Maintenance

You can easily and efficiently manage all setup data tasks in one place.

Steps to Enable

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

Key Resources

  • Check out the What's New content of the Capture Failure Information of Work Order Asset feature
  • Check out the What's New content of the Track Asset Failure using REST API feature

Access Requirements

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

  • Manage Failure Sets Using User Interface (MNT_MANAGE_FAILURE_SET)
  • View Failure Sets Using User Interface (MNT_VIEW_FAILURE_SET)
  • Manage Maintenance Management Work Area (MNT_MANAGE_MAINTENANCE_MANAGEMENT_WORK_AREA_PRIV)

These privileges were available prior to this update.

Associate Work Order Operation to a Failure Instance

Capturing asset failures, causes, and resolutions helps organizations measure and analyze asset reliability and availability, which also helps assess maintenance effectiveness and efficiency. As part of the manage maintenance work order and the maintenance dispatch list, you can create a failure event and report a failure instance that records the failure code, cause code, resolution code, and the failed component and asset number.

In this update, you can now identify the work order operation using the new field Operation Sequence when creating a new failure instance.

New Failure Instance with Operation Sequence Selection Drop Down

New Failure Instance with Operation Sequence Selection Drop Down

Associating a specific failure instance with a work order operation  makes it easier to understand what repair was done for each reported failure.

Steps to Enable

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

Tips And Considerations

It's necessary to have the following setup before attempting a failure capture for a work order asset:

  • Defining valid failure, cause, and resolution codes
  • Defining a default failure set

Key Resources

  • Check out the What's New content of the Capture Failure Information of Work Order Asset feature
  • Check out the What's New content of the Track Asset Failure using REST API feature
  • Note a new Optional attribute Op Seq was added to the Failure Instance REST

Access Requirements

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

  • Manage Failure Events for Work Order Asset (MNT_MANAGE_FAILURE_EVENT_WO_ASSET_PRIV)
  • Manage Maintenance Work Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)
  • Manage Maintenance Work Order Operations (MNT_MANAGE_MAINTENANCE_WORK_ORDER_OPERATIONS_PRIV)
  • Review Maintenance Dispatch List (MNT_REVIEW_MAINTENANCE_DISPATCH_LIST_PRIV)
  • Manage Maintenance Management Work Area (MNT_MANAGE_MAINTENANCE_MANAGEMENT_WORK_AREA_PRIV)

These privileges were available prior to this update.

Remove Items that aren't Asset Tracked Using a Maintenance Work Order

The report material transactions feature enables you to report the materials that are consumed in the work order operation. You can issue materials from inventory to the operation and return the issued materials to inventory. Depending on how the item is set up, you can issue materials from the common inventory or from the project-specific inventory.

New functionality as part of this update supports the following scenarios within reporting material transactions:

  • The ability to return nonasset-tracked items that weren't previously issued within the context of the work order operation.
  • The ability to return ad hoc nonasset-tracked items.  ad-hoc non-asset tracked items to inventory
  • The ability to remove items on a work order operation first when an open demand for the item exists

Return nonasset-tracked items that weren't previously issued within the context of the work order operation

Before this update, there were technical challenges in handling non-asset tracked items (components) on the Report Material Transaction UI. For example, you couldn't return nonasset-tracked items if they weren't previously issued within the context of the work order operation. With this update, you can better manage nonasset-tracked items.

For example, your work order has two operations: Operation (10) is used to issue a non-asset-tracked item to the work order asset, and operation (20) is used to test the newly configured asset (with the new item) before completing the job.  You perform the operation (10) and, report the issue of the non-asset-tracked item and complete the operation. During operation (20), you test the newly configured asset and determine that the item you installed in operation (10) is faulty. As a result, you need to remove it and issue a new one.  With this update, you can now return the non-asset tracked item that was previously issued in operation (10) in operation (20) and issue a new one.

Return ad hoc nonasset-tracked items to inventory

With this update, you can create material return transactions for ad-hoc nonasset-tracked items in the same way as you could create material return transactions for ad hoc asset-tracked items. For example, while physically inspecting an asset, you discover a faulty component that isn't recorded in the Oracle Fusion Application. It physically exists on the asset but isn't recorded as existing in the software. You can now create a return transaction for this component and create a record in the user interface, recording the component lot and serial number. The system creates a return record and allocates your newly created component on the selected subinventory locator.

Remove components with material demand

Before this update, you couldn't perform a remove material transactions for an Item if there was material demand for the Item on the same work order operation. For example, you have a  work order operation with material demand for Item A. As you are completing the work order in the Maintenance Dispatch List page, you want to perform the return material transaction for the defective Item A, before issuing the new Item A serviceable component, in the same manner as you physically perform the work. Previously, you had to perform the material issue transaction for the serviceable part (Item A) before performing the material return transaction for the defective one. With this update, you can initiate your maintenance in the system either way: issue it first and then return it, or start with a return transaction, followed by issuing it.

The same functionality also supports asset-tracked items.

The features are enabled on these use interfaces

  • Issue and Return Material from Inventory
  • Review Maintenance Dispatch List - Manual Reporting Completed
  • Review Maintenance Dispatch List - Complete with Details

Complete with Details

Complete with Details

You can perform material transactions for components that aren't asset tracked in same the manner as components that are asset tracked. You can report your material transactions in the system in the same order as your physically perform them on the asset.

Steps to Enable

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

Access Requirements

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

  • Manage Customer Assets (CSI_MANAGE_CUSTOMER_ASSETS_PRIV)
  • Manage Maintainable Assets (MNT_MANAGE_MAINTAINABLE_ASSETS_PRIV)

These privileges were available prior to this update.

Add Attachments to Maintenance Work Orders Using a REST Service

Work order attachments may contain important information and relevant instructions that can be used to effectively assess the work required and assign the right resources. Prior to this update, you were able to add attachments to work orders through the user interface only.  In this update, you can leverage the Work Order Attachments REST API to manage attachments on a work order. You are able to perform multiple actions including retrieving all attachments or a single attachment, adding or updating attachments to a work order, and deleting attachments.

Some tasks or business processes require that you store and maintain documents, images, or other files in the form of attachments for future reference. Attachments may exist in the form of large objects, text, an image, or a media file. There are three types of attachments supported, including text, URL, and files. A text attachment comprises unstructured written text, a URL attachment comprises a web link to an external web page when clicked, and a file attachment that comprises images or documents and media. In general, Oracle REST APIs support working with all types of attachments. In this update, you can now store attachments in a column within the same database table. The file contents should be provided in base64 format. Please use the link: https://www.base64encode.org to ensure the file is in the correct format.

You can now associate attachments with work orders using a REST resource in addition to associating attachments via user interface pages. You can also search for existing attachments or update your attachments using other operations in the same REST resource.

Steps to Enable

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

Key Resources

Access Requirements

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

  • Manage Customer Assets (CSI_MANAGE_CUSTOMER_ASSETS_PRIV)
  • Manage Maintainable Assets (MNT_MANAGE_MAINTAINABLE_ASSETS_PRIV)

These privileges were available prior to this update.

Manage Task Flows on the Maintenance Management Landing Page

The landing page provides a task navigator to access the different setup, management, and execution task flows. The task flow access is assigned to the maintenance manager and maintenance technician roles through security privileges.

You can access this existing task flow menu if you are responsible for the maintenance manager, customer asset, and technician tasks for your enterprise:

  • Asset and Work Definition
  • Maintenance Programs
  • Maintenance Setup
  • Work Management
  • Work Execution
  • Imports
  • Service Mapper for Asset (only shown via opt in)

If you've been assigned a job role your enterprise uses for maintenance manager, customer asset, and technician users, you can access the revised task flow menu in this update.

Revised task flow menu:

  • Asset and Work Definition
  • Work Management
  • Work Execution
  • Maintenance Programs
  • Supplier Warranty 
  • Imports
  • Maintenance Setup
  • Service Mapper for Asset (only shown via opt-in)

Here is an expanded view of the new task flow menu:

Tasks Menu

Tasks Menu

You can quickly and easily access your maintenance tasks from the newly reorganized task menu.

Steps to Enable

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

Access Requirements

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

  • Manage Maintenance Management Work Area (MNT_MANAGE_MAINTENANCE_MANAGEMENT_WORK_AREA_PRIV)

This privilege was available prior to this update.

Manage Maintenance Programs Across Organizations Using File-Based Data Import and REST API

Maintenance programs are used to define and generate a periodic preventative maintenance forecast for one or more affected assets in a maintenance-enabled organization. In this update, you can now create and update maintenance programs in a central planning organization to enable assets across operating different organizations to be included in the forecast. When assets move between organizations either temporarily or permanently, you can now determine when and where an asset will be maintained using a REST API or file-based data import.  These methods will continue to support assets that operate and will be maintained in their operating organizations as well.

The FBDI template provides tabs to define key program attributes and the template includes detailed column descriptions and sample data for common use cases.  The change log for this uptake includes:

  • The Maintenance Program (header) tab has the following new attributes: Program Type Code, Program SubType Code, Allow Global Assets Flag, Program Reference, Forecast Window in Days, Workorder Window in Days, Work Order Start Time, and Work Order Timezone

  • The Work Requirements tab has the following new attributes: Requirement Reference, Forecast Window in Days, Workorder Window in Days, Create Work Order Option Code, Work Order Status, Work Order Firm Flag, and Work Order Priority.

  • The Affected Assets tab has the following new attribute: Create Work Order Option Code

Additionally, complementary enhancements have been made to the Maintenance Programs REST API to ensure that cross-organization assets are supported and assets that operate and will be maintained in their operating organizations.  Examples are included in the REST API guide for Supply Chain Management under the Use Cases section, Maintenance folder and then the document Create and Update Maintenance Programs.

The updates to the Maintenance Program REST API and file-based data import support the user interface of the Manage Preventative Maintenance For Assets Across Organizations feature that's also available in this update.

Steps to Enable

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

You do not need to do anything to enable this feature.

Tips And Considerations

The Allow Global Assets is an optional attribute that's used during the creation of a new program. It can only be updated until the first work order is created for the program.

Access Requirements

No new roles or privileges are required for the new capabilities introduced in this service.

Manage Maintenance Forecast for an Asset Using a REST Service

Maintenance programs define and generate a preventive maintenance forecast for one or more affected assets in a maintenance-enabled organization. The forecast is then used as the basis for creating preventative maintenance work orders, thus reducing the workload for maintenance planners and allowing them to focus on maintenance program auditing, optimization, and exception-based events.

Customers with assets, such as vehicles that travel to different locations and across operating and maintenance organizations, requested the ability to forecast asset maintenance programs across all organizations and decide when and where a specific asset will be maintained based on its expected location as of the maintenance due date. For assets that are only maintained in their same operating organization, customers requested flexibility on adjusting the date when the asset will be maintained.

Previously, using the GET action of the Maintenance Forecasts REST resource, you were able to retrieve forecasted due date details. In this update, you can now perform the following actions using the REST API:

  • Define a requested due date that's the same or different than the forecasted due date. The due date must be after the last due date and before the next due date in the forecast for an asset.
  • Define a requested work order location that's the same or different than the forecasted location. This is only available if the due date was created from a program that's enabled for assets across organizations. The requested location must also be enabled for maintenance and have matching work definitions defined. Additionally, to create work orders for assets across organizations you must either define organizational relationships between maintenance organizations or enable a new parameter that wouldn't require relationships.
  • Skip a due date in the past, present, or future where there isn't an active work order. Skipping a due date will suppress the creation of a work order for the due date by the scheduled process.
  • Unskip a due date in the past, present, or future. Unskipping a due date enables the creation of a work order for the due date manually or by the scheduled process. If the due date is in the past, you can manually create a work order.
  • Use a special action to manually create a work order for a due date in the past, present, or future. This can be for any due date, regardless if it's set to automatically or manually create a work order. This action launches a concurrent process request to create the work order.
  • Use a special action to cancel a work order for a due date in the past, present, or future. You can cancel an existing work order, and then manually create a new work order on a different date and location. A work order can only be canceled if there haven't been any transactions recorded. Examples are operation completion, material issues, and resource reporting.

In this update, the REST API is also used by the Manage Forecasts page.

Examples of REST API payloads using PATCH:

fscmRestApi/resources/latest/maintenanceForecasts

  • Define a requested due date and location that is the same or different than the forecasted due date:

{"RequestedWoStartDate": "2023-08-10",

"RequestedWoOrganizationCode": "Organization A"

}

  • Skip or Unskip a due date

{    "SkipDueDateFlag": true or false}

Examples of REST API payloads using POST and a special action:

fscmRestApi/resources/latest/maintenanceForecasts

  • Create a work order for a due date based on the unique forecast id:

{"name": "manageForecastWorkOrders","parameters": [    {    "forecastId": 123456789    },    {    "workOrderActionCode": "ORA_CREATE"    }]}

  • Cancel a work order for a due date based on the unique forecast id:

{"name": "manageForecastWorkOrders","parameters": [    {    "forecastId":123456789    },    {    "workOrderActionCode": "ORA_CANCEL"    }]}

You can effectively manage the preventative maintenance on assets that operate both within and across organizations over time using the REST API and by using the new actions on the Manage Forecast page.

Steps to Enable

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

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

Tips And Considerations

If you want to define a requested start date or location, you must enable your maintenance programs to allow assets across organizations. Otherwise, you wouldn't be able to define a requested work order location for a due date.

Defining a requested start date and location will freeze the forecasted due date, and all previous due dates in history that don't have work orders. Generating the forecast for the program will only update and refresh due dates from the last frozen date in history. Therefore, care is taken when defining a requested start date or location for due dates into the future.

To create work orders for assets across organizations you must either define organizational relationships between maintenance organizations or enable a new parameter that wouldn't require relationships. For additional information on managing work orders across organizations, refer to Set Up Maintenance Organization Relationships section in the Implementing Manufacturing and Supply Chain Materials Management guide.

If you want to fully control the creation of work orders for an asset due date, then you must define the work orders creation option as manual in the work requirement. Else, you should leave the option set to automatic and use the scheduled process to generate work orders for due dates.

Key Resources

Access Requirements

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

  • Get Maintenance Forecasts by Service (MNT_GET_MAINTENANCE_FORECASTS_BY_SERVICE)
  • Manage Maintenance Forecasts by Service (MNT_MANAGE_MAINTENANCE_FORECASTS_BY_SERVICE)

These privileges are new in this update.

Manage Preventative Maintenance For Assets Across Organizations

Maintenance programs are used to define and generate a periodic preventative maintenance forecast for one or more affected assets in a maintenance-enabled organization. In this update, you can now optionally manage maintenance programs centrally in any organization that would enable assets across operating different organizations to be included in the forecast. When assets move between organizations either temporarily or permanently, you can now determine when and where an asset will be maintained.

This update includes the following additional changes besides the Allow Global Assets Flag that allows you to better manage your preventive maintenance plans.

  • The Maintenance Program (header) has the following new attributes: Forecast Window in Days, Workorder Window in Days, Work Order Start Time, Work Order Timezone, Program Reference, Program Type Code, and Program SubType Code.

  • The Work Requirements has the following new attributes: Requirement Reference, Forecast Window in Days, Workorder Window in Days, Create Work Order Option Code, Work Order Status, Work Order Firm Flag, and Work Order Priority.

  • The Affected Assets section has the following new option: Create Work Order Option.

Maintenance Program

Maintenance Program

Additionally, complementary enhancements have been made to the manage maintenance forecasts across organizations. You can now use a new Manage Forecasts UI to search and manage maintenance forecast for your assets. For a forecasted due date, you can optionally update the maintenance organization where work would be executed, and manually create a new work order or cancel an existing work order.

You can now centralize the definition of maintenance programs to a common maintenance planning organization. This capability streamlines your master data management and eliminates the need replicate maintenance programs across multiple organizations. With assets being maintained using these global programs, the maintenance history is preserved as the asset is moved across organizations.

Your work management procedures are also improved with the ability to vary the forecast and work order horizons at the program or work requirement level, predefining the work priority and the status in which the forecasted work order is created.

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

Tips And Considerations

  • The Allow assets from other organizations check box is an optional attribute during the creation of a new program.  It can be set if assets are centrally managed, or if assets operate across other organizations and require maintenance. The indicator can only be updated until the first work order is created for the program.
  • To create work orders for assets across organizations you must either define organizational relationships between maintenance organizations or enable a new parameter that wouldn't require relationships.  For additional information on managing work orders across organizations, refer Set Up Maintenance Organization Relationships in the Implementing Manufacturing and Supply Chain Materials Management guide.

Key Resources

Access Requirements

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

  • Manage Maintenance Programs (MNT_MANAGE_MAINTENANCE_PROGRAMS_PRIV)

This privilege was available prior to this update.

Manage Supplier Warranty Claims and Entitlements

Warranty claims are used to request the reimbursement of expenses incurred during the repair of an asset that's covered by a provider under a supplier warranty. A maintenance work order will be indicated as a warranty-eligible repair if the contextual asset, or its related assets in its physical hierarchy, has at least one active warranty contract. After operation completion, warranty claims can be created for the provider, by the scheduled process entitled Generate Supplier Warranty Entitlements, if reimbursable expense transactions are found. In this update, you can also use the new Manage Claims page to create, edit, view, and submit warranty claims and entitlements for expenses incurred during the repair of assets covered under supplier warranty.

Use the Manage Claims page to review and edit automatically created warranty claims for a work order. You can also manually create claims using the Manage Claims page. For example, you can create a manual claim to split existing work order reimbursement entitlements over more than one claim, perhaps for different providers, if required. Using the Manage Claims UI, entitlements can also be excluded or included from a warranty claim.

The Manage Claims page (Figure 1) allows you to quickly search for claims using parameters such as a claim number, warranty provider, work order number or status. You can perform quick edits to the claim by updating the claim status, submit by date or the assignee without navigating into the claim (Figure 2).

Claims UI offers a guided process navigation to review and edit the claim in a sequence of steps as shown in Figure 3.

Figure 1. Warranty Claims Page

Figure 1: Warranty Claims Page

Figure 2: Quick Edit Warranty Claims

Figure 2: Quick Edit Warranty Claims

Figure 3: Guided Process Navigation

Figure 3: Guided Process Navigation

Supplier warranty lets you track warranty extended from a supplier over the life of an asset. Warranty can then be considered during work order execution for an asset, letting you to make critical repair decisions that may result in a warranty claim for the reimbursement of expenses or replacement of a component. By automating the claims creation and reviewing them with the Warranty Claims page, you can file your claims in a timely fashion and track recoveries.

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

Key Resources

Access Requirements

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

  • Manage Supplier Warranty Claims (MNT_MANAGE_SUPPLIER_WARRANTY_CLAIMS_PRIV)
  • View Supplier Warranty Claims (MNT_VIEW_SUPPLIER_WARRANTY_CLAIMS_PRIV)
  • Use REST Service - Workers List of Values(PER_REST_SERVICE_ACCESS_WORKERS_LOV_PRIV)

These privileges are new in this update.

Manage Maintenance Forecast Across Organizations

Maintenance programs define and generate a preventive maintenance forecast for one or more affected assets in a maintenance-enabled organization. The forecast is then used as the basis for creating preventative maintenance work orders, thus reducing the workload for maintenance planners and allowing them to focus on maintenance program auditing, optimization, and exception-based events.

Customers with assets, such as vehicles that travel to different locations and across operating and maintenance organizations, require the ability to forecast asset maintenance programs across all organizations and decide when and where a specific asset will be maintained based on its expected location as of the maintenance due date. For assets that are only maintained in their same operating organization, customers may still want the flexibility to adjust the date when the asset will be maintained.

With this update, you can perform the following actions using the new Manage Forecast page.

  • View details about the due date, including the source maintenance program, work requirement and forecast method.
  • Provide a requested due date that's different than the forecasted due date. The due date must be after the last due date and before the next due date in the forecast for an asset.
  • Provide a requested work order location that's different than the forecasted location. This is only available if the forecast line was created from a program that's enabled for assets across organizations. The requested location must also be enabled for maintenance and have matching work definitions defined. Additionally, to create work orders for assets across organizations you must either define organizational relationships between maintenance organizations or enable a new parameter that will not require relationships.
  • Skip a due date in the past, present or future where there isn't an active work order. Skipping a due date will suppress the creation of a work order for the due date by the scheduled process.
  • Unskip a due date in the past, present or future. Unskipping a due date will enable the creation of a work order for the due date manually or by the scheduled process. If the due date is in the past, you can manually create a work order.
  • Create a work order for a due date in the past, present or future. This can be for any due date, regardless if it's set to automatically or manually create a work order. This action launches a concurrent process request to create the work order.
  • Cancel a work order for a due date in the past, present or future. You can cancel an existing work order, then manually create a new work order on a the same or different date or location. A work order can only be canceled if there haven't been any transactions record. Examples are operation completion, material issue, or resource reporting.

Manage Maintenance Forecasts Page

Manage Maintenance Forecasts Page

You can now effectively manage the preventative maintenance on assets that operate both within and across organizations over time using the Manage Forecast page. With this feature, you can plan centrally while executing maintenance anywhere.

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

Tips And Considerations

  • If you want to define a requested start date or location, you must enable your maintenance programs to allow assets across organizations. Else, you wouldn't be able to define a requested work order location for a due date.
  • Defining a requested start date or location will freeze the forecasted due date, and all previous due dates in history that don't have work orders. Generating the forecast for the program will only update and refresh due dates from the last frozen date in history. Therefore, care should be taken when defining a requested start date and location for due dates into the future.
  • To create work orders for assets across organizations you must either define organizational relationships between maintenance organizations or enable a new parameter that wouldn't require relationships. For additional information on managing work orders across organizations, refer the Set Up Maintenance Organization Relationships section in the Implementing Manufacturing and Supply Chain Materials Management guide.
  • If you want to fully control the creation of work orders for an asset due date, then you must define the work orders creation option as manual in the work requirement. Else, you should leave the option set to automatic and use the scheduled process to generate work orders for due dates.

Key Resources

Access Requirements

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

  • Manage Maintenance Forecasts (MNT_MANAGE_MAINTENANCE_FORECASTS_PRIV)
  • View Maintenance Forecasts (MNT_VIEW_MAINTENANCE_FORECASTS_PRIV)

These privileges are new in this update.

Service Logistics

Consider the Supplier Warranty When Routing Returns

Return routing rules now allow default destinations to be defined for assets associated with supplier warranty, so you can route the return accordingly.

First, create a supplier warranty for an asset item using Oracle Fusion Cloud Maintenance. Next, add a return routing rule for the asset item using the new Return Type field value of Supplier Warranty.

Manage Return Routing Rule

Manage Return Routing Rule

When using the Return Parts UI to return this asset item, the destination organization defaults from the asset item’s return routing rule. The defaulted destination organization is used in the following transactions:

  • Service Request Parts Return
  • Field Parts Inventory Return 

NOTE: The Supplier Warranty for Asset Items are created in the Oracle Fusion Cloud Maintenance .

Returned parts that are covered under a supplier warranty can now be properly routed to preferred recovery locations.

Steps to Enable

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

Calculate Estimated Sales Tax

You can now view estimated sales taxes when creating part requirements, field service charges, and depot repair charges.  These estimated taxes and the tax determinants used to calculate them are passed to the sales order created when the charges are posted.  The actual taxes are calculated when the invoice is generated in accounts receivable.

Part Charges with Sales Taxes

Part Charges with Sales Taxes

Field Service Charges with Sales Taxes

Field Service Charges with Sales Taxes

Field Service Charges with Sales Taxes - Redwood

Field Service Charges with Sales Taxes - Redwood

Depot Repair Charges with Sales Taxes

Depot Repair Charges with Sales Taxes

Depot Repair Charges with Sales Taxes - Redwood

Depot Repair Charges with Sales Taxes - Redwood

You can now give your customers a more complete estimate of the amount they can expect to pay for parts and services.

Steps to Enable

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

Update the Create Expense UI Fields to Quantity and Unit of Measure

In the Manage Charges and Estimates UI Expenses tab, the former Expense and Currency field names have been changed to Quantity and UOM (unit of measure).  This makes debriefing expenses that are not monetary based more intuitive.  For example, if you want to debrief a tool or equipment rental expense, you debrief the time the tool or equipment was rented instead of the money spent.

Expense Debrief with Currency UOM

Expense Debrief with Currency UOM

These updated field names more logically handle time based as well as monetary based expenses.

Steps to Enable

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

Perform Mass Updates on Part Requirement Lines

You can now update the following header fields in the Create Part Requirements UI and then copy this information to all part requirement lines not yet ordered.

  • Ship-to Customer
  • Ship-to Address
  • Need By
  • Bill-to Customer
  • Bill-to Account
  • Bill-to Address
  • Destination Organization
  • Destination Subinventory

Click the new Update Requirements button to update the part requirement lines with the latest header values, automatically recalculate the charges, and refresh the Requirement Lines table. The source stocking location for each part is not updated.

In the screen shots below, you can see most of  the header fields are now editable and the update requirements button has been added to the requirements line region.

Create Part Requirements UI - Service Request Document Type

Create Part Requirements UI - Service Request Document Type

Create Part Requirements UI - Work Order Document Type

Create Part Requirements UI - Work Order Document Type

Update Requirements Confirmation Message

Update Requirements Confirmation Message

You can now quickly update multiple part requirement lines saving time and reducing mistakes.

Steps to Enable

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

Use Smart Search to Search For and View Part Requirements

The new Part Requirements search UI uses an elastic search framework, resulting in fast and scalable searches. Use it to search for part requirement lines based on many attribute filters at once, such as Need by, Item Number, Document Type, and so on.

The UI automatically launches with the default filter of Need by set to This Week. You can refine the search by adding, updating, or removing attribute filters as required. Functionalities such as auto complete and fuzzy logic make it easier to search for part requirement lines matching your criteria. From the search results, create transfer orders or reservations for parts by selecting certain part requirement lines, then clicking the Order button.

The UI offers separate views for Field Service Administrators and Field Service Technicians. Administrators can see all part requirements, but technicians can view only part requirements assigned to them.

Access the Part Requirements search UI from the Service Logistics landing page by selecting Part Requirements.

Part Requirements

Part Requirements

Using the new Part Requirements search UI, you can search for part requirement lines that require your attention and quickly place orders. For example, a Field Service Administrator can search for the part requirements needed for this week or next week and place orders for them so that the technicians have the parts and can complete the tasks at hand.

Steps to Enable

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

Access Requirements

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

  • Access Parts Requirements Search for Administrator (RCL_ADMIN_PARTS_REQUIREMENTS_SEARCH_PRIV)
  • Access Parts Requirements Search for Technician (RCL_FSTECH_PARTS_REQUIREMENTS_SEARCH_PRIV)

These privileges are new in this update.