My Oracle Support Banner

Incorrect OutGoing Due-date After Promise2Pay Completion (Doc ID 2979906.1)

Last updated on OCTOBER 16, 2023

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


In a customer scenario, old OutGoing (OG) bar due date is modified to backdate, and then P2P (Promise2Pay) is applied, then pin_collection process is changing the new OG bar date to old OG bar’s original date.

Steps to replicate:

1.Create an account and ensure it enters collections and automatic OG bar is created (taking as OGBarD1 date).
2.As per business requirement this date OGBarD1 is being preponed (New Date OGBarD2). Here OGBarD2 < OGBarD1.
3.Promise2Pay (P2P) is placed on date D3 where OGBarD2 --> P2P due date < OGBarD1
4.When P2P is created, OG bar also triggered at Same time with due date OGBarD4 (which is equal to P2P due date)
5.When collection process is run on this OG bar due date OGBarD4, it is shifting back to OGBarD1.

Query: Why there is shift in the new OG bar of P2P?


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

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