Adobe Captivate - Oracle



Slide 3 - Oracle Financials Cloud Release 11

[pic]

Slide notes

Hello, my name is Prescilla. Welcome to training for Release 11.

In this session we will talk about what is available in Oracle Financials Cloud for Revenue Management Coexistence.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 4 - Agenda

[pic]

Slide notes

For the enhancements covered in this training, we’ll give an overview, followed by more detail to explain how you can use them, and what business value they bring.

Then we’ll walk you through a demonstration.

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

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 5 - Enhancements Overview : Revenue Management Cloud Coexistence

[pic]

Slide notes

• The coexistence feature enables you to deploy a uniform, centralized and comprehensive view of contracts with customers, unifying the details tracked in a variety of order management, retail point of sales, and billing systems.

• The product is integrated with both Oracle Financials Cloud and with Oracle E-Business Suite. Robust integration is available with third party applications. Integrated data includes sales orders, service contracts, sales invoices and other relevant sales and fulfillment data. Data from the various source systems is processed and managed centrally in Oracle Revenue Management Cloud.

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

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

Notes

| |

| |

| |

| |

| |

| |

| |

Slide 6 - Integration with Oracle E-Business Suite

[pic]

Slide notes

• Oracle E-Business Suite (EBS) products use the coexistence solution for integration with Revenue Management to bring in source document revenue lines from upstream systems. This coexistence solution provides out-of-the-box integration with the EBS products Order Management, Service Contracts and Receivables.

• Steps for integration with Oracle EBS products

• Apply Patches 16931007 and 16512637

• Configure the system options in EBS Receivables and Revenue Management

• Extract data from EBS by running the program Extract Revenue Basis Data

• Create revenue data file by running the program Create Revenue Management Data Export File

• Create billing data file by running the program Create Billing Data File

• Run the Import Revenue Basis Data program to import the revenue basis data.

• Run the Import Billing Data program to import the billing data.

• Validate and correct source data through FBDI

Notes

| |

Slide 7 - Slide 5

[pic]

Slide notes

-Sales order and return lines are extracted as source documents. These form the basis for revenue recognition process.

-Order lines are interfaced when the lines are billed.

-Accounting contracts are created to manage the revenue recognition process.

-Contracts are created for the sales orders.

-Fulfillments are interfaced as satisfaction events.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 8 - Slide 6

[pic]

Slide notes

-The service contract lines that are approved will be interfaced.

-Billing and revenue schedules are managed independently.

-Service contracts manages billing schedules.

-Revenue Management manages revenue schedules.

-Document versions are created to track terminations and changes to price and service duration.

-Contract terminations and changes to price and service duration are supported.

Notes

| |

| |

| |

| |

| |

| |

| |

Slide 9 - Slide 7

[pic]

Slide notes

-Specific transaction sources for Revenue Management integration pass through for non-EBS applications.

- EBS Receivables will only manage receivables and the revenue will be managed in Revenue Management after integration.

-Transactions are interfaced after they are completed in EBS Receivables.

-Contingencies are interfaced as satisfaction events.

-Invoice amount is credited to revenue clearing account.

-Billing lines are interfaced for comparison with revenue lines.

Notes

| |

| |

| |

| |

| |

| |

| |

Slide 10 - Slide 8

[pic]

Slide notes

For EBS customers, EBS General Ledger is the source of truth for financial reporting.

The accounting created in the Revenue Management for the sales cycle data integrated from EBS products Order Management, Service Contracts and Receivables is transferred to the EBS General Ledger through Fusion Subledger Accounting.

Let us understand how this can be done.

• Set the profile option “Enable Transfer to Oracle EBS GL” to Yes to make the “Transfer to Oracle EBS GL” option visible in “Manage Subledger Application” setup UI. And for Revenue Management, set the transfer option to ‘Oracle EBS GL’

• When create accounting is run, the accounting entries will NOT be posted into Financials cloud. But the accounting entries will be posted to a flat file.

• This file is placed in UCM to make it available for EBS General Ledger

• Run the program EBIZ GL:Import Journal Entries From Fusion Subledger Accounting to trigger the accounting entries to be posted into EBS General Ledger.

Notes

| |

| |

| |

Slide 11 - Integration with Oracle E-Business Suite

[pic]

Slide notes

-EBS extract contains all required and commonly used data elements.

-Use transformation hook to bring additional optional data elements for which extensible attributes are provided.

-Additional data elements may reside within EBS or outside Legacy applications, data warehouses, etc.

-Plug your custom code to add data elements to the standard extract. The code hook provided by the EBS extract program has to be used to populate values in these generic columns of the interface tables. Users have to write custom code to select values from the desired table or view and populate the values in the generic columns.

-Extensible attributes are used in Revenue Management configurations and processing, displayed on UI’s and available for reporting.

Notes

| |

| |

| |

| |

| |

| |

| |

Slide 12 - Integration with Oracle E-Business Suite

[pic]

Slide notes

-Create identical copies in Fusion Trading Community Architecture and Fusion Product Information Management using standard import interface

-Create cross reference records

-Pass account and site identifiers of EBS as cross reference value

-Pass item number of EBS as cross reference value

-Revenue Management derives Fusion values using cross reference records

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 13 - Integration with Oracle E-Business Suite

[pic]

Slide notes

To import customer data in bulk -

1. Create an import batch in Fusion (either manually or calling an API)

2. Get the batch_id of the import batch

3. Insert customer & item data records into the interface tables along with the batch_id

4. Import the batch by running the ESS job and providing the batch_id as the parameter

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 14 - Integration with Oracle E-Business Suite

[pic]

Slide notes

To import items in bulk -

1. Download the Import Items template

2. Fill the template with appropriate values and generate the CSV file

3. Upload the zip file in UCM

4. Insert data into interface table using ESS job: 'Load Interface File for Import'

5. Complete the import using Schedule Process: 'Item Import'

6. You can verify the items imported in Manage Items

Notes

| |

| |

| |

| |

| |

| |

Slide 15 - Integration with Oracle E-Business Suite

[pic]

Slide notes

-Fusion reference attribute values are derived using names like

Inventory org, business unit, legal entity, memo line

-It is recommended to have identical names in EBS and Fusion (Recommended)

-Alternatively, use transformation hook in EBS to provide Fusion values

When you have done optimization of structures in Fusion

When you cannot use EBS names in Fusion

Notes

| |

| |

| |

| |

| |

| |

| |

Slide 16 - Integration with Oracle E-Business Suite

[pic]

Slide notes

-Run the Extract Revenue Basis Data concurrent program to extract data from the source applications and load it in the interface tables

-Run the Create Revenue Management Data Export File program to convert the interface data into data file

-Data file is transferred to Revenue Management through Universal Content Management application

-You can automate these processes by scheduling the jobs to run periodically

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 17 - Integration with Oracle E-Business Suite

[pic]

Slide notes

-Run Load Interface File for Import program to import and load the revenue basis data into Revenue Management Interface tables by selecting the dat file.

-Run Validate Customer Contracts Source Data program to transform and validate the data.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 18 - Integration with Financials Cloud

[pic]

Slide notes

• In this release, integration with Financials Cloud is only for Fusion Receivables.

• Receivable transactions (invoices and credit memos) in Fusion Receivables can be sent to revenue management by running the scheduled process ‘Import Billing Data from Oracle Fusion Receivables.’

• Contingencies will be interfaced as satisfaction events.

• This feature will be used for sending transactions from applications that do not integrate directly with Revenue Management. For such documents, Fusion Receivables will only manage receivables and the revenue will be managed in Revenue Management.

• User can decide which transactions can be sent to Revenue Management based on the transaction source.

• Once a transaction source is enabled for integration, all the transactions created with that source will be sent to Revenue Management as the source document that forms the basis for creating the revenue.

• The start date is the attribute that determines the point of time when the revenue management function is transitioned from Fusion Receivables to Revenue Management for a transaction source.

• Start date refers to the transaction creation date and not the transaction date. All the transactions created on or after the start date will be sent to Revenue Management as source documents whose revenue will be managed in Revenue Management. Once the start date is entered and saved, the user will not be allowed to update it. User can end date it if he wants to switch back to Fusion Receivables.

• Billing data will be updated periodically in Revenue Management tables for comparison with revenue through the scheduled process ‘Import Billing Data from Oracle Fusion Receivables.’ You can automate to schedule this process periodically.

Notes

Slide 19 - Data Upload using FBDI templates

[pic]

Slide notes

• 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.

• You should prepare the table data and fill in each worksheet of the template with the appropriate data.

• After the data is prepared you should generate a DAT file.

• Import this file using the File Import and Export tool.

• Run the Import Revenue Basis Data program to import the revenue basis data.

• Run the Import Billing Data program to import the billing data.

• You can automate these processes by scheduling the jobs to run periodically.

Notes

| |

| |

| |

| |

| |

| |

Slide 20 - Data Upload using FBDI templates

[pic]

Slide notes

-Any errors after executing the program ‘Validate Customer Contract Source Data’ can be reprocessed.

-Correct import errors using the Correct Contract Document Errors spreadsheet.

-Launch the spreadsheet from the task pane landing page.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 21 - Revenue Management Cloud Coexistence

[pic]

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 EBS products Order Management, Service Contracts, Receivables and General Ledger.

• You can also integrate with Fusion Receivables.

• Import revenue and billing data from third party applications into Revenue Management using predefined File-Based Data Import (FBDI) templates for Revenue Basis and Billing data.

• Errors during import can be corrected using FBDI tool.

Notes

| |

| |

| |

| |

| |

| |

Slide 22 - Summary of Enhancement Capabilities

[pic]

Slide notes

Here is the summary of the features I have talked about today .

• The co-existence feature enables integration of EBS products with Revenue Management. Out of the box integration is supported for Order Management, Service Contracts, Receivables and General Ledger.

• Reference attribute values are transformed and validated data is transferred to Revenue Management.

• EBS and Fusion account codes are mapped using General Ledger Chart of Accounts Mapping feature.

• Data is extracted from the source applications and loaded into the interface tables; this data is converted into a data file and imported to Revenue Management.

• Any errors during import can be corrected through FBDI spreadsheet.

• Revenue Management integrates with Fusion Receivables for the revenue to be managed in Revenue Management.

• Revenue and billing data from third party applications can be uploaded using FBDI spreadsheets.

Notes

| |

| |

| |

Slide 23 - Implementation Advice

[pic]

Slide notes

In 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

| |

| |

| |

| |

| |

| |

| |

| |

Slide 24 - Feature Impact Guidelines

[pic]

Slide notes

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

All the above features are automatically available after upgrade.

Integration with EBS and Integration Fusion Receivables has a setup associated with it – setup specifies are covered later in this section.

All features can be accessed through existing shipped job roles.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 25 - Setup Summary - Integration with E-Business Suite

[pic]

Slide notes

The setup for Integration with EBS is achieved by

• Apply patch for integration

• Set the profile option AR: Source System Value for Revenue Management to EBIZ

• In the System Options for EBS Receivables

• Enable the source documents by giving a start date

• Enable the transaction sources by giving a start date

• Provide revenue clearing account and optionally check enable general ledger account code

• In Financials Cloud

• Set the transfer option to ‘Oracle EBS GL’ in Manage Subledger Application for Revenue Management subledger.

Notes

| |

| |

| |

Slide 26 - Integration with Oracle E-Business Suite – Setup Detail

[pic]

Slide notes

The Revenue Management tab in the system options of EBS Receivables will be enabled only when the Revenue Management integration patches are installed.

The profile option “AR: Source System Value for Revenue Management” is used to point to the source system integrated with Revenue Management. Users need to set the value to “EBIZ” for EBS. This is a mandatory setup to extract the revenue basis data from EBS.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 27 - Integration with Oracle E-Business Suite – Setup Detail

[pic]

Slide notes

Enable Source Application Documents:

-Enable Source Application Documents region allows the user to enable the documents in the source systems for integration with revenue management.

-Use start date as cut-off date for transition to Revenue Management.

-All documents created in the source application on or after the start date are eligible and transferred to Revenue Management.

-Start date cannot be changed after one or more documents are extracted for the relevant application.

Enable Receivable Transactions:

-This region allows the user to send receivable transactions (invoices and credit memos) in EBS Receivables to Revenue Management for revenue management purpose.

-This feature will be used for sending transactions from applications that do not integrate directly with Revenue Management. For such documents, EBS Receivables will only manage receivables and the revenue will be managed in Revenue Management.

 -The user can decide which transactions to send to Revenue Management based on the transaction source.

-The start date is the attribute that determines the point of time when the revenue management function is transitioned from EBS Receivables for a transaction source.

-Once the start date is entered and saved, the user will not be allowed to update it. This means that once the revenue management function for a transaction source is transitioned to FRM it cannot be switched backed to EBS AR.

 -The user will be allowed to add new records in this region but will not be allowed to delete the existing records.

Accounting:

-This region allows the user to specify the options related to accounting of the documents whose revenue is managed in Revenue Management.

-Revenue Clearing Account: This field allows the user to specify the revenue clearing account to be used when the revenue recognition is managed in Revenue Management. EBS Receivables will credit/debit this account instead of the revenue account. This field will be mandatory if any source document type or transaction source is enabled for integration.

-Transform General Ledger Account Codes is required only when Project Billing application is used; this is for future releases.

• Chart of Accounts Mapping is used when the chart of accounts of EBS and Fusion are not identical; Transformation is executed by the EBS extract program; The transformation will be performed using the chart of accounts (COA) mapping feature of the EBS General Ledger.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 28 - Integration with Oracle E-Business Suite – Setup Detail

[pic]

Slide notes

In Manage Subledger Applications, you will have the option to select EBS General Ledger as the target General Ledger for accounting for each subledger. For Revenue Management, select the transfer option ‘Oracle EBS GL’ to initiate the transfer of accounting entries.

You have to set the profile option “Enable Transfer to Oracle EBS GL” to Yes to make the “Transfer to Oracle EBS GL” option visible in “Manage Subledger Application” setup UI.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 29 - Setup Summary - Integration with Financials Cloud

[pic]

Slide notes

The setup is performed under Define Common Revenue Configuration.

The setup for Integration with Fusion Receivables and is achieved by

• Setting up the start date for the transaction sources of Fusion Receivables

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 30 - Integration with Financials Cloud – Setup Detail

[pic]

Slide notes

For 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

| |

| |

| |

| |

| |

| |

| |

| |

Slide 31 - Job Roles

[pic]

Slide notes

This 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

Slide 32 - Business Process Information

[pic]

Slide notes

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

The high level business process for integration with EBS is Define Revenue Management with activity Manage E-Business Suite Receivables System Options for Coexistence.

The high level business process for integration with Fusion is Define Common Revenue Configuration with activity Manage Revenue System Options.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 33 - Associated Release Training

[pic]

Slide notes

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

• Introduction to Revenue Management

• Contract Management

• Establish and Manage Standalone Selling Prices

• 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

| |

| |

| |

| |

| |

| |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download