You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Separate AR Invoices Due to Different OM and SMC Transaction Sources

in Order Management 1 comment

Summary:

We are testing Subscription Management amendment, renewal, and upsell scenarios. We observed that transactions originating from Order Management and Subscription Management appear to create separate AR invoices because different transaction sources are being used. We would like to understand whether Oracle supports using a common AR transaction source for OM and SMC transactions so that invoice consolidation can occur.

Content (please ensure you mask any confidential information):

We tested a subscription lifecycle involving creation through OM, renewal/amendment through SMC, and an upsell order through OM. Billing transactions are successfully interfaced to AR, but separate invoices are generated for OM-originated and SMC-originated transactions. We suspect this is due to different AR transaction sources being assigned during interfacing. From a business perspective, all billing events belonging to the same subscription should ideally be consolidated into a single invoice. Is the use of different transaction sources between OM and SMC expected behavior? Can OM-created and SMC-created subscription transactions be configured to use the same AR transaction source? Is invoice consolidation

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!