Account Modeling Where One Account Having Different Billing Profile
(Doc ID 2752762.1)
Last updated on FEBRUARY 16, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Below is the Hierarchy defined by the Customer
Account 16743 is the parent accounts and below are the child accounts
Child_Account 16743_B1_1 has two service (Service s1 and Service s2)
Child_Account 16743_B2_1 has Service S3
Child_Account 16743_B2_2 has Service S4
The Child Accounts (16743_B1_1,16743_B2_1,16743_B2_2) bills are paid by parent Account 16743 .
Following are clarification questions:
1. Is it fine we generate two invoices every month under 16743 each running say example on different ACTG_CYCLE_DOM?
2. Is it correct approach to extend /billinfo class and add some additional custom fields to capture attributes varchar field data like "prepaid"/"postpaid" ?
3. Is it correct approach to add custom fields under /billinfo class?
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