| 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-03 |
|
|
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-03 |
|
|
PDF · Mobi · ePub |
This chapter discusses how to change the database schema name of Oracle General Ledger, set up a schedule, and configure and run the process integration for revenue management.
The standard Oracle Application Integration Architecture (Oracle AIA) installation process assumes the Oracle General Ledger database schema name is the same as the database user name. If not, then you must run the following steps post installation.
To change the Oracle General Ledger database schema name:
Open a command prompt.
Source the file aiaenv.sh (if UNIX) or aiaenv.bat (if Windows) located in AIA_home/aia_instances/AIAHOME/bin.
Navigate to the directory ODI_home/oracledi/client.
Open Topology Manager as follows:
Run one of the following commands:
UNIX: ./odi.sh
Windows: odi.exe
Design Studio for Oracle Data Integrator (ODI) appears.
Click Connect to Repository.
The ODI dialog box appears.
From the Login Name list, select Repository.
In the User field, enter your username.
In the Password field, enter your password.
Click OK.
The Topology Manager appears.
Click the Topology tab.
On the Physical Architecture bar, expand the Technologies folder, then expand the Oracle folder.
If the version of Oracle General Ledger is 11.5.10, expand the Oracle GL 11 DS folder. (If the version is 12.1.1, skip to step 12.)
Right-click the Oracle GL 11 DS.apps child element and click Open.
The Physical Schema screen appears.
Change the values in the Schema (Schema) and Schema (Work Schema) fields to your G/L database schema name.
Note:
Both the Schema (Schema) and the Schema (Work Schema) fields must contain the same value.Click Apply.
Click OK.
If the version of Oracle General Ledger is 12.1.1, expand the Oracle GL Interface DS folder, right-click the Oracle GL Interface DS.GL child element, and click Open.
In the Physical Schema window, change the values of Schema (Schema) and Schema (Work Schema) to the actual G/L database schema name.
Note:
Both the Schema (Schema) and the Schema (Work Schema) fields must contain the same value.Click Apply.
Click OK.
Regenerate the scenario LOAD_PORTAL_DATA_TO_ORACLE_GL_PKG Version 001 from the Designer tab.
The standard Oracle AIA installation process completes the standard install for the process integration for revenue management. After the standard install, you must complete the following steps.
For more information about the standard installation process, see Oracle Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations.
Open the designer by running the following command in the oracledi/client directory:
UNIX: ./odi.sh
Windows: odi.exe
The ODI Login window appears.
Enter the appropriate credential to log in to Design Studio. If you have not set up the login, click the New button to create a login.
The Work Repository Connection window appears.
Enter the following values:
Login Name: The name by which you identify this integration at login. For example, Revenue Management.
User: User name of the Designer, for example, SUPERVISOR.
Password: Password for the user, for example, SUNOPSIS.
User: The master repository user, for example, odimaster.
Password: The password for the master repository user, for example, odimaster.
Driver List: Select Oracle JDBC Driver.
Driver Name: Enter oracle.jdbc.driver.OracleDriver.
Url: Enter jdbc:oracle:thin:@host:port:sid where host, port, and sid represent the database environment where you created the master repository.
Work Repository: Click the button to the right to display a list of available work repositories.
The system displays only one work repository. The repository name is the one that you chose during the standard installation.
Default Connection: Select this check box if you have multiple login name.s
Click OK.
If the Work Repository Connection asks for a password, enter the Work Repository database user password that you set during the standard installation.
The Designer window appears.
Expand the Portal to Oracle GL Project tree to Portal To Oracle GL Project, Packages, Load Portal Data To Oracle GL Pkg, Scenarios, LOAD PORTAL DATA TO ORACLE _GL_PKG Version 001, Scheduling.
Double-click the existing RevMgmtAgent scheduler.
The Scenario Scheduling window appears.
Enter or select the following values:
Context: Select Portal to GL Context.
Agent: Select RevMgmtAgent.
Log Level: 5.
Status: Select the Active option.
Execution: Select the On startup option.
Click the Execution Cycle tab.
Enter or select the following values:
Repetition: Select Many times.
Interval between Repetitions: Enter 30 and choose Second(s).
Click OK.
The scheduler is now configured.
After you install the process integration for revenue management, you must configure several parameters. Open the AIAConfigurationProperties.xml file that resides in the aia_instances/config/ folder. Entries in the AIAConfigurationProperties.xml file are case sensitive.
See the discussions of building AIA integration flows and how to set up AIA workstations in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information.
Configure the following parameters:
Under the moduleName RevMgmtSetOfBooksIDs find the <Property Name=" Source SystemID ">202</Property> property tag.
Replace the tag value SourceSystemID with the value of the SourceSystemID that comes in the in BRM XML GL report. For example, if you have two BRM instances feeding into Oracle General Ledger and the report from one instance has the SourceSystemID value as abc and the report from the other instance has the value as def, then change the section as follows:
<ModuleConfiguration moduleName="RevMgmtSetOfBooksIDs"> <Property name="abc">101</Property> <Property name="def">202</Property> ...... </ModuleConfiguration>
You must ensure that the value of the SourceSystemID in the BRM report is a value in the AIAConfigurationProperties.xml file.
Replace the value of the SourceSystemID, such as 202, with the SOB ID as defined in E-Business Suite R11.5.10 CU2 or with the Ledger ID defined in E-Business Suite 12.1.1.
Under the moduleName RevMgmtExchangeRateType find the <Property name="ExchangeRateType">DAILY</Property> property tag.
The attribute DAILY represents the Exchange Rate Type. Do not change the name attribute value. Replace DAILY with the required exchange rate type.
The Exchange Rate Type handles currency conversions. Oracle provides a placeholder for the Exchange Rate Type. The Exchange Rate Type is passed to the Oracle GL application and is handled by Oracle General Ledger when loading G/L report data from the interface table to Oracle General Ledger.
Under the moduleName RevMgmtParameters are several property tags with Name and Value attributes.
Do not edit the Name attribute value.
Table 3-1 lists value attributes.
| Name Attribute Value | Property Tag Value |
|---|---|
|
TargetID |
Specify whether the target application is E-Business Suite Release 11.5.10 CU2 or 12.1.1. This property contains the value EBS_01 for 12.1.1 and EBS_02 for 11.5.10 CU2. The default value is EBS_01. The values entered are case sensitive. |
|
ToMailAddress |
Specify the To email address of the person to whom an email is sent, notifying them that the integration process is complete. |
|
FromMailAddress |
Specify the From email address for the person who performs the integration process. |
|
TargetFileLocation |
Specify the folder name where you want the process to move the XML file after it is successfully loaded. |
|
ErrorFileTargetLocation |
Specify the folder name where you want the process to move the XML file if a failure occurs. |
|
SegmentSeparator |
Specify how the BRM XML document separates in representing the Oracle GL segments. |
|
PayloadSourceLocation |
Specify the folder name to which the BRM-generated XML files are moved. The staging/ODIInProcess folder cannot be used as the PayloadSourceLocation. See "Solution Constraints" for more information about constraints on where you can place BRM-generated XML files. |
|
Mail Server |
Specify the mail server name. |
|
RevMgmtHome |
Specify the location of the RevenueManagementHome folder. Normally, this folder is located at <AIAHome>/DISHome/RevenueManagementHome. |
Under the moduleName RevMgmtAccountFiltering specify what types of accounts you want to filter out (that is, to not load to the Oracle General Ledger interface table), as shown in Table 3-2.
Possible values are Yes and No, and they are case sensitive.
These parameters enable you to filter certain account types. If the value is No, then they are not filtered out (they are loaded). If the parameter value is Yes, then the corresponding revenue account type entries are filtered out (they are not loaded).
Table 3-2 Value Attributes: Filtering Account Types
| Name Attribute Value | Property Tag Value |
|---|---|
|
FilterARGrossAccount |
Specify No to load ARGrossAccount entries. Specify Yes to filter out this account. |
|
FilterARDiscountAccount |
Specify No to load FilterARDiscountAccount entries. Specify Yes to filter out this account. |
|
FilterARNetAccount |
Specify No to load ARNetAccount entries. Specify Yes to filter out this account. |
|
FilterARTaxAccount |
Specify No to load ARTaxAccount entries. Specify Yes to filter out this account. |
|
FilterOffsetGrossAccount |
Specify No to load OffsetGrossAccount entries. Specify Yes to filter out this account. |
|
FilterOffsetDiscountAccount |
Specify No to load OffsetDiscountAccount entries. Specify Yes to filter out this account. |
|
FilterOffsetNetAccount |
Specify No to load OffsetNetAccount entries. Specify Yes to filter out this account. |
|
FilterOffsetTaxAccount |
Specify No to load OffsetTaxAccount entries. Specify Yes to filter out this account. |
Whenever you change the AIAConfigurationProperties.xml file, you must restart the agent to reflect your changes.
You can schedule the integration between BRM and Oracle General Ledger to occur automatically. If the scheduler agent is kept running, then whenever BRM generates the report in XML format and writes the XML document into the specified directory, the integration process picks up the XML file, transforms it, and then transfers it to the interface table of Oracle General Ledger.
Note:
You can start or stop the scheduler agent whenever you want, which enables you to control the integration process. Therefore, to generate the reports in BRM in the last week of every month, then you can start the scheduler agent at the beginning of the last week and stop it when the week ends.See "Setting Up a Schedule" for more information.
A scheduler agent, RevMgmtAgent, is delivered and is running on default port 20910.
To start the schedule agent:
Navigate to the oracledi/agent/bin directory.
Run one of the following commands:
UNIX: ./agent.sh -NAME=RevMgmtAgent
Windows: agent.bat -NAME=RevMgmtAgent
This command starts the scheduler agent, which in turn launches a scenario. The scenario waits for a BRM XML report file to arrive in the specified directory. As soon as the report file arrives, the scheduler agent transfers the file to the Oracle General Ledger interface table. You can monitor the status of this integration process using the ODI Operator.
|
 Copyright © 2009, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
