1. Using Revenue Management
  2. Guidelines for Integrating Revenue Management with Oracle E-Business Suite

Guidelines for Integrating Revenue Management with Oracle E-Business Suite

Oracle Revenue Management enables you to automate end-to-end revenue compliance and revenue recognition processes for your enterprise.

You can integrate Oracle E-Business Suite products with Revenue Management to import source document lines from upstream sales cycle systems into Revenue Management.

Caution: Once you enable a transaction source, you can't disable it. Therefore, before integrating your data with any of these products, review and complete the required integration setup steps as detailed in the Revenue Management Cloud Service solution for Oracle E-Business Suite Documentation Note (2244173.1) on My Oracle Support at https://support.oracle.com.

Use this feature to integrate the following Oracle E-Business Suite products with Revenue Management:

  • Receivables: All transactions in a status of Completed are integrated into Revenue Management based on the start date and transaction sources specified on the System Options page. Fulfillment of contingencies in Oracle E-Business Suite Receivables are sent to Revenue Management as satisfaction events for revenue recognition.

  • Order Management: All sales orders and returns in a status of Booked are integrated into Revenue Management based on the start date and transaction sources specified on the System Options page. The Extract Revenue Basis Data process sends satisfaction events to Revenue Management based on fulfillment of orders.

  • Service Contracts: All approved service contracts are integrated into Revenue Management based on the start date specified on the System Options page. Oracle E-Business Suite Service Contracts manages billing schedules and Revenue Management manages revenue schedules. Revenue Management creates document versions to track terminations and changes to price and service duration. Revenue Management supports contract terminations and changes to price and service duration.

  • General Ledger: The accounting entries created in Revenue Management for the transactions extracted from Oracle E-Business Suite products can be integrated back into Oracle E-Business Suite General Ledger.

The start date can be any date on or after January 1, 2014. During the transition phase, you can:

  • Import historic revenue and billing data into Revenue Management.

  • Run all of the required processes to create and value customer contracts.

  • Allocate the transaction price across performance obligations in the contract.

  • Create accounting entries.

During this phase, you can discard the derived contracts, change contract and performance obligation identification rules, and rerun the processes to create the contracts based on your latest configuration.

Extract Data from Oracle E-Business Suite Applications

To import data from Oracle E-Business Suite Receivables, Order Management, and Service Contracts into Revenue Management, complete the following steps in Oracle E-Business Suite:

  1. Run the Extract Revenue Basis Data process from the Oracle E-Business Suite application that you want to extract data from.

  2. Run the Create Revenue Management Data Export File process from the Oracle E-Business Suite application that you want to extract data from.

  3. Run the Create Billing Data File process to create the billing data file from Oracle E-Business Suite Receivables.

The Create Revenue Management Data Export File process and the Create Billing Data File process trigger the Fusion File Transfer, ESS Job Loader process, which transfers the files to Oracle Receivables. This process initiates the File Import and Export process in Oracle Fusion Cloud Applications and the files are imported into the Revenue Management tables.

After the Data is Imported from Oracle E-Business Suite Applications

After extracting the data from Oracle E-Business Suite, complete the following steps in Revenue Management:

  1. Validate and correct the source data in Revenue Management:

    • Run the Validate Customer Contract Data process.

    • Correct validation errors using the Correct Contract Document Errors in Spreadsheet task.

  2. Run the Identify Customer Contracts process to identify and create contracts and to recognize revenue.

Transfer Data to Oracle E-Business Suite General Ledger

The Create Accounting process creates accounting entries for performance obligations in accounting contracts in Revenue Management based on the sales cycle data imported from Oracle E-Business Suite Order Management, Service Contracts, and Receivables. You can transfer the accounting entries from Revenue Management to Oracle E-Business Suite General Ledger through a flat file.

To create the accounting entries and transfer them to Oracle E-Business Suite General Ledger, complete the following steps:

  1. Within Oracle Financials Cloud, navigate to the Manage Profile Options task.

  2. Set the Enable Transfer to Oracle EBS GL profile option to Yes.

  3. Navigate to the Manage Subledger Accounting task from Setup and Maintenance. For the subledger Revenue Management, set the transfer option to Oracle EBS GL.

  4. Run the Create Accounting process. The process posts the accounting entries to a flat file. The file is available for further processing in Oracle E-Business Suite General Ledger.

  5. Run the EBIZ GL: Import Journal Entries from Fusion Subledger Accounting process in Oracle E-Business Suite General Ledger to trigger the accounting entries to be posted into Oracle E-Business Suite General Ledger.

Extract Additional Data Elements from Oracle E-Business Suite

The Create Revenue Management Data Export File process extracts all required and commonly used data elements.

To extract additional data elements not captured by the standard process, use the transformation hook provided by the Create Revenue Management Data Export File process. With this transformation hook you can extract:

  • Additional data elements from within Oracle E-Business Suite

  • Additional data elements from external locations such as legacy applications and data warehouses

The transformation hook then populates the values in the interface tables.

You can use company-defined codes to select values from the specified table or view and populate the values in the generic columns. These additional data elements can be used in Revenue Management as configurable attributes in defining rules.

Note: User interface pages don't display this information by default. You can use descriptive flexfields to display the information.

Import Customers and Items

Before importing customers and items, create identical copies of the customers and items in Oracle Trading Community Architecture and Oracle Product Information Management using the file-based data import tools. In the file-based data import spreadsheets, provide the Oracle E-Business Suite account and site identifiers as cross reference values for customers and the numbers in Oracle E-Business Suite used to identify the items as cross reference values for items. Revenue Management derives the values using the cross reference records.

Import multiple customer data in Oracle Receivables. For more information about customer data, see the Oracle Financials Cloud Implementing Receivables Credit to Cash guide.

Import multiple items in Oracle Product Information Management. For more information about items, see the Oracle SCM Cloud Implementing Product Management guide.