Managing Contract Identification Rules in Oracle Revenue Management Cloud

What is a Contract identification Rule?

Contract identification Rules is going to determine which transaction lines are included in a contract. The idea here is to use source document attributes to match the lines so that you can group them into a contract. Examples of those can be quote numbers, purchase order numbers, etc. If you have multiple transactional lines with the same quote number, then that can mean that these lines can be grouped into a customer contract. These rules are executed on a priority.

How do we create a Contract identification Rule?

To create a contract identification rule, navigate to the Functional Setup Manager, select the Financials offering and choose the Revenue Management functional area. And then the right, select All Tasks and navigate down to "Manage Contract Identification Rules".

Below is a quick video tutorial on creating Contract Identification Rules in Oracle Fusion applications:

A contract can include multiple source document types, so the relationship between a customer contract and a source document type does not have to be one-to-one.

Think about long and hard about defining Grouping Attributes. Grouping Attributes defines the attributes that you want the system to use for automatic customer contracts identification.

For example, we are saying that we're going to look at the customer name, the purchase order number and the quote number. If the system detects you have multiple transaction lines with the same customer, purchase order number and the quote number, it will group those together to form a customer contract.

Usually, Contract Identification Rules use Extensible Header attributes, while Performance Obligation Identification Rules use Extensible Line attributes. Extensible attributes can use up to 90 attributes each for header data and lines data.

There is an available FBDI template to upload Contract Identification Rules in bulk.

You can also add Reference Information for Contracts and Performance Obligations Identification Rules. Reference Information for Contracts and Performance Obligations can be used to populate important information from other systems (such as EBS, non-Oracle systems or other Fusion Cloud applications), into an extensible attribute. It can be the quote number, a Purchase Order number or any other information that may help end-users search for contracts.

For more full-detailed Tutorials and Tips, check out #TheOracleProdigy at https://lifeofanoracleprodigy.blogspot.com/

Follow The Oracle Prodigy on Facebook (https://www.facebook.com/theOracleProdigy/) and Twitter (https://twitter.com/D_OracleProdigy)