VGBP - Approval Workflow - Construct Mapping - TXN_DATA Not Getting Updated With New Value
(Doc ID 2737723.1)
Last updated on FEBRUARY 12, 2021
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 2.6.0.1.0 to 2.9.0.0.0 [Release 2]Information in this document applies to any platform.
Symptoms
On : 2.6.0.1.0 version, ENV - Environment
ACTUAL BEHAVIOR
---------------
TXN_DATA not getting updated with new value
EXPECTED BEHAVIOR
-----------------------
TXN_DATA should be updated with new value
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Modify the construct Mapping (in our case, a 6 digit BIN got updated to 8 digit BIN).
2) Submit it for approval.
3) On Approval Workflow compare screen, the modified values are shown properly.
4) Click Approve.
5) Still the old values are shown in the TXN_DATA.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot update with new value for TXN_DATA
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 |