Cloud Readiness / Oracle Maintenance Cloud
What's New
Expand All


  1. Update 20B
  1. Revision History
  2. Overview
  3. Optional Uptake of New Features (Opt In)
  4. Feature Summary
    1. Maintenance
        1. Manage Asset Groups
        2. Get Default Work Order Attribute Values
        3. Automatically Update Asset Meters with IoT Data
        4. View Lead and Opportunity Details for a Customer-Enabled Asset
        5. Upload Attachments in Oracle Maintenance Cloud Using a SOAP Service
        6. Capture Work Order Details Automatically on a Requisition Line

Update 20B

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 Feature Notes
20 MAR 2020   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

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.

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:

Access the Opt In page from the New Features Work Area

  1. Click the Navigator, and then click New Features (under the My Enterprise heading)
  2. On the New Features page, select the offering that includes new features you’d like to review
  3. Click Go to Opt In for any feature you want to opt in
  4. On the Edit Features page, select the Enable option for the feature, and then click Done.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may auto enable 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 auto enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Column Definitions:

Features Delivered Enabled

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
(Features 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.

Action is Needed BEFORE Use by End Users
(Features 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

Manage Asset Groups

Get Default Work Order Attribute Values

Automatically Update Asset Meters with IoT Data

View Lead and Opportunity Details for a Customer-Enabled Asset

Upload Attachments in Oracle Maintenance Cloud Using a SOAP Service

Capture Work Order Details Automatically on a Requisition Line

Maintenance

Manage Asset Groups

Manage your assets more efficiently by classifying them into groups according to your needs. For example, you can create an asset group for trucks of the same model based in a given location, then retrieve them easily from the asset management page. With this feature, you create group rules to specify grouping attributes for your groups. Then, you can create the groups and manage assignments of assets within the groups.

Here’s what you can do to classify your assets into groups: 

  • Create and manage asset group rules: A group rule defines the common characteristics of a group, such as grouping attribute or usages. You must define group rules before you create groups.
  • Create and manage asset groups: An asset group handles asset assignments based on the group rules. If the rule specifies usage of grouping attributes, then you must enter grouping attribute values when you create the group.
  • Manage Asset Assignments: Assign or unassign assets from groups either in the Asset Groups page or the Assets page. The asset assignment specifies if the asset is end dated or doesn’t match the grouping criteria after update.
  • You can also manage asset group rules, groups, and assignments using REST services.

This figure illustrates the process of how you can use asset groups to classify your assets:

Manage Asset Groups Tasks Diagram

ASSET GROUP RULES

You can create asset group rules on the Create Asset Group Rules page.

Create Asset Group Rules Page

You must specify the name and a unique code for the asset group rule. You can also specify these characteristics for the group rule:

  • Grouping Attributes: Select multiple grouping attributes from the selected list. When you create a group for the group rule, you must enter a value for each grouping attribute. The assets you assign to the group must also honor the group attribute values. For example, if you create a rule using Customer Number as a grouping attribute, then you must enter a value for Customer Number for each group you create for the rule. You can only assign assets to the group if the asset customer matches the group customer.
  • Usages: A usage is where you use asset groups in the application, such as for order entries or subscriptions: 
    • For order entries, you can specify a group while entering a new sales order line for an asset-tracked product. Once the sales order line is fulfilled, the created assets are automatically assigned to the group.
    • For subscriptions, you can use groups for contract lines in contract or subscription products. 

Usages aren’t enabled in the consuming applications in the initial release of the Manage Asset Groups feature. We strongly recommend that you don’t specify usages for group rules.

  • Enforce unique assignment of assets to groups within the rule: Select the check box to ensure an asset can only be assigned to one group of a given rule. If not selected, you can assign an asset to multiple groups within the rule.

ASSET GROUPS

Once you create the rules, you can create asset groups on the Create Asset Group page:

Create Asset Groups Page

Please note:

  • A group always has an associated group rule.
  • The number and the name of the group are defaulted for you with a unique number, but you can override them with any meaningful value you need.   
  • The grouping attribute values table is populated as soon as you have entered the group rule:
    • The list is composed of the grouping attributes you select when you define the rule
    • If no grouping attributes were selected, this list will be empty
    • You must enter a value for each grouping attribute in the list
    • You can only assign assets to the group if the assets honor the grouping attributes values 

ASSIGN AND UNASSIGN ASSETS

After you create the group, you can navigate to the Asset Group Assignment page using the Assign Assets button on the Asset Groups page. On this page, you can assign assets to the group using the Add button.

  • If the group doesn't have grouping attributes, all assets not already assigned to the group will be eligible for assignment.
  • If the group has grouping attributes, then only assets that match the grouping attribute values and not already assigned to the group will be listed.
  • If you selected the Enforce Unique Assignments while defining the group rule, the assets already assigned to another group of the same rule aren't listed.
  • You can unassign an asset from a group using the delete icon on the assignment row 

Asset Group Assignments Page

MANAGE ASSET ASSIGNMENTS IN THE ASSETS PAGE

You can search assets using the asset group name on the Assets page. A new tab, Groups, lists all the groups the asset is assigned to. On the tab, you can:

  • Unassign the asset from a group
  • Assign the asset to new groups using the Add button. You can assign the asset to groups whose grouping attributes the asset honors or groups that don’t have grouping attributes. If the asset is already assigned to another group, you can’t assign it to a group that only accepts unique assignments.

Asset Groups tab on the Edit Asset page

MANAGE ASSET GROUPS VIA REST SERVICES

You can also manage asset group rules, groups, and assignments using REST services. Here are some examples that show how you create the resources:

Create a group rule (POST)

Create a Group Rule Using a REST Service

URL: https://<Server>/fscmRestApi/resources/11.13.18.05/assetGroupRules

Create a group (POST)

Create a Group Using a REST Service

URL: https://<Server>/fscmRestApi/resources/11.13.18.05/assetGroups

Assign an asset (POST)

Assign an Asset to a Group Using a REST Service

URL: https://<Server>/fscmRestApi/resources/11.13.18.05/assetGroups/<GroupId>/child/assignments

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 ManagementNo Longer Optional From: Update 20D

After you opt in, perform these steps:

  1. Grant privileges to the users who manage asset group rules or groups.
  2. Create the desired asset group rules.

Tips And Considerations

In this release of the Manage Asset Groups feature, the group rule usages aren’t enabled in the consuming applications. We strongly recommend that you don’t specify usages for group rules. Usages will be enabled in future releases.

Key Resources

Role Information

  • Privilege Name and Code: 
    • Manage Asset Group Rules (CSE_MANAGE_ASSET_GROUP_RULES_PRIV)
    • View Asset Group Rules (CSE_VIEW_ASSET_GROUP_RULES_PRIV)
    • Manage Asset Group Rules by Service (CSE_MANAGE_ASSET_GROUP_RULES_BY_SERVICE)
    • Manage Asset Groups (CSE_MANAGE_ASSET_GROUP_PRIV)
    • View Asset Groups (CSE_VIEW_ASSET_GROUP_PRIV)
    • Manage Asset Groups by Service (CSE_MANAGE_ASSET_GROUP_BY_SERVICE_PRIV)
  • Job Role Name and Code: 
    • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER)
    • Maintenance Management setup administration Duty (ORA_MNT_MAINTENANCE_SETUP_DUTY)
    • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR)
    • Maintenance management web service duty (ORA_MNT_MAINTENANCE_SERVICE_DUTY)

Get Default Work Order Attribute Values

Improve data accuracy and save time when you create work orders. You can get default data for your Work Order Description, Work Order Type, and Work Order Subtype fields. The data is derived from either the context asset or applied maintenance work definition.

This process happens automatically when you create a work order manually on the user interface, and when using FBDI or REST services, or maintenance programs.

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 ManagementNo Longer Optional From: Update 20D

Tips And Considerations

Your work definitions now have two new fields: Work Order Type and Work Order Subtype. Note that your assets already had these fields in asset details. For both work definitions and assets, Work Order Type and Work Order Subtype fields are optional. Defaulting occurs automatically as soon as one of these fields is filled. This process cannot be disabled for a particular asset or work definition.Here are the rules of the defaulting process for work order type and subtype:

  1. Work definition takes precedence: when work a definition is selected, if values defined at work definition are not null, existing values of Work Order Type and Work Order Subtype fields are always overwritten. Else, if values pulled from work definition are null, then existing values (or null values) are retained.
  2. Values are defaulted from the asset only if:
    • No work definition is defined for the work order and even if Work Order Type and Work Order Subtype fields are manually defined.
    • A work definition is defined for the work order, but Work Order Type and Work Order Subtype fields are null.
  3. The defaulting process fills either the Work Order Type and Work Order Subtype, or the Work Order Type only, or nothing. As these fields are mandatory to create a work order, you manually select the missing required field(s).
  4. You can manually update the defaulted values at any time. But, if you later enter or update either asset or work definition, the existing values are overwritten by the defaulting process.

When you create a work order using FBDI or REST services, the values passed in the XLSM template or the REST Payload are used first. If no values are passed for Work Order Type, Work Order Subtype or Work Order Description, then defaulting occurs normally.

When you create a work order from a maintenance program, we automatically default the Work Order Type as preventive and Work Order Subtype as planned. The Work Order Description is defined based on the work order generation and the maintenance program setup.

This table discussed three scenarios with their specific defaulting rules:

Scenario Defaulting rule

The maintenance programs use a single work definition or concurrent requirements option is set to suppress.

Work Order Description is defaulted from the work definition description.

The work order is created from merged work definitions within a single maintenance program's work requirement.

Work Order Description is defaulted with the work requirement name

The work order is created from merged work definitions across multiple work requirements within a maintenance program.

Work Order Description is defaulted with the maintenance program name

We’ve updated the Work Definition FDBI and REST services and now support the Work Order Type and Work Order Subtype fields. Please update the latest XLSM template or payload.

Key Resources

Role Information

  • Job Role Name and Code:
    • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER)

Automatically Update Asset Meters with IoT Data

Define and use meters to track asset utilization as well as different parameters of the asset.  You can import these meters when you create a digital twin of the assets in Oracle Internet of Things (IoT) Asset Monitoring Cloud Service.

For each asset in IoT, you can link the sensor attributes to their corresponding sensor devices to provide asset monitoring.  You can also associate these sensor attributes to the corresponding asset meters.  When this link has been established, IoT data coming from devices can be automatically pushed and recorded as asset meter readings in Oracle Maintenance Cloud. 

With a seamless link between Asset Monitoring Cloud Service and Maintenance Cloud for asset meter readings, you can view data directly coming from the devices without having to physically access the asset.

Steps to Enable

Integrate the Oracle Maintenance Cloud with the Oracle IoT Asset Monitoring Cloud Service. For more details, refer to the Using Oracle IoT Asset Monitoring Cloud Service guide.

Tips And Considerations

You must first create assets and the associated meters in Oracle Maintenance Cloud. Then the assets and meters can be automatically synchronzed or manually imported into the IoT Asset Monitoring Cloud Service.

Role Information

  • Job Role Name and Code:
    • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER)
    • Customer Asset Administrator (CUSTOMER_ASSET_ADMIN_CUSTOM_ROLE)

View Lead and Opportunity Details for a Customer-Enabled Asset

View Lead and Opportunity details for a customer-enabled asset using the two new tabs on the Edit Asset page:

  • Leads: The Leads tab displays customer leads that are created for the asset.
  • Opportunities: The Opportunities tab displays customer opportunities that are created for the asset.

Steps to Enable

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

Role Information

  • Job Role Name and Code:
    • Customer Asset Administrator (CUSTOMER_ASSET_ADMIN_CUSTOM_ROLE)

Upload Attachments in Oracle Maintenance Cloud Using a SOAP Service

Maintainers who migrate from, or integrate with an external application, require an efficient way to associate specific attachments to assets, maintenance programs, work definitions, and different areas of the work order. For example, work instructions can be captured as an attachment file, text, or URL to provide key additional information for maintaining an asset or performing a specific operation.

Currently the tools for uploading or downloading these objects, such as REST services, file-based data import (FBDI), and Application Development Framework Desktop Integration (ADFdi) do not allow the inclusion of attachments when processing work definitions.

With this update, you can use the ERP Object Attachment SOAP service to perform the automatic, mass upload of attachments for maintenance assets, maintenance programs, maintenance work orders, maintenance work order operations, maintenance work order operation materials, maintenance work order operation resources, and maintenance work definition operations. You can specify the input parameters for the payload of this service to upload attachments.

By using a service-based approach for uploading attachments, the initial data load from an external source system or ongoing updates can be streamlined into Oracle Maintenance Cloud.

NOTE: This feature was also made available in a monthly update of 19D and 20A.

Steps to Enable

To get started, refer to the information provided in the Oracle Financials Cloud SOAP Web Services for Financials guide.

  • Chapter: Business Object Services
  • Section: ERP Object Attachment Service

REQUEST PAYLOAD

Here's a table with request payload information.

Element Name

Type

Description

entityName

String

Valid business entity names are:

  • ASSET – For Asset
  • MAINTENANCE_PROGRAM – For Maintenance Program
  • WORK_ORDER – For Work Order Header
  • WORK_ORDER_OPERATION – For Work Order Operation
  • WORK_ORDER_OPERATION_MATERIAL – For Work Order Operation Material
  • WORK_ORDER_OPERATION_RESOURCE – For Work Order Operation Resource
  • WORK_DEFINITION – For Work Definition Header
  • WORK_DEFINITION_OPERATION – For Work Definition Operation

categoryName

String

Document Category Name associated with the business entity.

allowDuplicate

String

Whether duplicate is allowed. Valid values are: Yes, No.

attachmentRows

 

List of elements, each containing the details of the attachment to upload. The details include the user keys, attachment type, and title. The user keys are used to identify the unique row in the appropriate business object entity.

attachmentRows ATTRIBUTES FOR ASSET

Here's a table with attachmentRows Attributes for Asset information.

Attribute Name

Type

Description

UserKeyA

String

Asset Number.

UserKeyB

String

Keep this key with value #NULL.

UserKeyC

String

Keep this key with value #NULL.

UserKeyD

String

Keep this key with value #NULL.

UserKeyE

String

Keep this key with value #NULL.

AttachmentType

String

Valid values are: FILE, TEXT, URL.

Title

String

The title of the attachment.

Content

String

The following is an example. Your content may be different.

URL: https://www.google.com

Text: Use Lathe L123.

File: Encode the source data to a Base64 string (Base64 encoding).

attachmentRows ATTRIBUTES FOR MAINTENANCE PROGRAM

Here's a table with attachmentRows Attributes for Maintenance Program information.

Attribute Name

Type

Description

UserKeyA

String

Organization Code.

UserKeyB

String

Program Code.

UserKeyC

String

Keep this key with value #NULL.

UserKeyD

String

Keep this key with value #NULL.

UserKeyE

String

Keep this key with value #NULL.

AttachmentType

String

Valid values are: FILE, TEXT, URL.

Title

String

The title of the attachment.

Content

String

The following is an example. Your content may be different.

URL: https://www.google.com

Text: Use Lathe L123.

File: Encode the source data to a Base64 string (Base64 encoding).

attachmentRows ATTRIBUTES FOR WORK ORDER HEADER

Here's a table with attachmentRows Attributes for Work Order Header information.

Attribute Name

Type

Description

UserKeyA

String

Organization Code.

UserKeyB

String

Work Order Number.

UserKeyC

String

Keep this key with value #NULL.

UserKeyD

String

Keep this key with value #NULL.

UserKeyE

String

Keep this key with value #NULL.

AttachmentType

String

Valid values are: FILE, TEXT, URL.

Title

String

The title of the attachment.

Content

String

The following is an example. Your content may be different.

URL: https://www.google.com

Text: Use Lathe L123.

File: Encode the source data to a Base64 string (Base64 encoding).

attachmentRows ATTRIBUTES FOR WORK ORDER OPERATION

Here's a table with attachmentRows Attributes for Work Order Operation information.

Attribute Name

Type

Description

UserKeyA

String

Organization Code.

UserKeyB

String

Work Order Number.

UserKeyC

String

Operation Sequence Number.

UserKeyD

String

Keep this key with value #NULL.

UserKeyE

String

Keep this key with value #NULL.

AttachmentType

String

Valid values are: FILE, TEXT, URL.

Title

String

The title of the attachment.

Content

String

The following is an example. Your content may be different.

URL: https://www.google.com

Text: Use Lathe L123.

File: Encode the source data to a Base64 string (Base64 encoding).

attachmentRows ATTRIBUTES FOR WORK ORDER OPERATION MATERIAL

Here's a table with attachmentRows Attributes for Work Order Operation Material information.

Attribute Name

Type

Description

UserKeyA

String

Organization Code.

UserKeyB

String

Work Order Number.

UserKeyC

String

Operation Sequence Number.

UserKeyD

String

Material Sequence Number.

UserKeyE

String

Keep this key with value #NULL.

AttachmentType

String

Valid values are: FILE, TEXT, URL.

Title

String

The title of the attachment.

Content

String

The following is an example. Your content may be different.

URL: https://www.google.com

Text: Use Lathe L123.

File: Encode the source data to a Base64 string (Base64 encoding).

attachmentRows ATTRIBUTES FOR WORK ORDER OPERATION RESOURCE

Here's a table with attachmentRows Attributes for Work Order Operation Resource information.

Attribute Name

Type

Description

UserKeyA

String

Organization Code.

UserKeyB

String

Work Order Number.

UserKeyC

String

Operation Sequence Number.

UserKeyD

String

Resource Sequence Number.

UserKeyE

String

Keep this key with value #NULL.

AttachmentType

String

Valid values are: FILE, TEXT, URL.

Title

String

The title of the attachment.

Content

String

The following is an example. Your content may be different.

URL: https://www.google.com

Text: Use Lathe L123.

File: Encode the source data to a Base64 string (Base64 encoding).

attachmentRows ATTRIBUTES FOR WORK DEFINITION HEADER

Here's a table with attachmentRows Attributes for Work Definition Header information.

Attribute Name

Type

Description

UserKeyA

String

Work Method Code

UserKeyB

String

Organization Code.

UserKeyC

String

Work Definition Internal Name.

UserKeyD

String

Keep this key with value #NULL.

UserKeyE

String

Keep this key with value #NULL.

AttachmentType

String

Valid values are: FILE, TEXT, URL.

Title

String

The title of the attachment.

Content

String

The following is an example. Your content may be different.

URL: https://www.google.com

Text: Use Lathe L123.

File: Encode the source data to a Base64 string (Base64 encoding).

attachmentRows ATTRIBUTES FOR WORK DEFINITION OPERATION

Here's a table with attachmentRows Attributes for Work Definition Operation information.

Attribute Name

Type

Description

UserKeyA

String

Work Method Code.

UserKeyB

String

Organization Code.

UserKeyC

String

Work Definition Internal Name.

UserKeyD

String

Version Number.

UserKeyE

String

Operation Sequence Number.

AttachmentType

String

Valid values are: FILE, TEXT, URL.

Title

String

The title of the attachment.

Content

String

The following is an example. Your content may be different.

URL: https://www.google.com

Text: Use Lathe L123.

File: Encode the source data to a Base64 string (Base64 encoding).

Tips And Considerations

The content for attachment of type FILE must be provided in the Base64 encoding.

Role Information

This privilege is needed for all the entities:

  • FSCM Load Interface Administration (ORA_FUN_FSCM_LOAD_INTERFACE_ADMIN_DUTY)

And for each of the entity, these privileges grant users access to upload attachments.

Business Object Entity

Functional Privilege

ASSET

Manage Maintainable Assets (MNT_MANAGE_MAINTAINABLE_ASSETS_PRIV)

Manage Customer Assets (CSI_MANAGE_CUSTOMER_ASSETS_PRIV)

MAINTENANCE_PROGRAM

Manage Maintenance Programs (MNT_MANAGE_MAINTENANCE_PROGRAMS_PRIV)

WORK_ORDER

Manage Maintenance Work Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)

WORK_ORDER_OPERATION

Manage Maintenance Work Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)

WORK_ORDER_OPERATION_MATERIAL

Manage Maintenance Work Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)

WORK_ORDER_OPERATION_RESOURCE

Manage Maintenance Work Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)

WORK_DEFINITION

Manage Maintenance Work Definitions (MNT_MANAGE_MAINTENANCE_WORK_DEFINITIONS_PRIV)

WORK_DEFINITION_OPERATION

Manage Maintenance Work Definitions (MNT_MANAGE_MAINTENANCE_WORK_DEFINITIONS_PRIV)

Capture Work Order Details Automatically on a Requisition Line

Capture work order details automatically on a requisition line when you navigate from the Maintenance Management work area to the Purchase Requisitions work area to shop items or services for the work order. As a maintenance manager, now you don't have to manually select the work order details such as destination type, work order number, and operation sequence every time you shop for a new item or service for the work order.

This illustration explains the changes in the process flow to capture work order details automatically on a requisition line.

CREATE REQUISITION DIALOG BOX

Now you can set the default work order values in the Create Requisition dialog box that opens before you navigate from the Maintenance Management work area to the Purchase Requisitions work area.

Create Requisition Dialog Box    

SELF SERVICE PROCUREMENT > REQUISITION PREFERENCES

When you navigate from the maintenance work order, the Requisition Preference page displays these additional attributes: Destination Type, Work Order Number, and Operation Sequence.  The default values of these attributes and Deliver-to Location are displayed from the context maintenance work order. Though these are default values, you can update the requisition preferences if required.

This screenshot shows the new fields that are added to the Requisition Preferences page.

    Edit Requisition Preferences Page

PURCHASE REQUISITION

When you create a requisition, default values of work order details are displayed from requisition preferences. 

  • When you create a new requisition for catalog items, default values of work order details are displayed in the Edit Requisition Page.

 

    Edit Requisition Page

  • When you create a new requisition for non-catalog items or when you use the Enter Requisition Line action, default values of the work order details are displayed in the Create Requisition page.

Enter Requisition Line Page

Steps to Enable

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

Tips And Considerations

The work order specific preferences are only available and applicable when you create a requisition for a maintenance work order.

Key Resources

Role Information

  • Job Role Name and Code: 
    • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER)