Reverse Auto-Populate (RAP) is Not Updating Destination Field When Record Status Meets Status Filter Value
(Doc ID 2452285.1)
Last updated on MARCH 23, 2022
Applies to:
Primavera Unifier Cloud Service - Version 18.7 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
After defining a reverse auto-populate (RAP) on a date in a BP and the Approved status is reached, the date is not reverse auto-populated into the destination field.
EXPECTED BEHAVIOR
-----------------------
Moving BP record through workflow will trigger reverse auto-populate and successfully update destination field.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Define a reverse auto-populate on a field in an Upper Form of a BP. Define a Status condition for the RAP - for example, Approved.
2. Move the BP record through a workflow (and update RAP field with a value for Example Actual Finish Date) to a point where BP record Status in Approved.
3. Check the destination RAP field to see if updated. For example, Actual Finish date in an Activity Sheet.
4. Notice that Actual Finish date is not updated via RAP date from the BP record.
BUSINESS IMPACT
-----------------------
Due to this issue, users cannot reverse auto-populate destination fields.
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 |
Cause |
Solution |