Adobe Captivate - Oracledownload.oracle.com/ocomdocs/global/fu… · Web view · 2016-11-29These five steps are the key steps laid out in ASC 606 and IFRS 15. ... • For EBS products,

Adobe Captivate Monday, May 08, 2023

Slide 3 - Oracle Financials Cloud

Slide notes

Hello, my name is Prescilla. Welcome to the Release Training for the new Oracle Financials Cloud, Oracle Fusion Revenue Management product. In this session, we’ll introduce you to this exciting new product and its capabilities.

Notes

Page 1 of 46


Slide 4 - Agenda

Slide notesWe’ll give an overview of Revenue Management, followed by more detail to explain how you can use it, and what business value this product brings.

We’ll also understand the capabilities provided by the new product along with business values.

Next we’ll explain what you need to consider before enabling these capabilities in your business, and what you need to know to set them up.

Notes

Page 2 of 46


Slide 5 - Introducing Revenue Management

Slide notesIn this release training module we will give an overview of the new product launched in Fusion Release 11 – Revenue Management.

Revenue Management reads the sales cycle data from on premise and other third party sources and executes the five step process of identification of contracts, identify performance obligations, determine transaction price, perform allocation based on standalone selling price and recognize revenue based on satisfaction events or satisfaction plans.

These five steps are the key steps laid out in ASC 606 and IFRS 15.

The accounting based on the new standards will be sent to either cloud General Ledger or EBS General Ledger.

Notes

Page 3 of 46


Slide 6 - Introducing Revenue Management

Slide notesRevenue Management enables you to ensure compliance with accounting standards ASC 606 and IFRS 15. However, it is your responsibility to ensure the compliance by configuring flexible rules.

Revenue Management enables you to fully automate your end-to-end revenue recognition process for your enterprise. Our product automates everything from contract identification, performance obligation identification, management of standalone selling prices and estimated selling prices, and revenue recognition based on satisfaction events or satisfaction plans. In addition to that, all revenue-related data is centrally stored within our system, enabling you to gain insights into your expected revenue stream as well as provide transparency to the revenue compliance audit process. We also provide tools for easy migration and uploading of data from upstream systems through spreadsheet integration.

The co-existence solution provides out-of-the-box integration with Oracle E-business Suite (EBS) in order to bring in source revenue lines from upstream systems, such as Order Management, Service Contracts and Receivables. Reference data, such as Customers and Inventory Items, is synchronized between EBS and Revenue Management.

Revenue Management is an EBS co-existence solution for EBS Release 12.1.3 and higher releases.

Revenue Management also integrates with Fusion Receivables. Integration with third party applications is also supported.

Notes

Page 4 of 46


Slide 7 - Revenue Management

Slide notes• Revenue Management offers an end-to-end fully automated solution with minimal user intervention.

• Manage Contracts –

• Enables you to ensure compliance with the new accounting standards ASC 606 and IFRS 15 through Revenue Management’s centralized repository that stores imported and processed sales data. Revenue Management analyzes the data, and with user-configurable rules automatically groups the data into performance obligations and accounting contracts.

• Determines the transaction price for each accounting contract.

• Allocates the transaction price, using relative allocation method where the total expected consideration, that is the total transaction price of the accounting contract, is allocated to the performance obligations using the relationship of the total transaction price to the total standalone or estimated selling prices.

• Recognizes revenue when each performance obligation is satisfied either at a point in time or over time, based on revenue satisfaction plans , or satisfaction events.

• Establish and manage standalone selling prices or estimated selling prices –

• For Observed Standalone Selling Price (OSSP) calculation, suggested OSSP values are automatically calculated based on imported standalone sales for each item and pre-defined pricing dimensions (such as customer creditworthiness, or geographic region). All the users need to do is to verify the suggested the values and decide whether or not to establish / approve them as revenue prices for any particular period.

• Standalone selling price s(SSP) can be uploaded through spreadsheet integration.

• The standalone selling prices can be tracked in multiple representation forms, such as Unit Selling Price, Discount Percentage of Unit List Price.

• Please note that the term SSP represents calculated standalone selling price or estimated selling price.

Page 5 of 46



Slide notes• Co existence –

• We integrate with on premise, cloud and third party systems.

• Out of the box integration for E-Business Suite products Order Management, Service Contracts, Receivables and General Ledger is supported.

• We also integrate with Fusion Receivables.

• Integration of data from third party sources can also be done using the easy to upload File Based Data Import (FBDI) templates.

• Independent of Billing –

• Revenue is managed independent of billing.

• For EBS products, revenue is managed in Revenue Management while receivables is managed in EBS Receivables.

• For Fusion Receivables, revenue is managed in Revenue Management while receivables is managed in Fusion Receivables.

• Revenue Management Landing Page –

• Our centralized landing page provides the ability to review and resolve customer contract exceptions, especially those that needs your attention, such as contracts pending revenue recognition and OSSP requiring attention.

Notes

Page 6 of 46



Slide notes

• Audit –

• Any changes made to the contract by the system or user are tracked for audit purposes.

• You can be assured that the revenue recognition is compliant with IFRS guidelines, as well as our solution provides complete transparency for audit purposes. All actions taken for establishing (approving) and uploading standalone selling prices are tracked within our system.

Notes

Page 7 of 46



Slide notesWith the demand for automation, many sources of truth, and pressure to comply, what you will achieve by using Revenue Management product is a much more streamlined and powerful revenue department, which will greatly increase your company’s revenue management operational efficiency.

Notes

Page 8 of 46



Slide notesLet’s take a look at the most common business scenario for bundled sales. Say your company has a bundle sale which consists of 3 components: Cloud Subscription which is sold at $100, Training at $20, and Consulting $80. The total deal on customer invoice is $200. This is how your company bills your customer.

Now what does this mean to your company in terms of revenue recognition over a period of time? Does it mean that it can recognize the revenue all-at-once immediately upon billing?

According to the IFRS 15 guidelines, your company needs to correctly allocate the transaction price to various performance obligations in the ratio of SSP. Then, recognize the revenue appropriately over a period of time or at a point in time when the performance obligation is satisfied.

The total expected consideration, that is the total transaction price of the accounting contract, is allocated to the performance obligations using the relationship of the total transaction price to the total standalone or estimated selling prices

In this example, the revenue earned on cloud subscription is recognized over time, training is recognized over a point of time and consulting is recognized over time as the performance obligations are satisfied.

Notes

Page 9 of 46


Slide 12 - Contract Management

Slide notes• You can ensure compliance with ASC 606 and IFRS 15 by configuring Revenue Management system options, defining user configurable contract and performance obligation identification rules, defining satisfaction plans and uploading ESPs /SSPs in Revenue Management. You can then integrate sales cycle data to Revenue Management which will analyze the data for processing.

• Revenue Management analyzes the data, and with user-configurable rules automatically groups the data into performance obligations and accounting contracts, determines the transaction price for each accounting contract, allocates the transaction price across performance obligations in an accounting contract and recognizes revenue when each performance obligation is satisfied either at a point in time or over time based on revenue satisfaction plans or satisfaction events.

• Recognizes revenue independent of billing and automatically accrues contract liability and contract assets.

Notes

Page 10 of 46


Slide 13 - Contract Management

Slide notes• With the key challenges of –

- demand for automation of contracts and performance obligations

- demand for automatic revenue recognition

- having a centralized repository of revenue data

- manage critical revenue data through landing page

- seamless accounting where accounts are derived based on seeded events

- pressure for statutory compliance of accounting standards

you will achieve a much more streamlined and powerful Revenue Department, which will greatly increase your company’s revenue management operational efficiency

Notes

Page 11 of 46


Slide 14 - Manage Observed Standalone Selling Prices

Slide notes• Our solution derives suggested OSSP of each item and pricing dimension combination based on median value of the qualified standalone sales in a given period.

• Pricing Dimension is basically what the company uses to determine the pricing structure of any product, for example, Customer Creditworthiness, or region that the product has been sold.

• The calculated OSSP values are presented in a very easy to understand format. The values are either ‘Suggested Valid’ or ‘Suggested Invalid’ based on a set of pre-defined criteria defined in revenue price profile for enough coverage within the tolerance as well as minimum standalone sales required.

• You can approve the OSSP by choosing to ‘Establish’ the value.

• We also provide advanced revenue price analytic insights through a graph along with trend analysis.

• Any approval actions or exceptions performed are fully tracked for audit purposes.

• Our solution also provides an easy-to-use migration tool, which is an excel spreadsheet, to manually upload SSP on a regular-basis in case OSSP values are unable to be established for any items. This Create Revenue Prices spreadsheet can be launched from the Revenue Price Profile page.

• We also provide a spreadsheet to Manage Revenue Prices in Spreadsheet which is a central location to review SSP of any item in any given period. You may also use it to compare the OSSP of items across periods as well.

Notes

Page 12 of 46


Slide 15 - Manage Observed Standalone Selling Prices

Slide notesNow, let’s talk about the business values that ’Manage Observed Standalone Selling Prices’ brings in –

• The first challenge is that most of our customers still use manual or semi-manual process to calculate OSSP, which is very time consuming. By using our solution, the extraction, aggregation (or the grouping of like-sales) are automated, thus tremendously increasing your revenue department’s productivity as well as efficiency.

• Usually the process to review the OSSP, and determine if the value should be considered or not is not a one-time process. Often time, it involves a couple of iterative process in order to exclude certain internal sales, or adjust observed standalone sales pool set value criteria. By performing this manually, it is prone to human error. Our solution provides very easy-to-use UI interface so that revenue analyst or revenue manager can quickly and easily review and determine qualified standalone sales. And if changes need to be made, our solution seamlessly integrates auto-recalculation of OSSP and provide the value online immediately.

• Our solution also provides analytical information in the form of an industry standard, as well as graph for the OSSP. The visualization we provide helps you quickly determine if you should establish the OSSP or not. This level of insights provide such a great benefit over the manual process.

• We provide a very easy-to-use spreadsheet that you can directly key-in the standalone selling prices and upload to Revenue Management. There is no need to worry about bringing in all standalone sales just to re-calculate OSSP value for the previous periods again.

• Revenue Management provides a centralized repository for standalone selling prices; thus user gets a complete view of the SSP trend of any items across periods without going to multiple sources of truth.

Notes

Page 13 of 46


Slide 16 - Audit and Reports

Slide notes• All actions performed on a contract or SSP either by the system or by user are tracked for audit purposes.

• We provide out-of-the-box report Revenue Contract Account Activity Report in this release.

• Use the Revenue Contract Account Activity report in Revenue Management to review account balances by accounting contract and performance obligation to support audit processes and perform detailed analysis of various accounts like Contract Asset, Contract Liability, Contract Revenue, Contract Discount, Contract Clearing and Contract Variance accounts.

Notes

Page 14 of 46


Slide 17 - Audit and Reports

Slide notes• All approvals, user actions and actions performed by the system are tracked for audit trail. You can review changes and approvals for each accounting contract within the Manage Customer Contracts Page.

• The output of the seeded report Revenue Contract Account Activity report provides account balances for contract or performance obligation.

• This data can be loaded into an analytical tool like Essbase for further analysis.

• Drill down from the summary report to the Manage Customer Contracts page is also supported for further analysis.

Notes

Page 15 of 46


Slide 18 - Revenue Management Landing Page

Slide notes• With the centralized Revenue Management Landing page, you can easily manage your entire revenue department in one location.

• All revenue related tasks are listed in the task pane by category for easy access.

• Search region provides quick and direct access to a contract.

• Report and analytics pane provide easy access to all seeded reports.

• Tasks requiring your immediate attention are pushed to the overview page, which is categorized into three sections

1. Contracts Requiring Attention – which lists contracts that are pending for review, allocation and revenue recognition.

2. Observed Standalone Selling Prices Requiring Attention – which lists OSSP pending establishment and research.

3. Process Monitor – to track scheduled processes.

Notes

Page 16 of 46



Slide notesContracts Requiring Attention

1. The Pending Review tab lists accounting contracts with a total transaction price over a certain threshold amount (significant value contracts).

2. The Pending Allocation tab lists accounting contracts where the standalone selling price has not been established and therefore, the transaction price cannot be allocated across performance obligations.

3. The Pending Revenue Recognition tab lists accounting contracts awaiting the appropriate data to recognize the revenue.

Notes

Page 17 of 46



Slide notesObserved Standalone Selling Prices Requiring Attention

OSSP values pending establishment and pending research are detailed under the Observed Standalone Selling Prices Requiring Attention section.

You can drill down to the details of the Observed Price Set for further action to establish, mark it valid, mark it invalid, mark it as do not establish, discard, and mark it as requiring investigation.

You can also exclude certain standalone sales from the set and recalculate OSSP.

Notes

Page 18 of 46



Slide notes• The Revenue Management Landing Page enables you to focus on contracts of significance and contracts with exceptions to be resolved.

• Actionable information is displayed here which helps you to prioritize the work.

Notes

Page 19 of 46


Slide 22 - Revenue Management Cloud Coexistence

Slide notes• To bring in revenue source data from upstream systems Revenue Management provides out-of-the-box integration with Oracle E-Business Suite (EBS) Order Management, Service Contracts, Receivables and General Ledger.

• Data from Fusion Receivables can be imported into Revenue Management by running the program ‘Import Billing Data from Oracle Fusion Receivables.’

• You can also bring in data from the 3rd party or your legacy application. Data can be brought in through FBDI templates.

• Revenue Management recognizes the revenue following the five step revenue recognition mode, manages standalone selling prices, creates accounting and facilitates audit and analysis.

• Billing data and satisfaction events are interfaced to Revenue Management for revenue recognition and comparison.

Notes

Page 20 of 46



Slide notes• For integration with EBS, you will extract data from EBS products to create a data file.

• This file is placed in UCM after which the Import Revenue Basis Data job will import the revenue data into the base tables of Revenue Management.

• You can also import revenue and billing data from third parties into Revenue Management using predefined File-Based Data Import (FBDI) templates for Revenue Basis and Billing data.

• Please note that the integration with Oracle EBS in pre-built.

Notes

Page 21 of 46



Slide notes• E-Business Suite products use the co-existence solution for integration with Revenue Management in order to bring in source document revenue lines from upstream systems. This co-existence solution provides out-of-the-box integration with the following EBS products Order Management, Service Contracts, Receivables and General Ledger.

• You can also integrate with Fusion Receivables out of the box.

• Revenue Management supports easy to use FBDI templates for upload billing and revenue data from third party applications.

Notes

Page 22 of 46


Slide 25 - Iterative Modeling During Transition Period to Adoption

Slide notes• Revenue Management is designed to help you comply with ASC 606 and IFRS 15.

• Revenue Management provides the capability to proactively contrast and compare sales cycle data between existing accounting standards you are following and various proposals for compliance with the new accounting standards during the transition period until the new ASC 606 and IFRS 15 accounting standards go into effect.

• You can perform what-if iterative studies of how you might implement the new rules, such as the impact of different definitions of contracts and performance obligations, different pricing paradigms, different satisfaction criteria, and so forth.

• Modify the setup for identification rules of contracts or performance obligations, performance obligation templates, implied performance obligation templates or correct the data in the extensible attributes.

• Accounting may be posted to a secondary ledger from which you can extract data to populate into an Enterprise Performance tool.

• Please note that the export of data in accordance with existing standards is the customer's responsibility.

You can use Oracle’ Essbase Dimensional Database or similar tools to compare and contrast your current deferred revenue month end balances with the performance obligation accounting from Revenue Management, and use it to compare and contrast different simulated output from Revenue Management as you validate the rules you use to implement ASC 606 and IFRS 15.

The new GAAP is different from the old – it is a radically new standard. Performance obligations are different to deferred revenue. The only generally true point of commonality between old and new GAAP guidance are monthly GL trial balances.

In Revenue Management, we’ve provided the capability to import your sales cycle data, create rules (identify contract, performance obligation, value the transaction, allocate, accrue, recognize), and then run waterfall reports (transactions over several periods). Send those reports to Essbase.

Page 23 of 46


Do it over and over, as you refine your understanding of the rules.

Then compare and contrast to new to old rules in Essbase. You can do iterative modelling in Revenue Management– you load data once (Your base line sales won’t change. You won’t have to re-import it. You can make changes to the rules (discard prior calculations and run new calculations) and extract resulting balances to Essbase to do another compare and contrast to baseline.

Revenue Management is engineered during the transition period not to populate the Primary Ledger, because you will still be doing old compliance in it. Instead, it will populate a Secondary Ledger. During your iterative study phase, make your entries reversing and reverse them after you have populated the Essbase Cube. This way, only the most recent iteration will be in the Secondary Ledger, but all of them are available in Essbase.

On Cutover day, you will use the finalized accounting rules in your Primary Ledger to start processing with new rules.

Notes

Page 24 of 46



Slide notesRevenue Management is engineered to address these accounting standards so you can:

- Perform what-if iterative studies of how you might implement the new rules, such as the impact of different definitions of contracts and performance obligations, different pricing paradigms, different satisfaction criteria, and so forth.

- Schedule Identify Customer Contracts job and review the generated accounting in DRAFT or FINAL.

- Review the accounting activity and account balances for each contract or performance obligation using the Revenue Contract Account Activity Report and also through the Account Inquiry feature of the General Ledger.

- Perform iterative modeling by discarding the processed contracts, reconfiguring your rules, and running the processes again to create accounting contracts. The imported data remains available for the next iteration.

- Modify the setup for identification rules of contracts or performance obligations, performance obligation templates, implied performance obligation templates or correct the data in the extensible attributes.

- Repeat the steps till you achieve desired results.

• We recommend that to ensure that default accounting will not corrupt your old rules accounting in your general ledger but instead, the accounting may be posted to a secondary ledger from which you can extract data to populate into an Enterprise Performance tool.

Notes

Page 25 of 46



Slide notes• Proactively contrast and compare sales cycle data between existing accounting standards and various proposals for compliance with the new accounting standards during the transition period until the new ASC 606 and IFRS 15 accounting standards go into effect.

• you can configure subledger accounting and ledgers to ensure the accounting will be posted to the appropriate ledger at the appropriate point in time, e.g. secondary ledger during transition, and primary ledger after adoption.

Notes

Page 26 of 46


Slide 28 - Summary of Capabilities

Slide notesHere is the summary of the features I have talked about today –

• Contract Management – follows the five step automated process of revenue management which includes identification of contracts, identification of performance obligations, determination of transaction price, allocation of transaction price and revenue recognition.

• Manage Observed Standalone Selling Prices – allows you to automatically calculate observed standalone selling price or upload standalone selling prices manually where required.

• Audit and Reports – All actions performed on a contract are tracked for audit purposes. Revenue Contract Account Activity Report which allows to review accounting by contract and performance obligation.

• Revenue Management Landing Page – Tasks requiring your immediate attention like Contracts Requiring Attention, Observed Standalone Selling Prices Requiring Attention are pushed to the landing page.

Notes

Page 27 of 46


Slide 29 - Summary of Capabilities

Slide notes• Revenue Management Cloud Coexistence – Integration of Revenue Management with EBS Products Order Management, Service Contracts, Receivables and General Ledger and with Fusion Receivables as well as third party integration is supported. FBDI tools facilitate import of data with ease including error handling.

• Iterative Modeling During Transition period to Adoption – Ability to proactively compare and contrast data between existing accounting standards and new proposals is supported.

Notes

Page 28 of 46


Slide 30 - Functional Architecture

Slide notesThis is an overview of Revenue Management Functional Architecture.

• The first column ‘Extract, Transform, and Load’ is about the source system data that needs to feed into Oracle Revenue Management Cloud in terms of creating metadata such as customers and items, as well as source data for revenue basis processing and invoice data (billing). You’d firstly register your data sources. If you’re using third party systems these needs to be registered. Oracle provides out of the box integration for E-Business Suite OM, AR, and Service Contracts for revenue basis and billing data. An FBDI file for Revenue Basis sets out the structure and fields that are required similar to typical interface approaches. The FBDI contains Headers, lines and sub lines. If some of the data that was imported was missing critical information needed by Revenue Management, you can easily review and fix data import errors by using pre-built ADFdi spreadsheet like integration for download and review of errors and upload of revised data after error correction.

• The second column ‘Manage Standalone Selling Prices’ enables you to configure pricing stratification (for instance defining a flexfield with segments: country, customer type, deal size) and revenue price profiles to enable the calculation of stand alone selling prices (SSP - median value) based on source data imported. You can easily review the SSP data and decide whether the SSP values for certain items should be established or not. If you don’t need the system to calculate the SSP because an Estimated Selling Price is more appropriate to your business, you can upload ESPs through ADFdi, again utilizing pricing stratifications. The SSP or ESP are referred to as revenue prices within Revenue Management and are used for allocation of revenue across performance obligations in a contract.

• The third column ‘5 step Revenue Recognition’ automates the process of creating contracts and performance obligations based on configurable rules engines available in Revenue Management. Once you’ve configured and tested the rules & resulting contracts and performance obligations (you can discard a process and change rules easily) as part of the implementation test phase you can set thresholds to push only contracts over a certain value to the Revenue Manager for review, and allow Revenue Management to process any contracts below that threshold automatically and automatically allocating the revenue across performance obligations.

• There’s a robust subledger accounting engine which generates the accounting for accounting events in Revenue Management, and the accounting rules engine is so flexible that you can change the accounting rules, should you need to.

Page 29 of 46


Slide 31 - Technical Architecture

Slide notes• As mentioned earlier, we provided out-of-the-box integration with Oracle E-business suite applications Order Management, Service Contracts, Receivables and General Ledger through both data view.

• We also provide integration with Fusion Financials cloud for Fusion Receivables.

• We also provide extensibility capability so that you can bring in additional attributes from upstream systems. These attributes can also be used in contract identification rules, performance obligation identification rules and pricing dimension assignments.

• Revenue contract account activity report is provided for audit and analysis.

Notes

Page 30 of 46


Slide 32 - Implementation Advice

Slide notesIn this implementation advice section we will go through what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

Page 31 of 46


Slide 33 - Feature Impact Guidelines

Slide notesThis table depicts key upgrade information for the features covered in this training.

All the features covered are automatically available after upgrade.

The features Manage Observed Standalone Selling Prices, Contract Management, Revenue Management Cloud Coexistence and Iterative Modeling During Transition Period to Adoption have setups associated with them.

All features can be accessed through existing shipped job roles.

Notes

Page 32 of 46


Slide 34 - Setup Summary

Slide notesThe setup for the product Revenue Management is achieved by –

• Define Revenue Common Configuration – has setup tasks related to system options and source document types for integration

• Define Revenue Contracts with Customers – has setup tasks related to contracts and performance obligations

• Define Observed and Estimated Standalone Selling Price – has setup tasks related to calculation and uploading of standalone selling price

• For Iterative Modeling During Transition period to Adoption, you have to define a Secondary Ledger for iterative modeling.

Notes

Page 33 of 46


Slide 35 - Contract Management – Setup Detail

Slide notes• Revenue Management allows you to create contract identification rules to determine the transaction lines that should be included in the contract.

Revenue Management provides three seeded contract identification rules:

1) Identify based on party and time duration. This rule will group all lines belonging to one party created in specific time duration into one revenue contract.

2)Identify based on source document. This rule will group all lines belonging to one source document into one customer contract.

3)Identify each source document line as customer contract.

• Your entity may need to keep at least one of the above seeded rules active. This will ensure that after the Identify Customer Contracts program has processed all lines in the unprocessed pool, every source document line will be part of a customer contract; either a newly identified customer contract or an existing customer contract.

• Rules are executed in the order of priority.

Notes

Page 34 of 46



Slide notes• Revenue Management provides performance obligation identification rules and selects those matching attributes that provide a common link for grouping the source document lines into performance obligations. To make the rules work, the deploying organization needs to capture the common link value in one or more attributes on the source document lines.

• Revenue Management provides three seeded performance obligation identification rules:

1) Identify based on element type. This rule will group source document lines as a performance obligation based on the element type.

2)Identify based on item. This rule will group source document lines as a performance obligation based on the item number on the line.

3)Identify based on source document line. This rule will identify each source document line as performance obligation.


Notes

Page 35 of 46



Slide notes• You can define Performance Obligation Template to handle the items that are grouped together to be easily associated to the Revenue Price Profile.

• The Performance Obligation Templates are specific to the business and cannot be predefined.


Notes

Page 36 of 46



Slide notes• Revenue Management allows you to automatically create performance obligations in a customer contract that are implied in nature but not captured in any upstream application as a source document line. Define implied performance obligation rules to address this requirement.

Notes

Page 37 of 46


Slide 39 - Establish and Manage Standalone Selling Prices – Setup Detail

Slide notes• The Revenue Price Profile governs the key setup attributes of Pricing Dimension structure to be used, revenue price representation type (such as ‘unit selling price’, or ‘discount percentage of the selling price’).

• It also consists of the list of items assigned to the profile. Any item that you need to establish the revenue price for (either calculated OSSP or manually uploaded using the spreadsheet), you would need to assign them to a revenue price profile.

• In addition to that, for each item, you need to specify the number of months to be covered in the calculation of OSSP and whether to include effective period in coverage period or not.

• You’d also specify when you want the system to consider the OSSP as ‘Valid’. This includes the high and low percentage of tolerance range together with its minimum coverage percentage required.

Notes

Page 38 of 46


Slide 40 - Revenue Management Cloud Coexistence – Setup Detail

Slide notesFor integration with source documents, you should enable the source document type for required ledger and provide the start date to extract data.

For integration with Fusion Receivables, you should enable the transaction source for required ledger and provide the start date to extract data.

Notes

Page 39 of 46



Slide notes• In System Options of Oracle E-Business Suite Receivables for integration with Revenue Management, you define the EBS source applications that you would like to integrate and their start dates. And also the EBS Receivables transaction sources and their start dates.

• Revenue Clearing Account has also to be specified for accounting purposes - this account is the corresponding offset to your Accounts Receivable Clearing account.

Notes

Page 40 of 46



Slide notesManage Source Document Types – This is the page you define the source document types which you would like to integrate with. You have to provide the satisfaction measurement model for each source document type.

Notes

Page 41 of 46


Slide 43 - Iterative Modeling During Transition Period – Setup Detail

Slide notesCreate Secondary Ledger – Create a Secondary Ledger for the iterative modeling to which you would like to post the accounting for comparison and analysis.

Notes

Page 42 of 46


Slide 44 - Job Roles

Slide notesThis table details the shipped job roles that will access the new capabilities covered in this training.

The associated duty roles of a Revenue Manager are –

- Revenue Document Management Duty

- Revenue Management Administration Duty

- Revenue Management Compliance Approval Duty

- Revenue Management Inquiry Duty

- Revenue Management Revenue Adjustment Duty

- Revenue Management Revenue Compliance Duty

- Revenue Management Setup Maintenance Duty

The associated duty roles of a Revenue Analyst are –

- Revenue Document Management Duty

- Revenue Management Inquiry Duty

- Revenue Management Revenue Adjustment Duty

- Revenue Management Revenue Compliance Duty

- Revenue Management Setup Maintenance Duty

Page 43 of 46


Notes

Page 44 of 46


Slide 45 - Business Process Information

Slide notesThe business processes associated with the new capabilities covered in this training are detailed here.

The high level business process is Manage Customer Revenue Life Cycle with activities

1) Manage Customer Contract Source Data

2) Manage Customer Contract Obligations and Allocations

3) Recognize Revenue for Customer Contracts

4) Calculate Observed Standalone Selling Price

5) Approve Observed Standalone Selling Price and

6) Upload Standalone Selling Prices via Spreadsheet

Notes

Page 45 of 46


Slide 46 - Associated Release Training

Slide notesOther training modules that are related to these new capabilities and are recommended viewing are –

• Contract Management

• Establish and Manage Standalone Selling Prices

• Revenue Management Cloud Coexistence

• Configuration of Revenue Management

This concludes this presentation, thank you for listening. You can easily pause and rewind any of these slides if you require additional time to take in the detail.

Notes

Page 46 of 46

Documents

Adobe Captivate - Oracledownload.oracle.com/ocomdocs/global/fu… · Web view · 2016-11-29These five steps are the key steps laid out in ASC 606 and IFRS 15. ... • For EBS products,