| Oracle® Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users Release 7.9.6.4 Part Number E35270-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users Release 7.9.6.4 Part Number E35270-01 |
|
|
PDF · Mobi · ePub |
This appendix provides instructions for setting parameters in the Informatica parameter files. It contains the following topics:
Section A.1, "Setting Common Parameters in Informatica Parameter Files"
Section A.2, "Setting Source System-Specific Parameters in Informatica Parameter Files"
Section A.3, "Setting Application-Specific Parameters in Informatica Parameter Files"
This section provides instructions for configuring the <Oracle BI Applications version>_UPG_PARAMS.txt file. You need to configure these files for each version of Oracle BI Applications to which you are upgrading.
This section contains the following topics:
Follow this procedure to set parameters in the 793_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.3.
To set parameters in the 793_UPG_PARAMS.txt file
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 793_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Set the parameter $$ETL_PROC_WID to the latest ETL_PROC_WID value from the database. You can get this value from W_PARAM_G.ETL_PROC_WID.
Set the parameter $$DATASOURCE_NUM_ID to the relevant value from the source system setup.
Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"
- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"
Follow this procedure to set parameters in the 794_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.4.
To set parameters in the 794_UPG_PARAMS.txt file
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 794_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Set the parameter $$ETL_PROC_WID to the latest ETL_PROC_WID value from the database. You can get this value from W_PARAM_G.ETL_PROC_WID.
Set the parameter $$DATASOURCE_NUM_ID to the relevant value from the source system setup.
Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"
- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"
Follow this procedure to set parameters in the 795_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.5.
To set parameters in the 795_UPG_PARAMS.txt file
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 795_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Set the parameter $$ETL_PROC_WID to the latest ETL_PROC_WID value from the database. You can get this value from W_PARAM_G.ETL_PROC_WID.
Set the parameter $$DATASOURCE_NUM_ID to the relevant value from the source system setup.
Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"
- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"
Follow this procedure to set parameters in the 7951_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.5.1.
To set parameters in the 7951_UPG_PARAMS.txt file
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 7951_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Set the parameter $$ETL_PROC_WID to the latest ETL_PROC_WID value from the database. You can get this value from W_PARAM_G.ETL_PROC_WID.
Set the parameter $$DATASOURCE_NUM_ID to the relevant value from the source system setup.
Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"
- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"
Follow this procedure to set parameters in the 796_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.
To set parameters in the 796_UPG_PARAMS.txt file
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 796_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
In the 796_UPG_PARAMS.txt file, set the following parameters:
$$ETL_PROC_WID. Set this parameter to the relevant value from the source system setup. You can get this value from W_PARAM_G.ETL_PROC_WID
$$DATASOURCE_NUM_ID. Set this parameter to the relevant value from the source system setup.
$$INITIAL_EXTRACT_DATE. Set this parameter to the initial extraction data of the data warehouse.
$$WH_DATASOURCE_NUM_ID. Set this parameter to the data source number ID you have set up for the data warehouse. This value should be the same data source number ID in the warehouse table W_DAY_D. If this is not set up correctly, the upgrade maps will fail with a NULL ROW_WID. Make sure this parameter is setup appropriately for your environment.
$$START_DATE. Get this value from the Source System Parameters tab in DAC.
$$END_DATE. Get this value from the Source System Parameters tab in DAC.
$$MASTER_ORG. Get this value from the Source System Parameters tab in DAC.
$$INV_PROD_CAT_SET_ID1. Get this value from the Source System Parameters tab in DAC.
$$PROD_CAT_SET_ID1. Get this value from the Source System Parameters tab in DAC.
Set the parameter $$IS_SOURCE_PRE_80 to Y if your source OLTP application was on a version prior to Siebel 8.0 before you began the upgrade process. Otherwise, set this parameter to N.
Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"
- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"
Follow this procedure to set parameters in the 7961_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.1.
To set parameters in the 7961_UPG_PARAMS.txt file
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 7961_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
In the 7961_UPG_PARAMS.txt file, set the following parameters:
$$ETL_PROC_WID. Set this parameter to the relevant value from the source system setup. You can get this value from W_PARAM_G.ETL_PROC_WID
$$DATASOURCE_NUM_ID. Set this parameter to the relevant value from the source system setup.
$$INITIAL_EXTRACT_DATE. Set this parameter to the initial extraction data of the data warehouse.
$$WH_DATASOURCE_NUM_ID. Set this parameter to the data source number ID you have set up for the data warehouse.
Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"
- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"
Follow this procedure to set parameters in the 7962_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.2.
Note: If your source system is PeopleSoft, you must also set the parameters in Section A.2.3, "Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems."
To set parameters in the 7962_UPG_PARAMS.txt file
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 7962_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
In the 7962_UPG_PARAMS.txt file, set the following parameters:
$$ETL_PROC_WID. Set this parameter to the relevant value from the source system setup. You can get this value from W_PARAM_G.ETL_PROC_WID
$$DATASOURCE_NUM_ID. Set this parameter to the relevant value from the source system setup.
$$INITIAL_EXTRACT_DATE. Set this parameter to the initial extraction data of the data warehouse.
$$WH_DATASOURCE_NUM_ID. Set this parameter to the data source number ID you have set up for the data warehouse.
Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"
- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"
Follow this procedure to set parameters in the 7963_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.3.
To set parameters in the 7963_UPG_PARAMS.txt file
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 7963_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
In the 7963_UPG_PARAMS.txt file, set the following global parameters:
$$ETL_PROC_WID. Set this parameter to the relevant value from the source system setup. You can get this value from W_PARAM_G.ETL_PROC_WID
$$WH_DATASOURCE_NUM_ID. Set this parameter to the data source number ID you have set up for the data warehouse.
In the 7963_UPG_PARAMS.txt file, set the following common dimension parameters:
Locate the section in the file that lists common dimension parameters for your source system, and set the following parameters.
$$DATASOURCE_NUM_ID. Set this parameter to the relevant value from the source system setup.
$$INITIAL_EXTRACT_DATE. Set this parameter to the initial extraction data of the data warehouse.
$$DFLT_LANG. The default value for this parameter is $$DFLT_LANG=US. This value is appropriate for Oracle source systems when the transactional database language is English (US).
For Siebel and JD Edwards source systems with the transactional database language as English (US), set the value for the parameter to $$DFLT_LANG=ENU.
If the default language of your transactional database is not English (US), you need to set the DFLT_LANG parameter to the appropriate language for your data source database. To find the value to specify, execute the following query against the transactional database.
select VAL from S_SYS_PREF where SYS_PREF_CD='ETL Default Language';
Note: PeopleSoft source systems do not use the $$DFLT_LANG parameter.
Follow this procedure to set parameters in the 7964_UPG_PARAMS.txt file. This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.1.
To set parameters in the 7964_UPG_PARAMS.txt file
Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 7964_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
In the 7964_UPG_PARAMS.txt file, set the following parameters:
$$ETL_PROC_WID. Set this parameter to the relevant value from the source system setup. You can get this value from W_PARAM_G.ETL_PROC_WID
$$DATASOURCE_NUM_ID. Set this parameter to the relevant value from the source system setup.
$$INITIAL_EXTRACT_DATE. Set this parameter to the initial extraction data of the data warehouse.
$$WH_DATASOURCE_NUM_ID. Set this parameter to the data source number ID you have set up for the data warehouse.
Search for parameter values defined with the "TO_DATE" function. Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"
- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"
This section provides instructions for setting parameters in the Informatica parameter files that are specific to various source systems. You may need to set or update these parameters depending on your environment. The topic headings below indicate the source system and version of the parameter file that require configuration.
This section includes the following topics:
Section A.2.1, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle EBS 11i Source Systems"
Section A.2.2, "Setting Parameters in 796_UPG_PARAMS.txt for Siebel Source Systems"
Section A.2.3, "Setting Parameters in 7962_UPG_PARAMS.txt for PeopleSoft Source Systems"
Note: If you are using Oracle Financial Analytics and your source system is either PeopleSoft or Oracle EBS 11.5.10 family pack OIE.I and OIE.J, there are additional parameters you must set. For instructions, see Section A.3.5, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Financial Analytics."
This procedure is only applicable to Oracle EBS 11i source systems and for upgrades to Oracle BI Applications release 7.9.6.
To set parameters in the 796_UPG_PARAMS.txt file for Oracle EBS 11i source systems
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the file 796_UPG_PARAMS.txt.
Note the values for the following parameters:
$$ORA_DATASOURCE_NUM_ID_LIST
$$GRAIN
$$GBL_DATASOURCE_NUM_ID
$$QUALIFICATION_CATEGORY_LIST
In DAC, go to the Design view, and select the appropriate custom container.
Select the Source System Parameters tab.
Query for the parameters listed in Step 3, and compare the values.
If necessary, change the values for the parameters in the 796_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.
Save the 796_UPG_PARAMS.txt file.
This procedure is only applicable to Siebel source systems and for upgrades to Oracle BI Applications release 7.9.6.
To set parameters in the 796_UPG_PARAMS.txt file for Siebel source systems
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the file 796_UPG_PARAMS.txt.
Note the values for the following parameters:
$$HI_DT
$$LOW_DT
$$NAME_ORDER_WITH_FIRSTNAME
In DAC, go the Design view, and select the appropriate custom container.
Select the Source System Parameters tab.
Query for the parameters listed in Step 3, and compare the values.
If necessary, change the values for the parameters in the 796_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.
Save the 796_UPG_PARAMS.txt file.
If your source system is PeopleSoft, you must follow the instructions in this section after completing the instructions in Section A.1.7, "Setting Parameters in 7962_UPG_PARAMS.txt." This procedure is applicable for upgrades to Oracle BI Applications release 7.9.6.2.
To set parameters in the 7962_UPG_PARAMS.txt file for PeopleSoft source systems
Open the 7962_UPG_PARAMS.txt file.
Note: Make sure you perform the procedure in Section A.1.7, "Setting Parameters in 7962_UPG_PARAMS.txt" before you begin this procedure.
If you are using PeopleSoft version 8.9 or higher, set the following parameters in the 7962_UPG_PARAMS.txt file specific to multiple product category enhancement:
For the $$TREE_NAME1 parameter, set the value to a tree name for which you want to include the product categories. Generally, this value is ALL_PURCHASE_ITEMS. You can use the following SQL to obtain the TREE_NAMES:
SELECT * FROM PSTREEDEFN WHERE TREE_STRCT_ID = 'ITEMS'
The TREE_STRUCT in the PeopleSoft Tree that defines the Item Category Tree generally has the value ITEMS. If you changed this value, you must update the parameter $$TREE_STRUCT_ID_LIST with the appropriate value.
Verify the value for the PSFT_OLTP_VER parameter matches the version of PeopleSoft you are using.
| PeopleSoft Version | Enter Parameter Value |
|---|---|
|
PeopleSoft version 8.9 |
PSFT_OLTP_VER=90 |
|
PeopleSoft version 9.0 |
PSFT_OLTP_VER=90 |
|
PeopleSoft version 9.1 |
PSFT_OLTP_VER=91 |
The default value for this parameter is PSFT_OLTP_VER=91.
Caution:
You must enter the correct value for this parameter or else the upgrade process will fail.
This procedure is applicable when you are upgrading to Oracle BI Applications release 7.9.6.3 and the source system is Siebel Industry Applications.
To set parameters in the 7963_UPG_PARAMS.txt file for Siebel Industry Applications source systems
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the file 7963_UPG_PARAMS.txt.
Search for the parameter $$VERTICAL_UPGRADE.
If you are using Siebel Industry Applications, set the value to 1.
For example: $$VERTICAL_UPGRADE=1
If you are not using Siebel Industry Applications, leave the default value (0).
Save the 7963_UPG_PARAMS.txt file.
This section provides information about setting parameters in the Informatica parameter files that are specific to an Oracle BI Applications application. You may need to set or update these parameters depending on your environment. The topic headings below indicate the application and version of the parameter file that require configuration.
This appendix includes the following topics:
Section A.3.2, "Setting Parameters in 796_UPG_PARAMS.txt for Oracle Project Analytics"
Section A.3.5, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Financial Analytics"
Section A.3.6, "Setting Parameters in 7963_UPG_PARAMS.txt for Oracle Human Resources Analytics"
This section provides information about parameters and mappings specific to Oracle Financial Analytics that you may need to configure or update depending on your environment. The procedures in this section are applicable for upgrades to Oracle BI Applications release 7.9.6.
This section includes the following topics:
Section A.3.1.1, "Setting Parameters for Value Set Hierarchies and FSG Hierarchies"
Section A.3.1.2, "Setting Parameters for GL Data Extraction"
Section A.3.1.3, "Setting the COGS Fact Mapping for Oracle EBS R12"
Section A.3.1.4, "Setting the $$Hint1 Parameter for Oracle Databases"
In Oracle Financial Analytics, the default behavior is for Value Set Hierarchies to be enabled and Financial Statement Generator (FSG) Hierarchies to be disabled.
If you have changed this behavior by disabling Value Set Hierarchies and enabling FSG Hierarchies, then you need to set the parameters that control this behavior in the 796_UPG_PARAMS.txt file and the DAC configuration tags.
To set the FSG Hierarchies and Value Set Hierarchies parameters
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 796_UPG_PARAMS.txt file.
Search for the parameter $$IS_FSGHIERARCHY_INSTALLED, and set the value to Y.
For example:
$$IS_FSGHIERARCHY_INSTALLED=Y
Search for the parameter $$IS_VALUESETHIERARCHY_INSTALLED, and set the value to N.
For example:
$$IS_VALUESETHIERARCHY_INSTALLED=N
If you have configured your GL data extraction to limit the set of books or ledgers extracted, you need to set the appropriate parameters in the 796_UPG_PARAMS.txt file to match the same parameters in the DAC source system parameters.
This section includes the following topics:
Section A.3.1.2.1, "Setting GL Data Extraction Parameters for Oracle EBS 11i Sources"
Section A.3.1.2.2, "Setting GL Data Extraction Parameters for Oracle EBS R12 Sources"
Follow this procedure to set GL data extraction parameters for Oracle EBS 11i sources.
To set GL data extraction parameters
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 796_UPG_PARAMS.txt file.
Note the values for the following parameters:
$$FILTER_BY_SET_OF_BOOKS_ID
$$FILTER_BY_SET_OF_BOOKS_TYPE
$$SET_OF_BOOKS_ID_LIST
$$SET_OF_BOOKS_TYPE_LIST
In DAC, go to the Design view, and select the appropriate custom container.
Select the Source System Parameters tab.
Query for the parameters listed in Step 3, and compare the values.
If necessary, change the values for the parameters in the 796_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.
Save the 796_UPG_PARAMS.txt file.
Follow this procedure to configure GL data extraction parameters for Oracle EBS R12 sources.
To set GL data extraction parameters
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 796_UPG_PARAMS.txt file.
Note the values for the following parameters:
$$FILTER_BY_LEDGER_ID
$$FILTER_BY_LEDGER_TYPE
$$LEDGER_ID_LIST
$$LEDGER_TYPE_LIST
In DAC, go to the Design view, and select the appropriate custom container.
Select the Source System Parameters tab.
Query for the parameters listed in Step 3, and compare the values.
If necessary, change the values for the parameters in the 796_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.
Save the 796_UPG_PARAMS.txt file.
For Oracle EBS R12 sources, follow this procedure to update the COGS fact mapping.
To set the COGS fact mapping
Launch Informatica PowerCenter Designer.
Navigate to the folder UPGRADE_7951_TO_796_ORA12.
Open the mapping SDE_ORA_GLCOGSFact_UPG796.
Open the mapplet mplt_BC_ORA_GLCOGSFact.
Open the Source Qualifier Transformation, do the following:
Open the SQL Query property.
In the WHERE clause of the query locate the hard-coded filter on the Transaction Type ID and Transaction Action ID.
For example:
MMT.TRANSACTION_TYPE_ID IN (15, 33, 10008) AND (MMT.TRANSACTION_ACTION_ID,MTA.ACCOUNTING_LINE_TYPE) IN ((27, 2), (1, 36), (36, 35))
Change the values to the actual values you used in the SDE_ORA_GLCOGSFact mapping in the base Informatica Repository code.
If your target data warehouse is an Oracle database server, follow this procedure to set the $$Hint1 parameter.
To set the $$Hint1 parameter
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 796_UPG_PARAMS.txt file.
Locate the $$Hint1 parameter for the appropriate version of the Oracle database, and enter the following value:
/*+ USE_HASH(W_GL_BALANCE_F, W_GL_ACCOUNT_D, W_GLACCT_SEG_CONFIG_TMP) */
For example:
mplt_GLBalanceAggrByAcctSegCodes.$$Hint1=/*+ USE_HASH(W_GL_BALANCE_F, W_GL_ACCOUNT_D, W_GLACCT_SEG_CONFIG_TMP) */
Save the 796_UPG_PARAMS.txt file.
If you are deploying Oracle Project Analytics and you are upgrading to Oracle BI Applications release 7.9.6, follow the procedure in this section to configure the IS_PROJECTS_INSTALLED parameter.
To set the IS_PROJECTS_INSTALLED parameter
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 796_UPG_PARAMS.txt file.
Search for the parameter $$IS_PROJECTS_INSTALLED, and set the value to Y.
For example:
$$IS_PROJECTS_INSTALLED=Y
Save the 796_UPG_PARAMS.txt file.
If you are deploying Oracle Supply Chain and Order Management Analytics and you are upgrading to Oracle BI Applications release 7.9.6, follow the procedures in this section to set parameters in 796_UPG_PARAM.txt.
This section includes the following topics:
If you are deploying Oracle Supply Chain and Order Management Analytics, you need to configure the TIME_GRAIN parameter for the Sales Order Lines Aggregate Fact table and for the Invoice Lines Aggregate Fact table. For instructions, see the section titled, "Process of Aggregating Oracle Supply Chain and Order Management," in Oracle Business Intelligence Applications Configuration Guide for Informatica PowerCenter Users.
If you are deploying Oracle Supply Chain and Order Management Analytics, you need to configure the $$PERIOD parameter for the Customer Status History Fact table. For instructions, see the section titled, "How to Configure the Customer Status History Fact Table," in Oracle Business Intelligence Applications Configuration Guide for Informatica PowerCenter Users.
If you are deploying Oracle Financial Analytics and you are upgrading to Oracle BI Applications release 7.9.6.2, follow the procedures in this section for your particular source system to set parameters in 7962_UPG_PARAM.txt.
This section includes the following topics:
Section A.3.4.1, "Setting GL Data Extraction Parameters for Oracle EBS 11i Sources"
Section A.3.4.2, "Setting GL Data Extraction Parameters for Oracle EBS 12 Sources"
Section A.3.4.3, "Setting GL Data Extraction Parameters for PeopleSoft Sources"
Section A.3.4.4, "Setting the COGS Fact Mapping for Oracle EBS R12"
Follow this procedure to configure GL data extraction parameters for Oracle EBS 11i sources.
To set GL data extraction parameters
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 7962_UPG_PARAMS.txt file.
Note the values for the following parameters:
mplt_BC_ORA_GL_Balance_Fact.$$FILTER_BY_SET_OF_BOOKS_ID
mplt_BC_ORA_GL_Balance_Fact.$$FILTER_BY_SET_OF_BOOKS_TYPE
mplt_BC_ORA_GL_Balance_Fact.$$SET_OF_BOOKS_ID_LIST
mplt_BC_ORA_GL_Balance_Fact.$$SET_OF_BOOKS_TYPE_LIST
In DAC, go to the Design view, and select the appropriate custom container.
Select the Source System Parameters tab.
Query for the parameters listed in Step 3, and compare the values.
If necessary, change the values for the parameters in the 7962_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.
Save the 7962_UPG_PARAMS.txt file.
Follow this procedure to configure GL data extraction parameters for Oracle EBS 12 sources.
To set GL data extraction parameters
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 7962_UPG_PARAMS.txt file.
Note the values for the following parameters:
mplt_BC_ORA_GL_Balance_Fact.$$FILTER_BY_LEDGER_ID
mplt_BC_ORA_GL_Balance_Fact.$$FILTER_BY_LEDGER_TYPE
mplt_BC_ORA_GL_Balance_Fact.$$LEDGER_ID_LIST
mplt_BC_ORA_GL_Balance_Fact.$$LEDGER_TYPE_LIST
In DAC, go to the Design view, and select the appropriate custom container.
Select the Source System Parameters tab.
Query for the parameters listed in Step 3, and compare the values.
If necessary, change the values for the parameters in the 7962_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.
Save the 7962_UPG_PARAMS.txt file.
Follow this procedure to configure GL data extraction parameters for PeopleSoft 8.8, 8.9, and 9.0 sources.
To set GL data extraction parameters
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 7962_UPG_PARAMS.txt file.
Note the values for the following parameters:
mplt_BC_PSFT_GLBalanceFact.$$FISCAL_YEAR
$$LOW_DATE
In DAC, go to the Design view, and select the appropriate custom container.
Select the Source System Parameters tab.
Query for the parameters listed in Step 3, and compare the values.
If necessary, change the values for the parameters in the 7962_UPG_PARAMS.txt file to match the values for the parameters in the DAC Source System Parameters tab.
Note:
The parameter $$FISCAL_YEAR is fiscal year from which you want to extract the GL Balances into the data warehouse. GL Balances from PS_LEDGER will be extracted from this year forward into the data warehouse. All balances prior to this year will not be extracted.
Save the 7962_UPG_PARAMS.txt file.
For Oracle EBS R12 sources, follow this procedure to update the COGS fact mapping.
To set the COGS fact mapping
Launch Informatica PowerCenter Designer.
Navigate to the folder UPGRADE_7961_to_7962_ORAR12.
Open the mapping SDE_ORA_GLCOGSFact_UPG7962.
Open the mapplet mplt_BC_ORA_GLCOGSFact.
Open the Source Qualifier Transformation, and do the following:
Open the SQL Query property.
In the WHERE clause of the query, locate the hard-coded filter on the Transaction Type ID and Transaction Action ID.
For example:
MMT.TRANSACTION_TYPE_ID IN (15, 33, 10008) AND (MMT.TRANSACTION_ACTION_ID,MTA.ACCOUNTING_LINE_TYPE) IN ((27,2),(1,36),(36,35))
Change the values to the actual values you used in the SDE_ORA_GLCOGSFact mapping in the main Informatica Repository code.
If you are deploying Oracle Financial Analytics and you are upgrading to Oracle BI Applications release 7.9.6.3, follow the procedures in this section for your particular source system to set parameters in 7963_UPG_PARAM.txt.
This section includes the following topics:
Section A.3.5.1, "Setting Parameters for All Source Systems"
Section A.3.5.2, "Setting Parameters Specific to PeopleSoft"
Section A.3.5.3, "Setting Parameters Specific to Oracle EBS 11.5.10 Family Pack OIE.I and OIE.J"
This section provides instructions for setting parameters in the 7963_UPG_PARAMS.txt file for Oracle Financial Analytics for all source systems, including Oracle EBS 11i, Oracle EBS 12, PeopleSoft, and JD Edwards.
To set the soft delete parameter
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 7963_UPG_PARAMS.txt file.
Note the value for the parameter $$IS_SOFT_DELETE_IMPLEMENTED.
The default value for this parameter is $$IS_SOFT_DELETE_IMPLEMENTED=N.
If the Soft Delete parameter is implemented for any of the Oracle Financial Analytics modules, for example, GL, AP, AR, and Profitability (COGS/Revenue), you must change the parameter value to $$IS_SOFT_DELETE_IMPLEMENTED=Y for the appropriate module for which it is implemented.
Save the 7963_UPG_PARAMS.txt file.
This section provides instructions for setting a parameter for Oracle Financial Analytics in the 7963_UPG_PARAMS.txt file that is specific to PeopleSoft source systems.
To set the parameter specific to PeopleSoft source systems
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 7963_UPG_PARAMS.txt file.
The parameter $$PSFT_OLTP_VER specifies the version of the PeopleSoft OLTP. The default value for this parameter is $$PSFT_OLTP_VER=90.
Change the parameter value to match the appropriate version of the PeopleSoft OLTP. For example:
For PeopleSoft version 8.9, enter $$PSFT_OLTP_VER=89.
For PeopleSoft version 9.0, enter $$PSFT_OLTP_VER=90.
For PeopleSoft version 9.1, enter $$PSFT_OLTP_VER=91.
Note: This parameter is needed to run the Transaction type dimension maps, which are missing in the PeopleSoft 8.9 source system. Therefore, setting this parameter is particularly important if you are using PeopleSoft 8.9.
Save the 7963_UPG_PARAMS.txt file.
This section provides instructions for setting a parameter for Oracle Financial Analytics in the 7963_UPG_PARAMS.txt file that is specific to Oracle EBS 11.5.10 family pack OIE.I and OIE.J.
To set the parameter specific to Oracle EBS 11.5.10 OIE.I or OIE.J
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 7963_UPG_PARAMS.txt file.
The parameter $$ORA_OLTP_VER specifies the version of the Oracle EBS OLTP.
Change the parameter value to match the appropriate version of the family pack for your Oracle EBS 11.5.10 environment.
For Oracle EBS 11.5.10 family pack OIE.I, enter $$ORA_OLTP_VER=OIEI.
For Oracle EBS 11.5.10 family pack OIE.J, enter $$ORA_OLTP_VER=OIEJ.
Save the 7963_UPG_PARAMS.txt file.
If you are deploying Oracle Human Resources Analytics and you are upgrading to Oracle BI Applications release 7.9.6.3, follow the procedure in this section to set parameters in 7963_UPG_PARAM.txt.
To set the parameter for Oracle Human Resources
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 7963_UPG_PARAMS.txt file.
Search for the parameter $$HR_WRKFC_EXTRACT_DATE.
The parameter value is defined with the "TO_DATE" function.
Edit the function to use the appropriate function for data conversion based on the database type:
- For Oracle databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For SQL Server databases, use "CONVERT(datetime,'1899-01-01')"
- For DB2 databases, use "TO_DATE('1899-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')"
- For Teradata databases, use "cast('1899-01-01' as timestamp format 'YYYY-MM-DD')"
Save the 7963_UPG_PARAMS.txt file.
Follow the procedure in this section if you are deploying Oracle Procurement and Spend Analytics on a PeopleSoft 9.0 source system.
To set the parameters for Oracle Procurement and Spend Analytics
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 7963_UPG_PARAMS.txt file.
Set the parameter $$PSFT_DATASOURCE_NUM_ID to the relevant value from the source system setup.
Save the 7963_UPG_PARAMS.txt file.
Follow the procedure in this section if you are deploying Oracle Procurement and Spend Analytics on a Oracle EBS 11i and 12 source systems.
To set the parameters for Oracle Procurement and Spend Analytics
Navigate to the SrcFiles folder on the Informatica Server machine, for example, <INFA_HOME>\server\infa_shared\SrcFiles.
Open the 7963_UPG_PARAMS.txt file.
Search for the entry:
[UPGRADE_7962_to_7963_ORA<version>.SIL_PurchaseCycleLinesFact_UPG7963]
Set the parameter $$ORA_DATASOURCE_NUM_ID to the relevant value from the source system setup.
The default value for Oracle EBS 11i is
$$ORA_DATASOURCE_NUM_ID_LIST=(4)
The default value for Oracle EBS 12is
$$ORA_DATASOURCE_NUM_ID_LIST=(9)
Save the 7963_UPG_PARAMS.txt file.
|
 Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
