| Oracle® Application Integration Architecture Oracle Communications Billing and Revenue Management Integration Pack for Oracle E-Business Suite: Revenue Accounting Implementation Guide Release 11.1 Part Number E27226-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Oracle Communications Billing and Revenue Management Integration Pack for Oracle E-Business Suite: Revenue Accounting Implementation Guide Release 11.1 Part Number E27226-01 |
|
|
PDF · Mobi · ePub |
This chapter describes how to set up the process integration for revenue management integration and lists the prerequisites. It discusses how to perform setup tasks, configure and generate general ledger (GL) data in Oracle Communications Billing and Revenue Management (Oracle BRM), and how to transform the GL data.
This chapter includes the following sections:
Section 2.2, "Setting Up the Revenue Management Integration"
Section 2.4, "Configuring and Generating GL Data in Oracle BRM"
Complete these tasks before you install, deploy, configure, and run the process integration for revenue management:
Install ODI.
Install the revenue management integration.
For more information, see the Oracle Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations.
Install Oracle BRM GL and complete the initial setup tasks.
To obtain a complete list of the initial setup tasks, see the Oracle BRM product documentation.
Install Oracle E-Business Suite and Oracle General Ledger Release 11.5.10 CU2 or 12.1.1 and complete its initial setup tasks.
To obtain a complete list of Oracle GL setup tasks, refer to the Release 11.5.10 CU2 or 12.1.1 Oracle GL product documentation. Install Oracle E-Business Suite General Ledger Release 11.5.10 CU2 Seed Patch 6012471 or Oracle E-Business Suite General Ledger Release 12.1.1 Seed Patch 8344349. If the patch is absent or not available, make the following changes manually in Oracle GL:
Add the Portal GL Journal Source.
Add these Journal categories:
Unbilled unearned
Unbilled earned
Billed unearned
Billed earned
Prior billed earned
Billed
Unbilled
Note:
If you are applying Seed Patch to Oracle E-Business Suite General Ledger Release 12.1.1, manually change the Journal category Prior Billed earned to Prior billed earned in Oracle GL.
Journal categories are case sensitive and must match the Oracle BRM configuration.
To set up the revenue management integration, perform these steps:
Configure Oracle General Ledger (Oracle GL) and its Accounting Flexfield.
Map and configure Oracle GL accounts into Oracle BRM.
Generate GL data in Oracle BRM.
Rerun reports if the system identifies errors. The system moves GL data to the directory that you specified in Oracle BRM and Oracle Data Integrator (ODI).
Use ODI to pick up the GL data and load the GL Interface table with the accounting transactions.
Handle re-runs. If an error occurs, you must fix the source system and export the XML files again.
Use Oracle GL to import the journals into the Oracle GL application.
Manually or automatically import the reports into journal entries.
Optionally, you can delete the interface data if the system identifies an error before importing the interface data.
Use Oracle GL to review and post or delete. With deletion, the system deletes the data from both the interface tables and the journals.
Post journals to GL accounts using the Oracle GL application.
Manually or automatically post the imported journal entries into the corresponding GL accounts.
Optionally, delete the journal entries if the system identifies an error after the batch is imported but before it is posted.
Optionally, reverse the journal if the system identifies an error after posting.
Reconcile or review journal entries.
Review journal entries and, if errors occurred, create the appropriate adjustment entries.
This section discusses these topics:
Complete these tasks in Oracle GL:
Define your Set of Books (SOB) with Oracle E-Business Suite R11.5.10 CU2 or ledgers with Oracle E-Business Suite R12.1.1.
Load the journal entry source seed data.
You can also specify whether you want Oracle GL to store journal reference information from Oracle BRM for a particular source.
Seed data is provided using a patch. Refer to the prerequisites section of this document for the patch number or manual steps if the seed patch is not available.
Load the journal entry categories seed data.
Seed data is provided using a patch. Refer to the prerequisites section of this document for the patch number or manual steps if the seed patch is not available.
If you want Journal Import to assign sequential numbers to your journal entries, enable sequential numbering, specifying Automatic as both your numbering method and document generation method.
Run the Optimizer program to create indexes for your account segments.
Define the concurrent program controls to improve the performance of Journal Import by setting the amount of disk space and memory it uses.
The Journal Import program requires approximately 1.4 megabytes of memory to run. You can also specify whether to save your Journal Import data each time you run Journal Import. Journal Import runs faster if you do not archive your data.
Disable dynamic insertion. Journal Import runs much faster when it is not required to create new account combinations dynamically.
Set the status of the accounting period (for which the integration is running) to either Open or Future Enterable.
Complete these tasks in Oracle BRM:
Configure the Oracle GL export configuration file.
In addition to the standard configuration parameters, you must also specify the Source System Identifier, which is the value of the SOB Id (with Oracle E-Business Suite R11.5.10 CU2) or Ledger Id (with Oracle E-Business Suite R12.1.1) mapping in the integration layer configuration file.
Customize the policy opcode PCM OP GL POL EXPORT GL to map the Oracle BRM GL account names to the appropriate Oracle GL accounts.
This mapping is done by modifying the relevant fields in the generated ledger report object. The Oracle GL accounts must be the concatenation of the individual Oracle GL segment values separated by the V segment separator string. This segment separator string must be the same as the one configured in the integration layer. For example, the system can map an internal Oracle BRM GL account name such as west.california to an Oracle GL account XXX/YYY/ZZZ if the three Oracle GL segments have values of XXX, YYY, ZZZ, and the segment separator.
Note:
Customizing the opcode is only required if the Oracle BRM GL account names are different from the Oracle GL account names (including the segment separator). If the Oracle BRM and Oracle GL account names are the same, then you are not required to transform the names using the policy opcode. Also, the segment separator string is not required to be V, but both the policy opcode and the integration layer configuration must use the same separator string.
For more information, see Oracle Communications Billing and Revenue Management (BRM) Documentation, "BRM Documentation," Billing Customers, Collecting General Ledger Data.
For the integration layer, you must configure the parameters in the integration configuration file, including the mapping of the Source System Identifier to the SOB Id (with Oracle E-Business Suite R11.5.10 CU2) or Ledger Id (with Oracle E-Business Suite R12.1.1).
By just using the Gross, Net, or certain revenue account types when the GL account configuration contains --N/A-- for the output values, list the account types that the integration layer must ignore in order not to get an error.
For more information about configuring ODI, see the Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack.
This section discusses these topics:
Before running any GL data, you must set up Oracle BRM to:
List all Oracle BRM GL accounts.
Create GL Ids that assign GL codes to Oracle BRM balance impacts.
Configure the summarization of Oracle BRM GL accounts into the Oracle GL accounts.
You can map Oracle BRM revenue into Oracle GL accounts in two ways:
Configure the Oracle BRM GL accounts independently of the Oracle GL accounts, and map the Oracle GL accounts within the policy opcode.
Configure the Oracle GL accounts within Oracle BRM GL configuration files.
If you cannot configure the exact name of an Oracle GL account, then you must customize Oracle BRM to configure the proper account Id. No pattern for configuring the accounts is specified, but typically Oracle BRM GL reporting is more detailed than Oracle GL, where accumulation is done.
Each GL segment contains its own set of GL Ids (and accounts). The balance impacts always use the GL Ids that are dependent on the product rated against, and they are independent of the GL segment with which the account is associated. The segments do not necessarily match the Oracle GL segments, but they should to simplify the integration.
For more information, see Oracle Communications Billing and Revenue Management (BRM) Documentation, "BRM Documentation," Billing Customers, Collecting General Ledger Data, About Collecting General Ledger data.
Oracle BRM can generate summary and detailed reports. You can use the summary report for this integration to Oracle GL. You can start with detailed report data and customize it to summarize the data, but what is handed to the integration is always a summary report.
You can pick a segment for reporting or, by default, all configured segments are reported.
In Oracle BRM, you must configure the GL account Ids to correspond with the target accounts in Oracle GL.
For more information, see Oracle Communications Billing and Revenue Management (BRM) Documentation, "BRM Documentation," Billing Customers, Collecting general ledger data, Loading general ledger configuration data. See also "BRM Documentation," Billing Customers, Collecting general ledger data, Exporting general ledger (G/L) reports to XML files.
The process integration for revenue management uses ODI to pick up the Oracle BRM data files, transform them from XML, and load the GL interface table. After the interface table is loaded, you use Oracle GL to import and post the journals.
In Oracle BRM, you configure the OutputDirectory to be the same directory that you specified in the AIAConfigurationProperties.xml file. After generating an Oracle BRM GL data file, when the file enters that directory, ODI picks it up and transforms it to the Oracle GL interface table.
Figure 2-1 illustrates the load process:
When this business process initiates, it:
Reads and stores configuration parameters from the configuration files.
Reads the Oracle BRM XML file.
Checks for the value of the property TargetID from AIAConfigurationProperties and executes the mapping for either Oracle E-Business Suite Release 11.5.10 CU2 or 12.1.1.
Checks to see if the AR discount account element is configured to be filtered out.
If it is, then the system moves to the next element. Otherwise, it loads the AR discount account element.
If the load is successful, the system moves to the next element.
If the load fails, the system moves the Oracle BRM XML file to the error folder, stops processing, and sends an email notification that the load failed.
Checks to see if the AR gross account element is configured to be filtered out.
If it is, then the system moves to the next element. Otherwise, it loads the AR gross account element.
If the load is successful, the system moves to the next element.
If the load fails, the system moves the Oracle BRM XML file to the error folder, stops processing, and sends an email notification that the load failed.
Checks to see if the AR net account element is configured to be filtered out.
If it is, then the system moves to the next element. Otherwise, it loads the AR net account element.
If the load is successful, the system moves to the next element.
If the load fails, the system moves the Oracle BRM XML file to the error folder, stops processing, and sends an email notification that the load failed.
Checks to see if the AR tax account element is configured to be filtered out.
If it is, then the system moves to the next element. Otherwise, it loads the AR tax account element.
If the load is successful, the system moves to the next element.
If the load fails, the system moves the Oracle BRM XML file to the error folder, stops processing, and sends an email notification that the load failed.
Checks to see if the offset discount account element is configured to be filtered out.
If it is, then the system moves to the next element. Otherwise, it loads the offset discount account element.
If the load is successful, the system moves to the next element.
If the load fails, the system moves the Oracle BRM XML file to the error folder, stops processing, and sends an email notification that the load failed.
Checks to see if the offset gross account element is configured to be filtered out.
If it is, then the system moves to the next element. Otherwise, it loads the offset gross account element.
If the load is successful, the system moves to the next element.
If the load fails, the system moves the Oracle BRM XML file to the error folder, stops processing, and sends an email notification that the load failed.
Checks to see if the offset net account element is configured to be filtered out.
If it is, then the system moves to the next element. Otherwise, it loads the offset net account element.
If the load is successful, the system moves to the next element.
If the load fails, the system moves the Oracle BRM XML file to the error folder, stops processing, and sends an email notification that the load failed.
Checks to see if the offset tax account element is configured to be filtered out.
If it is, then the system moves to the next element. Otherwise, it loads the offset tax account element.
If the load is successful, the system moves to the final step.
If the load fails, the system moves the Oracle BRM XML file to the error folder, stops processing, and sends an email notification that the load failed.
Finally, the system moves the successful payload to the target folder and sends an email notification that the load is successful.
|
 Copyright © 2001, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
