Invoice Construct Config To Share Same Usage Acct Mapping To Invoice Acct In Discreet Hierarchy
(Doc ID 2469378.1)
Last updated on MARCH 26, 2019
Applies to:Oracle Financial Services Revenue Management and Billing - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
As per requirements for our next phase, we need to invoice certain charges of particular usage account to two different invoice accounts (may or may not belong to usage account hierarchy) on the basis of price item code. Currently, system does not allow usage account to map to different invoice constructs.
Usage account: BIN1-UA1
Receives transactions belonging to Price Items: BL1 and BL2
Transactions for Price Item BL1 should be invoiced on Invoice Account - BID1-IA1 (immediate parent)
Transactions for Price Item BL2 should be invoiced on Invoice Account - BID2-IA2 (in different hierarchy, does not share any parent with BIN1-UA1)
How this could be configured in ORMB?
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