How to Group Revenue Contracts Across Multiple Oracle Sources — Cloud Customer Connect
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

How to Group Revenue Contracts Across Multiple Oracle Sources

Summary:

In Oracle RMCS, we are trying to group revenue contracts across multiple source systems — specifically Sales Orders, Subscriptions, and Fusion Contracts. Our goal is to create a single revenue contract when a common attribute (e.g., Extensible Header Character Attribute 1) is shared across these sources.

However, in the Contract Identification Rules setup, the Source is marked as a required field, which prevents grouping transactions from various sources into the same revenue contract, even if they share the same value in the identifying attribute.

Is there a supported approach to group transactions from various sources into one revenue contract using a common attribute, despite the "Source" field being mandatory in Contract Identification Rules? If not, are there any workarounds or best practices to achieve this type of grouping?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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