Source Document Types and Type Codes in Revenue Management Cloud

What is a Source Document Type?

Source Document Types are used for integrating third-party applications and Revenue Management Cloud. Examples of Source Documents are Sales orders, Service contract, Warranty contract, etc. Source Document Types are attached to System Options and is a required and integral setup in Revenue Management

There are Source Document Types already predefined for integrations with Oracle E-Business Suite and for Oracle Cloud applications. If you are bringing data or integrating to third party applications, you're going to have to create custom ones. If you are interested to know which of these Source Document Types were predefined or seeded, notice the "Created By" column. If see the value "Oracle" then that means that's something that was predefined.

Source Document Types brings together the Revenue Scheduling Rules (also known as Performance Satisfaction Plan), the Satisfaction Measurement Model (SMM) and the Document Type Code.

What is a Satisfaction Measurement Model?

A Satisfaction Measurement Model answers how you measure satisfaction such as Quantity, Period or Percentage, depending on how your organization measures satisfaction. For example, if it's a service that you provide over time, the SMM would probably be based on the accounting period.

What is a Source Document Type Code?

Source Document Type Codes are used to define the attributes that can be used in a number of setups in Revenue Management such as Contract Identification Rules, Performance Obligation Rules, Pricing Dimension Assignments and also for defining subledger accounting rules.

Document Type Codes are synonymous to Descriptive Flexfields (DFFs). DFFs are fields that allow you to track and capture data points that may be specific to your organization or industry. To define new Document Type Codes, The name of the implementation task is "Manage Revenue Management Descriptive Flexfields".

Source Document Type Codes are important aspects in identifying contracts with the customer (Contract Identification Rules), and also to identify performance obligations (Performance Obligation Identification Rules). Source Document Type Codes can contain two types of Data:

1. Source Document Header data - These are usually header-level data such as sales order number, a contract number, contract date or Customer information
2. Source Document Lines data - These are usually line-level data such as inventory item, numbers or IDs, product descriptions, line amounts, etc.

Both Header and Line data can contain up to 90 extensible attributes that you can populate.

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)