EMM: PM LINKING BY CYCLE OCCURRENCE DATA NEEDS TO BE ADJUSTABLE ON PM LINKING TAB (Doc ID 2308134.1)

Last updated on SEPTEMBER 15, 2017

Applies to:

PeopleSoft Enterprise FIN Maintenance Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms


ACTUAL BEHAVIOR
---------------

If new equipment/PM Schedules are put into service from today's date moving forward, everything is on schedule, due dates align and PM Linking works as expected. However, not all equipment is new and therefore not all PM next due dates should be calculated from today's basis date. PeopleSoft delivered next due dates need to be coded to match the legacy due dates. Unfortunately, the occurrence data (which is used to calculate when the linking should occur) is not adjustable in PeopleSoft and therefore limits customer's ability to match the PM cycles they have in their
Legacy system.

Real world scenario: Facility A is going live on 7/1/2017 and Asset 1 has a Minor monthly schedule and a Major Quarterly. Both next due dates are on 7/1/2017. However 2 minors have already been completed in May and June previous to go-live. That would mean in their Legacy system (if we are translating terms into PeopleSoft) the minor schedule is on its 2nd occurrence and July would be the 3rd occurrence. Therefore in July, only the Major should be created, suppressing the Minor.

PeopleSoft cannot be retrograded to calculate that on 7/1/2017 the minor should be suppressed and the Major created resulting in the Major PM not being generated (skipped) when in the Legacy system it would have been generated. The needed outcome could not be achieved by adjusting the basis dates, the effective dates, and etc.


EXPECTED BEHAVIOR
-----------------------
As the customer is migrating from their legacy system, either the PM linking current occurrence and current cycle fields should be updated behind the scenes, or the occurrence data on the PM Linking tab should be adjustable so that when the projection process runs it will account for the maintenance generated in the legacy system.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a Monthly Schedule with Date of Month 01 and Interval 1
Main Menu> Maintenance Management> Preventive Maintenance> PM Schedule Management Setup> Location Schedule
2. Create another Monthly Schedule with Date of Month 01 and Interval 2 for the same asset id
This schedule will act Primary Schedule and the previous one will be secondary
3. Add the schedule created in Step 1 as Secondary Schedules to the Schedule created in Step 2
4. Run the Projection for both the schedules
Main Menu> Maintenance Management> Preventive Maintenance>Run projection
5. View the projection Summary for that process instance
Main Menu> Maintenance Management> Preventive Maintenance>View Projection Summary
There is no PM linking for the created projections.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the customer is unable to configure the occurrence data on the PM Linking tab of the PM Schedule such that when the projection process runs it will account for the maintenance
generated in the legacy system.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms