Document History

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

Date Update Version Notes
10 MAY 2019 Update 18C Revised update 18C.
06 APR 2018 Update 18B Delivered new features in update 18B.
05 FEB 2018 Update 18A Revised update 18A.

Update 18C

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
10 MAY 2019 Manage Maintenance Programs Through Maintenance Interval Optimization

Updated document. Added opt-in expiry update for this feature.

10 MAY 2019 Manage Maintenance Programs Using Asset Meters and Events

Updated document. Added opt-in expiry update for this feature.

10 MAY 2019 Manage Maintenance Work Orders Based on IoT Events

Updated document. Added opt-in expiry update for this feature.

10 MAY 2019 Use Resource Instances in Manufacturing and Maintenance

Updated document. Added opt-in expiry update for this feature.

10 MAY 2019 View and Edit Meter Reading Transaction History

Updated document. Added opt-in expiry update for this feature.

10 MAY 2019 Display Additional Asset Information Updated document. Added opt-in expiry update for this feature.
21 SEP 2018   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)

We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can opt in to a feature in two ways:  by using the New Features work area, or by using the Setup and Maintenance work area.

To opt in using 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 that you want to opt in to.
  4. On the Edit Features page, select the Enable option for the feature, and then click Done.

To opt in using the Setup and Maintenance work area:

  1. Click the Navigator, and then click Setup and Maintenance.
  2. On the Setup page, select your offering, and then click Change Feature Opt In.
  3. On the Opt In page, click the Edit Features icon.
  4. On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close
  5. Click Done.

Feature Summary

Column Definitions:

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

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

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


Opt In Only = These features are made available for use via Opt In. No additional setup steps are required.

Opt In, Plus Additional Steps Required = To use these features you must first Opt In, then perform additional setup steps.

Steps Required (No Opt In) = Setup steps must be performed before these features can be used. For example, new or expanded BI subject areas need to first be incorporated into reports. Integration is required to utilize new web services.

New Features Delivered Ready to Use
(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.

New Features That Customer Must Take Action to Use (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*

Customer Action:
Opt In Only

Customer Action:
Opt In, Plus Additional Steps Required

Customer Action:
Steps Required (No Opt In)

Maintenance

Use Resource Instances in Manufacturing and Maintenance

Enhance Maintenance Work Order Material Transaction with a REST Service

Display Additional Asset Information

Manage Maintenance Programs Through Maintenance Interval Optimization

Manage Maintenance Programs Using Asset Meters and Events

Import Work Definitions Through Spreadsheet

View and Edit Meter Reading Transaction History

Enable E-Records and E-Signatures in Deferred Mode for Maintenance Exceptions

Manage Maintenance Work Orders Based on IoT Events

Maintenance

Use Resource Instances in Manufacturing and Maintenance

Define resource instances for labor and equipment resources, and assign them to work order operations. You can specify a resource instance while reporting a resource transaction or while reporting a production or maintenance exception.

Resources, such as equipment and labor, are an integral part of maintenance or manufacturing activities. They can be used to track actual time spent against standards, and enables accurate costing.

A resource instance is a granular representation of a resource that identifies the specific equipment or person working on production or maintenance activities. For example, in a machining work center there may be three lathes that are identical in model, production capacity, machine specifications, and usage cost. Each of these lathes is a resource instance and can be uniquely identified using the equipment serial number. Similarly, you may have a labor resource called the lathe operator. There may be several people in the workforce that have the same skills and labor rates to be a lathe operator, and are uniquely identified as individuals by names as resource instances.

In addition to having better visibility and utilization of labor and equipment resource instances, you can also report resource usages against specific resource instances so that you can analyze resource utilization and cost them accordingly.

Prior to this update, you could only define a resource and classify it as equipment or labor and report usage against the resource. With this update, you can report usage, and production or maintenance exceptions against a resource instance.

FEATURE DETAILS

DEFINE LABOR AND EQUIPMENT RESOURCE INSTANCES

You can define labor resource instances that represent a specific person working on the shop floor or in maintenance activities. You may have different types of labor resources like employees, contingent workers, or partner contacts. You can define the employees and contingent workers using Oracle Human Capital Management (HCM) Cloud and then associate them with the defined resource instance.

You can define equipment resource instances that represent the name of an actual machine on a shop floor. For example, two machines available on the shop floor are Lathe-1 and Lathe-2, and you define them as two resource instances of a Lathe resource. You can optionally associate a resource instance to an asset number in the asset master.

You can define these resource instances using the user interface or using REST services.

The following is a screenshot that shows how to define labor resource instances on the Edit Resource page:

Define Labor Resource Instance

ASSIGN RESOURCE INSTANCES TO WORK ORDER OPERATIONS

As a Production Supervisor or Maintenance Manager, you can optionally assign as many resource instances to a work order operation resource. This helps you identify the actual people or machines used in execution of production or maintenance activities.

You can track the actual usage at the resource level or a resource instance level, based on the level at which resource transactions are reported.

You can assign these resource instances using the user interface, REST services, or the file-based data import (FBDI) process.

CHARGE RESOURCE INSTANCES IN WORK EXECUTION 

As a Production Operator or Maintenance Technician, you can record resource transactions with resource instance details while manually charging resources, performing orderless completions, or reporting operation completions for automatically charged resources.

When reporting a resource transaction at a resource level, the required quantity reflects the exact quantity required based on the work order.

However, when reporting at the resource instance level, the required quantity is zero, because it is not possible to split the required quantity against each instance. However, you can report any quantity against the instances. You can also review resource instance information for the resources on the Production Transactions History page.

You can report these resource transactions at the instance level using the user interface, REST services, or the file-based data import (FBDI) process.

The following is a screenshot of the Report Resource Transactions page where you can charge at the resource instance level:

Report  Resource Transactions at the Instance Level

REPORT MAINTENANCE EXCEPTIONS 

When you report a production or maintenance exception of type resource, you can capture the specific resource that has an exception. You can now additionally capture the instance of the resource that has an exception. The resource exception notification includes the resource details as well as the resource instance details.

ANALYZE RESOURCE INSTANCES

When you report resource transactions at an instance level, you can analyze the resource usage in real time using Oracle Transactional Business Intelligence (OTBI). You can use the resource instance as a dimension and perform detailed analysis in conjunction with the asset dimension in Oracle Maintenance Cloud, as well as person detail dimension in Oracle Human Capital Management Cloud.

You can also review the details of resource instances in the Work Order Details report.

NOTE: In this update, you can only analyze resource instances using Oracle Transactional Business Intelligence (OTBI) for manufacturing, and not for maintenance.

Steps to Enable

You must opt in 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: 11.13.19.04.0

Before using this feature, you can optionally set up the following.

Tips And Considerations

Consider the following:

Role Information

Enhance Maintenance Work Order Material Transaction with a REST Service

The Maintenance Material Transactions resource manages the movement of an item between the shop floor and the subinventory. Prior to this update, the following transactions were supported:

With this update, the following transactions are also supported:

You can now remove an asset or component from any parent asset in the asset structure. Similarly, you can also install an asset or component to any parent asset in the asset structure.

The following screenshot shows a sample payload of the enhanced REST service:

Sample REST API Payload of Negative Material Issue and Negative Material Return Transactions

The new parameters in the REST payload are as follows:

All of these parameters are optional attributes for executing material transactions.

Steps to Enable

Review the changes to the Maintenance Material Transactions service, and update your REST client as desired.

Tips And Considerations

Consider the following:

Key Resources

Role Information

Display Additional Asset Information

With this update, you can use the new security privileges to set the context of the Manage Assets page, and manage one type of assets at a time. You can access all the maintenance and customer assets by leveraging the same user interface.

FEATURE DETAILS

MANAGE ASSETS 

The enhanced Manage Assets page lets you create new assets, create assets from an existing asset by copying, edit existing assets, and view related attributes of assets.

There is also a hyperlink to the new Asset 360 View, which provides you a networked view of the related objects with metrics and navigation links.

The following is a screenshot of the Assets page:

Manage Assets

CREATE NEW ASSETS 

When you create a new maintenance asset, you can now control the corresponding item selection by selecting an operating organization. Additionally, you can select the Use BOM for Initial Hierarchy check box. If you select this check box, during asset creation, the application will automatically create child assets using a BOM explosion method. For this, there must be a BOM hierarchy defined in the Product Information Management work area for the item, and the option should be enabled.

When you create a new customer asset, you can now also specify the customer and the shipment date, which are required attributes.

For either asset type, there is a new Enable IoT check box. If you select the check box, during asset creation there will be a synchronization with the IoT Asset Monitoring Cloud, to create a digital twin of the asset.

The following screenshots illustrate these new attributes on the Create Asset page:

Create Maintenance and Customer Assets

CREATE ASSETS FROM COPY 

You can also create an asset by copying an existing asset. You can decide whether you want to copy the related objects over to the newly created asset, such as attachments, primary image, meters, and parts list. The fields are dynamically displayed based on your selection of the asset type.

The following screenshot displays the Create from copy option on the Create Asset page:

Create from Copy Option

EDIT ASSETS 

The Assets Overview page has a new vertical tab layout which exposes tabs based on the asset type and the related security privileges.

The Overview tab dynamically displays the key fields based on the type of the the asset, maintenance or customer. In the Asset Images area, images are defaulted from the item setup in the Product Information Management work area, including the primary image. You can add new image files, or edit the existing files as required.

The following is a screenshot of the descriptive flexfields Additional Attributes, which you can choose to show or hide. You can view and edit the descriptive flexfields as required:

Edit Asset Page

VIEW LAST SALES ORDERS AND CONTRACTS 

On the Edit Asset page, there are two new tabs, the Last Sales Order Details and the Contract Details.

The Last Sales Order Details tab displays the sales order and related details of an asset which is sold to a customer.

The Contracts tab displays the related service contract details of the asset.

The following two screenshots show the two tabs on the Edit Asset page:

Last Sales Order and Contracts Tabs

For both types of assets, there is also an Asset Hierarchy tab. For each asset, the hierarchy represents the physical parent and child relationships between the related assets.

During asset creation, a hierarchy can be optionally created based on BOM explosion process. After creating an asset, you can manually interact and update each asset using the new hierarchy viewer.

The following is a screenshot of the Asset Hierarchy tab:

Asset Hierarchy

VIEW ASSETS IN 360-VIEW

For both types of assets, there is a new Asset 360 View page, which you can navigate to from a link in the results region of the Manage Assets page.

This page provides an interactive overview of the asset and its related objects. Each object will display key metrics and navigation links to the Edit Asset page or related object pages.

The following is a screenshot of the Asset 360 View page:

Asset 360 View

VIEW ASSET OPERATING ORGANIZATION 

For a maintenance asset, the operating organization defines where an asset is operating, such as an inventory, a manufacturing organization or a maintenance organization.

The new related maintenance organizations define where an asset could be maintained. With this update, you get a basic reference of such an organization.

The following is a screenshot of the operating organization attribute on the Asset Overview page:

Operating and Maintenance Organizations

Steps to Enable

You must opt in 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: 11.13.19.04.0

Role Information

Manage Maintenance Programs Through Maintenance Interval Optimization

Maintenance programs are a foundational requirement for preventative maintenance of an asset. Over time, they require periodic auditing to make sure that they are aligned with the latest supplier-defined recommendations, meet maintenance availability goals, and are optimized to reduce labor and material costs. These recommendations can come from Oracle’s maintenance machine learning platform or from other artificial or human intelligence sources.

FEATURE DETAILS

VIEW RECOMMENDATIONS 

The Recommendations page displays recommendations for optimizing maintenance intervals. Recommendations can be to either lengthen or shorten calendar-based intervals, or to increase or decrease meter-based intervals. These recommendations can come from Oracle’s maintenance machine learning platform or from other artificial or human intelligence sources.

Along with each recommendation, insights from the recommender indicating why the recommendation was made, and the confidence in the recommendation are also displayed.

The following is a screenshot of the Recommendations page:

Recommendations Page

ACCEPT, REJECT, OR OVERRIDE RECOMMENDATIONS 

You can accept, reject, or override a recommendation. This action is recorded in the recommendation table for audit and feedback purposes. If you choose to reject or override a recommendation, you can optionally capture a reason, or enter comments to explain your decision.

The following is a screenshot of the Mass Actions menu on the Recommendations page. You can select multiple recommendations and define an action:

Recommendation Actions

AUTOMATICALLY APPLY RECOMMENDATIONS 

In most cases, accepted recommendations will be automatically applied to the maintenance interval setup on the work requirement. If the recommendation is for a calendar-based interval, the change will likely be to the number of intervals per cycle, the calendar pattern, or the due at cycle interval value. When optimizing calendar-based intervals that use yearly, monthly, or weekly calendar patterns, the algorithm will convert that calendar pattern to a daily pattern to allow for finer-grained optimizations.

CAPTURE REASON AND COMMENTS 

For rejected or overridden recommendations, you can optionally capture a reason either by choosing a predefined reason from the list of values or with free text comments. A few reasons are predefined, but the assumption is that most businesses will want to create their own list of reasons for reporting, auditing, and feedback purposes.

The following is a screenshot of the Reason list of values on the Recommendations page:

Reasons for Rejecting or Overriding Recommendations

CREATE RECOMMENDATIONS 

A new Recommendations REST service is available which allows addition of recommendations to the Recommendations table. This REST service is used by the maintenance machine learning platform to populate the Recommendations table, but can also be used by other sources as well, for example, third-party machine learning platforms.

Steps to Enable

You must opt in 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: 11.13.19.04.0

Role Information

Manage Maintenance Programs Using Asset Meters and Events

Maintenance programs are a foundational requirement for preventive maintenance of an asset. The forecast is then used to create preventive maintenance work orders, reducing the workload for maintenance planners, allowing them to focus on maintenance program auditing, optimization, and exception-based events.

This update introduces a new page dedicated to the creation and editing of work requirements. This new page intuitively walks you through the process of selecting an asset or Item, the methods used for generating a forecast, and then defining what work is required, and how often it should occur. Work requirements now include expanded capabilities like forecasting by calendar pattern, utilization meter, or by both.

FEATURE DETAILS

MANAGE MAINTENANCE PROGRAMS 

The Manage Maintenance Programs page supports the creation, editing, viewing, and auditing of programs. After you have created a program, you can now search by a unique work requirement name in the filter criteria to find the corresponding program.

Additionally, while creating or editing a program, the Overview tab now displays enhanced program metrics, as well as program review tracking fields. This lets you record the last time a program was reviewed or optimized, increasing the effectiveness of maintenance planning.

The following is a screenshot of the Overview tab on the Maintenance Program page:

Maintenance Programs - Overview Tab

MANAGE WORK REQUIREMENTS 

In this update, there is a dedicated page for the creation and editing of work requirements. This new page intuitively walks you through the process of selecting an asset or item, the methods used for generating a forecast, defining what work is required, and how often it should occur. Work requirements now include expanded capabilities like forecasting by calendar pattern, by utilization meter, or by using both methods, whichever comes first.

There is also support for IoT-based conditional events using a new forecast method, Condition Event, which is available only for noncycle-based requirements. After you have enabled this forecast method, you can define one or more condition codes, which will be used to provide a cross-reference for an asset and its applicable work definitions during the REST processing.

The following is a screenshot of the Work Requirement tab on the Maintenance Program page:

Maintenance Programs - Work Requirements Tab

MANAGE CYCLE AND NONCYCLE INTERVALS 

You can choose to forecast work requirements either based on a cycle of specific intervals, or on a noncyclical basis. By default, you can create the forecast using a cycle based on a number of user-defined intervals. Alternatively, you can choose to create a noncycle-based forecast.

MANAGE MERGING AND SUPPRESSING OPTIONS 

You can now define merging and suppressing options for a single work requirement, as well as across work requirements.

MANAGE FORECASTS USING METERS 

You can now use meter intervals to forecast preventative maintenance by using an asset’s utilization meter. This lets you accurately forecast maintenance based on an asset’s utilization. The meter method can be used along with or instead of a calendar pattern.

MANAGE MULTIPLE WORK DEFINITIONS 

You can now model multiple work definitions for an asset, falling on different intervals in a cycle, based on competing forecast methods, all in a single work requirement. You can view the impact of merge and suppress options and evaluate the Forecasted To value. You can therefore quickly apply and evaluate the adjustments to the forecast methods and the work definition intervals.

MANAGE FORECAST VISUALIZATION 

On the Forecast Gantt Chart View tab, you can now see the name of a work requirement, its details, and an enhanced chart. You can view the relevant details of the enhanced work requirements.

The following is a screenshot of the Forecast Gantt Chart View tab on the Maintenance Program page:

Maintenance Programs - Forecast Gantt Chart View Tab

Steps to Enable

You must opt in 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: 11.13.19.04.0

Role Information

Import Work Definitions Through Spreadsheet

With this update, you can import a high volume of maintenance work definitions using the file-based data import (FBDI)  process. The import process supports both initial data load and data upload scenarios.  This feature brings a high business value to your organization when you migrate a high volume of work definitions from a legacy system at the start of the implementation.

You can import the following attributes of a maintenance work definition using the work definition import spreadsheet:

The import of work definitions through the FBDI spreadsheet also supports management of complex and iterative work definitions, because you can create or update any work definition operation, including the impacted resources and materials.

Steps to Enable

Download and review the latest Work Definitions import template in the File-Based Data Import for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center. To import data using the template, follow the instructions in the Loading Data into Tables: Explained topic.

Role Information

View and Edit Meter Reading Transaction History

Asset meters support subscription-based billing, utilization, and condition-tracking for an asset. You can manually create meter readings using either the Maintenance application or a REST service. With this update, you can review, update, and disable the meter reading history records on the Meter Reading History page.

FEATURE DETAILS

MANAGE METERS FOR ASSETS 

The Asset Meters tab now displays the displayed reading and the life-to-date reading values.

Additionally, you can also select the History icon on the Asset Meters tab. This directs you to the Reading History page in the context of the selected meter. The icon is enabled only after the first meter reading history is created.

The following screenshot displays the Asset Meters tab with the new column values:

Asset Meter List

VIEW AND EDIT READING HISTORY 

Use the Reading History page to filter, sort, and edit the last active reading in history.  The last active reading is enabled for editing which lets you update the reading, the reading date, and the comments.  When you save the new reading, the same validations are applied, and the displayed reading and life-to-date values are recalculated.

The Reading History row also displays the net change value, which is the difference or delta value between historical readings. Additionally, all readings display a status value which gives you additional details about the reading.

The following is a screenshot of the Reading History page:

Meter Reading History

DISABLE EXISTING READINGS 

You can also choose to disable the last active reading in history.  This capability is useful when you need to retain the reading for historical auditing, but do not wish for it to be considered in calculations for subsequent readings in history.

The following is a screenshot that shows how you can disable a reading:

Disable Reading

ENTER NEW READINGS AFTER EDITING HISTORY

After you have edited or disabled historical readings, you can enter new readings on the Readings page. These new readings may be inserted either before or after a disabled row, as determined by the date or time entered.

The validations will then skip any disabled rows in history, looking for the last active reading row on which to base the calculation for the displayed and life-to-date readings.

The following is a screenshot of a new reading row:

New and Disabled Readings in History

CREATE INITIAL READINGS 

When you manually add a meter template to an asset, the start date-time is now based off the template start date, and not the application date and time. IPrior to saving the data, you can edit the date and time.

The following is a screenshot of the various date-time values for an initial reading:

Initial Reading

ENTER ROLLOVER READINGS 

For an absolute change meter, tthe application can automatically detect a rollover, and it systematically calculates the displayed and life-to-date readings based on the meter template. This reduces the complexity in the user interface, and provides you with a a seamless experience.

The following is a screenshot of a rollover reading:

Rollover Reading

ENTER RESET READINGS 

You can now know if you can reset a meter or not based on the reading type, which displays a list of values on the Enter Readings page. When you select the reading type as reset, the new reading value will be automatically set, as defined in the meter template, and can’t be edited. When you save your changes, a new reading is created, displaying a status of reset meter reading in history.

The following is a screenshot of the Enter Readings page and the Reading Type list of values:

Reset Reading

Steps to Enable

You must opt in 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: 11.13.19.04.0

Role Information

Enable E-Records and E-Signatures in Deferred Mode for Maintenance Exceptions

Enable deferred electronic records and electronic signatures for maintenance exceptions in Oracle Maintenance Cloud with Oracle E-Records and E-Signatures (ERES).

Companies in regulated industries must keep detailed records of their product manufacturing processes in accordance with the United States Food and Drug Administration (FDA) regulation on electronic records and signatures called the 21 Code of Federal Regulations (CFR) Part 11. Oracle E-Signatures and E-Records is a configurable framework which helps you in securely capturing, storing, retrieving, and printing electronic records and signatures.

With this update, you can close a maintenance exception through the user interface, a REST service, or the mobile application. When you close an exception, an electronic record is created and it supports the deferred capture of an electronic signature.

A transaction Maintenance Exception Closure, is introduced to enable or disable electronic signatures for exceptions. If electronic records and electronic signatures are enabled, the exception status reflects the current status in the approval process which works in conjunction with the approval workflow.

FEATURE DETAILS

MANAGE MAINTENANCE EXCEPTIONS USING E-RECORDS AND E-SIGNATURES (ERES)

When you are ready to close a maintenance exception, submit the exception for approval rather than directly closing it. This sends notifications to the approvers to review the electronic record and capture the electronic signatures. The exception is held in a pending approval status until all approvals are complete.

The following is a screenshot of the Maintenance Exceptions page:

Maintenance Exception Closure

GENERATE E-RECORD UPON APPROVAL 

The electronic records for maintenance exceptions are stored in a secured document repository and cannot be modified or deleted. You can search the electronic records based on any of the transactional information displayed in the electronic record in order to retrieve and print an electronic record.

The following is a screenshot of an e-record for a maintenance exception:

E-Record for Maintenance Exception

Steps to Enable

You must opt in 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                         

You must opt in to and enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Role Information

Manage Maintenance Work Orders Based on IoT Events

You can now create maintenance work orders based on Internet of Things (IoT) events. This new capability leverages the existing maintenance programs and work order execution functionality.

FEATURE DETAILS

ASSETS ENABLED FOR IoT

You can choose to specify an asset as IoT enabled when you create an asset using the Manage Asset page or a REST service. If set to yes, the newly created asset will synchronize and create a digital twin in the IoT Asset Monitoring Cloud. Once available in IoT, it will be available for monitoring, condition event triage, and inclusion in maintenance program optimization.

The following is a screenshot of the IoT-Enabled indicator of an asset:

IoT Digital Twin

IoT WORK ORDER CREATION 

Within the latest work requirement, there is a new forecast method named Condition Event, which is available only for noncycle-based requirements. If you enable this forecast method, you can define one or more condition codes, which are used to provide a cross-reference for an asset and its applicable Work Definitions during the REST process.

The following is a screenshot of the parameters that you can define to generate a forecast:

Work Requirement Definition

Steps to Enable

You must opt in 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: 11.13.19.04.0

Role Information

Update 18B

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 APR 2018   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.

Customers Upgrading from Release 12

If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (updates 17B - 17D, as well as, updates 18A - 18B) to learn about all of the features available in release 13.

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)

We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can opt in to a feature in two ways:  by using the New Features work area, or by using the Setup and Maintenance work area.

To opt in using 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 that you want to opt in to.
  4. On the Edit Features page, select the Enable option for the feature, and then click Done.

To opt in using the Setup and Maintenance work area:

  1. Click the Navigator, and then click Setup and Maintenance.
  2. On the Setup page, select your offering, and then click Change Feature Opt In.
  3. On the Opt In page, click the Edit Features icon.
  4. On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close
  5. Click Done.

Feature Summary

Action Required to Enable Feature

Feature

None (Automatically Available)

Enable via Opt In UI Only

Enable via Opt In UI Plus Additional Steps

Not Enabled via Opt In UI but Setup Required

Issue Service Request

Maintenance

Delete a Work Definition

Manage Meter Reading Using REST Services

Manage Meter Templates Using a REST Service

Maintenance

Delete a Work Definition

You can now physically delete a work definition that was created through either a manual or an automatic process and has not been referenced in work orders or published in cost scenarios.  Deletion removes the work definition and all of its versions.  You can correct a data entry mistake and create a new work definition by reusing the work definition name and item as intended.

You can delete a work definition on the Manage Work Definitions page:

Manage Maintenance Work Definitions

Manage Work Definition

You can delete all versions of a specific work definition only if this work definition is not used in any maintenance program or in any maintenance work order.

Steps to Enable

You must opt in to and enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Role Information

Manage Meter Reading Using REST Services

Asset meters provide the ability to support subscription-based billing, utilization, and condition tracking for an asset.  You can create and reuse meter template definitions across multiple assets. After you associate a template to an asset, you can record the meter reading history. Oracle Maintenance Cloud provides an external REST web service to support the recording and review of meter reading history records.

The Meter Reading REST API supports the creation and review of meter reading history.

CREATION AND REVIEW OF METER READINGS

You can record the following attributes for each meter asset, whether it is active or inactive:

The validations and error messages during the REST payload processing will make you aware of any issues with the data being submitted. You can correct the issues and resubmit the readings via the REST payload.

If a meter reading resulted in a meter rollover, you can specify the event occurred, which relaxes certain validations and allows reading capture.

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

The following points must be considered:

Key Resources

Role Information

Manage Meter Templates Using a REST Service

Meters provide the ability to support subscription-based billing, utilization, and condition-tracking for an asset. You can create and reuse meter template definitions across multiple assets. Oracle Maintenance Cloud provides an external REST web service to support the creation, review, and update of information for template definitions. Optionally, you can also associate applicable inventory items to each template definition by organization with the web service. During maintenance asset or customer asset creation, based on an item in an organization, the application will identify template definitions that match and automatically create the meters for an asset.

The Meter Template REST API supports the following:

DEFINE AND UPDATE METER TEMPLATE DEFINITIONS

Meter templates are created to model a physical meter which is installed on an asset. These physical meters have mechanical or electrical properties which define how they capture and record an asset’s utilization over time.  The template provides the basis for controlling how the corresponding meter readings are recorded, while enforcing specific data validations during reading capture.

Meter templates can be modeled for both continuous and gauge type of meters. A continuous meter can be an odometer while a gauge meter can be a thermometer. After creation, a template can be associated to one or many assets, which share the same type of meter, but will have unique associations and meter reading history.

Use the following actions in REST API for this purpose:

ASSOCIATE ITEMS TO A METER TEMPLATE DEFINITION

During meter template definition creation or update, inventory items can be associated as child resources of the template.

Use the following actions in REST API for this purpose:

Steps to Enable

No steps are required to enable this feature.

Key Resources

Role Information

Update 18A

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
05 FEB 2018

Maintain Calendar-Based Preventive Maintenance Plans

Updated document. Added feature delivered in update 18A.
19 JAN 2018   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.

Customers Upgrading from Release 12

If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (updates 17B - 17D, as well as, updates 18A - 18B) to learn about all of the features available in release 13.

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)

We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can opt in to a feature in two ways:  by using the New Features work area, or by using the Setup and Maintenance work area.

To opt in using 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 Opt In for any feature that you want to opt in to.
  4. On the Edit Features page, select the Enable option for the feature, and then click Done.

To opt in using the Setup and Maintenance work area:

  1. Click the Navigator, and then click Setup and Maintenance.
  2. On the Setup page, select your offering, and then click Change Feature Opt In.
  3. On the Opt In page, click the Edit Features icon.
  4. On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close
  5. Click Done.

Feature Summary

Action Required to Enable Feature

Feature

None (Automatically Available)

Enable via Opt In UI Only

Enable via Opt In UI Plus Additional Steps

Not Enabled via Opt In UI but Setup Required

Issue Service Request

Maintenance

Capture Purchase, Registration, Installation, and In-Service Dates for Customer Assets

Capture Information for Upgrades and Replacements of Assets

Select and Add Components from a Customer Asset Structure

Maintain Calendar-Based Preventive Maintenance Plans

Define Meters for an Asset

Create Customer Asset Analyses and Reports Using Oracle Transactional Business Intelligence

Pick Materials for Work Orders

Maintenance

Capture Purchase, Registration, Installation, and In-Service Dates for Customer Assets

With this update of Installed Base, you can now capture the purchase, registration, installation, and in-service dates of customer assets in addition to shipment and termination dates of assets as captured with the previous Installed Base updates.

All these dates are exposed in the customer asset REST API and the customer asset import spreadsheet which allows you to create and update the assets with the corresponding dates.

Certain consistency validations are applied to these dates at the time of processing. They are summarized in the following table:

Asset Date

Validations

Purchase 

  • Cannot be a future date

Registration

  • Cannot be a future date
  • Cannot be before the purchase date
  • Cannot be before the shipment date
  • Cannot be captured if the purchase date is not provided

Installed Date

  • Cannot be a future date
  • Cannot be before the shipment date

In-Service Date

  • Cannot be a future date
  • Cannot be before the shipment date
  • Cannot be before the installation date

The dates are cleared from the asset if the customer information changes, or if a serialized asset is returned for credit, or is directly returned to inventory. However, all values are retained in the asset transaction history.

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

With this update of Installed Base, the creation and update of these dates are not interfaced to Enterprise Contracts.

Role Information

The following privileges and roles are required to use this feature:

Capture Information for Upgrades and Replacements of Assets

Capture information related to upgrades and replacements of assets from order management systems using a web service to ensure accurate contract updates.

A new REST service, Customer Asset Transactions, has been added to Installed Base which helps you perform the following tasks:

If you are using Oracle Order Management Cloud as the source of orders, then only intended processes supported. If you are using an external order management application as the source of orders, then only completed processes are supported.

CAPTURE REPLACEMENT OR UPGRADE INFORMATION USING ORACLE ORDER MANAGEMENT CLOUD

The following diagram depicts a product replacement flow using Oracle Order Management Cloud:

Regular Replacement Flow with Usage of Oracle Order Management Cloud

The following table further explains the behavior of the various applications that are involved at the successive steps:

#

Steps

Order Management

Installed Base

Enterprise Contracts

1

A product is sold and shipped to the customer.

Order is entered and fulfilled.

A customer asset is created.

Related product contracts are created.

2

The product has a defect. An agreement is made with the customer to replace the product.

None

None

None

3

A return order is entered for the original product. 

Return order is booked.

None

None

4

A sales order is entered for the shipping of the replacement product. 

Sales order is  booked.

None

None

5

A call is made to the Installed Base transaction web service, requesting for the asset to be replaced, and recording the return and the replacement sales order.   

None

The intended replacement is recorded and interfaced to Enterprise Contracts.  

The intended replacement is recorded.

6

The original product is returned.

Return order is  fulfilled

The original customer asset is updated as returned and terminated.

The return is recorded.

7

The replacement product is shipped.

The replacement sales order is  fulfilled.

The replacement customer asset is created.

The contracts are updated from old to new asset.

At the time of the Customer Asset Transaction call, the following information must be provided:

It must be noted that when an asset is identified as pending for replacement, this state is stored in Installed Base and it is not possible to update this asset anymore from this point forward. When the flow is completed, this asset will be terminated when returned. Otherwise the flow can be canceled, in which case the asset is made available for update again.

CANCEL REPLACEMENT OR UPGRADE INFORMATION WITH ORACLE ORDER MANAGEMENT CLOUD

The intended replacement or upgrade operation can be canceled in Installed Base and Enterprise Contract if the operation is not fully completed and either none of the return and sales orders are fulfilled or only one of the two is fulfilled.

On the side of Installed Base and Enterprise Contract, the cancellation is achieved by calling the Customer Asset Transaction REST service with a cancellation transaction type and requesting for the previous transaction to be canceled.

CAPTURE REPLACEMENT OR UPGRADE INFORMATION WITH AN EXTERNAL ORDER MANAGEMENT SYSTEM

The following diagram depicts a product replacement flow using an external order management system:

Regular Replacement Flow with Usage of an External Order Management System

The following table further explain the behavior of the various applications that are involved at the successive steps:

#

Steps

External Order Management System 

Installed Base

Enterprise Contract

1

a product is sold and shipped to the customer.

The order is entered and fulfilled, and the asset is interfaced to Installed Base.  

A customer asset is created.

Related product contracts are created.

2

The product has a defect. An agreement is made with the customer to replace the product.

None

None

None

3

A return order is entered for the original product. 

Return order is booked.

None

None

4

A sales order is entered for the shipping of the replacement product. 

Sales order  is booked.

None

None

5

The original product is returned.

Return order is fulfilled.

None

None

6

The replacement product is shipped.

Replacement sales order is  fulfilled and the asset is interfaced to Installed Base.  

A customer asset is created.

None

7

A call is made to the Installed Base Customer Asset Transaction service, requesting for the completion of the replacement.

None

The replacement is recorded and interfaced to Enterprise Contracts. 

The contracts are updated from old to new asset.

The following points must be considered when you use an external order management system:

Steps to Enable

No steps in Installed Base are required to use this feature if the source of orders is an external order management application.

If the source of orders is Oracle Order Management Cloud, the following behavior modifications must be implemented in Order Management:

Tips And Considerations

In this update, note the following details about this feature:

Role Information

The following privileges and roles are required to use this feature:

Select and Add Components from a Customer Asset Structure

The Select and Add Customer Asset feature facilitates the selection of assets for your task at hand, by enabling you to optionally include asset components in the search results, and by enabling you to view a particular asset in the context of its structure.

The Select and Add Customer Asset dialog is a common installed base component currently used by the Enterprise Contract product in the context of adding covered assets to contract lines.

INCLUDE OR EXCLUDE ASSET COMPONENTS IN THE SEARCH RESULTS FOR CUSTOMER ASSETS 

With this release, a new check box Include asset components is added to the Add: Customer Assets dialog box. By selecting this check box you can include all assets matching the other search criteria regardless of the assets being top-parent assets or component assets.

If you do not select this check box, only top-parent assets are retrieved in the search results. This is the default behavior.

The following examples illustrate how you can choose to include or exclude asset components in the search results:

  1. In the following screenshot, assets of the customer Business World are searched for and the Include asset components check box is not selected. As a result, only top-parent assets are listed in the search results:     

Exclude Asset Components from the Search Results

  1. In the following screenshot, assets of the customer Business World are searched for and the Include asset components check box is selected. As a result, all top-parent assets along with their components are listed in the search results and are available for selection.

Include Asset Components in the Search Results

SELECT ASSET COMPONENTS IN CONTEXT OF THEIR ASSET STRUCTURE

In the search results table, for each asset, a new icon Asset Relationship has been introduced. The icon is enabled only if the corresponding asset is part of an asset structure.

When you select the Asset Relationship icon for an asset, the Add: Customer Assets dialog box will change to a hierarchical view of the selected asset in the context of its structure enabling you to select it, select its parent, or its child. You can also select multiple assets from the hierarchical view.

The following example illustrates how asset components are displayed in the context of their structure:

  1. All assets of the customer Business World, including its components, are searched.

Initial Search Results

  1. The Asset Relationship icon for the asset TOP-001-CMP1 is selected. The Add: Customer Assets dialog is refreshed to show a hierarchical view of the asset component in context of its structure.

Hierarchical View of the Asset Component in the Context of its Structure

Steps to Enable

No steps are required to enable this feature.

Role Information

The following role is required to use this feature

Maintain Calendar-Based Preventive Maintenance Plans

Calendar-based maintenance programs provides a group of programs to plan, monitor, and complete maintenance operations to minimize equipment breakdowns and unscheduled repairs. When you manage your equipment maintenance needs, you define the type and frequency of each maintenance requirement for each asset in your organization.

The following figure illustrates the relationships between the Maintenance Programs, forecast and preventive maintenance work orders.

relationships between the Maintenance Programs, forecast and preventive maintenance work orders

Relationships Between the Maintenance Programs, Forecast and Preventive Maintenance Work Orders

FEATURE DETAILS

The calendar-based maintenance programs is designed to support the following:

MAINTENANCE PROGRAM

Organize and Group Maintenance Activities

Calendar-based maintenance programs are independent from any asset structure or plant organization. Calendar-based maintenance programs allows you to group your assets and maintenance activities to optimize your maintenance strategy.

Define Work Requirements for Asset Number or Asset Item

Calendar-based preventive maintenance plans allows you to define maintenance work requirement for an asset or an item. Defining a maintenance activity for an asset will automatically assign this activity to all the existing assets created from this item, but also to future assets you will create.

Although, if required, you can manually manage a list of excluded assets.

Define Schedule Patterns and Associate Work Definition

Calendar-based maintenance programs introduce the concept of work requirement. A work requirement is essentially composed by:

Schedule pattern allows you to easily create daily, weekly, monthly, or yearly patterns with various options.

All the asset numbers or an asset items and work definitions you define within your organization can be associated to a work requirement.

Forecast the Maintenance Work and Generate Work Orders

Calendar-based preventive maintenance plans allows you to generate maintenance forecast. This could be achieved manually or by scheduling operation on regular basis.

You can decide to forecast maintenance work for a single or multiple calendar-based preventive maintenance plans.

Going forward, you can create maintenance work orders based on maintenance work you forecast.

Manage Concurrent Requirements

During the creation of your maintenance plans, you can decide how to handle concurrent requirements.

A typical concurrent requirement use case is when you define a maintenance operation every other day, but you also need to perform different operations every Friday. When both occur on the same day, calendar-based preventive maintenance plans gives you the option to decide if you want to suppress one maintenance operation or merge both of them.

Steps to Enable

You must opt in to and enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Role Information

Define Meters for an Asset

Meters provide the ability to support subscription-based billing, utilization, and condition tracking for an asset. Meter definition templates can be created and reused across multiple assets. Once associated to an asset, you can record the meter readings through a user interface or a web service.

FEATURE DETAILS

ASSET METERS

Manage Meters for an Asset

The Meter tab will provide a list of all the meters which have been associated to an asset.  You can create new Meter Templates or add an existing Template to an asset.

After a Template is created or added to the Meter List, you can further define the start and end dates as well as an initial reading.  After saving this, a unique association is created between the asset and the meter.

Asset Meter List

Define New Meter Templates for an Asset

Meter templates are created to model a physical meter which is installed on an asset. These physical meters have mechanical or electrical properties which define how they capture and record an asset’s utilization over time.  The template provides the basis for controlling how the corresponding Meter Readings are recorded, while enforcing specific data validations during reading capture.

Meter Templates can be modeled for both Continuous, for instance an odometer, and Gauge, for instance a thermometer, types of meters.  Once created, a template can be associated to one or many assets which share the same type of meter, but will have unique associations and Meter Reading History.

Create Meter Template

Assign Existing Meter Templates to an Asset

Existing meter templates can be searched, selected, and added to a meter’s list. Searching by an existing asset provides a quick capability to associate existing meters between similar assets.  Else, you may search without any search attributes selected.

For a result row, you can easily view meter template details in a dialog box which provides insight into the template’s behavior.  Inactive meter templates and duplicate meters, that is meters already associated to the asset, cannot be added to the asset.

Assign Existing Meter Template

Record Meter Readings for an Asset

You can enter new meter readings, date, and comments for each meter in the list, whether active or inactive.

The new readings for each meter must follow the validation rules which are defined by the meter template definition.  They must also occur sequentially in history, as governed by the reading date and time being entered.  Validations and error messages, both in-row and at the page level after saving, will alert you to any issues with the data being entered. You can correct the issue and save the readings again.

If a meter reading resulted in a meter rollover, you can indicate the event occurred, which relaxes certain validations and allows reading capture.  You can easily view the meter template details for each meter row in a dialog box which provides insight into the template’s behavior.

Enter Meter Reading

Steps to Enable

You must opt in to and enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Role Information

Create Customer Asset Analyses and Reports Using Oracle Transactional Business Intelligence

With this update, the Installed Base business intelligence solution provides you a complete definition of customer asset and its configuration. The solution delivers an Oracle Transactional Business Intelligence layer over Installed Base data enabling operational reporting on an easy to use platform.

Two subject areas are available:

You can create analyses and reports with data from the subject areas to answer the following key business questions:

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

In the subject area Installed Base - Customer Asset Real Time, the main dimension is Customer Asset Details. It includes the customer asset’s identifying attributes, the customer and its current location, and the associated sales order information. The dimension Customer Assets has the metric Customer Asset Count.

Role Information

Pick Materials for Work Orders

In Oracle Maintenance Cloud, material is manually issued from a subinventory to the work order or is backflushed from the inventory based on the material assigned to the work order. Prior to this update, there was no way to pick and stage material for production. In industries with long lead times or many common materials, there is a need to move material from the warehouse or a common stock subinventory to a shop floor supply subinventory based on the jobs that are scheduled for production in the near future.

Companies that backflush material commonly mark this supply subinventory as nonreservable and not available-to-promise supply to prevent production material from being used for other purposes, while giving cost accountants a convenient way to report on the value of the material that is staged for production but not yet issued to work orders. Companies that require a manual transaction to charge material to the job often have the picking process issue the material directly to the work order, saving their shop floor operators from having to perform a second manual transaction.

In the warehouse, the physical picking process is the same whether the demand is a work order, a shipment, or a movement request, and it is often performed by the same personnel. With this update, enhancements to the products allow you to pick work orders from Oracle Inventory Management Cloud. There are four aspects to the enhancements:

REQUEST WORK ORDER MATERIAL PICKING

Initiate the picking task to ensure material-tracking and timely availability of materials during Mainenance. You can initiate this process from the Manage Maintenance Work Orders task and the Manage Material Availability Assignments task.

You can also schedule the picking task periodically to generate the picking request.

In some companies, the person requesting for picking of work orders may be different from the person managing the work orders. In such cases, the Pick Materials for Work Orders task in the Work Execution and in the Inventory work areas allows you to choose parameters based on which you want to request for picking of materials. The parameters allow you to specify the following:

The pick slip grouping rule and the pick slip printing attributes default from the plant parameters you have specified, but they can also be overridden.

You can select the Pick Materials action to initiate the scheduled process. The scheduled process creates a movement request to move the components to the appropriate shop floor location.

Pick Materials for Work Orders Scheduled Process

In many companies, the person that is managing and releasing work orders to the shop floor is the same person that initiates the pick process to stage material for production. In such cases, you can directly release and pick components from either the Manage Maintenance Work Orders task or the Material Availability Assignments task in the Maintenance Management work area.

You can select one or more maintenance work orders and select the Release and Pick action. You are asked to confirm the pick slip grouping rule that should be used, whether or not you want to print the pick slip, and if you want to force each work order to be picked completely.

After you submit the request, the application will release all unreleased work orders for production and submit the background process to generate a pick request for all components that are eligible for picking based on the inventory picking rule, plant parameters, and the picking status.

You can also select the Release and Pick action to repick an order that was already released and is partially picked.

The scheduled process generates a movement request to move the components to the applicable shop floor location.

Picking from Manage Maintenance Work Orders Page

Picking from Material Availability Assignments Page

EXECUTE PICKING IN THE WAREHOUSE

When you initiate picking in Maintenance, a maintenance  movement request is created in Inventory. Maintenance passes the pick slip grouping rule, the print pick slip parameter, the pick complete indicator, as well as indicates for each component whether the component will be issued directly to the work order or moved to the supply subinventory, based on the supply type of the component and the plant parameters setup.

After the material movement request is created, Inventory reserves and picks material using the scheduled process Print Movement Request Pick Slip Report.

The pick slip is generated using the pick slip grouping rule assigned in Maintenance. The pick slip grouping rule allows you to group pick slips in the warehouse and by a variety of pick slip attributes such as work order number, work area, work center, and push or pull activity.

Using the Confirm Pick page in Inventory, you can optionally select pick slips by pick slip type Shop Floor to confirm the details of the picked material, to move the material to the destination subinventory defined on the work order, and to update inventory balances.

After pick confirm, the application will either issue materials or move materials based on values passed from Maintenance.

The allocation for the lines eligible for partial picking is done based on the on-hand quantity available for the component. The work order is eligible for pick release after the partial pick has been performed for a work order component. Maintenance sets the work order pick release status to Pick Partial based on what Inventory was able to pick.

VIEW ALLOCATED QUANTITY AND PICKED QUANTITY IN MAINTENANCE

You can view the allocated and picked quantities for each material of the work order in the following pages:

Allocated and Picked Quantity in Edit Operation Items

Allocated and Picked Quantity in Material Availability Details

MANAGE WORK ORDER CHANGES

The application allows you to monitor and manage changes to work orders and the picking process in the following manner:

Steps to Enable

You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Also, the following plant-level parameters have been added to control the default behavior of the work order picking process for a given facility, and give you the ability to do the following:

Manage Plant Parameters

Role Information

With this update, a new functional privilege for work order picking has been added and can be assigned to any maintenance or inventory user.  Users with that privileges will have access to this feature.