Configure Exchange Rate Types

1.      When Oracle BI Applications converts your transaction records' amount from

document currency to global currencies, it also requires the exchange rate types to use

to perform the conversion.

2.      For each of the global currencies, Oracle BI Applications also allows you to specify the exchange rate type to use to perform the conversion.

3.      Oracle BI Applications also provides three global exchange rate types for you to

configure.

4.      Oracle BI Applications also converts your transaction records' amount from document

currency to local currency.

5.      Local currencies are the base currencies in which your accounting entries and accounting reports are recorded.

6.      In order to perform this conversion, Oracle BI Applications also allows you to configure the rate type that you want to use when converting the document currency to the local currency.

To configure exchange rate types

1. In DAC, select your custom container from the drop-down list to the right of the

Execute button.

2. Click the Source System Parameters tab.

3. Locate the following DAC parameters and set the exchange rate type values for

them in the Value field:

■ $$GLOBAL1_RATE_TYPE

$$GLOBAL2_RATE_TYPE

$$GLOBAL3_RATE_TYPE

■ $$DEFAULT_LOC_RATE_TYPE (the conversion rate type for document

currency to local currency conversion).

Make sure you spell the exchange rate type values as they are spelled in your
source OLTP system.

4. Save your changes
 

Set up an enterprise calendar using an Oracle EBS source system

To set up an enterprise calendar using an Oracle EBS source system:

1.    In the DAC, display the Design tab, and select an appropriate adapter.

2.    Display the Source System Parameters tab.

3. Set the value of $$GBL_CALENDAR_ID and $$GBL_DATSOURCE_NUM_ID as

follows:

■ GBL_CALENDAR_ID:

This parameter is used to select the Enterprise Calendar.

It should be the MCAL_CAL_NAME~MCAL_PERIOD_TYPE for Non-Generated Calendars. For example GBL_CALENDAR_ID will be 'Accounting~41', if the Enterprise Calendar id='Accounting' and the calendar  period_type='41'.

■ GBL_DATASOURCE_NUM_ID:

If Enterprise Calendar is not a Generated Calendar: Should be the DATASOURCE_NUM_ID of the source system from where the Calendar definition is taken.

(Example: If we have two Data source as PeopleSoft and Oracle, and our Global Calendar is from Oracle source, then parameter value should be of Oracle source.)

Note: The tasks that load the Enterprise calendar will run as part of the execution plan for your subject area. Please note that is no separate subject areas for common dimensions. They are included in the core subject areas.