Update 23A

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Module	Feature	Notes
28 FEB 2023	Maintenance	Manage Asset Supplier Warranty	Updated document. Revised feature description.
02 DEC 2022			Created initial document.

Overview

HAVE AN IDEA?

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

GIVE US FEEDBACK

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

DISCLAIMER

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

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

Pre-Update and Post-Update Tasks

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

Optional Uptake of New Features (Opt In)

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

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

Here’s how you opt in to new features:

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

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

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

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

Opt In Expiration

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

Feature Summary

Maintenance

Maintenance

Map Order Management Flexfields to Installed Base Asset Attributes

Sales orders are used to sell items to customers. During the order fulfillment process, installed base assets are created if there is a specific step defined as part of the Sales Orchestration process. As part of asset creation, basic sales order details are captured in the asset record, such sales order number, customer purchase date, registration date, in-service date, bill-to customer, and bill-to account number. You can now capture additional details in an asset record based on extended attributes in a sales order using service mapping functionality.

Mapping Overview

Service mapping functionality allows you to define the source and destination for the additional sales order data to be captured in an asset during creation. From the source sales order, the data can be from extensible flexfields (EFFs) at the header or line levels. For the destination asset, the data will be captured in either descriptive flexfields (DFFs) or extensible attributes managed using Application Composer.

During sales order fulfillment, assets are created when the orchestration picks the asset creation task. After creation, running the scheduled process Process Pending and In-Error Genealogy and Installed Base Transactions will consider service mappings and enrich the asset record. After an asset is created, the mapped data can be viewed on the Asset Overview page, and with the Installed Base Asset REST API.

During asset creation if any of the service mapping data fails its destination field validations, it will be identified in the process error logs. To correct the data mapping issues, you can use an in-session ADFdi spreadsheet named Manage Sales Order to Asset Data Collection in Spreadsheet, that's available from the task menu on the Maintenance Management landing page. Using this spreadsheet, you can correct any source data issues, then reprocess the mapping. If successful, you will receive a confirmation message and can verify the data in the Asset Overview page.

Defining Service Mapping

You must first define service mapping in the context of a sandbox. In a sandbox, you will start by using the Manage Service Mappings task flow, available from the task menu on the Maintenance Management work area landing page. This task flow will navigate you to the mapping page, where you will be presented with a seeded mapping entitled Asset Integration.

For this mapping, you will see three tabs:

• Entities – Defines the source and destination data. You'll need to create new entities for the sales order header and lines, to include the source EFFs. For the destination asset, you can use the seeded entity named Asset Order Map.

• Sources – Defines the data source for each attribute defined in the Entities tab by referencing the specific source view object and attribute.

• Services – Defines the unique data characteristics for each mapped attribute. For source attributes, set them to be READ only, where destination attributes must be set to both READ and WRITE. This allows for data correction in case of any validation errors during asset creation.

Defining Algorithms 

After you have defined the service mapping, you must define the algorithms that are used to configure the source data before it's captured in the destination asset. Use the Manage Algorithms task flow available from the task menu on the Maintenance Management work area landing page. This task flow navigates you to the Algorithms page, where you will be presented with a seeded mapping named Asset Management and Order Management Integration. Edit the algorithm to define groovy scripts to transform each data attribute during mapping.

Service mapping allows you to enrich an asset with additional sales order details that are relevant to your business.

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 23C

Tips And Considerations

When you initially define your algorithm, this version will be used by the service mapping. You can create new versions of the algorithm to define different data configurations.  You must then promote the algorithm so it transitions from a status of In Progress to Promoted. For the latest version to be considered, you must update the profile option QP_ALGO_ENABLE_FACTORY_MODE_RUN. By default, this profile is set to Yes, which considers the seeded algorithm. To use the latest version, set this profile option to No.

Role And Privileges

• Users who are assigned any of these predefined job roles can access this feature:
  • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)

• 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)
  • Manage Maintenance Work Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)
  • Manage Maintenance Work Order Operations (MNT_MANAGE_MAINTENANCE_WORK_ORDER_OPERATIONS_PRIV)

Use the Enhanced OTBI Subject Areas for Maintenance Management and Installed Base

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
Maintenance Management - Forecast Real Time	New folder added to forecast subject area to support your list of affected assets: Maintenance Program Work Requirement Affected Item or Asset Asset Number Description Serial Number Allow Work Order Work Order Created Historical Last Completed Historical Last Interval Forecast Start Forecast Last Completed Forecast Last Interval Forecast Next Due Forecast Next Interval Status
Maintenance Management - Work Requirement Real Time	New folder added to Work Requirement subject area to support your list of affected assets: Maintenance Program Work Requirement Affected Item or Asset Asset Number Description Serial Number Allow Work Order Work Order Created Historical Last Completed Historical Last Interval Forecast Start Forecast Last Completed Forecast Last Interval Forecast Next Due Forecast Next Interval Status
Maintenance Management - Resource Usage Real Time	New folder added to Resource Usage subject area to support your Equipment and Job Profiles. Equipment Profile: Equipment Profile Code Equipment Profile Description Equipment Profile Id Equipment Profile Name Equipment Qualification Requirement Code Equipment Qualification Requirement Description Equipment Qualification Requirement Name Inactive On Job Profile: Content Item Content Type Date From Date To Job Profile Code Job Profile Description Job Profile Id Job Profile Name Mandatory Profile Type Rating Level 1 Rating Model 1

OTBI empowers you to 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

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

Role And Privileges

• Users who are assigned any of these predefined job roles can access this feature:
  • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)

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

Reactivate an Inactive Work Definition

Occasionally, maintenance managers deactivate a work definition to obsolete or temporarily hold its usage but also need a way to revert this action. With this update, you can reactivate a maintenance work definition to make it available again for use in work order creation. Reactivation applies to all versions of the work definition by restoring the active status and clearing the inactive on date in the work definition header. You can reactivate a specific work definition, using file-based data import (FBDI) or a REST service.

Work definition reactivation provides greater flexibility in controlling its usage in maintenance without having to introduce a new work definition and name.

Steps to Enable

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

Tips And Considerations

• You can reactivate maintenance work definition using REST and file-based data import (FBDI), all versions of a deactivated work definition, and not a specific version. The work definition status is either active or inactive depending on reactivation or deactivation, respectively.

• You can't edit the inactive on date for a work definition. It is automatically cleared or defaulted depending on reactivation or deactivation, respectively.

• You can’t reactivate maintenance work definition in user interface. It is supported only in FBDI and REST.

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 this predefined job role can access this feature:
  • Maintenance Manager - ORA_MNT_MAINTENANCE_MANAGER_JOB

• Users who are assigned a configured job role that contains this privilege can access this feature:
  • Manage Maintenance Work Definitions - MNT_MANAGE_MAINTENANCE_WORK_DEFINITIONS_PRIV

Search for Work Order Operations by Resource Instance and Work Order Description in the Maintenance Dispatch List

In Work Execution, maintenance technicians use the Review Maintenance Dispatch List to review work order operations and report transactions, such as operation completion, material issue or, return, and resource consumption or reversal. In order to access their assigned work at the Review Maintenance Dispatch List, maintenance technicians manually search for their assigned work using search attributes such as asset, work order, status, start date, work area, work center, resource, and completion date.

Maintenance technicians also want to find their assigned work by Resource Instance, and Work Order Description which prior to this update were not available as search options. Therefore, the Maintenance Dispatch List User Interface has been enhanced to make it possible to search by these two new attributes:

• Resource Instance
• Work Order Description

The maintenance technician can add these two additional filter attributes to the search via the “Add” tab at the bottom of the search page. These two new search attributes are designed with a free-text design pattern which allows the user to perform partial keyword searches.

In addition to searching by Work Description, you can also see the Work Description as a column in the search results table view. Resource Instance is not available to be displayed in the search results table view.

Searching in the Maintenance Dispatch List by Resource Instance and Work Order Description makes it easier for maintenance technicians to find their work.

Steps to Enable

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

Tips And Considerations

Since the search results table does not display the Resource Instance name, it is recommended when using the Resource Instance free-text field to search, that you use both First and Last name. This is to help ensure the search results only include your assigned work. 

To improve your search effectiveness, please understand that these new search fields are case-sensitive.

Role And Privileges

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

• Privileges:
  • 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)

Failure Analysis View Objects for Oracle Business Intelligent Cloud Connector

The Business Intelligence Cloud (BICC) is an extraction tool that allows you to extract data out of Fusion Cloud application. Internal data warehouse solutions use it and you can integrate it with third-party systems for reporting purposes.

The following failure analysis view objects are delivered in this update as part of an Oracle Fusion initiative to provide a data management extraction tool:

• Failure Set Association
• Failure Set
• Failure Set Translation
• Condition Evens Code Translation
• Failure Events
• Failure Instance
• Failure Symptoms
• Failure Root Causes
• Failure Root Chain

The BICC provides the ability to perform data extraction for data warehousing and external integration. This is the recommended tool for bulk extractions

• Full Extraction (initial or on-demand)Incremental Extraction.
• Selective Object Extraction.
• Scheduling for Incremental Data Extraction.
• Leverages Standard Security Methods of Fusion Cloud Applications.
• Improve BICC to support FAW and resolve existing BICC customer issues.

Steps to Enable

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

Tips And Considerations

Theses are the steps to extract data from Oracle Business Intelligence Cloud Connector Console.

• Create a Job from the Manage Job drawer.
• Selects BI VOs (Data Store) to extract.
• Schedule or execute an Extract.
• Monitor Extract execution.
• Files are transferred to UCM server.
• Files are transferred over network by UCM client at customer site.

Role And Privileges

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

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

Manage Asset Supplier Warranty

Oracle Fusion Cloud Maintenance provides an integrated Asset Supplier Warranty solution for Enterprise Assets, allowing you to track warranty for an asset throughout its service lifetime, from purchase until disposal. Warranty can then be considered during work order execution for an asset, letting you to make timely repair decisions that may result in a warranty claim for the reimbursement of expenses or replacement of a component. Warranty is expected to naturally expire over time for an asset.

The Supplier Warranty Solution includes the following flows:

• Managing Warranty Coverages
• Managing Warranty Contracts
• Item Purchase, Receipt and Asset Creation
• Managing Maintenance Work Order Execution

Managing Warranty Coverages

Supplier Warranty begins by defining warranty coverages. They are reusable templates that you can use to translate and model the warranty terms extended by a warranty provider from the purchase of an asset or the continued support of an existing asset through an extended warranty period. Use the Manage Coverages page to search for existing coverages, view coverage details or to create a new coverage. The page is accessible from the Maintenance Management Landing Page task menu, under the Maintenance Setup section. This page consists of a search bar, results region, and Create Coverage button. Upon rendering, the page automatically presents a list of search results sorted alphabetically. The search bar allows you to further refine the search results for existing coverages by Name, Code, Description, Type, or Warranty Provider. Clicking the hyperlinked name of an existing coverage navigates you to the Warranty Coverage guided process, where you can further edit and save any changes to the coverage.

Manage Coverage Search

Clicking Create navigates you to the Warranty Coverage guided process, whereby clicking Start, you can define and save a new coverage and its details. Clicking Cancel returns you to the Manage Coverage page.

Create New Coverage

A coverage includes what's extended under the warranty terms, who's responsible for the repair or replacement of an asset or its associated components, and how long the warranty period lasts. The provider is the main supplier reference on the coverage and its related warranty contracts. The provider is also the supplier to whom you will typically submit a Warranty Claim for the reimbursement of in-house repair or component replacement expenses.

Coverage Header

After the coverage essentials are defined and saved, you can optionally navigate to the other steps to further define the coverage:

• Terms of service is an optional step used to define additional details about the terms and conditions of the warranty, as well as reimbursement details. The free form text fields are used to capture different aspects of the warranty from the provider. You can also use the slider options to highlight key coverage details, which are viewable and will be referenced in downstream processes.

• Covered items is an optional step used to define items and suppliers from whom you would purchase an item that will become an enterprise asset. This setup is only recommended if you wish to automatically create warranty contracts for newly purchased and received items. Contracts are instantiated from matching coverages by item and supplier by running a scheduled process after an item is received and the asset is created.

• Utilization meters is an optional step used to define Meter Intervals that will be used to track the dynamic expiration of a warranty contract for an asset over time. As an asset gains utilization through meter reading reporting, the Calculated Expiration Date and Status of a Warranty Contract will be updated by the scheduled process. When a meter interval is reached, the contract will move from a status of Ready to Expired.

• Repair transaction codes is an optional step used to define repair transaction codes that reference the asset system, component, and item that are covered by the warranty. These codes must be used if you'd like to reference them in downstream processes.

After the coverage and its additional details are defined, you can set it to a status of Ready, allowing the coverage to be used to instantiate a unique warranty contract for an asset.

Managing Warranty Contracts

Use the Manage Contracts page to search for existing contracts, view contract details or to create a new contract. The page is accessible from the Maintenance Management Landing Page task menu, under the Asset and Work Definition section. The page consists of a search bar, results region and Create Contract button. Upon rendering, the page automatically presents a list of search results that are sorted alphabetically. The search bar allows you to further refine the search results for existing contracts by Contract Number, Coverage Name, Asset Number, or Warranty Provider. Clicking the hyperlinked name of an existing contract navigates you to the Warranty Contract guided process, where you can further view, edit, and save any changes to the coverage.

Manage Contract Search

Clicking Create renders a drawer to the right, where you can select an asset, coverage, and other fields that's used to create a new contract. If you decide not to create the contract, then click the Cancel button to return to the search results. After you have defined the fields for a new contract, you must click the Create action in the drawer. This creates a contract and you will navigate to the Warranty Contract guided process to review and further edit the contract, as covered below.

Create a New Contract

To review or edit an existing contract, you can click an existing contract hyperlink in the results rows of the Manage Contract page or you can create a new contract. You will navigate to the Warranty Contract guided process overview page, where you can click Start to begin the review of the contract or click Cancel to return to the Manage page. Clicking Start navigates you to step 1, where you can review the main details of the contract. This step is used to review and edit header details for the contract. A contract must typically be created with a status of Ready, but could be set to a status of Draft if additional review is required.

View and Edit a Contract

You can then intuitively navigate through the other 4 steps to define and review additional details. After you've finished, you can click Complete on step 5, or you can click Cancel to return to the Manage page.

Item Purchase, Receipt and Asset Creation

Purchase orders are used to buy an item from a supplier in an organization. Upon receipt, if the item is set up as an asset tracked item, then an asset will be created. During creation, the asset may also have one or meters instantiated. After created, the asset can be validated by a scheduled process to determine if one or more warranty contracts must be created as well. This process will look for warranty coverages where the purchased item, and optionally a supplier have been defined. If there are matching items found, then new contracts will be created for each coverage with the indicated contract status. You can then review the newly created contracts and edit if necessary.

Managing Maintenance Work Order Execution

Supplier warranty contracts can be considered in the maintenance work order execution flows across several user interfaces. This information can be used to make warranty decisions on the repair of the asset or its components.

• The Manage Maintenance Work Orders search results display a column called Warranty, with a checkbox icon. If an icon is displayed for a work order, then either the work order asset or an asset in its physical hierarchy has an active warranty contract. Clicking the icon navigates you to the Edit Work Order page, rendering the Supplier Warranty tab and results.

• When editing a maintenance work order, a Supplier Warranty tab will be displayed. The tab includes the count of number of active warranty contracts, and the list of contracts by asset that are active. The list includes contracts for the work order asset, and any related assets in its physical hierarchy.

Work Order Supplier Warranty Tab

List of Warranty Contracts

• The Manage Maintenance Dispatch List search results include a column called Warranty, with a checkbox icon.

• During work order operation completion, you may need to report resource transactions. Resource transaction rows will include a Repair Transaction Code attribute that can be optionally defined to reflect the asset’s system, component, and item that were repaired. The field will be used for reporting in this uptake. In future, uptakes will be used by downstream processes for warranty entitlement, and claims processes.

• During work order operation completion, you may need to report material transactions. If you are using the report page that includes a hierarchy viewer, then each transaction row will include a Repair Transaction Code attribute that can be optionally defined to reflect the asset’s system, component, and item that were repaired. The field will be used for reporting in this uptake. In future, uptakes will be used by downstream processes for warranty entitlement and claims processes.

Supplier warranty lets you to 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 timely repair decisions that may result in a warranty claim for the reimbursement of expenses or replacement of a component.

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 23C

Coverage Type is an optional attribute in the coverage header that can be used to further describe or group similar coverages. This type may be helpful to manage coverages across users and to further refine your search results. Examples may include types such as New Purchase, Extended Warranty, and OEM Warranty.  An administrator can define the Type codes by using the user-defined lookup ORA_CSE_WTY_COVERAGES_TYPE.

When creating new warranty contracts in the user interface, you must select an asset using a LOV that uses the asset smart search. Therefore, the asset smart search must be enabled for the Supply Chain Execution offering and the latest asset data ingested. For more information about the asset smart search, refer to the following:

• How You Use Smart Search to Search For and View Assets in the New Assets UI
• How You Manage Assets in the User Interface

Tips And Considerations

Before you create the first coverage, consider the following dependencies across other objects and setups:

• Items that will be used to create enterprise assets must be set up in the Product Information Management (PIM) offering. The items must be set up as full life cycle, maintainable, serial controlled, and purchasable from suppliers. You can optionally reference them in a coverage, allowing for the automatic instantiation of warranty during the purchase of an item from a supplier.

• If you define coverages, you must have Inventory Organization and Item Class access granted to define items and suppliers in step 3 of a coverage. You can find additional details in the Maintenance chapter within the Implementing Manufacturing and Supply Chain Materials Management guide.

• Assets that are based on these types of items would be eligible for supplier warranty. You can create the assets from purchase order receipt or when you create them manually.

• Suppliers must be set up in Oracle Supplier Management. These will be the suppliers from whom an item is purchased from and who will extend warranty terms as the warranty provider.

• Manufacturer is an optional attribute in the coverage header that can be used to track an OEM reference for a supplier warranty, typically if the warranty provider isn't the OEM.  If used, they must be set up as a party that has a usage as a manufacturer.

• Utilization meters may be optionally used to define and track the coverage terms using a warranty contract. Examples may include an Odometer or Hour meter. You can define the meter templates and then instantiate them against each applicable asset that uses the meter prior to creation of a warranty contract using the coverage.  You can find the additional details in the following Purchase Receipt section.

• Repair Transaction Codes may be optionally used to define the unique references for an asset’s system, component, and item that are covered by warranty. These codes can then be referenced during work order execution for resource and material transactions. These codes are set up using the Manage Condition Event Codes task flow.  When defining new codes, you must select a Transaction code type only.

• After contracts are being created, you must run the Process Supplier Warranty Contracts - Additions and Changes scheduled process on a regular basis. This process will review every contract, update its calculated expired date (if meter intervals are defined), update the contract status (if Expired), create new warranty contracts for purchased items and assets, and enrich assets with supplier warranty details to allow the viewing of warranty in the execution process.

Key Resources

• Watch the Asset Supplier Warranty Demo

Role And Privileges

• Users who are assigned any of these predefined job roles can access this feature:
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)
  • Maintenance Technician (ORA_MNT_MAINTENANCE_TECHNICIAN_JOB)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Manage Supplier Warranty Duty (ORA_MNT_MANAGE_SUPPLIER_WARRANTY_DUTY_CRM)
  • View Supplier Warranty Duty (ORA_MNT_VIEW_SUPPLIER_WARRANTY_DUTY)

Qualify Equipment When Assigning Work or Reporting Resource Usage

Equipment being used in maintenance work order operations may need to be qualified for their intended usage or regulatory compliance. For example, an inspection equipment needs to be calibrated for it to be used in an inspection operation. With this feature, you can verify that an equipment is qualified to perform a maintenance operation based on the qualification requirements defined in a qualification profile and restrict the same during assignment or charging against a maintenance work order.

For leveraging this feature, it's imperative to associate an equipment resource instance to an asset defined in Oracle Fusion Cloud Maintenance. This also means that the required qualifications are managed in the asset.

You can create a qualification requirement for calibration to check the calibration status. An equipment profile is automatically created based on the qualification requirement details. The qualification requirements and qualification profiles are generic entities that aren't associated to any organization. Further, an asset as an equipment is qualified for the calibration by adding the relevant qualification requirement to the same with appropriate date validity. Post valid date the qualification requirement for calibration must be added to asset again with new valid dates. This qualification detail is accessible from both the asset record and the resource instance record. You can view the asset qualifications for a history of qualifications with the last qualified date, qualified by, and the next qualification date in the new tab called Qualifications within the Edit Asset page.

Define Qualification Requirement

Automatically Created Qualification Profile

Asset Number Associated to a Resource Instance - Qualified for Calibration

By associating the qualification profile to a resource in a standard operation, a maintenance work definition operation, or directly to a maintenance work order operation, the qualification criteria for the resource instance and the same is used as basis for resource instance assignment or charging against the maintenance work order.

The equipment qualification check is enforced when assigning work to an equipment resource instance or reporting resource usage as follows:

• You can confirm the equipment qualification when assigning an equipment resource instance to a maintenance work order operation. If the equipment resource instance doesn't qualify during the assignment to a work order operation, you receive a warning message and can proceed or replace with another qualified equipment.

Maintenance manager is warned if unqualified equipment is assigned.

Equipment Profile Association to Operation Resource and Subsequent Validation During Resource Instance Assignment

• You can confirm the equipment qualification when reporting an operation or resource transaction using the equipment resource instance. During operation completion or resource charging, you can't proceed with an unqualified equipment and need to reassign to a qualified equipment.

Resource Transaction Requires a Qualified Equipment Resource Instance to be Specified that Meets the Qualifications Specified in the Equipment Profile

In addition, you can view the equipment profile and requirements for an equipment resource in which the resource instance is assigned to or transacted in a work order operation by adding this new column to your maintenance reports in OTBI. The new dimension for equipment profile is now available in the Maintenance - Resource Usage Real Time subject area.

Equipment Profile is Exposed in the Resource Usage Real Time Subject Area

File-based data import (FBDI) changes:

You can associate the equipment profile to a standard operation resource, work definition operation resource, and work order operation resource using file-based data import (FBDI). A new column called Equipment Profile Code has been added to the respective FBDI templates. You can't report operation completion if an operation resource has an associated equipment profile and has charge type as Automatic, because resources and resource instances can't be reported for operation transactions through FBDI. To report completion for such operations through FBDI, you can set the resource charge type to Manual and use the Work Order Resource Transaction Import.

REST API changes:

You can associate the equipment profile to a standard operation resource, work definition operation resource, and work order operation resource using a REST service. The REST payload accepts Equipment Profile Code and Profile ID values. You can't report operation completion if an operation resource has an associated equipment profile and has charge type as Automatic, because resources and resource instances can't be reported for operation transactions through REST. To report completion for such operations through REST, you can set the resource charge type to Manual and use the Work Order Resource Transaction REST service.

Integrated inline checks for equipment qualification reduces the likelihood of noncompliance, defects, or failures in maintenance operations.

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 23C

To use this feature, it is required to associate asset number to the equipment resource instance. You must first define qualification requirements belonging to a qualification profile in Oracle Fusion Cloud Maintenance. Then, you must define qualification records for the eligible asset numbers.

Tips And Considerations

• You can define the qualifications required for a maintenance operation using an equipment qualification profile for an asset in Oracle Fusion Cloud Maintenance. You must associate the resource instance to an asset number to perform the equipment qualification check for the resource instance.

• You can use an equipment qualification profile for any work order type for maintenance work orders. However, you can't enforce the qualification check for a supplier operation in outside processing work order.

• You can associate an equipment profile to a work definition operation resource to apply the same qualification requirement to all of its equipment resource instances during work order assignment and operation or resource transaction reporting. If an equipment is qualified to do more than one type of work, then you can create different equipment profiles that aligns with the different operations.

• You can create a new work definition version to track changes in the equipment profile that contains the qualification requirements associated with an operation.

• You can enforce the qualification check when reporting operation or resource transactions through the UI, REST, and FBDI.

• You can't leverage an external system for the equipment qualification check, because only the integrated check with a maintenance asset is supported.

• You can't use the quick complete process on the Review Dispatch List page when a work order has an equipment profile required for any of its operation resources.

• You can't override the work order operation assignment or operation and resource transaction reporting with an unqualified resource at this time. Qualifications are checked against the assigned equipment resource instance. To resolve an invalid qualification, you can either reassign to a qualified equipment or rectify the equipment qualification profile with the appropriate qualifications.

• In the user interface, a qualification profile can be associated to one qualification requirement. However, using a REST service it's possible to associate more than one qualification requirements to a qualification profile.

Key Resources

• Refer the Qualify Equipment When Assigning Work or Reporting Resource Usage feature under Oracle Fusion Cloud Manufacturing.
• Refer the Set up Asset Qualifications using REST API feature under Oracle Fusion Cloud Maintenance.

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 this predefined job role can access this feature:
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)

• Users who are assigned a configured job role that contains this privilege can access this feature:
  • Manage Qualification Requirements (MNT_MANAGE_QUALIFICATION_REQUIREMENTS_PRIV)
  • Manage Qualification Requirements by service (MNT_MANAGE_QUALIFICATION_REQUIREMENTS_BY_SERVICE_PRIV)
  • Manage Qualification Profiles by service (MNT_MANAGE_QUALIFICATION_PROFILES_BY_SERVICE_PRIV)
  • Manage Enterprise Assets (CSE_MANAGE_ENTERPRISE_ASSETS_PRIV)
  • View Asset Qualifications (MNT_VIEW_ASSET_QUALIFICATIONS_PRIV)
  • Manage Maintenance Standard Operations (MNT_MANAGE_MAINTENANCE_STANDARD_OPERATIONS_PRIV)
  • Manage Maintenance Work Definitions (MNT_MANAGE_MAINTENANCE_WORK_DEFINITIONS_PRIV)
  • Manage Maintenance Work Order Operations (MNT_MANAGE_MAINTENANCE_WORK_ORDER_OPERATIONS_PRIV)
  • Report Maintenance Operation Transactions (MNT_REPORT_MAINTENANCE_OPERATION_TRANSACTIONS_PRIV)
  • Report Maintenance Resource Transactions (MNT_REPORT_MAINTENANCE_RESOURCE_TRANSACTIONS_PRIV)

Integrate and Extend Maintenance Using REST Services

Set Up Asset Qualifications Using REST API

Qualifications are recorded for an asset. The details of the asset qualifications are qualification requirement, qualified date, next qualification due and these are required setups before recording the qualification.

You can set up the asset qualification details like creation of qualification requirements and qualification profiles using REST API. Also, the qualification itself can be recorded for an asset using a REST service.

Resource Names

• Qualification Requirements
• Qualification Profiles
• Asset Qualifications (this is a child resource of the Installed Base Assets resource)

Here's what you can do with this update:

Qualification Requirements

• Create a qualification requirement
• Update a qualification requirement
• Get the qualification requirement details

Qualification Profile

• Create a qualification profile
• Update a qualification profile
• Get the qualification profile details
• Create the association of one or more qualification requirements to a qualification profile
• Update the association of the qualification requirement and qualification profile
• Get the association details of the qualification requirement and qualification profile

Asset Qualifications

• Create a qualification for an asset
• Update the asset qualification
• Get the asset qualification details

The assetQualifications REST resource is a child to the existing installedBaseAssets resource.

Set up your asset qualifications easily using the respective REST APIs.

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.

Tips And Considerations

The asset qualification can be recorded using a REST service. The new REST service is a child resource to the exiting installedBaseAssets resource.

Using REST service, it's possible to associate more than one qualification requirements to a qualification profile. However, in the user interface, a qualification profile can be associated to one qualification requirement.

Key Resources

• Refer to the REST APIs for Oracle SCM Cloud documentation available on the Oracle Help Center.
• Refer to the release documentation of the Qualify Equipment When Assigning Work or Reporting Resource Usage feature.

Role And Privileges

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

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

• Users who are assigned configured job roles that contain one or more of these service privileges will be able to access this feature:
  • Manage Qualification Requirements by service (MNT_MANAGE_QUALIFICATION_REQUIREMENTS_BY_SERVICE_PRIV)
  • Manage Qualification Profiles by service (MNT_MANAGE_QUALIFICATION_PROFILES_BY_SERVICE_PRIV)
  • 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)

Manage Asset Supplier Warranty Using REST API

Oracle Fusion Cloud Maintenance provides an integrated asset supplier warranty solution for enterprise assets, allowing you to track warranty for an asset throughout its service lifetime, from purchase until disposal. Warranty can then be considered during work order execution for an asset, letting you to make timely repair decisions that may result in a warranty claim for the reimbursement of expenses or replacement of a component. Warranty is expected to naturally expire over time for an asset. In this uptake, there are several new REST APIs that support the introduction of this new capability:

• Asset Warranty Coverages REST API is used to define the coverage header, terms and conditions, and optionally a time based duration. You can leverage any of its child resources to define the applicable items and suppliers, utilization meters and intervals, or repair transaction codes that further describe the coverage.

• Asset Warranty Contracts REST API is used to create and update contracts for an asset based on a coverage. The contract header or meters child resource can be used to adjust the contract until its expiration.

For additional details about Supplier Warranty, reference the What's New for the main feature Manage Asset Supplier Warranty.

For additional details and use cases about the REST APIs, refer to the guide REST API for Oracle Fusion Cloud Supply Chain Management.

Using the new services during implementation, you can define coverages for your suppliers (warranty providers) that extend warranty from the purchase of an item or through an extended warranty term on an asset. After warranty contracts are created, you can use the services to retrieve warranty information for an asset.

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.

Tips And Considerations

The supplier warranty user interfaces for warranty coverages and contracts use the Redwood theme. Therefore, all interactions with these objects will be based on using their respective REST APIs. Your users must have the appropriate access to either view or manage supplier warranty.

Key Resources

• REST API for Oracle Fusion Cloud SCM on the Oracle Help Center.

Role And Privileges

• Users who are assigned any of these predefined job roles can access this feature:
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)
  • Maintenance Technician (ORA_MNT_MAINTENANCE_TECHNICIAN_JOB)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Manage Supplier Warranty Duty (ORA_MNT_MANAGE_SUPPLIER_WARRANTY_DUTY_CRM)
  • View Supplier Warranty Duty (ORA_MNT_VIEW_SUPPLIER_WARRANTY_DUTY)

Service Logistics

Create Reservations When Sourcing and Ordering Parts

You can now automatically create inventory reservations when sourcing parts needed for B2B and third-party work orders from site dedicated, unmanned, and field technician stocking locations. These reservations ensure that required parts are not reused for another purpose. Currently, you create inventory transfer orders when you source parts from manned parts stocking locations, but they are not created for the types of stocking locations where a field technician typically picks up the parts instead of the parts being shipped to the customer site or some other field location.

You now create parts inventory reservations when you click Order on the Manage Part Requirements UI, the Create Part Requirements UI, and the Edit Part Requirements UI. They are also created automatically when you create a B2B work order in the Create Work Order UI and when you add a part requirement to a B2B work order in the Edit Work Order UI Parts tab. These inventory reservations display on a new Reservations UI accessed from the Manage Field Parts Inventory UI.

You can delete part requirement inventory reservations using the following methods:

1. Manually by the user in the new Part Reservations Popup UI.
2. Manually by the user in the in the Create and Edit Part Requirements UIs and in the Edit Work Order UI's Parts Tab.
3. Automatically when the associated B2B Work Order is cancelled.
4. Automatically when a parts usage debrief line is created for the same work order, item and stocking location.
5. Automatically, when charges are posted for the first time and the PR Reservation was unused (a corresponding parts debrief transaction was not created).

The Transfer Part and Return Part UIs have been enhanced to prohibit users from transferring reserved parts. Also, the OIC Field Service Cloud Inventory Download now subtracts out reserved parts.

Manage Parts Inventory UI with Reservation

Reservations UI

Manage Part Requirements UI

This feature completes our parts sourcing and ordering solution by ensuring successful utilization of parts stocked in field locations where parts are typically picked up by field technicians.  Customer service is improved as this feature insures the parts will be available when the field technician arrives to pick them up.

Steps to Enable

Use the Manage Stocking Locations UI to set up field technician, site dedicated and unmanned field parts stocking locations.

Role And Privileges

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

Capture Return-From Customer and Return-From Address for More Flexible and Accurate Return Processing

You can now capture a return-from customer and address when you initiate returns, exchanges, and Depot Repair RMAs. You can also leverage the return-from address to create a sales order RMA line, as well as determine the return routing rules. Use these two new fields, Return-from Customer and Return-from Address, on the Add Part and Edit Part UIs, which you can access from the Manage Part Requirements and the B2B Service Request pages.

The example below uses the Create Part Requirements page to create a part requirement for the customer Small Inc’s service request. Since the part is physically located at a different address, use the Add Part page to change the Return-from Customer to BIG COMPUTERS. The Return-from Address defaults to BIG COMPUTERS’ primary address, but you have the option to select another BIG COMPUTER address. The sales order created for the part uses the Return-from Customer and Address field values from the Add Part page when creating the return line.

Create Part Requirements Page Header

Add Part Page with New Fields Return-from Customer and Return-from Address

RMA Line Using Values from the Add Part Page Return-from Customer and Return-from Address Field

Call Center Agents, Support Engineers and Field Service Administrators can now return parts to a customer address other than the address associated with the document type. The Return-from Customer and Address fields also facilitate the creation of sales orders that contain valid customer and address information for tax credit calculations. Service Technicians now receive accurate Return Routing Rules based on the Return-from Address.

Steps to Enable

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

Role And Privileges

• To access this feature, you'll need any predefined job role, or a configured job role that contains at least one of these privileges:
  • Access Service Logistics Landing Page (RCL_PORTAL_ACCESS_LANDING_PAGE_PRIV)
  • View Requirement Lines (RCL_PARTS_REQ_VIEW)
  • Access Debrief Page (RCL_PORTAL_VIEW_DEBRIEF)
  • Manage Estimates (RCL_MANAGE_ESTIMATES_PRIV)

Receive In-Transit Inventory Transfers

You can now create and receive inbound in-transit inventory transfers from the Receive Parts page by entering the Shipment number.

Receive Parts UI

In-transit transactions help to manage service inventory transfers across organizations as well as returns from technician trunk stock.

Steps to Enable

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

Use Oracle Integration Cloud for More Flexible Preventive Service

You can now use a new Oracle Integration Cloud process to manage the integration between preventive work orders and Oracle B2B Service. This new process has been added as an alternative to using the existing ESS job that creates B2B Service requests and work orders for preventive maintenance work.

Schedule Parameters for the Oracle Integration Cloud process for preventive maintenance

Administrators can periodically run (or schedule to run) the new Service Logistics Preventive Maintenance process in Oracle Integration Cloud. This process creates B2B Service requests and work orders for preventive maintenance work orders generated in Maintenance Cloud.

You can configure this integration process to fetch additional details from Maintenance Cloud, such as the work order area to use based on an asset’s time zone, and provide these details to B2B Service. You can then copy details from the work area, such as flexfields and attachments from the maintenance work definition, into the B2B work order.

Use this new process to manage and configure integration related updates from maintenance work orders to B2B work orders.

Steps to Enable

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

Tips And Considerations

Use this Oracle Integration Cloud process as an alternative to the existing ESS job. It performs the same function of integrating preventive maintenance work orders with B2B service. Determine which of these processes to use based on your needs.

Key Resources

• Set Up Field Service Preventive Maintenance

Role And Privileges

• Users who are assigned this predefined job role can access this feature:
  • Field Service Administrator (ORA_RCL_FIELD_SERVICE_ADMINISTRATOR)