My Oracle Support Banner

W1-ASSET Not Superseding When An Outstanding PM Activity Already Exists (Doc ID 3017460.1)

Last updated on APRIL 22, 2024

Applies to:

Oracle Utilities Work and Asset Management Enterprise Edition - Version 2.3.0.0.0 to 2.4.0.1.1 [Release 2.3 to 2.4]
Information in this document applies to any platform.

Symptoms

On : 2.3.0.0.0 version, Functional

ACTUAL BEHAVIOR
---------------
W1-ASSET not superseding when an outstanding PM activity already exists

We have run into a scenario where there were several 12 month and 3 month PMs to fire on the same day. I've set them up to supersede as the documentation recommends. This is working for the majority. However, I ran into several where both the 3 month and the 12 month kicked out on the same day when W1-ASSET batch ran. The 3 month would actually kick out before the 12 month which was odd because it should be kicking out after. I noticed the 3 month would have a WO number of 100001 and then the 12 month would have a WO number of 100002. In this situation, the logic the batch used for superseding couldn't have worked because the 3 month was kicking out prior to the 12 month. My understanding is the W1-ASSET logic kicks out the 12 month first and then checks the service history type on the 12 month PM to determine if a 3 month needs to be kicked out or not. Once it sees the 3 month service history on the 12 month PM, it would skip generating a 3 month PM. What we found is the ones that are not superseding have an outstanding 3 month PM work order/activity already out there. Not for sure why this would prevent the superseding logic from happening, but it seems some logic to verify you can create multiple in process activities is happening first and creating the new PM activity before the superseding logic can happen. we can't see the underlying code to say for sure, but the common theme is superseding does not seem to work when there's an outstanding PM work activity out there already for the higher frequency PM that would normally be superseded.

Expected Result: Work Activity should get created for the low sequenced maintenance trigger and then for the next sequenced maintenance trigger i.e., Work Activities should get created based on the ascending order of Maintenance Triggers sequence number.

Actual Result: Work Activities are getting created based on the ascending order of Maintenance Trigger ids.

 

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.