RAP Fails When Destination Is in a Different Project/Shell - Reason: Integration Interface Not Defined for Business Process
(Doc ID 2846242.1)
Last updated on JANUARY 10, 2024
Applies to:
Primavera Unifier Cloud Service - Version 21.10 to 21.12 [Release 21.10 to 21.12]Information in this document applies to any platform.
Symptoms
On Unifier : Version 21.10
When Reverse Auto-Population (RAP) is designed to RAP to a Business Process (BP) record in a different Project/Shell:
Expected Result
The RAP should be triggered and the destination record should be updated with the entry from the source.
Actual Result
When Reverse Auto-Population (RAP) is triggered the event fails and a system generated e-mail notification is sent with:
Reverse Auto-populate : Failed
Reason: Integration interface not defined for business process.
It is noted that the entry for "Destination Business Process" in the e-mail is empty - this should have been populated with some entry.
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 |
| References |