Oracle Revenue Management

Cloud – Setup Example

March 2017
 Contents

Oracle Revenue Management Cloud – Setup Example ...............................................................................................................1

Contents ...............................................................................................................................................................................................2
Overview................................................................................................................................................................................................4
Key Implementation Considerations and High Level Process..........................................................................................................4
Scope of This Document......................................................................................................................................................................5
Implementation Project .........................................................................................................................................................................6
Assign Revenue Contract Event Class to Subledger Accounting Method ...............................................................................10
Source Document Codes ..............................................................................................................................................................11
Source Document Types ...............................................................................................................................................................14
Accounts ..........................................................................................................................................................................................15
Items.................................................................................................................................................................................................16
Revenue System Options ..................................................................................................................................................................18
Revenue Price Effective Periods...................................................................................................................................................20
Lookups for Contract Class............................................................................................................................................................21
Contract Identification Rules ..........................................................................................................................................................22
Lookups for Performance Obligation Classification Codes ........................................................................................................25
Performance Obligation Identification Rules ................................................................................................................................26
Implied Performance Obligation ....................................................................................................................................................31
Item Classification Lookup .............................................................................................................................................................32
Pricing Dimension Setup - High Tech Example...........................................................................................................................34
Manage Key Flexfields...............................................................................................................................................................34
Manage Structures.....................................................................................................................................................................34
Pricing Dimension Assignments ...............................................................................................................................................39
Pricing Dimension Bands ..........................................................................................................................................................40
Revenue Price Profile ................................................................................................................................................................41
Pricing Dimension Setup - Telecommunications Example.........................................................................................................43
Manage Key Flexfields...............................................................................................................................................................43
Manage Structures.....................................................................................................................................................................43
Pricing Dimension Assignments ...............................................................................................................................................47
Revenue Price Profile ................................................................................................................................................................48
Pricing Dimension Setup - Manufacturing Example....................................................................................................................50
Manage Key Flexfields...............................................................................................................................................................50
2
 Manage Structures.....................................................................................................................................................................50
Pricing Dimension Assignments ...............................................................................................................................................55
Revenue Price Profile ................................................................................................................................................................56
Customer Classification..................................................................................................................................................................59
Manage Descriptive Flexfields.......................................................................................................................................................60
HiTech_Prof_Services ...............................................................................................................................................................62
HiTech_Subscription ..................................................................................................................................................................65
Telco_Devices ............................................................................................................................................................................68
Telco_Subscriptions ...................................................................................................................................................................71
Mfg_Machines ............................................................................................................................................................................74
Mfg_Maintenance.......................................................................................................................................................................77
Customer Maintenance .............................................................................................................................................................80

3
Overview
Welcome to Oracle Applications Cloud! This document is targeted toward system integrators who are assisting customers
with the implementation of Oracle Revenue Management Cloud (Revenue Management). In order to help facilitate your
success, this document demonstrates a setup example to give you an overview of the overall setup steps required for
Revenue Management and a head start on configuration. It is not meant to replace Oracle’s general user guide
documentation.

Key Implementation Considerations and High Level Process

1. Identify the current footprint in terms of your client’s existing ledgers used for corporate reporting and national statutory reporting
respectively.
2. Discuss and understand your client’s decision on retrospective adoption of ASC 606 / IFRS 15 (that is, revision of the opening
balance sheet).
3. Discuss and understand your client’s decision on explaining the impact to investors through either the restatement of the previous
years’ results at cut-over, or the disclosure of the subsequent year’s results under the old rules at the end of that year.
4. Be sure to get an ASC 606 / IFRS 15 (not an ASC 605 / IAS 18) articulation of your client’s main revenue use cases that they have
validated with an accounting advisor, tabulate them in “review at inception” mode (a phrase from the standard) and analyze that
table in terms of the data needed to identify and process them.
a. Ensure that your client identifies every use case data source: documents, inception-, billing-, interim- and revenue-
satisfaction events that trigger action, standalone selling or estimated selling prices and the related pricing policies,
contract revisions, and the expected accounting entries throughout the life cycle of the accounting contract.
b. Use that information and the File Based Data Import (Revenue Basis Data Import and Billing Data Import) templates to
prepare the file import from the third party systems or supplemental data from EBS or other Cloud Services.
5. When you have obtained the use case data, set the Revenue Management product up in a Cloud pod reflecting the client’s
standard business environment.
6. Create a first draft set of rules in Revenue Management to automatically identify and create accounting contracts and performance
obligations and to account for contract liabilities, contract assets, and revenue.
a. Import the oldest relevant data on a period by period basis such as January 2016, February 2016 et cetera, test the rules,
and review the results in an Enterprise Performance Management (EPM) Tool such as Oracle Planning and Budgeting
Cloud, or Oracle Hyperion Essbase. If your client doesn’t like the results, discard the contracts, revise the rules, and try
again. Save each iteration in the EPM tool. You client will be validating their interpretation of the standard and the
appropriateness of their proposed compliance with concepts like Performance Obligation and Standalone Selling Price.
b. When the results are validated by your client as giving the appropriate outcome, save the results in the EPM tool, and
book the transaction output in an additional secondary ledger, the ASC 606 or IFRS 15 Adoption Ledger, and import more
source data for subsequent periods.
7. Your client can use the EPM data to plan and budget next year’s revenue, to validate your Governance, Risk and Compliance
around the new standard, and perhaps, in the client’s external reporting.
8. The data that has been posted to an additional secondary ledger will support a revised retrospective opening balance sheet on cut-
over day. It will become subledger data to your regular corporate ledger on that date. Oracle provides a cutover utility that will
support your adoption journal entry, and replace the old-rules deferred revenue processes you will stop using.
a. Cut over process on cutover day – to be executed in the General Ledger:
i. Manual journal entry to equity to reverse the ASC 605 / IAS 8 deferred revenue balances.
ii. Manual journal entry “from” equity to record the IFRS 15 / ASC 606 balances (contract assets, contract
liabilities, discount allocation liabilities).
b. Revenue Management enables you to:
i. Re-point Revenue Management sub ledgers from a temporary secondary ASC 606 / IFRS 215 Adoption ledger
to corporate standard ledger.
ii. Provide supporting detail on IFRS 15 / ASC 606 balances.
c. Stop using deferred revenue subledgers.

4
Scope of This Document
» This document focuses on key implementation consideration step 5 outlined above and describes a setup example for third party
integration with Revenue Management, assuming the user has the requisite system access.
» Information on how to configure General Ledger Cloud setup (such as ledgers, chart of accounts and more), setup for customers and
items is not covered in this document, as such implementation documentation is already available on docs.oracle.com
» Setup for Financials Cloud to Revenue Management integration is not covered in this document. This information is explained with the
Release 11 Release Training recordings here.
» Setup for E-Business Suite to Revenue Management integration is not covered in this document. This information is explained with the
Release 11 Release Training recordings here.

5
Implementation Project
Firstly you need to configure the offering in order to create the implementation project for Oracle Revenue Management
Cloud. The setup steps are outlined below.

Navigator > Setup and Maintenance.

Select Financials Offering icon.

The Provisioned dropdown shows whether or not an offering is installed.
Click the Financials icon, then click Actions > Change Configuration.

Expand any offering (via the folder icon) to find its optional features, called Select Feature Choices. If an offering does not
have Feature Choices, a folder icon is not displayed.

Click the Enable for Implementation check box for each product you plan to implement. Some products have specific
features. Click the Features icon to review those.

6
The Implementation Status column indicates the current status of the implementation. The default status is set to Not
Started, which you can change if the offering has been enabled for Implementation.

Click the Not Started link then select the In Progress radio button.

Click Actions > Go to Offerings.

You are now ready to create an implementation project and generate setup tasks.

Before you begin creating your enterprise structure and performing setup tasks, you must create an implementation project.
An implementation project defines the scope of the implementation. The implementation project can be populated by
adding one or more related offerings or task lists.

In this example, you will be adding the Financials offering and required product task lists.

7
Perform the following tasks:
 Navigate from the Home page: Navigator> Setup and Maintenance.
 Select the Implementation Projects button.
 Select the Create icon.
 Enter a unique Name such as Revenue Management Implementation Project. When you tab from the Name field,
the Code and Description fields will be populated automatically and can be modified if required.
 Tab to the Code field. REV_MGT_IMPLEMENTATION.
o Note: The value in the Code field must be uppercase letters with no spaces.
 Optionally change the default Description: Revenue Management Implementation Project.

 Select the Next button. (The ‘Create Implementation Project: Select Offerings to Implement’ page will be
displayed.)
 Expand the Financials offering.
 Select the Include checkbox for Financials, and the nested offering, Revenue Management.

8
  Click Save and Open Project.

 Expand the Financials task list and view the implementation tasks that were included in the Financials offering.
Delete most tasks except for two: Define Common Applications Configuration for Financials, and Define Revenue
Management.
 This is the number of tasks that should be shown at end of the setup.

The Task Lists below should be included in the Implementation Project related to Revenue Management.
 Define Common Applications Configuration for Financials
 Define Revenue Management

 Click Done to close the Manage Implementation Projects window.

9
Assign Revenue Contract Event Class to Subledger Accounting Method
You will need to assess the number of primary and secondary ledgers needed during your client’s transition period as well
as at the time of adoption of ASC 606 and IFRS 15. That assessment is, however, not the focus of this document.
In this setup example, we focus only on third party integration, and therefore the primary ledger has a Subledger Accounting
Method assigned that includes the new the Revenue Contract event class, which enables you to address ASC 606 / IFRS
15 e.g. in this case the setup reflects the definition after adoption.
However, if your client’s current ERP system is Oracle E-Business Suite or Oracle ERP Cloud, you would need to identify
the primary and secondary ledgers currently in use. Then define another secondary ledger and assign a Subledger
Accounting Method with the new Revenue Contract event class so that you can execute iterative modeling to address
ASC 606 / IFRS 15 during the transition period and review the results via the secondary ledger, without impacting any of the
existing primary or secondary ledgers in your system.

Note: Do not modify any seeded Oracle Subledger Accounting Methods, as any modifications to the Oracle seeded Subledger Accounting
Methods will be lost during an upgrade. Instead you can copy a seeded Subledger Accounting Method, save it with a new name and
assign the Revenue Contract event class to ensure compliance with ASC 606 and IFRS 15.

For more information, refer to the section on Preparing for Adoption of ASC 606 and IFRS 15 in the data sheet here and the
FAQ here.

At time of adoption you would switch to the appropriate ledger for corporate reporting and ensure the Subledger Accounting
Method containing the Revenue Contract event class is applied.

Details on how to define Ledgers, Subledgers, Subledger Accounting Rules and more is available via docs.oracle.com as
these are features utilized by the products within Oracle Enterprise Resource Planning Cloud Services.

10
Source Document Codes
Source Document Codes that are defined here are used in the subsequent definition of Source Document Types.

For the purpose of this setup example source document codes are required to support High Tech, Telecommunications
and Manufacturing lines of business.

Navigation (from Implementation Project):

Define Common Reference Objects for Financials > Manage Descriptive Flexfields.

Search for Name: VRM SOURCE DOCUMENT.

Click on Edit.
Click on Manage Contexts.
Click on Add (+).
Display Name: HiTech Professional Services, add descriptions.

Click on Save and Close.

11
Click on Add (+).
Repeat for the following:
 HiTech Subscription
 Manufacturing Machines
 Manufacturing Maintenance
 Telco Devices
 Telco Subscriptions

Select Done, select Save and Close.

On Manage Descriptive Flexfield, click on Deploy Flexfield button.

12
Select OK.

Select Done.
Note: Source Document Type Codes seeded by Oracle are reserved for current or future use, and Source Document Type Codes are
unique, so when you define a new Source Document Type Code ensure it does not clash with any already defined by Oracle, otherwise
you will encounter an error due to trying to create duplicate values.

13
Source Document Types
For the purpose of this setup example source document codes are required to support High Tech, Telecommunications
and Manufacturing lines of business.

Navigation (from Implementation Project):

Define Revenue Management > Define Common Revenue Configuration > Manage Source Document Types.

Create the following Source Document Types:

Satisfaction Performance
Measurement Satisfaction Document Type Created
Name Description Model Plan Code By Active
High Tech High Tech
Professional Services Professional Services Quantity HiTech_Prof_Services Customer Yes
High Tech High Tech Cloud Daily Rate All
Subscription Services Subscription Services Period Periods HiTech_Subscription Customer Yes
Manufacturing Manufacturing
Machines Machines Quantity Mfg_Machines Customer Yes
Maintenance of
Manufacturing Manufacturing Daily Rate All
Maintenance Machines Period Periods Mfg_Maintenance Customer Yes
Telecommunication Telecommunication
Devices Devices Quantity Telco_Devices Customer Yes
Telecommunication
Telecommunication Subscriptions for Daily Rate All
Subscriptions Data, Voice and Text Period Periods Telco_Subscriptions Customer Yes

Select Save and Close.

14
Accounts
Additional natural accounts need to be defined to support the accounting requirements of ASC 606 / IFRS 15.

Navigation (from Implementation Project):

Define Common Applications Configuration for Financials> Define Enterprise Structure for Financials> Define Financial
Reporting Structures> Define Chart of Accounts> Manage Chart of Accounts Value Set Values.

Enter Value Set Code: Corporate, select Search.

Select Corporate Account.
Select Manage Value Button.
Add the following:
Third
Party
Value Set Allow Allow Account Control Financial
Code Value Description Summary Posting Budgeting Type Account Reconcile Category
Corporate Revenue
Account 12104 Clearing N Y Yes A N N AR
Corporate Contract
Account 12360 Asset N Y Yes A N N AR
Contract
Liability for
Corporate Performance
Account 24510 Obligations N Y Yes L N N ACC LIAB
Corporate Contract
Account 24520 Discount N Y Yes L N N ACC LIAB
Revenue -
Corporate Performance Sales
Account 41100 Obligations N Y Yes R N N Revenue
Revenue -
Corporate Price Sales
Account 41110 Variance N Y Yes R N N Revenue

Note: The decision on whether to enable “Third Party Control Account” is up to your client.

15
Items
Items need to be created to support import of any sales cycle data from your sales cycle source systems.

Navigator >Product Information Management > (panel drawer) Create Items

Organization:
Record the following inventory items in item org 000 and 001:
RM20001 Phone model 01
RM30001 Supersonic Machine Excel Lux 01
RM30002 Supersonic Machine Excel 02
RM40001 Dell XPS Model 9999
RM 40002 Office Software
RM 40004 Wireless Headset Model 8888
RM 40005 Monitor Cleaner Kit

The remaining items are recorded against item org 000.

Assigning an Item to organization 001 automatically assigns it to the master organization 000.

Note (i): In this particular setup example the item classes used are existing item classes. No new item classes were created. Naturally, for
your own implementation you can create additional Item Classes as needed.
Note (ii): Be sure to get the Unit of Measure (UOM) correct, once saved you cannot change it.
Note (iii): In order to be able to assign a sales account (revenue) to an inventory organization’s item, you must first assign a management
business unit, and then assign a ledger to the inventory organization.

Revenue Management Items for this Setup Example are listed below.
Sales Account
(Specifications tab, Sales
and Order Management
Item Description UOM link) Item Class
RM10000 HCM Cloud Service Month No Support
RM10001 ERP Cloud Service Month No Support
RM10002 Consulting Service Day No Consulting
RM10003 Education Day No Support
RM10004 HCM Promotion Discount Month No Support
103-10-41100-410-000-
RM20001 Phone model 01 Each 000 Smartphones
Warranty and
RM20002 Unlimited Talk & Text Month No Service
RM20003 Data plan 3GB Month No Smartphones
Supersonic Machine Excel Lux 103-10-41100-410-000-
RM30001 01 Each 000 Green Servers
103-10-41100-410-000-
RM30002 Supersonic Machine Excel 02 Each 000 Green Servers
Maintenance Supersonic
RM30003 Machine Excel Lux 01 Month No Green Servers
Maintenance Supersonic
RM30004 Machine Excel 02 Month No Green Servers
RM40001 Dell XPS Model 9999 Each 103.10.41100.420.000.000 Tablet_Components
RM 40002 Office Software Each 103.10.41100.420.000.000 Tablet_Components
16
 Sales Account
(Specifications tab, Sales
and Order Management
Item Description UOM link) Item Class
(Defined in 001, but no
RM 40003 System Installation Day sales account) Support
RM 40004 Wireless Headset Model 8888 Each 103.10.41100.420.000.000 Tablet_Components
RM 40005 Monitor Cleaner Kit Each 103.10.41100.420.000.000 Tablet_Components
RM 40006 System Support Month Support

Click Relationships > Spoke System Items > Create Row.

The Spoke System value, here defined as Legacy System 1, relates to the Source value that you’ll need to include in the
Revenue Basis Import FBDI when loading in source document lines for such goods or services into Revenue
Management.

Select OK, Select Save.

Note: Ensure that the Spoke System value for the items matches the original system source system reference of the
customer records to support a successful upload of source data via the “Revenue Basis Data Import” File Based Data
Import (FBDI).

17
Revenue System Options
Some setup is centralized for Oracle Revenue Management Cloud through Revenue System Options.

Navigation (from Implementation Project):

Define Revenue Management > Define Common Revenue Configuration > Manage Revenue System Options.

Set the value for the Conversion Rate Type.

In this setup example it is set to Corporate.

Establish the Revenue Clearing Account for each Source Document Type used in the Primary Ledger.
In this setup example the Revenue Clearing Account is defined as displayed below.
Ledger Source Document Type Revenue Clearing Account
US Primary Ledger High Tech Professional Services 103-10-12104-000-000-000
US Primary Ledger High Tech Subscription 103-10-12104-000-000-000
US Primary Ledger Manufacturing Machines 103-10-12104-000-000-000
US Primary Ledger Manufacturing Maintenance 103-10-12104-000-000-000
US Primary Ledger Telecommunication Devices 103-10-12104-000-000-000
US Primary Ledger Telecommunication Subscriptions 103-10-12104-000-000-000

Select Save

18
In this setup example the ‘Oracle Fusion Receivables Transaction Sources’ is left blank.

Establish the Revenue Accounting and Thresholds and Accounts

Select Save and Close

19
Revenue Price Effective Periods
It is important to assess the pricing policies of your goods and services and how frequently these change as that will help
you determine the Effective Period to use overall for Standalone Selling and Estimated Selling Prices of your goods and
services. In this setup example the Effective Period has been defined as a Quarterly time frame.

Navigation (from Implementation Project):

Define Revenue Management > Define Observed and Estimated Standalone Selling Prices > Manage Revenue Price
Effective Periods.
(Remember to Save Early and Often!)
Note: The system will change the ‘In use’ value once it is used. The system will not accept gaps.

Select Save and Close.

20
Lookups for Contract Class
Navigation (from Implementation Project):
Define Revenue Management > Define Common Revenue Configuration > Manage Revenue Management Lookups.

Note: This setup example was validated in an older version of Release 11 Oracle Revenue Management Cloud environment where a bug
was encountered that prevented new Contract Classes to be added but that has since been fixed. In the example below the Meaning and
Description were therefore overwritten for four existing lookups in order to get more meaningful Contract Classes, such as High Tech,
Telecommunication, and Manufacturing.

These values are subsequently assigned as Default Contract Class in the next step when defining Contract Identification
Rules.

You should, however, not encounter such a problem and should be able to define new Contract Classes.

Due to the aforementioned bug we changed the descriptions for the first four of the original values, as shown below.
Here is what it looks like after the values were updated:

21
Contract Identification Rules
To gain an understanding on how sales cycle source document data is processed by Contract Identification Rules in
Revenue Management, refer to the Getting Started Guide on My Oracle Support Doc ID: 2205721.1.

Navigation (from Implementation Project):

Define Revenue Management > Define Contracts with Customers > Manage Contract Identification Rules.

There are three seeded rules and they are there as a catch all to ensure contracts can be processed, even if you don't
define any new rules. They can't and should not be deleted.

In this setup example, different common identifiers for source document data for each type of contract have been defined,
as outlined below.

Header level - Contract Rule ID:

Default Freeze In
Name Description Priority Classification Enabled Period Use
Cloud Customer Purchase Order
Contract and Quote Number 100 High Tech Yes 10 No
Bill-to Customer Party ID and
Telco Contract Quote Number 110 Telecommunication Yes 10 No
Bill to Customer and
Mfg Contract Customer Purchase Order 120 Manufacturing Yes 10 No

Cloud Contract - (detail level information):

Grouping Attributes
Source Document Source Document Attribute Matching
Type Name Group Comment
High Tech Subscription Named Attribute (Customer PO NO,
Services Customer Purchase Order Number 1 for example CPO1009915)
High Tech Professional Named Attribute (Customer PO NO,
Services Customer Purchase Order Number 1 for example CPO1009915)
High Tech Subscription Extensible Header Character (Quote Number, for example e.g.
Services Attribute 3 2 QTE00013)
High Tech Professional Extensible Header Character (Quote Number, for example e.g.
Services Attribute 3 2 QTE00013)
*Note: After each Contract Identification Rule is entered, you Save first, then select Close – You cannot select Save and Close.

22
Telecommunications Contract - (detail level information):
Grouping Attributes
Source Document Source Document Attribute Matching
Type Name Group Comment
Telecommunication
Devices Bill-to Customer Party Identifier 1 Named Attribute
Telecommunication
Subscriptions Bill-to Customer Party Identifier 1 Named Attribute
Telecommunication Extensible Header Character (Quote Number, for example e.g.
Devices Attribute 3 2 QTE00013)
Telecommunication Extensible Header Character (Quote Number, for example e.g.
Subscriptions Attribute 3 2 QTE00013)
*Note: After each Contract Identification Rule is entered, you Save first, then select Close – You cannot select Save and Close.

Manufacturing Contract - (detail level information):

Grouping Attributes
Source Document Source Document Attribute Matching
Type Name Group Comment
Manufacturing
Machines Bill-to Customer Party Identifier 1 Named Attribute
Manufacturing
Maintenance Bill-to Customer Party Identifier 1 Named Attribute
Manufacturing Customer Purchase Order Named Attribute (Customer PO
Machines Number 2 NO, for example CPO1009915)
Manufacturing Customer Purchase Order Named Attribute (Customer PO
Maintenance Number 2 NO, for example CPO1009915)
*Note: After each Contract Identification Rule is entered, you Save first, then select Close – You cannot select Save and Close.

Select Add (+) icon, Enter Header attributes and grouping rules.

*Note: After each Contract Identification Rule is entered, you Save first, then select Close – You cannot select Save and Close.

23
Select Add (+) icon, Enter Header attributes and grouping rules.

*Note: After each Contract Identification Rule is entered, you Save first, then select Close – You cannot select Save and Close.

Select Add (+) icon, Enter Header attributes and grouping rules.

*Note: After each Contract Identification Rule is entered, you Save first, then select Close – You cannot select Save and Close.

24
Lookups for Performance Obligation Classification Codes
Performance Obligation Classification Code lookups are used in subsequent definition of Performance Obligation
Identification Rules.

Navigation (from Implementation Project):

Define Revenue Management > Define Common Revenue Configuration > Manage Revenue Management Lookups.

Add the following Performance Obligation Classification Codes, such as:

Reference Data Start

Lookup Code Set Enabled Date Meaning Description
Cloud Subscription Common Set Y 1/1/1991 Cloud Subscription Cloud Subscription
Professional Professional
Professional Services Common Set Y 1/1/1991 Services Services
Data and Voice Data and Voice
Data and Voice Plans Common Set Y 1/1/1991 Plans Plans
Device Common Set Y 1/1/1991 Device Device
Maintenance Common Set Y 1/1/1991 Maintenance Maintenance
Machines Common Set Y 1/1/1991 Machines Machines

Search for Lookup Type - ORA_VRM_OBLIG_CLASSIF_CODE.

Select the Add (+) icon

Select Save and Close.

25
Performance Obligation Identification Rules
To understand more about how source line document data is processed by Performance Obligation Identification Rules in
Revenue Management, refer to the Getting Started Guide in My Oracle Support Doc ID: 2205721.1

Navigation (from Implementation Project):

Define Revenue Management > Define Contracts with Customers > Manage Performance Obligation Identification Rules.

There are three seeded Performance Obligation Identification Rules and they are there as a catch all to ensure contracts
can be processed, even if you don't define any new rules. They can't and should not be deleted.

In this setup example, the additional Performance Obligations Identification Rules to be created are displayed below.

Exempt
Satisfaction In from Default
Name Description Priority Method Enabled Use Allocation Classification
Cloud service
subscription and
High Tech consulting - allows partial Cloud
Subscription satisfaction method 100 Allow Partial Yes No No Subscription
High Tech Professional
Consulting Consulting services 105 Allow Partial Yes No No Services
Education Services
High Tech require complete Require Professional
Education satisfaction method 110 Complete Yes No No Services
Telco subscriptions -
Telco allows partial satisfaction Data and
Subscriptions method 120 Allow Partial Yes No No Voice Plans
Telco devices - require
Telco complete satisfaction Require
Devices method 130 Complete Yes No No Device
Maintenance of machines
- allows partial
Maintenance satisfaction method 140 Allow Partial Yes No No Maintenance
Machines - require
complete satisfaction Require
Machines method 150 Complete Yes No No Machines

26
Select Add (+) icon.
Performance Obligation Rule Name: High Tech Subscription
Source Document Type: High Tech Subscription Services
Source Document Attribute Name Extensible Line Character Attribute 1

Select Save and Close button.

Select Add (+) icon.

Performance Obligation Rule Name: High Tech Consulting
Source Document Type: High Tech Professional Services
Source Document Attribute Name: Extensible Line Character Attribute 1

Select Save and Close button.

27
Select Add (+) icon.
Performance Obligation Rule Name: High Tech Education
Source Document Type: High Tech Professional Services
Source Document Attribute Name: Extensible Line Character Attribute 2

Select Save and Close button.

Select Add (+) icon.

Performance Obligation Rule Name: Telco Subscriptions
Source Document Type Source Document Attribute Name
Telecommunication Subscriptions Extensible Line Character Attribute 1

Select Save and Close button.

28
Select Add (+) icon.
Performance Obligation Rule Name: Telco Devices
Source Document Type: Telecommunication Devices
Source Document Attribute Name: Extensible Line Character Attribute 1

Select Save and Close button.

Select Add (+) icon.

Performance Obligation Rule Name: Maintenance
Source Document Type: Manufacturing Maintenance
Source Document Attribute Name: Extensible Line Character Attribute 1

Select Save and Close button.

29
Select Add (+) icon.
Performance Obligation Rule Name: Machines
Source Document Type: Manufacturing Machines
Source Document Attribute Name: Extensible Line Character Attribute 1

When searching for the performance obligation rules that you defined make sure you set your 'Exempt from Allocation' to
'No' to view all the rules you just defined.

30
Implied Performance Obligation
In this setup example, the customer receives 15 days free education when consulting is sold on a High Tech Cloud
Contract. Therefore an implied performance must be defined whenever this condition is met.

Navigation (from Implementation Project):

Define Revenue Management > Define Contracts with Customers > Manage Implied Performance Obligation Templates.

In this setup example the Implied Performance Obligation must be defined as displayed below.

Header,
Satisfaction Default
Name Description Method Enabled Classification Currency
Education Education implied with Require Professional
Implied consulting services Complete Yes Services USD

Promised Details Item Education tab,

Satisfaction Performance Unit
Memo Measurement Satisfaction Cost List Base
Item Line Description Model Plan UOM amount Price Quantity price
Education Education Quantity Day 15

Conditions tab,
Left Hand Left Hand Right Right
Side Side Hand Side Hand Side
Case Expression Expression Expression Expression Unit
Conjunction Sensitive Expression Operand Expression Operand List Base
Operator Comparison Type Name Operator Type Value Price Qty price
Extensible
Line
Character
<Checked> Attribute Attribute 4 Equals Literal Consulting

Select Add (+) icon.

Enter Header and Promised Details as follows:

(Note: UOM display known issue in the particular environment. The value ‘zzf’ = ‘days’)

31
Enter Implied Conditions:

Select Save and Close button.

Item Classification Lookup

Item Classification lookups are used in the setup of Revenue Price Profiles, which is covered later in this document.

Navigation (from Implementation Project):

Define Revenue Management > Define Common Revenue Configuration > Manage Revenue Management Lookups.

Note: There are seeded values available that can be disabled as required.
Add Item Classification values, for example:
 Cloud Subscription
 Professional Services
 Device
 Voice Plan
 Data Plan
 Supersonic Machines
 Machine Maintenance

Search for: VRM_ELEMENT_TYPE (This will soon be renamed to Item Classification).

32
Note: Select Detach button to easily review all values.
Select the Add (+) icon. In this example the values added were:
 Machine Maintenance
 Supersonic Machines
 Data Plan
 Voice Plan
 Device
 Professional Services
 Cloud Subscription

Note: If you previously selected the Detach button, select the Detach button again to reverse detachment.
Select Save and Close.

33
Pricing Dimension Setup - High Tech Example
To gain a deeper understanding of Pricing Dimension Structures and Value Sets please refer to Getting Started Guide on
My Oracle Support Doc ID: 2205721.1

Manage Key Flexfields

Navigation (from Implementation Project):
Financials > Define Common Applications Configuration for Financials > Define Common Reference Objects for Financials
> Manage Key Flexfields.

Search Key Flex field code as VRM.

Manage Structures
Select the row and Click Manage Structures button, do blind search; it will give existing structures in Revenue
Management (code: VRM).

Select the Add (+) icon.

Provide the values,
Code: Region and Sales Channel
Name: Region and Sales Channel
Delimiter: -
Enabled: Check
Click Save.

In this setup example Pricing Dimension Structure, value sets, assignments and Revenue Price Profile are defined for a
High Tech Cloud Contract type.

34
 Add 3 segments for example, Customer Region, Sales Channel, and Deal Band
Segment 1:
Select the Add (+) icon.
Provide the values,
Segment Code: Customer Region
Name: Customer Region
Description: Customer Region
Display Width: 30
Sequence: 1
Prompt: Customer Region
Short Prompt: Customer Region
Enabled: Check
Column Name: SEGMENT1
Default Value Set Code: VRM Zone (if you want to populate existing values from value set).
Move set band to Selected labels tab. (Zones are related to Set band).
Click on Save and Close.

Segment 2:
Select the Add (+) icon.
Provide the values,
Code: Sales Channel
Name: Sales Channel
Description: Sales Channel
Display Width: 30
Sequence: 2
Prompt: Sales Channel
Short Prompt: Sales Channel
Enabled: Check
Column Name: SEGMENT2
Default Value Set Code: 30 Characters
Click on Save and Close.

35
Segment 3:
Select the Add (+) icon.
Provide the values,
Code: Deal Band
Name: Deal Band
Description: Sales Channel
Display Width: 18
Sequence: 3
Prompt: Deal Band
Short Prompt: Deal Band
Enabled: Check
Display Width: 18
Column Name: SEGMENT3
Default Value Set Code: VRM Value
Move Amount Band to selected labels tab. (VRM value is amount based value set).
Click on Save and Close.

36
After adding required number of segments, it should look like the following:

Click on Save and Close.

Click on Done.
Click on Deploy Flexfield
After completion of deployment, it will give the confirmation message saying "Deployment completed successfully.

Click on OK.

37
There is one more setup Manage Structure Instances, as you need to create an instance for the structure.

 Select the row and Click on Manage Structure Instances.

o Click on create icon.
o Provide the values: Code > Region and Sales Channel, Name > Region and Sales Channel, enabled >
Check, Dynamic Creation > check.
o Select the correct structure (Region and Sales Channel) that you created Manage Structures UI.
o after Selecting the name, the page should look like in this:

 Click Save and Close.

 Click Done.
 Click on Deploy Flexfield.

After completion of deployment, it will give the confirmation message saying "Deployment completed successfully. Start
a new session of the runtime application to view changes."

38
Pricing Dimension Assignments
Navigation (from Implementation Project):
Define Revenue Management > Define Common Revenue Configuration > Define Observed and Estimated Standalone
Selling Prices > Manage Revenue Pricing Dimension Assignments.

High Tech
In the Pricing Dimension Assignments region, select the Add (+) icon.
Name: Cloud Services
Description: Cloud Services
Pricing Dimension Structure: Region and Sales Channel
Enabled: Checked

39
 In the Document Assignments region,
Select the Add (+) icon.
Document Type: High Tech Professional Services
Customer Region: Bill-to Customer Country
Sales Channel: Extensible Header Character Attribute 1
Deal Band: Amount Line

Select the Add (+) icon.

Document Type: High Tech Subscription Services
Customer Region: Bill-to Customer Country
Sales Channel: Extensible Header Character Attribute 1
Deal Band: Amount Line

Pricing Dimension Bands

Navigation (from Implementation Project):
Define Revenue Management > Define Common Revenue Configuration > Define Observed and Estimated Standalone
Selling Prices > Manage Revenue Pricing Dimension Bands

For example, Deal Size and Revenue Management Zone Band Set.

Select the Add (+) icon.

Name: Deal Size
Description: Deal Size
Dimension Value Set: VRM Volume Band Set
Pricing Dimension Type: Amount Band
Context Value:
In Mappings region, provide value for each range, for each currency.

Select Save and Close.

40
 Revenue Price Profile
In this setup example for the High Tech industry a Cloud SSP Revenue Price Profile is created.
Navigation (from Implementation Project):
Define Revenue Management > Define Observed and Estimated Standalone Selling Prices > Manage Revenue Price
Profiles.

Select the Add (+) icon.

Name: Cloud SSP
Description: SSP profile for cloud subscriptions and services
Revenue Price Representation: Unit Price
Pricing Dimension Assignment: Cloud Services (defined in Pricing Dimension Assignments)
Cover Effective Period: Uncheck
Note: Uncheck means exclude current quarter (quarter is the Effective Period measurement in this setup
example) i.e. include past quarters only without current quarter.
Leave Cover Effective Period and Context Value blank.

Segment Assignments region values are defaulted based upon Pricing Dimension Assignment.

Enter Default Assignment Attributes:

Minimum Standalone Sales: 15
Months Covered: 6
Item Classification: blank
Revenue Price Tolerance Usage: Median
Coverage: 80
High Tolerance Range: 15
Low Tolerance Range: 15

In the Price Bands region, select Price Bands for each Pricing Dimension Segment, one which is seeded and another
which was defined in Pricing Dimension Bands setup step.

41
In this setup example the following Price Bands must be assigned:
Customer Region: Revenue Management Zone Band Set
Deal Band: Deal Size

In the Assignment region, the following Item(s) must be assigned, and Item Classification and Effective Start Period applied.

Note: This example uses an Effective Start Period of Quarter 1-2015.

Click on Save and Close.

42
Pricing Dimension Setup - Telecommunications Example
Manage Key Flexfields
Navigation (from Implementation Project):
Financials > Define Common Applications Configuration for Financials > Define Common Reference Objects for Financials
> Manage Key Flexfields.

Search Key Flex field code as VRM.

Manage Structures
Select the row and Click Manage Structures button, do blind search; it will give existing structures in Revenue
Management (code: VRM).

Select the Add (+) icon.

Provide the values,
Code: Customer Class & Product Group
Name: Customer Class & Product Group
Description: Customer Class & Product Group
Delimiter: -
Enabled: Check
Click Save.

In this setup example Pricing Dimension Structure, value sets, assignments and Revenue Price Profile are defined for a
Telecommunications Contract type.

43
 Add 2 segments for Customer Class and Product Group.
Segment 1:
Select the Add (+) icon.
Provide the values,
Code: Customer Class
Name: Customer Class
Display width: 30
Description: Customer Classification
Sequence: 1
Prompt: Customer Class
Short Prompt: Customer Class
Enabled: Check
Column Name: SEGMENT1
Default Value Set Code: VRM Customer Class (select from existing value set).
Click on Save and Close.

Segment 2:
Select the Add (+) icon.
Provide the values,
Code: Product Group
Name: Product Group
Display width: 30
Description: Product Group
Sequence: 2
Prompt: Product Group
Short Prompt: Product Group
Enabled: Check
Column Name: SEGMENT2
Default Value Set Code: 30 Characters
Click on Save and Close.

44
After adding the required number of segments the page should look like this:

Click on Save and Close.

Click on Done.

45
 Click on Deploy Flexfield
After completion of deployment, it will give the confirmation message saying "Deployment completed successfully.

Click on OK.

There is one more setup Manage Structure Instances, so you need to create an instance for the structure.

 Select the row and Click on Manage Structure Instances.

o Click on create icon.
o Provide the values: Code > Customer Class and Product Group, Name > Customer Class and Product
Group, enabled > Check, Dynamic Creation > check.
o Select the correct structure (Customer Class and Product Group) that you created Manage Structures UI.
o after Selecting the name the page should look like this:

 Click Save and Close.

 Click Done.
 Click on Deploy Flexfield.

After completion of deployment, it will give the confirmation message saying "Deployment completed successfully. Start
a new session of the runtime application to view changes."

46
Pricing Dimension Assignments
Navigation (from Implementation Project):
Define Revenue Management > Define Common Revenue Configuration > Define Observed and Estimated Standalone
Selling Prices > Manage Revenue Pricing Dimension Assignments.

In the Pricing Dimension Assignments region:

Select the Add (+) icon.
Name: Telecommunications
Description: Telecommunications
Pricing Dimension Structure: Customer Class & Product Group
Enabled: checked

In the Document Assignments region, select the Add (+) icon.

Document Type: Telecommunications Devices
Customer Class: Bill-to Customer Class
Product Group: Extensible Header Character Attribute 2

Select the Add (+) icon.

Document Type: Telecommunications Subscriptions
Customer Class: Bill-to Customer Class
Product Group: Extensible Header Character Attribute 2

Click on Save and Close.

47
 Revenue Price Profile
In this setup example for the Telecommunications industry a Telecommunication SSP Revenue Price Profile is created.
Navigation (from Implementation Project):
Define Revenue Management > Define Observed and Estimated Standalone Selling Prices > Manage Revenue Price
Profiles.

Select the Add (+) icon.

Name: Telecommunications SSP
Description: SSP profile for telecommunication devices and services
Revenue Price Representation: Unit Price
Pricing Dimension Assignment: Telecommunications (as defined in prior step in Pricing Dimension Assignments)
Cover Effective Period: Uncheck
Note: Uncheck means exclude current quarter (quarter is the Effective Period measurement in this setup
example) i.e. include past quarters only without current quarter
Leave Cover Effective Period and Context Value blank.

Segment Assignments region values are defaulted based upon Pricing Dimension Assignment

Enter Default Assignment Attributes:

Minimum Standalone Sales: 15
Months Covered: 6
Item Classification: blank
Revenue Price Tolerance Usage: Median
Coverage: 80
High Tolerance Range: 15
Low Tolerance Range: 15

In the Price Bands region no Price Bands are needed.

48
In the Assignment region, the following Item(s) must be assigned, and Item Classification and Effective Start Period applied.

Note: This example uses an Effective Start Period of Quarter 1-2015.

Click on Save and Close.

49
Pricing Dimension Setup - Manufacturing Example
Manage Key Flexfields
Navigation (from Implementation Project):
Financials > Define Common Applications Configuration for Financials > Define Common Reference Objects for Financials
> Manage Key Flexfields.

Search Key Flex field code as VRM.

Manage Structures
Select the row and Click Manage Structures button, do blind search; it will give existing structures in Revenue
Management (code: VRM).

Select the Add (+) icon.

Provide the values:
Code: Region Product & Sales Channel
Name: Region Product & Sales Channel
Description: Region Product & Sales Channel
Delimiter: -
Enabled: Check
Click Save.

In this setup example Pricing Dimension Structure, value sets, assignments and Revenue Price Profiles are defined for a
Manufacturing Contract type.

50
 Add 3 segments for Region, Product, and Sales Channel.
Segment 1:
Select the Add (+) icon.
Provide the values,
Code: Customer Region
Name: Customer Region
Display width: 30
Description: Customer Region
Sequence: 1
Prompt: Customer Region
Short Prompt: Customer Region
Enabled: Check
Column Name: SEGMENT1
Default Value Set Code: VRM Zone (select from existing value set).
Segment Labels: Set Band
Click on Save and Close.

Segment 2:

Select the Add (+) icon

Provide the values,
Code: Product Group
Name: Product Group
Display width: 30
Description: Product Group
Sequence: 2
Prompt: Product Group
Short Prompt: Product Group
Enabled: Check
Column Name: SEGMENT2
Default Value Set Code: 30 Characters
Click on Save and Close.

51
 Segment 3:
Select the Add (+) icon
Provide the values,
Code: Sales Channel
Name: Sales Channel
Display width: 30
Description: Sales Channel
Sequence: 3
Prompt: Sales Channel
Short Prompt: Sales Channel
Enabled: Check
Column Name: SEGMENT3
Default Value Set Code: 30 Characters
Click on Save and Close.

52
After adding the required number of segments the page should look like this:

Click on Save and Close.

Click on Done.
Click on Deploy Flexfield
After completion of deployment, it will give the confirmation message saying "Deployment completed successfully.

Click on OK.

53
There is one more setup Manage Structure Instances, as you need to create an instance for the structure.

 Select the row and Click on Manage Structure Instances.

o Click on create icon.
o Provide the values: Code > Region Product & Sales Channel, Name > Region Product & Sales
Channel, enabled > Check, Dynamic Creation > check.
o Select the correct structure (Region Product & Sales Channel) that you created Manage Structures UI.
o after Selecting the name the page should look like this:

 Click Save and Close.

 Click Done.
 Click on Deploy Flexfield.

After completion of deployment, it will give the confirmation message saying "Deployment completed successfully. Start
a new session of the runtime application to view changes."

54
Pricing Dimension Assignments
Navigation (from Implementation Project):
Define Revenue Management > Define Common Revenue Configuration > Define Observed and Estimated Standalone
Selling Prices > Manage Revenue Pricing Dimension Assignments.

In the Pricing Dimension Assignments region, select the Add (+) icon.
Name: Manufacturing Services
Description: Manufacturing Services
Pricing Dimension Structure: Region Product & Sales Channel
Enabled: checked

In the Document Assignments region, select the Add (+) icon.

Document Type: Manufacturing Machines
Customer Region: Bill-to Customer Country
Product Group: Extensible Header Character Attribute 2
Sales Channel: Extensible Header Character Attribute 1

Select the Add (+) icon.

Document Type: Manufacturing Maintenance
Customer Region: Bill-to Customer Country
Product Group: Extensible Header Character Attribute 2
Sales Channel: Extensible Header Character Attribute 1

Click on Save and Close.

55
 Revenue Price Profile
In this setup example for the Manufacturing industry two Telecommunication SSP Revenue Price Profiles are created:
 Unit MFG SSP (for machines)
 Percentage MFG SSP (for maintenance of the machines)

Navigation (from Implementation Project):

Define Revenue Management > Define Observed and Estimated Standalone Selling Prices > Manage Revenue Price
Profiles.

Select the Add (+) icon.

Name: Unit MFG SSP
Description: Manufacturing Price SSP Profile
Revenue Price Representation: Unit Price
Pricing Dimension Assignment: Manufacturing Services (as defined in prior step in Pricing Dimension
Assignments)
Cover Effective Period: Uncheck
Note: Uncheck means exclude current quarter (quarter is the Effective Period measurement in this setup
example) i.e. include past quarters only without current quarter.
Leave Cover Effective Period and Context Value blank.

Segment Assignments region values are defaulted based upon Pricing Dimension Assignment.

Enter Default Assignment Attributes,

Minimum Standalone Sales: 15
Months Covered: 6
Item Classification: blank
Revenue Price Tolerance Usage: Median
Coverage: 80
High Tolerance Range: 15
Low Tolerance Range: 15

In the Price Bands region, select the seeded Price Band Revenue Management Zone Band Set.
56
 In the Assignment region, the following Item(s) must be assigned, and Item Classification and Effective Start Period applied.

Note: This example uses an Effective Start Period of Quarter 1-2015.

Click on Save and Close.

Select the Add (+) icon.

Name: Percentage MFG SSP
Description: SSP profile for hardware maintenance
Revenue Price Representation: Percentage of base unit price
Pricing Dimension Assignment: Manufacturing Services (as defined in prior step in Pricing Dimension
Assignments)
Cover Effective Period: Uncheck
Note: Uncheck means exclude current quarter (quarter is the Effective Period measurement in this setup
example) i.e. include past quarters only without current quarter.
Leave Cover Effective Period and Context Value blank.

Segment Assignments region values are defaulted based upon Pricing Dimension Assignment.

Enter Default Assignment Attributes:

Minimum Standalone Sales: 15
Months Covered: 6
Item Classification: blank
Revenue Price Tolerance Usage: Median
Coverage: 80
High Tolerance Range: 15
Low Tolerance Range: 15

57
In the Price Bands region, select the seeded Price Band Revenue Management Zone Band Set.

In the Assignment region, the following Item(s) must be assigned, and Item Classification and Effective Start Period applied.

Note: This example uses an Effective Start Period of Quarter 1-2015.

Click on Save and Close.

58
Customer Classification
Navigation (from Implementation Project):
Financials > Define Common Applications Configuration for Financials > Define Common Reference Objects for
Financials > Manage Standard Lookups.
Search for 'CUSTOMER CLASS' lookup type.
Add the new customer classification that you want.
Click on create icon and Provide the values in meaning, code and effective date.

You can see new classifications in 'Manage Customers' UI afterwards.

Click on Save and Close.

59
Manage Descriptive Flexfields
When you use extensible attributes with the source data you’re importing in Revenue Management, and that you’re using
when defining Contract Identification Rules and/or Performance Obligation Identification Rules, you can display the
extensible attributes and their values in the Manage Contracts UI by configuring Descriptive Flexfields.

In this setup example extensible attributes were used and configured for display in Manage Contracts UI.

Navigation (from Implementation Project):

Financials > Define Common Applications Configuration for Financials > Define Common Reference Objects for Financials
Manage Descriptive Flexfields.

Search for Task 'Manage Descriptive Flexfields'.

In the field 'Name' search for 'VRM Source Document'.
Select row 'VRM Source Document'.
Select ‘Action’ and 'Edit'.

Select Right Hand button 'Manage Context'.

Select Save and Close.

Then do an open ended Search.

60
You'll see the sources below.
For each of the sources highlighted in the red box, you need to select 'Actions' and 'Edit’.

61
HiTech_Prof_Services
Select HiTech_Prof_services.
Select Edit icon.

Context Sensitive Segments:

Select the Add (+) icon.
Name: Sales Channel
Description: Sales Channel
Enabled: checked

(Sequence: 10)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR1
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15
Click on Save and Close.

Select Save and Close.

62
Select the Add (+) icon.
Name: Quote Number
Description: Quote Number
Enabled: checked

Context Sensitive Segments:

Select the Add (+) icon.
(Sequence: 20)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR3
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15

Select Save and Close.

After adding the two Descriptive Flexfield segments the page should look like this:

Select Save and Close.

Click on Done.

63
Click on Deploy Flexfield.
After completion of deployment, it will give the confirmation message saying "Deployment completed successfully.

64
HiTech_Subscription
Select HiTech_Subscription.
Select Edit icon.

Context Sensitive Segments:

Select the Add (+) icon.
Name: Sales Channel
Description: Sales Channel
Enabled: checked

(Sequence: 10)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR1
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15

Select Save and Close.

65
Select the Add (+) icon.
Name: Quote Number
Description: Quote Number
Enabled: checked

Context Sensitive Segments:

Select the Add (+) icon.
(Sequence: 20)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR3
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15
Click on Save and Close.

Select Save and Close.

After adding the two Descriptive Flexfield segments the page should look like this:

66
Select Save and Close.
Click on Done.
Click on Deploy Flexfield.
After completion of deployment, it will give the confirmation message saying "Deployment completed successfully.

67
Telco_Devices
Select Telco Devices.
Select Edit icon.

Context Sensitive Segments:

Select the Add (+) icon.
Name: Product Group
Description: Product Group
Enabled: checked

(Sequence: 10)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR2
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15
Click on Save and Close.

68
Select the Add (+) icon.
Name: Quote Number
Description: Quote Number
Enabled: checked

Context Sensitive Segments

Select the Add (+) icon
(Sequence: 20)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR3
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15
Click on Save and Close.

69
After adding the two Descriptive Flexfield segments the page should look like this:

Select Save and Close.

Click on Done.
Click on Deploy Flexfield
After completion of deployment, it will give the confirmation message saying "Deployment completed successfully.

70
Telco_Subscriptions
Select Telco_Subscriptions.
Select Edit icon.

Context Sensitive Segments:

Select the Add (+) icon.
Name: Product Group
Description: Product Group
Enabled: checked

(Sequence: 10)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR2
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15

Select Save and Close.

71
Select the Add (+) icon.
Name: Quote Number
Description: Quote Number
Enabled: checked

Context Sensitive Segments:

Select the Add (+) icon.
(Sequence: 20)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR3
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15

Select Save and Close.

72
After adding the two Descriptive Flexfield segments the page should look like this:

Select Save and Close.

Click on Done.
Click on Deploy Flexfield.
After completion of deployment, it will give the confirmation message saying "Deployment completed successfully.

73
Mfg_Machines
Select Mfg_Machines.
Select Edit icon.

Context Sensitive Segments:

Select the Add (+) icon.
Name: Product Group
Description: Product Group
Enabled: checked

(Sequence: 10)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR2
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15

Select Save and Close.

74
Select the Add (+) icon.
Name: Sales Channel
Description: Sales Channel
Enabled: checked

Context Sensitive Segments:

Select the Add (+) icon
(Sequence: 20)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR1
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15

Select Save and Close.

After adding the two Descriptive Flexfield segments the page should look like this:

Select Save and Close.

Click on Done.
75
Click on Deploy Flexfield
After completion of deployment, it will give the confirmation message saying "Deployment completed successfully.

76
Mfg_Maintenance
Select Mfg_Maintenance.
Select Edit icon.

Context Sensitive Segments:

Select the Add (+) icon.
Name: Product Group
Description: Product Group
Enabled: checked

(Sequence: 10)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR2
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15

Select Save and Close.

77
Select the Add (+) icon.
Name: Sales Channel
Description: Sales Channel
Enabled: checked

Context Sensitive Segments:

Select the Add (+) icon
(Sequence: 20)
Data Type: Character
Table Column: SRC_ATTRIBUTE_CHAR1
Value Set: 30 Characters
Prompt: Quote Number
Display Type: Text box
Display Size: 15

Select Save and Close.

78
After adding the two Descriptive Flexfield segments the page should look like this:

Click on Done.
Click on Deploy Flexfield.
After completion of deployment, it will give the confirmation message saying "Deployment completed successfully.

79
Customer Maintenance
In the Manage Customer UI, go to the customer site Reference Accounts and update the Revenue account segment to
41100 instead of 41000 so Revenue Management can derive an account. Though note that items can also store a Sales
Revenue account.

80
Follow us at:

blogs.oracle.com/oracle facebook.com/oracle t witter.com/oracle oracle.com

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes
only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor
subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and
conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this
document, and no contractual obligations are formed either directly or indirectly by this document. This document may
not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our
prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under
license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the
AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark
of The Open Group.
0115

Oracle Revenue Management Cloud Oracle Corporation, World Worldwide Inquiries

Headquarters
March 2017 Phone: +1.650.506.7000
500 Oracle Parkway
Fax: +1.650.506.7200
Redwood Shores, CA 94065, USA

81