Informatica

Oracle BI Applications are a complete, end-to-end BI environment covering the Oracle BI EE platform and the prepackaged analytic applications. The Oracle BI Applications discussed below is solely pertaining to its use with Informatica PowerCenter as the ETL tool. The current version of Oracle BI Applications which is intended for use with Informatica PowerCenter 8.6.1 is 7.9.6.1.                                                            Courtesy: Oracle Corporation As shown above, the packaged ETL mappings consume operational data from sources comprising J D Edwards, Oracle, PeopleSoft and Siebel with the aid of source-specific adaptors as well as universal adaptors, which are used for leg...

The purpose of the mappings discussed below are to report the difference rows between two sources in different scenarios. Scenario 1: When there are difference rows in one of the sources and both the sources are either flat files or a flat file and a relational table. To illustrate this scenario, the two sources considered are two comma separated flat files - EMPLOYEE_FILE_1.txt and EMPLOYEE_FILE_2.txt. The EMPLOYEE_FILE_2.txt has some extra records that need to be reported or loaded into the target which is a relational table having the same definition as the sources. The difference rows between the two flat files are highlighted in red as shown below. Import the two flat file definitions using the Source Analyzer in Informatica PowerCenter Designer client tool as shown below. Create a new mapping in the Mapping Designer and drag the two source definitions into the workspace. Now, to identify the extra records from EMPLOYEE_FILE_2, a Joiner transformation followed b...

The Mapping Wizard available in the Informatica PowerCenter Designer client provides pre-designed mapping templates to create mappings based on specific requirements like SCD Types 1, 2 & 3. The example below explains the creation of an SCD Type 2 mapping using the Mapping Wizard . The source table is EMPLOYEES that contains employee information like Employee ID, Name, Role, Department ID, Location, Employment Status and the Date of joining. The EMPLOYEES table is shown below. EMPLOYEES EMP_ID EMP_NAME EMP_ROLE DEPT_ID LOCATION EMPL_STATUS JOIN_DT 1321 Shaun Mathews Clerk 209 Atlanta Active 13-Apr-08 1487 Shane Smith Supervisor 110 Atlanta Active 4-Aug-08 1678 Katie Wells Manager 198 Atlanta Active 20-Aug-08 The field EMP_ID is the primary key for the EMPLOYEES table. The fields on which history needs to be maintained are EMP_ROLE , DEPT_ID , LOCATION and EMPL_ST...