Skip Headers
Oracle® Business Intelligence Applications Installation and Configuration Guide
Version 7.9.4
E10742-01
  Go To Documentation Library
Library
Go To Product List
Product
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

8 Configuring Common Areas and Dimensions

This chapter contains configuration steps for Oracle Business Intelligence that you need to follow for any applications you deploy (for example, Oracle Financial Analytics, Oracle Human Resources).

This chapter contains the following topics:

8.1 Source Independent Configuration Steps

This section contains configuration steps that apply to Oracle Business Intelligence Applications deployed with any source system.

This section contains the following topics:

8.1.1 Configuration Required Before A Full Load

This section contains configuration steps required before a full data load that apply to Oracle BI Applications deployed with any source system, and contains the following topics:

8.1.1.1 How to Configure Initial Extract Date

TBD.

8.1.1.2 How to Configure Global Currencies

Currency conversions are required because your business might have transactions involving multiple currencies. To create a meaningful report, you have to use a common currency. The Oracle Business Analytics Warehouse stores amounts in the following currencies:

  • Document currency. The currency of the transaction. For example, if you purchase a chair from a supplier in Mexico, the document currency is probably the Mexican

    peso. Or you made a business trip to UK and filed an expense report for meal expenses in UK, the document currency of the expense report will most likely be in GBP.

  • Local currency. This is the base currency of your ledger, the currency in which your accounting entries are recorded in.

  • Global currencies. Out of the box, Oracle BI Applications provides three global currencies, which are the common currencies used by the Data Warehouse. For example, if your organization is a multinational enterprise that has its headquarters in the United States, you probably want to choose US dollars (USD) as one of the three global currencies. The global currency is useful when creating enterprise-wide reports. For example, a user might want to view enterprise-wide data in other currencies. For every monetary amount extracted from the source, the load mapping loads the document and local amounts into the target table. It also loads the exchange rates required to convert the document amount into each of the three global currencies. In the target table, there will be two amount columns, and three exchange rate columns. In most cases, the source system provides the document currency amount. This is the most common situation, and thus is the Oracle Business Analytics Warehouse's default for handling currency. If the source system provides only the document currency amount, the Source Adapter performs lookups to identify the local currency codes based on the source system. Based on the source system the appropriate currencies are assigned. After the lookups occur, the extract mapping provides the load mapping with the document currency amount and the document and local currency codes. The load mapping will then use the provided local currency codes and perform currency conversion to derive the local amount. The load mapping will also fetch the global currencies setup from DAC parameters and look up the corresponding exchange rates to each of the three global currencies.

To configure the global currencies you want to report in your warehouse:

  1. Log into DAC (for more information, see Section 4.10.2, "How to Log Into the DAC".

  2. Open your custom container

  3. Display the 'Source System Parameters' tab.

  4. Locate the following parameters and set the currency code values for them in the 'Value' box:

    • $$GLOBAL1_CURR_CODE (for the document currency).

    • $$GLOBAL2_CURR_CODE (for the local currency).

    • $$GLOBAL3_CURR_CODE (for the global currency).

    Make sure you spell these currency as they are spelled in your source OLTP system.

  5. Save your changes

8.1.1.3 How to Configure Exchange Rate Types

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. For each of the global currencies, Oracle BI Applications also allows you to specify the exchange rate type to use to perform the conversion. Oracle BI Applications also provides three global exchange rate types for you to configure.

Oracle BI Applications also converts your transaction records' amount from document currency to local currency. Local currencies are the base currencies in which your accounting entries and accounting reports are recorded. In order to perform this conversion, Oracle BI Application also allows you to configure the rate type that you want to use when converting the document currency to the local currency.

To configure the currency rate types:

  1. Log into DAC (for more information, see Section 4.10.2, "How to Log Into the DAC".

  2. Open your custom container

  3. Display the 'Source System Parameters' tab.

  4. Locate the following DAC parameters and set the exchange rate type values for them in the 'Value' box:

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

  5. Save your changes

8.1.1.4 How to Configure Fiscal Calendars

This sections explains how you configure the time dimension in the Oracle Business Analytics Warehouse, and contains the following sections:

8.1.1.4.1 Overview To Setting Up The Time Dimension

When you configure Time Dimension tables, W_DAY_D is the base table that represents the time dimension in the Oracle Business Analytics Warehouse. There are two lines of aggregate dimension tables built on this table, as follows:

  • Regular Calendar tables.

  • Fiscal Calendar tables.

Table 8-1 shows the tables used to store calendar information.

Table 8-1 Tables in base table W_DAY_D that are used to store calendar information

Regular calendar tables in W_DAY_D Fiscal calendar tables in W_DAY_D

W_WEEK_D

W_FSCL_WEEK_D

W_MONTH_D

W_FSCL_MONTH_D

W_QTR_D

W_FSCL_QTR_D

W_YEAR_D

W_FSCL_YEAR_D


There are two parameters $$Start_Date and $$End_date for the task SIL_DayDimension that need to be setup to load the calendar data in W_DAY_D. The SIL mappings use standard time functions to create records for each calendar day falling within the boundary defined by these two parameters. Once the records are created in W_DAY_D, the aggregate calendar tables are loaded by their respective SIL mapping.

8.1.1.4.2 Setting Up Fiscal Calendar

Installed out of the box, Oracle BI Applications supports one fiscal calendar. Fiscal data is first loaded in the W_DAY_D table and then the SIL mappings read data from W_DAY_D and load data into the aggregate Fiscal Time Dimension tables such as Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year.

You may choose to provide Fiscal calendar information in terms of the Fiscal Weeks of your organization or in terms of the Fiscal months of your organization. In either case, The SIL mappings are designed to derive the Fiscal Week from the Start and End Date of a Fiscal Month by grouping into periods of seven days each.

8.1.1.4.3 Setting Up Fiscal Calendar By Fiscal Week

In this option you provide data for the Fiscal Year, Fiscal Month, Fiscal Week and Start Date of Fiscal Week. The Fiscal Month information is derived using the 4-4-5 rule for grouping weeks into months. The Fiscal Week End Date is derived based on the start date of the next week that is supplied in the data file. Fiscal Months are grouped into sets of 4 months each to determine the Fiscal Quarter.

8.1.1.4.4 Setting Up Fiscal Calendar By Fiscal Month

In this option you can provide data at the level of Fiscal Month. The SIL_DayDimension_FiscalMonth_Extract task divides the Fiscal Month into Fiscal Weeks of seven days each. If the number of days in the Fiscal Month is not in multiples of seven, the last week will have less number of days.

8.1.1.4.5 Process of Setting Up The Fiscal Calendar

To configure Fiscal Calendar by Fiscal Week

  1. Open the file fiscal_week.csv using a text editor in the $PMRootDir\SrcFiles directory. Enter the Fiscal Year, Fiscal Month, Fiscal Week and the Start Date of Fiscal Week in YYYYMMDD. Records must be inserted in ascending order of Fiscal Year, Fiscal Month, Fiscal Week. Save and close the file.


    Note:

    Make sure you enter accurate Fiscal Data as there is no check done within the Informatica mappings.

  2. Deactivate the task SIL_DayDimension_FiscalMonth_Extract in the Data Warehouse container in DAC. Then right click and push to references.

  3. Activate the task SIL_DayDimension_FiscalWeek_Extract in the Datawarehouse container in DAC. Then right click and push to references.

To configure Fiscal Calendar by Fiscal Month

  1. Open the file fiscal_month.csv using a text editor in the $PMRootDir\SrcFiles directory. Enter the Fiscal Year, Fiscal Month and the Start Date of Fiscal_Month in YYYYMMDD format. Save and close the file.


    Note:

    Make sure that you enter accurate Fiscal Data as there is no check done within the Informatica mappings.

  2. Activate the task SIL_DayDimension_FiscalMonth_Extract in Datawarehouse container in DAC. Then right click and push to references.

  3. Deactivate the task SIL_DayDimension_FiscalWeek_Extract in Datawarehouse container. Then right click and push to references.

8.1.1.4.6 Reloading the Time Dimension Tables After Your Data Warehouse is Populated

The data in time dimension is loaded once during the initial full load. Subsequently, the SIL_*_UpdateFlag mappings run everyday to update the domain value codes, which indicate whether a day, week, month, quarter or year is 'Current', 'Next' or 'Previous' as of the current day. The SIL_Fiscal_UpdateFlag mappings also update the flags that indicate whether a fiscal week, month, quarter or year is 'Current', 'Previous' or 'Next' with respect to the system date.

You might want to extend the range of data that you have in your time dimension sometime after the warehouse is in production. In order to achieve this, please follow the steps below that will kick off the full load ETL run of the W_DAY_D and all the aggregate time dimension tables.

To set up the load strategy of the time dimension table

  1. In DAC, go to Setup, then Physical Data Sources and click on the connection DataWarehouse.

  2. Go the Refresh Dates tab in the bottom panel.

    The Refresh Date of all the tables will be given there. Double click on the Refresh Date of W_DAY_D and make it Null. Do the same for the following aggregate time dimension tables: W_WEEK_D, W_QTR_D, W_MONTH_D, W_YEAR_D,W_FSCL_WEEK_D, W_FSCL_QTR_D, W_FSCL_MONTH_D, and W_FSCL_YEAR_D.

  3. Display the Design\Task tab and open the task SIL_DayDimension in DataWarehouse container.

  4. Set the $$Start_date and $$End_Date parameters to the appropriate start date and end date of the new date range.

  5. Save the task and push the changes to references.


    Note:

    Make sure that the new date range defined by the parameters $$Start_date and $$End_date encompasses the old date range entirely. Otherwise records can be lost. Also make sure you have provided the fiscal information for the new date range also in the appropriate fiscal input file. The next time you run your ETL execution plan, the calendar dimension will be truncated and reloaded with the new date range that you have specified. Since the calendar dimensions use smart keys, none of the fact tables that refer to these tables need to be reloaded.

8.1.1.4.7 Notes

The following notes pertain to the process of setting up the fiscal calendar:

  • If there is a week (starting on a Sunday and ending on a Saturday) that falls across two Calendar years, the week is counted in both years. For example the week that starts on 12/30/2007 will be counted in both 2007 and 2008. In 2007 the week Start Date will 12/30/2007 and the End Date will be 12/31/2007. In 2008 this will be the first week with Start Date as 01/01/2008 and End Date as 01/05/2008.

  • W_DAY_D stores 31 records for each month irrespective of whether the month actually has 31 days or not. If the month actually has less number of days, there will be records with Null values in the Calendar Date and Day Date columns. These extra records are loaded for the calculation of Period Ago metrics in the RPD, and will not affect the ETL or reporting.

  • There are some attributes on the W_DAY_D table that are not mapped in the physical layer of the RPD. Therefore, before creating any new attribute in the RPD, check whether the attribute is already available in the physical layer and if it can be mapped directly.

  • If your fiscal calendar contains more than 12 months, the extra months will be assigned a value of 0 for the Fiscal Quarter. The same holds for the Fiscal Trimester and Fiscal Half values.

8.1.2 Configuration Steps for Controlling Your Data Set for All Source Systems

This section contains additional configuration steps that apply to Oracle BI Applications deployed with any source system, and contains the following topics:

8.1.2.1 How to Configure Data Source Num IDs

DATASOURCE_NUM_ID is a system column in the data warehouse that uniquely identifies a data source category and indicates which source systems the data comes from. For example, the value '1' indicates one of the Siebel data sources, and the value 2 indicates an Oracle 11.5.8. data source.

Oracle Business Intelligence is installed with a number of pre-defined data source templates that you can edit to specify OLTP and OLAP data sources. If you create a new data source without using one of the pre-defined templates, you must specify the correct DATASOURCE_NUM_ID for that data source category. For example, if you specify an Oracle EBS data source, you must specify the DATASOURCE_NUM_ID value '9'. For more information about specifying data sources, see Section 4.11.2, "How to Specify Transactional and Data Warehouse Data Sources in the DAC".

The table below shows the data sources that are supported by Oracle Business Intelligence and their associated DATASOURCE_NUM_ID values.

Table 8-2 Data Sources and Associated DATASOURCE_NUM_ID Values

Data Source Name Data Source Number

ORA_11_5_8

2

ORA_11_5_9

5

ORA_11_5_10

4

ORACLE_R12

9

PSFT_8_4_FINSCM

7

PSFT_8_8_FINSCM

8

PSFT_8_8_HCM

6

SEBL_63

1

SEBL_771

1

SEBL_753

1

SEBL_78

1

SEBL_80

1

SEBL_VERT_771

1

SEBL_VERT_753

1

SEBL_VERT_78

1

SEBL_VERT_80

1

SRV_SEBL_80

1

UNIV

3


To configure a DATASOURCE_NUM_ID value:

  1. Log into DAC (for more information, see Section 4.10.2, "How to Log Into the DAC".

  2. Display the Set tab.

  3. Display the 'Physical Data Sources' tab.

  4. Select a data source from the list.

  5. On the Edit tab, edit the value in the Data Source Number field.

  6. Click Save.

If you do choose to modify the Data Source Number and if you implement Supply Chain Analytics, it is Mandatory that you finish the steps in section Section 9.2.2.2, "How to Configure the DAC parameter for Purchase Cycle Line".

8.2 Oracle EBS-Specific Configuration Steps

This section contains configuration steps that apply to Oracle Business Intelligence Applications deployed with Oracle EBS source systems.

This section contains the following topics:

8.2.1 Configuration Required Before A Full Load for Oracle EBS

This section contains configuration steps required before a full data load that apply to Oracle BI Applications deployed with Oracle EBS source systems, and contains the following topics:

8.2.1.1 Configuration of Product hierarchy (except for GL, HR modules)

There are two dimension tables that have built-in product hierarchies - the Product and Inventory Product dimension tables. These dimension tables share one Product category staging table.

ETL extracts the Product and Sales Product staging tables separately, and then joins these tables with the shared category staging table to load hierarchies. The category extract mapping controls the category sets that are used in the Product and Sales Product dimensions. The load mappings for the Product and Inventory Product dimensions specifies which Category Set is used to load to the hierarchy columns.

As initially configured, the Oracle Business Analytics Warehouse extracts product categories where the CATEGORY_SET_ID is 2 or 27. However, it is likely that the categories you extract from the source system are different from these prepackaged category sets. Therefore, you must reconfigure your product category sets by making the following changes:

  • Identify and extract only the categories that you want to report against into the Product Hierarchy sets Staging table.

  • Properly position the data so that it loads into the Oracle Business Analytics Warehouse.

8.2.1.1.1 How to identify Category Sets from EBS

To find out the category sets that your organization is using:

  1. Login to the instance.

  2. Navigate to Setup > Items > Categories > Default Category Sets

  3. Look for functional Area Inventory and place the cursor in the Category Set Field

  4. Then click menu Help > Diagnostics > Examine, and provide the apps user password

  5. Click the Field LOV button and select CATEGORY_SET_ID, note down the value

  6. Repeat step 3-5 for Purchasing functional area.

8.2.1.1.2 To configure product category sets extract from Oracle Applications

To configure product category sets extract from Oracle Applications:

  1. Identify the categories that need to be mapped to the extension hierarchy columns.

    These categories are extracted from the source and placed in the hierarchy column specified.

  2. In PowerCenter Workflow Manager, open the Configuration for Oracle Applications v11i.

  3. Open the SDE_ORA_PRODUCT_CATEGORY_DERIVE session with the Task Developer.

  4. In the Mappings tab, click MPLT_BC_ORA_PRODUCT_CATEGORY.SQ_MTL_CATEGORIES.

  5. In the right pane, scroll down and click SQL Query to edit session SQL override.

  6. Click the arrow to edit the WHERE clause.

    The following statement is an example of how to structure the WHERE clause:

    WHERE...MTL_CATEGORY_SETS_B.CATEGORY_SET_ID IN (27,2)

    In this example, the WHERE clause extracts categories where the Category SetID is 27 or 2.

  7. Click OK, and then click OK to close the Edit Tasks box.

  8. Repeat steps 3 to 7 for the SDE_ORA_PRODUCT_CATEGORY_DERIVE_FULL session.


Note:

The default product hierarchy level is two. If you only have one product hierarchy level, you need to make the following modifications:

1. In the EXP_PRODUCTS expression transformation in the mplt_SA_ORA_ProductDimension mapplet, modify the EXT_PROD_HIER1_CODE port to INP_SEGMENT1.

2. In the SDE_ORA_ProductDimension mapping, open the EXP_W_PRODUCT_DS transformation expression and modify the PROD_HIER1_CODE port expression to IN_PROD_HIER1_CODE.



Note:

The category set chosen as a value for this parameter must be a Category Set controlled at a Master Level but not at the Org level as the grain of the Product dimension is at the Master level.

8.2.1.1.3 To configure the Category Sets for Product Hierarchy

To configure the Category Sets for Product Hierarchy:

  1. Open the ParameterOLTP.TXT file in OracleBI\DAC\Informatica\parameters\input folder.

  2. Replace the default parameter in SDE_ORA_Product_Dimension:

    • $$CATEGORY_SET_ID=2

  3. Save and Exit the Parameter file.

  4. Restart the DAC Server to load the parameter changes.

8.2.1.1.4 To reconfigure the product hierarchy loads

To reconfigure the product hierarchy loads:

  1. In PowerCenter Designer, open the Configuration for Oracle Applications v11i folder, and expand the Mapplets folder.

  2. Open the mplt_SA_ORA_ProductDimension mapplet for Oracle 11i.

  3. Double-click the EXP_PRODUCTS expression transformation to open the Edit Transformation box.

  4. In the Ports tab, scroll down to find the hierarchy code port.

    Hierarchy levels are named with the following convention EXT_PROD_HIERX_CODE, where X denotes the level within the hierarchy. For example, if you want to edit the first level of your hierarchy, you must edit the definition for EXT_PROD_HIER1_CODE port.

    The first two levels are preconfigured as follows:

    EXT_PROD_HIER1_CODE = IIF(ISNULL(INP_SEGMENT1) OR ISNULL(INP_SEGMENT2), NULL, INP_SEGMENT1||'~'||INP_SEGMENT2)

    EXT_PROD_HIER2_CODE = INP_SEGMENT1

  5. Modify the expression that defines your hierarchy code.

  6. Validate and save your changes to the repository.

8.2.1.1.5 To configure the Category Sets for Inventory Product Hierarchy

To configure the Category Sets for Inventory Product Hierarchy:

  1. Open the ParameterOLTP.TXT file in OracleBI\DAC\Informatica\parameters\input folder.

  2. Replace the default Category Set ID (27) with your new value.

  3. Save and close the file.

8.2.1.2 Configure the Master Inventory Organization in Product dimension Extract for Oracle 11i adapter (Except for GL & HR Modules)

In Oracle 11i applications, the products are defined in a Master Organization and then copied into the other Inventory Organizations for transactions. The Product dimension Extract mapping 'SDE_ORA_ProductDimension_Derive' has been enabled for configuration of this Master Organization based on the configuration in the OLTP. This is enabled via a session parameter "MASTER_ORG" in the parameter file (OracleBI\DAC\Informatica\parameters\input\ParameterOLTP.TXT) for the ETL. Out-of-the-box, this parameter is set to "$$MASTER_ORG=204". This organization Id 204 needs to be changed based on the individual implementation of OLTP in your deployment.


Note:

This ETL implementation supports the best practice prescribed by Oracle for the creation of Single Master Organization for defining the Product master. This ETL implementation does not support the multiple master Organizations if the same product is defined in multiple master organizations.

8.2.2 Configuration Steps for Controlling Your Data Set for Oracle EBS

This section contains additional configuration steps that apply to Oracle BI Applications deployed with Oracle EBS source systems, and contains the following topics:

8.2.2.1 Configuring the Country Region and State Region Name

For Oracle 11i, you can reconfigure the region, state, and country names. This configuration information applies only to plant, storage, and supplier locations. By default, the Region Name column (EXT_REGION_NAME) is populated using the same code value as the Region Code column (EXT_REGION_CODE). However, you can redefine the load mapping's Source Adapter mapplet to load a source-supplied region name instead of the code. If you want to reconfigure the load in this manner, you can load the region code and region name into the W_CODE_D table. For information on loading codes and code names into the W_CODE_D table, see Section 6.10, "Codes Lookup".

When you have loaded the region code and region name into the W_CODE_D table, you can remove the expression in the Source Adapter that defines the Region Name column. By making the Region Name's expression blank, the SIL looks up the Region Name in the W_CODE_D table, using the supplied region code when the load occurs. The load mapping then inserts the region name and region code into the data warehouse table.

To configure the Country Region Name:

  1. In Informatica PowerCenter Designer, open the Configuration for SDE_ORA1158_adapter folder.

  2. Open the mapplet you want to edit.

    The following is a list of all Source Adapter mapplets that use the EXT_COUNTRY_REGION column:

    • mplt_SA_ORA_SupplierDimension

    • mplt_SA_ORA_BusinessLocationDimension_Plant

    • mplt_SA_ORA_BusinessLocationDimension_StorageLocation

  3. Double-click the Expression transformation to open the Edit Transformations dialog box, and click the Port tab to display the EXT_COUNTRY_REGION port.

  4. Edit the condition by removing the assigned value if you want the lookup to occur.

  5. Click Apply.

  6. Validate the mapplet, and save your changes to the repository.

To configure the State Region Name

  1. In Informatica PowerCenter Designer, open the SDE_ORA<Ver>_adapter.

  2. Open the mapplet you want to edit.

    The following is a list of all Source Adapter mapplets that use the EXT_STATE_REGION column:

    • mplt_SA_ORA_SupplierDimension

    • mplt_SA_ORA_BusinessLocationDimension_Plant

    • mplt_SA_ORA_BusinessLocationDimension_StorageLocation

  3. Double-click the Expression transformation to open the Edit Transformations dialog box, and click the Port tab to display the EXT_STATE_REGION port.

  4. Edit the condition by removing the assigned value if you want the lookup to occur.

  5. Click Apply.

  6. Validate the mapplet, and save your changes to the repository.

8.2.2.2 Configuring the State Name

For Oracle 11i, you can reconfigure the region, state, and country names that apply to the Supplier locations only. By default, the State Name column (EXT_STATE_NAME) is populated using the same code value as the State Code column (EXT_STATE_CODE). However, you can redefine the load mapping's Source Adapter mapplet to load a source-supplied state name instead of the code. If you want to reconfigure the load in this manner, you can load the state code and state name into the W_CODE_D table. For information on loading codes and code names into the W_CODE_D table, see Section 6.10, "Codes Lookup".

When you have loaded the state code and state name into the W_CODE_D table, you can remove the Expression in the Source Adapter that defines the State Name column. By setting the State Name's expression to null, the SIL looks up the state name in the W_CODE_D table using the supplied state code, during the load process. The load mapping then inserts the state name and state code into the data warehouse table.

To configure the State Name:

  1. In Informatica PowerCenter Designer, open the SDE_ORA<Ver>_adapter.

  2. Open one of the following mapplets:

    • mplt_SA_ORA_SupplierDimension

    • mplt_SA_ORA_BusinessLocationDimension_Plant

    • mplt_SA_ORA_BusinessLocationDimension_StorageLocation

  3. Double-click the Expression transformation to open the Edit Transformations dialog box, and click the Port tab to display the EXT_STATE_NAME port.

  4. Edit the condition by removing the assigned value if you want the lookup to occur.

  5. Click Apply.

  6. Validate the mapplet and save your changes to the repository.

8.2.2.3 Configuring the Country Name

For Oracle 11i, you can reconfigure the region, state, and country names that apply to supplier locations only. By default, the Country Name column (EXT_COUNTRY_NAME) is populated using the same code value as the Country Code column (EXT_COUNTRY_CODE). However, you can redefine the load mapping's Source Adapter mapplet to load a source-supplied country name instead of the code. If you want to reconfigure the load in this manner, you can load the country code and country name into the W_CODE_D table. For information on loading codes and code names into the W_CODE_D table, see Section 6.10, "Codes Lookup".

When you have loaded the country code and country name into the W_CODE_D table, you can remove the expression in the Source Adapter that defines the Country Name column. By setting the Country Name's expression to null, when the load occurs, the SIL looks up the country name in the W_CODE_D table, using the supplied country code. The load mapping then inserts the country name and country code into the data warehouse table.

To configure the Country Name:

  1. In Informatica PowerCenter Designer, open the SDE_ORA<Ver>_adapter.

  2. Open one of the following mapplets:

    • mplt_SA_ORA_SupplierDimension

    • mplt_SA_ORA_BusinessLocationDimension_Plant

    • mplt_SA_ORA_BusinessLocationDimension_StorageLocation

  3. Double-click the Expression transformation to open the Edit Transformations dialog box, and click the Port tab to display the EXT_COUNTRY_NAME port.

  4. Edit the condition by removing the assigned value if you want the lookup to occur.

  5. Click Apply.

  6. Validate the mapplet, and save your changes to the repository.

8.2.2.4 Configuring the Configuring the Make-Buy Indicator

The Make-Buy indicator specifies whether a material that was used to manufacture a product was made in-house or bought from an outside vendor. By default, the indicator is set using the INP_PLANNING_MAKE_BUY_CODE. If the code is set to 1, then the indicator is set to M (for make). However, if the code is set to 2, then the indicator is set to B (for buy). Otherwise, the indicator is set to null.

Your organization may require different indicator codes. If so, you can modify the indicator logic by reconfiguring the condition in the mapplet mplt_SA_ORA_ProductDimension. For example, you may want your indicator code to be 0 for make, and 1 for buy.

To configure the Make-Buy Indicator:

  1. In Informatica PowerCenter Designer, open the SDE_ORA<Ver>_adapter.

  2. Open one of the following mapplets:

    • mplt_SA_ORA_SupplierDimension

    • mplt_SA_ORA_BusinessLocationDimension_Plant

    • mplt_SA_ORA_BusinessLocationDimension_StorageLocation

  3. Double-click the Expression transformation to open the Edit Transformations dialog box, and click the Port tab to display the EXT_COUNTRY_NAME port.

  4. Edit the condition by removing the assigned value if you want the lookup to occur.

  5. Click Apply.

  6. Validate the mapplet, and save your changes to the repository.

8.3 PeopleSoft-Specific Configuration Steps

This section contains configuration steps that apply to Oracle Business Intelligence Applications deployed with PeopleSoft source systems.

This section contains the following topics:

8.3.1 Configuration Required Before A Full Load for PeopleSoft

Not applicable to Oracle BI Applications Version 7.9.4.

8.3.2 Configuration Steps for Controlling Your Data Set for PeopleSoft

Not applicable to Oracle BI Applications Version 7.9.4.

8.4 Siebel-Specific Configuration Steps

This section contains configuration steps that apply to Oracle Business Intelligence Applications deployed with Siebel source systems.

This section contains the following topics:

8.4.1 Configuration Required Before A Full Load for Siebel Source Systems

Not applicable to Oracle BI Applications Version 7.9.4.

8.4.2 Configuration Steps for Controlling Your Data Set for Siebel Source Systems

Not applicable to Oracle BI Applications Version 7.9.4.