My Oracle Support Banner

Merge Work Definitions Option in Maintenance Programs is Skipped in Some Cases When Generating Work Orders (Doc ID 2606520.1)

Last updated on NOVEMBER 06, 2019

Applies to:

Oracle Maintenance Cloud Service - Version 11.13.19.07.0 and later
Information in this document applies to any platform.

Symptoms

Creating work orders using maintenance program is skipping merge of work
definition contrary to setups in maintenance program requirement.

There are 3 work definitions for the maintenance of an asset e.g. oil change,
filter change and tire rotation. As per the requirement, a program required
so work orders will be generated for 800 hours, 1600 hours and 3200 hours of
the run for the asset. The meter runs 24 hours in a day, so the "Base
Utilization Rate per Day" is 24 "Number of Readings for Calculating a
Utilization Rate" is 1 . The program and work definitions are set to merge.
For 800 hours only work definition for 800 hours should apply which is oil
change, while for 1600 hours work definition for 800 and 1600 hours merge (so
it should do oil and filter change) while for 3200 hours, work definitions
for 800, 1600 and 3200 hours need to merge (i.e. oil change, filter change
and tire rotation).

The program requirement has 4 intervals (800, 1600, 2400 and 3600 hrs) and is
forecast using cycle. The basis for the next forecast due date is based on
meter with a base interval of 800 hrs. Work definition for 800 hrs will be
due in 1st cycle (and repeats in the cycle), work definition for 1600 hrs
will be due in 2nd cycle (and repeats in the cycle) while work definition for
3200 hrs will be due only at 4th cycle and no work definitions are due in 3rd
cycle i.e. for 2400 hrs.

The issue is though the work orders are created for 1st, 2nd, and 4th
intervals but the work definition for the 3200 hrs and 1600 hrs is not merged
on to the 4th intervals. In the backend it seems they merged to third 3rd
interval but that does serve the purpose of the requirement since work order
is not created for the 3rd interval.

EXPECTED BEHAVIOR
-----------------------
Work orders created for the 4th interval should merge operations in work
definitions for 800, 1600 and 3200 hrs.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create 3 maintenance work definitions, with 1 operation each for 800 hrs,
1600 hrs and 3200 hrs
2. Create a meter with Base Utilization Rate per Day for 24.
3. Create a maintenance program by navigating to Supply Chain Execution >
Maintenance > Task list > Manage Maintenance Program
3. Set the 'Concurrent Requirement' to 'Merge', it has 4 intervals (800,
1600, 2400 and 3600 hrs) and is forecast using cycle. The basis for the next
forecast due date is based on meter with a base interval of 800 hrs.
4. Add the work definitions for 800, 1600 and 3200 hours in the maintenance
program. Work definition for 800 hrs will be due in 1st cycle (and repeats in
the cycle), work definition for 1600 hrs will be due in 2nd cycle (and
repeats in the cycle) while work definition for 3200 hrs will be due only at
4th cycle and no work definitions are due in 3rd cycle i.e. for 2400 hrs.
5. On generating the forecast and creating work orders, the work orders are
created.
6. See that for work order generated for 3200 hours only the operation for
work definition 800 hours is available while they are expecting it to have
operations for 800, 1600 and 3200 hours.


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.