1.) Prerequisites for SFDC, Revenue and Billing data.
Before you work on getting the SFDC into RMCS, you need to have the following reference
data/understanding in place :-
Enterprise Structures – such as legal entities, ledgers, and business units
Customers – Party, Party Sites, Customer Account, Customer Account Sites.
Inventory Items (Hardware,Software,Service & Extended warranties)
SLA For Revenue Management, Cost Management and AR Invoicing (To recognize for
Normal invoices and not derive from RMCS the Revenue Recognition)
Sales Order Activities mapped with AR transaction types (Invoice, Credit Memo &
Debit Memo)
Sales Order types for which revenue recognition is not applicable.
Sales Order Events which could contribute to Revision, Change Order, Return
Material Authorization, Cancellation
Accounting/Invoicing treatment for Demo/Freebies Order.
SFDC mapping file required to create contracts in Revenue Management to reflect
the shipped sales order and carve outs.
Error Handling Mechanism while importing the contracts from SFDC to RMCS using
OIC
Finance team to provide the SSP (Standalone Selling Price) in Standard ADFDI Format
and addition/revisions for future periods to be discussed.
Business understanding the newly introduced performance obligation accounting
related to Contract Asset, Contract liability and Revenue Clearing.
Scenario based accounting entries with satisfaction criteria related to Revenue
recognition.
CDS process of recognizing the revenue through AR and VBS using RMCS for
recognizing.
Gross Margin BIP report logic
RMCS CWB with components that needs to be synchronized back to SFDC for data
integration/migration (Ex: Scheduling rules, Source document type, Source System,
LE, BU, Item Number etc.)
Historical revenue and billing data for iterative modelling and comparative analysis.
2.) Integration From SFDC to RMCS (Technical & Functional Architecture)
There are three types of integrated data in Revenue Management:
1. Contract-related information such as sales order lines.
2. Billing-related information, such as sales invoices.
3. Satisfaction-related information such as product shipment and
fulfilment, or Order milestone completion.
Prior to Performing a third-party or spreadsheet integration, you must register the source
system so that you can then bring data into the Oracle Cloud and over to the Revenue
Management interface tables. The Steps to Registering a Source System are:
1. Create a source system within the Trading Community Model
2. Import a source system reference file from a Spreadsheet
If Revenue contract data is captured in a SFDC and needs to be pulled into RMCS .
We need to use two FBDI data templates to load source data. The first is the
Revenue Basis Data Import template used to load the contract data with headers,
lines, and sublines. The second is the Billing Data Import template used to load
billing data into RMCS.
With help of OIC staging, the equivalent data mapping has to be populated from
SFDC and loaded into the UCM server with ImportBulkData Service(The
importBulkData operation uploads a file to the Oracle Universal Content
Management (UCM) server based on the document details specified and submits an
ESS job to load and import the uploaded files to an application table), Once the file is
placed into the UCM server, run/schedule the "Load Interface File for Import" with
Import Revenue basis data program to load the file data into RMCS interface tables.
Import
Interface Id Family Product Business Object UCM Account
Job
VRMIRB
1 FIN VRM revenueBasisLine fin/RevenueManagement/import
D
VRMIBD receivablesInvoic
2 FIN VRM fin/RevenueManagement/import
P e
The contract data is loaded into the following three interface tables –
VRM_SOURCE_DOCUMENTS (Contract Header Information)
VRM_SOURCE_DOC_LINES (Contract Line Information)
VRM_SOURCE_DOC_SUB_LINES (Satisfaction Event Information)
The billing data is loaded into the below interface table –
VRM_BILLING_LINE_DETAILS (Billing Information)
Once you sign in to cloud the data and personalized content is loaded and into the
interface tables, run the "Validate Customer Contract Source Data" program. This
program verifies the data into the interface table to ensure the data is all good to
create the contract. If there are any errors, it is flagged with an error message that
can be viewed and corrected using the "Correct Contract Document Errors in
Spreadsheet" option.
After validating the customer contract data in the interface tables, the next step is to
run the process "Identify Customer Contracts." This process creates revenue
contracts with performance obligations, promise details, and satisfaction events. It
also recognizes revenue if performance obligations are satisfied through satisfaction
events.
The process "Recognize Revenue of Customer Contracts" generates the journal entries to
account for the billing of performance obligations.
To import data into Fusion RMCS, you can use ImportBulkData service.
Request Payload:
Request Payload:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/
model/erpIntegrationService/types/"
xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/
model/erpIntegrationService/">
<soapenv:Header/>
<soapenv:Body>
<typ:importBulkData>
<typ:document>
<!--Optional:-->
<erp:Content>UEsDBBQAAAAIAIRhdUuBB6ZvXQEAAAoNAAAeAAAAVnJtUmJsSW1w
b3J0XzIwMTcxMTIxXzEyMTIuZGF07ZZNb4IwGIDvS/
YfSO8mFKduxw467SLQ0bJlJ0KcBxODC+jF7MePqjgsUNgnJiN5Ds3b7/
Z9CmAC3sCR4eBG1/OBFNN1+HAwgkMprsPefRj14KiqDcKW1KU5mHBTu/
UZcTBj2thzfVqs3iSLaJ4k2jhebV5rh9yT7bBqVx3fARr9K7nUEOvpJBPNVbSOw9k6AZcXY
Cq1zS4RKsb7TCpXsd1OD7NAozBYZfRMUB3Or9Lkdv4t4lAcUHo44lEDKocInbgOrp0ij2
RViuuhwMaI+R4OHnzkcMKfA4Y4YXdk92B/
mFc3+Bfo62lqKIw2FH1/0GgxDRyUGX19xkaDtpxqcjttkf8N6cOeNZ/
tyy2SOW5IcRrG60W41Og8XqxeNLoMI9BAe2Yjj5dmqwK1+BR7xLX+TnuhPCuGxZJ2aw
jwI3Z4wGz7+Cal1ULVMukluu9NRymSA/mX4pAr+b/
Md1BLAQIUABQAAAAIAIRhdUuBB6ZvXQEAAAoNAAAeAAAAAAAAAAEAIAAAAAAAAA
BWcm1SYmxJbXBvcnRfMjAxNzExMjFfMTIxMi5kYXRQSwUGAAAAAAEAAQBMAAAAm
QEAAAAA</erp:Content>
<erp:FileName>Vrmrevenueimport_20171122_sha6.zip</erp:FileName>
<erp:ContentType>zip</erp:ContentType>
<erp:DocumentTitle>Vrmrevenueimport_20171122_sha6</erp:DocumentTitle>
<erp:DocumentAuthor>[email protected]</erp:DocumentAuthor>
<erp:DocumentSecurityGroup>FAFusionImportExport</erp:DocumentSecurityGroup
>
<erp:DocumentAccount>fin$/revenueManagement$/import$</erp:DocumentAccou
nt>
<erp:DocumentName>Vrmrevenueimport_20171122_sha6</erp:DocumentName>
</typ:document>
<typ:jobDetails>
<erp:JobName>/oracle/apps/ess/financials/revenueManagement/shared,VRMPRCBL
</erp:JobName>
<erp:ParameterList>#NULL</erp:ParameterList>
</typ:jobDetails>
<typ:notificationCode>#NULL</typ:notificationCode>
<typ:callbackURL>#NULL</typ:callbackURL>
<typ:jobOptions>InterfaceDetails=54</typ:jobOptions>
</typ:importBulkData>
</soapenv:Body>
</soapenv:Envelope>
Response Payload:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsa="http://www.w3.org/2005/08/addressing">
<env:Header>
<wsa:Action>http://xmlns.oracle.com/apps/financials/commonModules/shared/model/
erpIntegrationService//ErpIntegrationService/importBulkDataResponse</wsa:Action>
<wsa:MessageID>urn:uuid:ca4a1c06-3465-4676-8676-a464841fb51d</wsa:MessageID>
</env:Header>
<env:Body>
<ns0:importBulkDataResponse
xmlns:ns0="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/
erpIntegrationService/types/">
<result xmlns="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/
erpIntegrationService/types/">70074</result>
</ns0:importBulkDataResponse>
</env:Body>
</env:Envelope>
Importing Bulk Data into Oracle ERP Cloud using FBDI through OIC
1. Get the required fields from the flat file by configuring its respective adapter.
2. The records are looped and CSV files for the FBDI are created in the OIC stage, and
its values are mapped from the looped records to create the CSV template.
3. A properties file with a .csv extension has to be written for the RMCS program to run
the FBDI.
4. All the CSV files are zipped and passed to Oracle ERP Cloud adapter to run the
program.
5. A call back integration is created with app-driven orchestration to run immediately
after the program running is completed to check the status of the load.
6. The Source system connection is configured and is used as invoke to get the required
fields from the source to be used in the FBDI mapping.
7. The FBDI file is built in the OIC stage and the values are mapped from source to FBDI
template fields:
This 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 e.g. 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, Projects, and Service Contracts for revenue basis and billing data. A FBDI file for
Revenue Basis sets out the structure and fields that are required e.g. similar to typical
interface approaches e.g. The FBDI contains Headers, lines and sublines.
If some of the data that was imported was missing critical information needed by Oracle
Revenue Management Cloud, 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 standalone 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 Oracle Revenue
Management Cloud, 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 Oracle
Revenue Management Cloud. 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 Oracle Revenue Management
Cloud 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 Oracle Revenue Management Cloud , and the accounting rules engine
is so flexible that you can change the accounting rules, should you need to.
Error Correction for Integrations
The below is a spreadsheet template that Oracle provide that allows you to not only
correct import errors but check for errors. This function is called "Correct Contract
Document Errors in Spreadsheet" and is found by navigating to the Revenue
Management work area.
There is a spreadsheet template that Oracle provide that allows you to not only correct
import errors but check for errors. This function is called "Correct Contract Document Errors
in Spreadsheet" and is found by navigating to the Revenue Management work area.
4. Manage Customer Contracts Once Imported into RMCS
5. Accounting in Revenue Management
Here is an overview of which parts of the data is derived based on source data and
configurations in Oracle Revenue Management Cloud, and the accounting generated by
Oracle Revenue Management Cloud
Source data can include named attribute data (such as customer party and site, customer
purchase order) and extensible attributes which can be specific to your business and can be
used as common identifiers to create customer contracts such as opportunity number or
quote number. You may also have other extensible attributes that can help identify if two
source lines should be grouped into one performance obligation with two promised details
or should be created as two distinct performance obligations.
Business Event – in RMCS you can configure satisfaction plans. When importing source data
you can reference such satisfaction plans and provide start date and end date. In addition,
for performance obligations that are Point in Time events you can import the satisfaction
event and satisfaction date.
RMCS will process initial performance obligations (typically CR Contract Liability and DR
Contract Asset) and process satisfaction events, utilizing the Subledger Accounting Rules
engine to generate the accounting for revenue and reducing the contract liability.
Contract Price Variance represents the differences in the CA & CL accounts caused due to
the fluctuations in foreign exchange rates
Revenue management will pick up contract price variance code combination account from
manage revenue system options page.
