Batch C1-REPC1 Not Stamping Correct Start Date
(Doc ID 2999418.1)
Last updated on JANUARY 23, 2024
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 5.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On RMB v5.1.0.0.0, C1-REPC1 batch not stamping the correct Start Date.
STEPS:
1) Load 2000 enrollments
2) Run Batch C1-REPC1
3) Cancel the batch in the middle of a run
4) Re-submit Batch C1-REPC1
- processed all the outstanding records
- got illegal session exceptions or null pointers
5) Observe discrepancy (incorrect date in start_dt column of memberships) in C1_PRC_RULE_MEMB
MEMBERSHIP_ID PRICING_RULE_ID MEMBPR_START_DT MEMBPR_END_DT PRIMARY_PRICING_RULE_ID BATCH_NBR STATUS
1 001236777328445 207905202373535 1/1/2024 5/31/2024 22 A
2 001236777328445 242106202370085 4/1/2024 5/31/2024 207905202373535 22 A
3 001236777328445 186206202305585 4/1/2024 5/31/2024 207905202373535 22 A
4 001236777328445 112008202303049 4/1/2024 5/31/2024 207905202373535 22 A
If we run CM-FLUSH or restart TPW before resubmitting the batch in step#4, then this incorrect date is not stamped.
But this should work without the restart or flush.
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 |