My Oracle Support Banner

EMM: When Priority Code Is Modified On Service Request, It's Not Carried Over To Work Order After Upgrade (Doc ID 2422975.1)

Last updated on JULY 13, 2018

Applies to:

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

Symptoms

On : 9.2 version, PUM # 25.Work Order

ACTUAL BEHAVIOR
---------------
 When Priority Code is modified on SR, it's not carried over to Work Order after upgrade to PUM-25

After upgrade to PUM-25 when Priority Code is modified on SR, it's not carried over to Work Order. This functionality worked fine in PUM-19.

EXPECTED BEHAVIOR
-----------------------
Priority code should remain same as that of the SR.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Add a new SR with priority code of 3.
2. Create a WO by changing the priority to 1.
3. Go back to WO and still shows as 3 instead of High.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use correct priority codes on WO's via SR.

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!


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