My Oracle Support Banner

OG Bar Creating With One Day Delay After P2P (Doc ID 2988590.1)

Last updated on NOVEMBER 28, 2023

Applies to:

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


Question 1: Consider the below scenario
1. Create an account with service
2. Bill the account
3. Make collection entry
4. Complete the first Outgoing (OG) bar
5. Add Promise-to-Pay (P2P) with 5 days, OG with P2P due date is created
6. Run pin_collections utility on same day
8. Observe new OG bar date (it is extended to one day)

There is customization involved for collection action, but there is no customization in P2P expiry logic. Collection is getting rescheduled by out-of-box (OOB) code when P2P is getting expired by running pin_collection_process on the day of P2P expire. How to resolve this issue?
Question 2: If the rescheduling is done one day after the P2P due date, why is OG bar due date has the same date as that of P2P due date on the creation date? Does the OG bar date reschedule to +1 day when the collection process is run on P2P due date?


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.