Update 22D

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
21 NOV 2022	Maintenance	Schedule Work Orders Manually	Updated document. Delivered feature in update 22D.
16 SEP 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 SCM Cloud: Performing Your Quarterly Update (doc ID 2337485.1) on My Oracle Support.

Optional Uptake of New Features (Opt In)

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

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

Here’s how you opt in to new features:

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

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

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

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

Opt In Expiration

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

Feature Summary

Maintenance

Maintenance

Enable Deferred Electronic Records and Electronic Signatures for Maintenance Work Order Release

Oracle Electronic Signatures and Electronic Records is a configurable framework for securely capturing, storing, retrieving, and printing electronic records and signatures.

Today, there is no formal approval process before releasing a maintenance work order. With this update, you can enforce the generation of an e-record and capture of e-signatures when a work order is initially changed to the Released status on the following pages:

• Edit Work Order
• Manage Maintenance Work Orders

The maintenance work order e-record contains the following information as applicable in the work order:

• Work order header and details
• Work definition details
• Asset information details
• Project details
• Operation details, including operation information, operation items, operation resources, and operation resource instances
• Maintenance exceptions
• Attachment details

E-Record for Maintenance Work Order Release

Using a deferred approval process with notifications, the maintenance work order is held in a Pending Approval status until the approvals are obtained. Depending upon the outcome of the approval, the work order is saved in the Approved status or rolled back to the previous status.

1. Update maintenance work order the status to Released and submit for approval.

2. Update confirmation will be displayed.

3. Search for above work order to verify the status that's moved to Pending Approval.

Now, work order is in the Pending Approval status.

4. The following screenshot shows the notification for approval of the specific electronic record.

5. After approval, you can see that the maintenance work order is in the Released status.

Controlling the release of a work order through the e-record and e-signature process ensures adherence to specifications and procedures before starting a maintenance work order.

Steps to Enable

• To enable electronic records and capture electronic signature for maintenance, you must determine and configure electronic signatures for each inventory organization using the Configure Electronic Signature Preferences task in the Setup and Maintenance work area. The transaction to be configured is Maintenance Work Order Approval.

• After you enable electronic signatures for a transaction, you must also define configurable business process rules in Oracle Business Process Management using the Manage Task Configurations for Supply Chain Management task, and the Manage Approval Groups task in the Setup and Maintenance work area to determine the approver for each transaction. The task to be configured is WorkOrderDeferredApproval.

Tips And Considerations

• You can enable e-records and e-signatures for discrete manufacturing and process manufacturing work orders separately from maintenance work orders.

• You can submit a work order for approval when the initially changing to a user-defined status that's associated with the system status of Released.

• You can't update a work order in Pending Approval status through the UI, FBDI, or REST. You must wait for the approval process to complete as approved or rejected before making further changes.

• You can't initiate the e-record and e-signature process for work orders created in the Released status.

• You can't submit a work order that has been previously released for e-record and e-signature approval again. Instead, you can enable audit trail to track work order changes.

• You can't release and pick a work order in a single action when e-records and e-signatures is enabled. Instead, you can release a work order and submit it for approval before picking materials.

• You can't release a work order for e-record and e-signature approval through FBDI, REST, Edit Maintenance Exception page, or the Production Supervisor Mobile application.

• You can't configure the suppression of the e-signature approval based on specific conditions. However, you can configure an automatic, conditional approval based on approval rules.

Key Resources

You can refer to these guides on the Oracle Help Center for details about setting up and using Oracle E-Signatures and E-Records:

• Using E-Signatures and E-Records
• Implementing Manufacturing and Supply Chain Materials Management: E-Signatures and E-Records chapter

Role And Privileges

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 Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)

Define Maintenance Program Day Interval Using REST API

The Maintenance Programs REST API allows you to define and update key details of a program and its work requirements. With this uptake, you can now use the service to define, view, and manage functionality that was introduced in the 21D feature entitled Generate Maintenance Program Forecasts Using Number of Days. This capability includes the ability to define a forecast interval method based on a number of days, in addition to the previous methods of a calendar pattern and asset meter, as well as including or excluding assets for an item-based work requirement.

The service has been improved at the Work Requirement resource level by exposing additional attributes that are used for both asset and item-based definitions. These attributes are returned in the GET response, and many can be set or updated using POST or PATCH transactions:

• Type - read-only meaning of the type of work requirement. Values are Asset or Item, based on the selected Type Code.

• Include Assets Code - indicates if assets are included automatically or manually for an item-based requirement. During creation, the value is default to Automatic, but you can set as Manual.  It will be set to null, but considered as set to Automatic, for all existing requirements prior to this uptake.

• Include Assets - meaning of the Include Assets Code.

• Allow Work Orders Flag - read-only indicator for an asset-based requirement that work orders may be created for the asset.

• Work Orders Create Flag - read-only indicator for an asset-based requirement that work orders have already been created for the asset.

• Historical Last Completion Date - optional value for an asset-based requirement. You can define the last date in which similar maintenance was accomplished in an external system prior to the first work order.

• Historical Last Completed Interval - optional value for an asset-based requirement. You can define the last interval in which similar maintenance was accomplished in an external system prior to the first work order.

• Status Code - read-only status of the work requirement.

• Status - meaning of the status code.

• Day Based Flag - optional indicator used in the work requirement to select a forecast method using a day interval. If set, you must also provide a day interval.

• Day Interval - value for the number of days between intervals in a Day Forecast method.

• Day Calculate Next Due Code - indicates if the next due interval for a day-based forecast will be per the Base Interval or the Last Completion. The default is Base Interval if not defined.

• Day Calculate Next Due - meaning of the Day Calculate Next Due Code.

The Work Requirement resource also includes a new Affected Assets child resource. This resource is used to define, view and manage assets in a forecast.

• For an asset-based work requirement:
  • You can manage the historical details only at this resource level. Additionally, you can manage them at the Work Requirement resource level as well.

• For an item-based requirement where assets are automatically included:
  • By default, all assets for the item in that organization will be explicitly included. You can use GET method to return the complete list of assets that are included.
  • You can then use the service to exclude assets or to define historical details used to initialize the first due date in the forecast.
  • Later you can also choose to include a previously excluded asset and it will be considered for the forecast.

• For an item-based requirement where assets are manually included:
  • By default, all assets for the item in that organization will be explicitly excluded. You can use GET method to return the complete list of assets that are excluded.
  • You can then use the service to include assets or to define historical details used to initialize the first due date in the forecast.
  • Later you can also choose to exclude a previously included asset and it will no longer be considered for the forecast.

• For either method of asset inclusion or exclusion, you can define the details using the following methods:
  • During POST creation of a new Work Requirement, you can include or exclude assets and their historical details. 
    • However, you can't update them at the Work Requirement level.
  • When a Work Requirement is created, you can manage the assets using the Affected Assets resource for a unique Work Requirement. 
    • You can directly define or update an asset's status by using the POST transaction.
    • You can also set the context to an individual affected asset and use the PATCH transaction to update it.

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

The updated service allows you to more easily define, view and manage their maintenance programs for preventative maintenance.

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.

Key Resources

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

Role And Privileges

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

View and Search by Additional Attributes in the Asset Information Management Page

In this uptake, you can now search for assets by their location type, maintenance programs allowed indicator, and work orders allowed indicator in the Asset Information Management page. Clicking a filter chip will add it to the search bar, automatically providing additional filtering of the list of results.

Search Filters

When a filter chip is in the search bar, you can further refine your results by clicking the chip, and selecting one or more additional filter criteria. This additional filtering is available for all 3 of the new chips.

Filter by chip

Additionally, you can now view Asset Group details by clicking on any asset row in the search results table. The drawer region will now show Asset Group details, as well as global and context-sensitive descriptive flexfield segments, for the selected asset row. The Asset Group details include the Asset Group Rule Name, Asset Group Name, and Asset Group Description of each group for which an asset is associated. When you click on different asset rows in the result table, the drawer contents will be updated. You can close the drawer by clicking on the x at the top corner of the drawer or clicking the Escape (Esc) key.

Asset Drawer

The Asset Group details can also be used to further refine your results, allowing you to incrementally refine your results.

For example, entering a Group Name as a search term refines the results list to 8 assets:

Search by Asset Group Name

Then adding another search term based on the Asset Group Description refines the results list to a single asset:

Search by Asset Group Description

The additional search filter chips provide the ability to further refine the asset result rows, reducing the number of result rows that are returned. Additionally, searching by and then being able to view the asset group details in the drawer region provides you to more easily identify asset group associations and interact with the subset of result rows that are returned.

Steps to Enable

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

Role And Privileges

No additional user roles or privileges are required to use this feature.

Qualify Operators When Assigning Work or Reporting Labor Usage

Companies often have separate processes and systems for maintaining operator skills or training records, and executing operations that could pose a potential risk in ensuring that their operators are properly trained before performing their work. With this update, you can verify that an operator is qualified to perform a maintenance operation based on the specified job profile.

For initial setup, you can leverage Oracle Fusion Cloud Talent Management, part of Oracle Cloud Human Capital Management, to define job profiles for specific job requirements and track an employee talent profile for competencies with corresponding proficiency levels and certifications. You then require that an operator must meet the specific job requirements by associating the job profile to a standard operation resource, maintenance work definition operation resource, or directly to maintenance work order operation resource.

Associate a job profile to an operation resource.

Create work definition with above standard operation.

This qualification check is enforced when assigning work to an operator or reporting labor usage as follows:

• You can confirm the operator's qualifications when assigning a labor resource instance to a maintenance work order operation. In the event that the operator does not qualify during the assignment to a work order operation, you receive a warning and can proceed or replace with another qualified operator.

Supervisor is warned if unqualified operators are assigned.

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

Supervisor will get an error message that, resource transaction requires an operator to qualify against the job profile associated to the resource.

File-based data import (FBDI) changes:

You can associate the job profile to standard operation resource, work definition operation resource, and work order operation resource using file-based data import. A new column called Job Profile Code has been added to the respective FBDI templates.

REST API changes:

You can associate the job profile to standard operation resource, work definition operation resource, and work order operation resource using REST service. REST payload accepts Job Profile Code and Profile ID. You can't report operation completion if an operation resource has an associated job profile 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.

ADFdi changes:

You can associate the job profile to standard operation resource through ADF desktop integration service (ADFdi). Job Profile Name and Profile Code are both exposed in the templates with code being given precedence.

Built-in operational checks for compliance with training and job requirements reduces the likelihood of noncompliance, defects, or failures in maintenance operations while adhering to standard operating procedures and regulatory requirements. For additional information, refer to the Talent Management documentation under resources section.

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

Prerequisites: You must set up job profiles and skills and qualifications in HCM. Here’s how:

HCM Setup

Use the following setup from the Oracle Fusion Cloud Talent Management.

Define a Job Profile.

Adding the job skills to an employee.

Tips And Considerations

• You can use a job profile for any work order type and work method including in-house maintenance.

• You can add an active job profile to a standard operation, work definition operation, or work order operation through the UI and other ways including REST, File Based Data Import (FBDI), and Application Development Framework Desktop Integration (ADFdi) as supported by the Maintenance work method.

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

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

• You can delete the job profile associated to a work definition operation to disable the qualification check required in the work order and during work execution.

• 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 qualification check, because only the integrated check with HCM is supported.

• You can't use the Quick Complete process on the Review Dispatch List page when a work order has a job profile required for any of its operation resources.

• You can't override skill validation during resource transaction reporting. Qualifications of the assigned labor resource instance is checked against the job profile requirements. The user who is logged into report the transactions isn't used for verification.

Key Resources

To understand more about how to create job profiles and manage employee talent profiles, please refer to Talent Management documentation which is part of Oracle Fusion Cloud Human Capital Management 

Role And Privileges

• Users who are assigned this predefined job role can automatically access this feature:
  • Maintenance Manager - ORA_MNT_MAINTENANCE_MANAGER_JOB

• Users who are assigned this job role can create job profiles with required qualifications since they need to access functionality from Oracle Fusion Cloud Human Capital Management: 
  • Human Resources Specialist - ORA_PER_HUMAN_RESOURCE_SPECIALIST_JOB

Schedule Work Orders Manually

Maintenance work orders are automatically created through maintenance programs or are manually created by users. In both situations, the work order dates are compressed to eliminate or minimize any time gaps within the work order through the background unconstrained scheduling engine.

In addition, if any of the work order dates are updated by the user, the same background unconstrained scheduling engine is invoked, which compresses any of the corresponding work order dates through forward, mid-point, or backward scheduling.

However, due to various maintenance business needs, users want to be able to create and update work dates without having the unconstrained scheduling engine automatically invoked. Examples include wanting to schedule work orders with gaps of time between the operations and resources and defining overlapping operation and resource time durations.

For example, if a maintenance operation involves painting, the following work operation should be scheduled to start only after some time elapses for drying time. The work order requires that the next operation starts after a gap of time between the previous operation’s scheduled completion time.

Before this update, work orders were always scheduled automatically with no gap or overlap between the operation and resource dates.

With this update, you can schedule work orders manually to enable gaps or overlaps between operations or resources.

Here are the capabilities supported by this feature:

• Set up a work order for manual scheduling

• Manually schedule work orders
  • Manual update of work order start and completion dates
  • Manual update of work order operation starts and completion dates
  • Manual update of work order resource start and completion dates

Set up a work order for manual scheduling

The scheduling method is displayed in the work order header for both maintenance and manufacturing work orders. You can select one of the following two values:

• Default Scheduling
• User or External Scheduling

Edit Work Order> General Information> Details

Manually schedule work orders

• Manual update of work order start and completion dates

You can manually update the start and completion dates of the work order. The unconstrained scheduling won't be invoked if your scheduling method is User or External Scheduling.

• Manual update of work order operation starts and completion dates

You can manually update the start and completion dates of the work order operations. The unconstrained scheduling won't be invoked if your scheduling method is User or External Scheduling. However, the work order start and completion dates will be synchronized with the earliest operation start date and the latest completion date if they are outside the work order start and completion date.

• Manual update of work order resource start and completion dates

You can manually update the start and completion dates of the work order resources. The unconstrained scheduling won't be invoked if your scheduling method is User or External Scheduling. However, the work order operation starts, and completion dates and the work order start and completion dates will be synchronized with the earliest resource start date and the latest resource completion date, if they are outside the work order or operation dates.

Oracle Fusion Cloud Supply Planning, including Production Scheduling, will consider manually scheduled work orders during scheduling. If Oracle Supply Planning, including Production Scheduling, updates the work order dates, Oracle Fusion Cloud Maintenance will honor the recommendations.

Using the manual scheduling of work orders, you can better manage real time requirements of shop floor scheduling, to meet your business needs.

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

Tips And Considerations

• The Firm indicator would be automatically selected if the scheduling method is changed to User or external scheduling method. However, it can be optionally deselected.

• This enhancement is supported in the User interface only. FBDI and REST will continue to support the existing behavior.

Role And Privileges

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

Service Logistics

Support In-Transit Part Returns and Transfers

You can now create in-transit transactions for returns and transfers in Service Logistics. This helps manage service inventory transfers across organizations as well as returns from technician trunk stock.

When transferring or returning a part to another organization, you can now select In-transit Shipment in the Type field. You can also choose whether to generate or manually add a shipment number.

Create an In-Transit Transfer

An in-transit transfer automatically generates a receiving transaction at the destination organization. By using an in-transit transfer to create separate shipping and receiving transactions, you now have a traceable view into your parts supply chain.

Steps to Enable

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

Tips And Considerations

If you typically use in-transit transactions between two organizations, then use the Create Interorganization Parameters page to set the Transfer Type field value to In transit.  This causes the Type field value to default to In transit Shipment in the Transfer Part page.

Set Up an Interorganization Transfer with the In Transit Transfer Type

Key Resources

• Watch Use Transfer Orders to Support Complex Depot Repair Logistics Readiness Training.

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)