custom etl

Upload: krreation7086

Post on 11-Oct-2015

57 views

Category:

Documents


0 download

DESCRIPTION

Custom ETL

TRANSCRIPT

  • Oracle BI Applications 7.9: Implementation for Oracle EBSActivity Guide

    D55409GC10

    Edition 1.0

    October 2008

    D56566

  • Copyright 2008, Oracle. All rights reserved.

    Disclaimer

    This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle.

    The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free.

    Restricted Rights Notice

    If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable:

    U.S. GOVERNMENT RIGHTSThe U.S. Governments rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.

    Trademark Notice

    Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

    AuthorJim Sarokin

    Technical Contributors and ReviewersDan HilldaleMitravinda KolachalamManmohit SaggiPhillip ScottKasturi ShekharAlbert Walker Jr.

    EditorsRaj Kumar Daniel Milne Joyce Raftery

    PublisherGiri Venugopal

  • iii

    Contents

    Practice 2-1: Matching Oracle Business Analytics Warehouse Components................... 5 Solutions 2-1: Matching the Oracle Business Analytics Warehouse Components ........... 7 Practice 2-2: Locating the Oracle Business Analytics Warehouse Components.............. 8 Solutions 2-2: Locating Oracle Business Analytics Warehouse Components .................. 9 Practice 4-1 Configuring the Training Environment......................................................... 11 Practice 5-1: Exploring Oracle BI ETL Metadata............................................................. 27 Solutions 5-1: Exploring Oracle BI ETL Metadata........................................................... 35 Practice 6-1: Working with Informatica Designer ............................................................ 39 Practice 7-1: Creating and Running an Informatica Workflow ........................................ 47 Practice 8-1 Exploring a Prebuilt SDE Mapping.............................................................. 51 Practice 8-2 Exploring a Prebuilt SIL Mapping................................................................ 57 Practice 9-1: Exploring the DAC...................................................................................... 63 Solutions 9-1: Exploring the DAC.................................................................................... 73 Practice 10-1: Configuring Common Areas and Dimensions Before Running a Full Load................................................................................................... 77 Practice 10-2: Configuring General Ledger Account Hierarchies ................................... 80 Practice 10-3: Mapping Oracle GL Natural Accounts to Group Account Numbers......... 85 Practice 10-4: Creating a New Metric Based on a New Group Account Number ........... 89 Practice 11-1: Customizing DAC Metadata..................................................................... 93 Practice 13-1: Creating a Custom SDE Mapping ............................................................ 99 Practice 13-2: Creating a Custom SIL Mapping ............................................................ 103 Practice 13-3: Adding DAC Tasks and Running Customized ETL................................ 107 Practice 14-1: Adding a New Dimension in the OBAW................................................. 115 Practice 14-2: Creating an SDE Mapping to Load the Dimension Staging Table......... 118 Practice 14-3: Creating an SIL Mapping to Load the Dimension Table ........................ 122 Practice 14-4: Creating an SDE Mapping to Load the Fact Staging Table................... 125 Practice 14-5: Creating an SIL Mapping to Load the Fact Table .................................. 127 Practice 14-6: Adding DAC Tasks and Running Customized ETL................................ 130

  • iv

  • Lesson 2: Oracle Business Intelligence Applications Architecture Overview

    Oracle BI Applications 7.9: Implementation for Oracle EBS 5

    Practice 2-1: Matching Oracle Business Analytics Warehouse Components

    Goals To match the core Oracle Business Analytics Warehouse components with their corresponding functions

    Scenario You have received your Oracle Business Analytics Warehouse software, and you begin by validating your knowledge of its components.

    Outcome You will have a list of the components and terms related to the software you are about to deploy.

    Time 1015 minutes

    Instructions:

    1. Match the Oracle Business Analytics Warehouse component names on the left to their descriptions on the right. Write the appropriate letter of the description in the blank.

  • Lesson 2: Oracle Business Intelligence Applications Architecture Overview

    6 Oracle BI Applications 7.9: Implementation for Oracle EBS

    Component Description

    1. Mapping Designer

    2. Oracle Business Analytics Warehouse Database

    3. Analytical System

    4. Informatica Designer

    5. DAC

    6. Informatica Repository

    7. Dimensional Schema

    8. Fact Table

    9. Transformations

    10. Batch

    11. Repository Manager

    12. DW Database Server Machine

    13. Administrator Workstation Machine

    14. Dimension Table

    15. ETL

    16. Transactional System

    17. Mappings

    a. Contains the components used to create and administer the data warehouse

    b. Extract, transform, and load data c. Program that runs ETL to load the data warehouse d. Transform data between source and target e. Online analytical processing f. Relational tables, custom-built for the Oracle

    Business Analytics Warehouse, that store mappings, transformations, and other metadata

    g. Enables you to administer the Informatica Repository

    h. Enables you to create and modify the Informatica mappings, transformations, and target tables

    i. Online transaction processing j. Contains the data warehouse k. Format for data that allows for effective querying l. Table in a dimensional schema that stores

    descriptions; has a single primary key m. Central table in a dimensional schema; the only

    table with multiple joins to other tables n. Used to run, schedule, manage, and configure ETL o. Set of instructions for retrieving data, performing

    computations, and loading data p. Used to create mappings q. Database composed of dimensional schemas that

    stores data warehouse data

  • Lesson 2: Oracle Business Intelligence Applications Architecture Overview

    Oracle BI Applications 7.9: Implementation for Oracle EBS 7

    Solutions 2-1: Matching the Oracle Business Analytics Warehouse Components

    Answers:

    1. Match the Oracle Business Analytics Warehouse component names on the left to their descriptions on the right. Write the appropriate letter of the description in the blank.

    Component Description

    p 1. Mapping Designer

    q 2. Oracle Business Analytics Warehouse Database

    e 3. Analytical System

    h 4. Informatica Designer

    n 5. DAC

    f 6. Informatica Repository

    k 7. Dimensional Schema

    m 8. Fact Table

    d 9. Transformations

    c 10. Batch

    g 11. Repository Manager

    j 12. DW Database Server Machine

    a 13. Administrator Workstation Machine

    l 14. Dimension Table

    b 15. ETL

    i 16. Transactional System

    o 17. Mapping

    a. Contains the components used to create and administer the data warehouse

    b. Extract, transform, and load data c. Program that runs ETL to load the data warehouse d. Transform data between source and target e. Online analytical processing f. Relational tables, custom-built for Oracle Business

    Analytics Warehouse, that store mappings, transformations, and other metadata

    g. Enables you to administer the Informatica Repository

    h. Enables you to create and modify the Informatica mappings, transformations, and target tables

    i. Online transaction processing j. Contains the Data Warehouse k. Format for data that allows for effective querying l. Table in a dimensional schema that stores

    descriptions; has a single primary key m. Central table in a dimensional schema; the only

    table with multiple joins to other tables n. Used to run, schedule, manage, and configure ETL o. Set of instructions for retrieving data, performing

    computations, and loading data p. Used to create mappings q. Database composed of dimensional schemas that

    stores data warehouse data

  • Lesson 2: Oracle Business Intelligence Applications Architecture Overview

    8 Oracle BI Applications 7.9: Implementation for Oracle EBS

    Practice 2-2: Locating the Oracle Business Analytics Warehouse Components

    Goals To determine the recommended location for each core component

    Scenario You have received your Oracle Business Analytics Warehouse software, and you begin by validating your knowledge of its components.

    Outcome You will have a list of the component locations for the Oracle Business Analytics Warehouse.

    Time 1015 minutes

    Instructions:

    1. Using the list provided, place a check mark in the appropriate column for the recommended locations for setup and installation of each item.

    ETL Servers Component ETL Clients Component

    OBAW Database

    Component

    ETL Repositories Component

    DAC Client

    DAC Server

    DAC Repository

    Oracle Business Analytics Warehouse Database

    Informatica Integration Services

    Informatica Repository Service

    Informatica Workflow Manager

    Informatica Client (Repository Manager, Designer, and so on)

    Informatica Repository

    Oracle Business Analytics Warehouse Tables

  • Lesson 2: Oracle Business Intelligence Applications Architecture Overview

    Oracle BI Applications 7.9: Implementation for Oracle EBS 9

    Solutions 2-2: Locating Oracle Business Analytics Warehouse Components

    Answers:

    1. Using the list provided, place a check mark in the appropriate column for the recommended locations for setup and installation of each item.

    ETL Servers Component

    ETL Clients Component

    OBAW Database

    Component

    ETL Repositories Component

    DAC Client 9 DAC Server 9 DAC Repository 9 Oracle Business Analytics Warehouse Database

    9

    Informatica Integration Services 9 Informatica Repository Service 9 Informatica Workflow Manager 9 Informatica Client (Repository Manager, Designer, and so on)

    9 Informatica Repository 9 Oracle Business Analytics Warehouse Tables

    9

  • Lesson 2: Oracle Business Intelligence Applications Architecture Overview

    10 Oracle BI Applications 7.9: Implementation for Oracle EBS

  • Lesson 4: Installing Oracle BI Applications

    Oracle BI Applications 7.9: Implementation for Oracle EBS 11

    Practice 4-1 Configuring the Training Environment

    Goals To configure the training environment before you populate and customize the Oracle Business Analytics Warehouse

    Scenario Oracle Business Intelligence platform and Oracle BI Applications have already been installed in this training environment. This includes Informatica PowerCenter, the Data Warehouse Application Console (DAC), two database schemas (DAC and INFA) that were created during the installation process, and one database schema (BIAPPS) that is included as part of the training environment: DAC: contains DAC repository tables INFA: contains Informatica repository tables BIAPPS: contains Oracle E-Business Suite source data In this practice you perform additional, post-installation configuration of the DAC and Informatica in your environment. Performing these tasks is a convenient debugging technique, as most configuration issues arise from steps performed in this practice.

    Time 4050 minutes

    Instructions:

    1. To review the steps that were used to install the Oracle BI components, double-click the Installing shortcut on the desktop to view demonstrations of the Oracle BI Applications and Informatica installation processes. When you are done with the demonstrations, close the browser.

    2. Modify the Informatica PowerCenter initialization file to disable validation of data code pages. a. In Windows Explorer, navigate to C:\Informatica\PowerCenter8.1.1\client\bin. b. Double-click powrmart.ini to open the file using Notepad. c. Locate the following entry at the end of the file:

    [Code Pages] ValidateDataCodePages=Yes

    d. Disable the validation of data code pages by changing the value to No. The data code page is disabled here because the code page is identical for both the source and target databases in this training environment. It is not necessary to validate the code page when the data is moved between compatible source and target databases: [Code Pages]

  • Lesson 4: Installing Oracle BI Applications

    12 Oracle BI Applications 7.9: Implementation for Oracle EBS

    ValidateDataCodePages=No

    e. Select File > Save to save the powrmart.ini file after the modification. f. Select File > Exit.

    3. Copy source files and lookup files. You need to copy source files and lookup files from the Oracle Business Intelligence Applications installation directory to the Informatica directory on the Informatica PowerCenter Services machine. In this training environment, everything is installed on one machine, so you copy between directories. a. Navigate to C:\OracleBI\dwrep\Informatica\SrcFiles and copy all the source files

    in the directory. b. Paste all the source files into

    C:\Informatica\PowerCenter8.1.1\server\infa_shared\SrcFiles. Replace any existing files.

    c. Copy all the lookup files from C:\OracleBI\dwrep\Informatica\LkpFiles and paste into C:\Informatica\PowerCenter8.1.1\server\infa_shared\LkpFiles.

    4. Identify the machine name. You will be using this name throughout this course. a. On the desktop, right-click the My Computer icon and select Properties. b. Select the Computer Name tab and make a note of the machine name, referred to hereafter

    as .

    c. Click OK to close the System Properties window.

    5. Restore the Oracle Business Intelligence prebuilt repository. An Informatica repository file named Oracle_BI_DW_Base.rep is installed into the OracleBI\dwrep\Informatica\Repository directory during the Oracle Business Intelligence Applications installation. You use the restore option in Informatica PowerCenter Administration Console to load this prebuilt Oracle_BI_DW_Base repository. a. Navigate to C:\OracleBI\dwrep\Informatica\Repository. b. Copy the file Oracle_BI_DW_Base.rep and paste it into

    C:\Informatica\PowerCenter8.1.1\server\infa_shared\Backup.

  • Lesson 4: Installing Oracle BI Applications

    Oracle BI Applications 7.9: Implementation for Oracle EBS 13

    c. Double-click the Services icon on the desktop and verify that the service Informatica Services 8.1.1 SP4 is started. If it is not started, start it and wait a minute before continuing with the next step.

    d. Select Start > Programs > Informatica PowerCenter 8.1.1 > Services > Launch Admin Console.

    e. Log in as admin with password admin. f. In the left pane, select the Oracle_BI_DW_Base repository service that was created during

    the installation process. g. In the right pane, select the Properties tab h. Click Edit in the General properties area. i. Set the Operating Mode to Exclusive and click OK. j. Click Yes when prompted to restart repository service. k. Verify that Complete is selected, and then click OK. l. After a few minutes, verify that the service is running.

    m. Select Actions > Delete Contents. n. In the Delete contents for Oracle_BI_DW_Base dialog box, enter Administrator as the

    repository username and Administrator as the password, and then click OK. o. Wait for a Succeeded message. The repository now has no content.

    p. Select Actions > Restore Contents.

  • Lesson 4: Installing Oracle BI Applications

    14 Oracle BI Applications 7.9: Implementation for Oracle EBS

    q. In the Restore Contents dialog box, select Oracle_BI_DW_Base from the Select backup file list and select the Restore as new check box.

    r. Click OK to start the restore process. This takes about 5-10 minutes to complete. s. Verify that the restore completes successfully. The screenshot below shows a partial view.

    t. Click Save to save the log file to the desktop. u. Click Close.

    6. Promote the repository to a global repository. When a repository is restored, the repository becomes a stand-alone repository. After restoring the repository, you need to promote it to a global repository. a. In the Properties tab, click Edit in the General properties area.

  • Lesson 4: Installing Oracle BI Applications

    Oracle BI Applications 7.9: Implementation for Oracle EBS 15

    b. Change the OperatingMode value to Normal.

    c. Click OK. If prompted, enter Administrator for the repository username and password. d. Verify that the repository service Oracle_BI_DW_Base is enabled and running in normal

    mode.

    7. Set PowerCenter Integration Services custom properties. a. In the left pane, select Oracle_BI_DW_Base_Integration_Service. b. Display the Properties tab. c. In the right pane, scroll down to the Custom properties area and click Edit. d. Create the custom properties in the table below by clicking Add to display new Name and

    Value fields. Custom Properties Name Custom Properties Value

    SiebelUnicodeDBFlag No

    ServerPort 4006

    overrideMpltVarWithMapVar Yes

    SiebelUnicodeDB biapps@orcl obaw@orcl e. Verify the results. Be sure to leave a space between biapps@orcl and obaw@orcl:

    f. Click OK. You should receive a message that integration service properties were updated. g. Log out of the Administration Console and close the browser.

    8. Set up the DAC client. a. Copy Hibernate libraries to the appropriate DAC directories. To run the DAC client or DAC

    server, you need to have libraries from an open source software product called Hibernate. Hibernate libraries are not installed as part of Oracle Business Intelligence Applications 7.9.5, but have to be downloaded from the Hibernate Web site. Oracle recommends that you download Hibernate Core Package Version 3.2.x GA or later. Newer versions of Hibernate

  • Lesson 4: Installing Oracle BI Applications

    16 Oracle BI Applications 7.9: Implementation for Oracle EBS

    Core Package 3.2 are now available (for example, Hibernate Core Package Version 3.2.5 GA). DAC is supported on the libraries of these versions also. You can download the Hibernate Core Package from http://www.hibernate.org. For this training, the Hibernate libraries have already been downloaded to your training environment. i. Navigate to C:\PracticeFiles\hibernate-3.2. ii. Copy the Hibernate files from the C:\PracticeFiles\hibernate-3.2 directory to the

    C:\OracleBI\DAC directory as described in the following table. Copy only the files described in the table. You do not need to copy any of the other files in the C:\PracticeFiles\hibernate-3.2 directory. Files Copy from Copy to

    *.jar \hibernate-3.2\lib \DAC\lib

    hibernate3.jar \hibernate-3.2 \DAC\lib

    hibernate-configuration-3.0.dtd \hibernate-3.2\src\org\hibernate \DAC

    hibernate-mapping-3.0.dtd \hibernate-3.2\src\org\hibernate \DAC b. Install JDBC drivers for DAC database connectivity. You must install the appropriate JDBC

    driver in the DAC\lib directory to enable DAC database connectivity. In this training environment you copy the driver from the oracle database directory. i. Navigate to C:\oracle\product\11.1.0\db_1\sqldeveloper\jdbc\lib. ii. Copy ojdbc14.jar. iii. Paste ojdbc14.jar into C:\OracleBI\DAC\lib.

    c. Open the DAC config.bat file and verify the connection configuration for the DAC repository: i. In C:\OracleBI\DAC directory, right-click config.bat and select Edit. ii. Verify that the JAVA_HOME variable points to the directory where Java SDK is

    installed. In this training environment it should be set JAVA_HOME= C:\jdk1.5.0_12. Make sure there are no spaces in the path reference.

    iii. Verify that the DAC_HOME variable points to the directory where DAC is installed. In this training environment it should be set DAC_HOME= C:\OracleBI\DAC.

    iv. Close config.bat.

    9. Enable DAC client communication with Informatica PowerCenter. The DAC client uses the Informatica pmrep and pmcmd command-line programs to communicate with Informatica PowerCenter. The DAC client uses pmrep to synchronize DAC tasks with Informatica workflows and to keep the DAC task source and target tables information up-to-date. a. Install the Informatica pmcmd and pmrep command-line programs.

    i. The pmrep program is installed in the Informatica PowerCenter Client and Informatica PowerCenter Services bin directories. Because of the requirement to co-locate the DAC client with the PowerCenter client, the pmrep program is already available on the machine for the DAC client to use.

    ii. The pmcmd program is installed in the PowerCenter Services bin directories. In this training environment, PowerCenter Services 8.1.1 SP 4 has been installed on the same machine as the DAC client and PowerCenter client 8.1.1 SP4. Copy the pmcmd.exe program from the C:\Informatica\PowerCenter8.1.1\server\bin directory to the C:\Informatica\PowerCenter8.1.1\client\bin directory.

  • Lesson 4: Installing Oracle BI Applications

    Oracle BI Applications 7.9: Implementation for Oracle EBS 17

    b. Set environment variables for the DAC client. In order for the DAC client to be able to use the pmrep and pmcmd programs, you need to define the path of the Informatica domain file domains.infa. i. Verify that domains.infa file is located in C:\Informatica\PowerCenter8.1.1. ii. On the Desktop, right-click My Computer and select Properties. iii. Select Advanced > Environment Variables. iv. Click New to create new system variable. v. Name the variable INFA_DOMAINS_FILE. vi. Set the variable value to C:\Informatica\PowerCenter8.1.1\domains.infa. The path

    should include the name of the file.

    vii. Click OK to close the dialog box. viii. In the Environment Variables dialog box, under System variables, select the path

    system variable and click Edit. ix. In the Edit System Variable dialog box, add the directory path to Informatica

    PowerCenter binaries to the end of the path environment variable. The screenshot shows only a partial view. Be sure to include the semicolon before the directory path:

  • Lesson 4: Installing Oracle BI Applications

    18 Oracle BI Applications 7.9: Implementation for Oracle EBS

    ;C:\Informatica\PowerCenter8.1.1\client\bin

    x. Click OK to close the Edit System Variable dialog box. xi. Click OK to close the Environment Variables dialog box. xii. Click OK to close the System Properties dialog box.

    c. Verify that the DAC client is able to use pmrep and pmcmd. i. From a Windows command prompt, execute pmrep and then pmcmd. The test is

    successful if the pmrep and pmcmd prompts appear.

  • Lesson 4: Installing Oracle BI Applications

    Oracle BI Applications 7.9: Implementation for Oracle EBS 19

    ii. Close the command window.

    10. Create a DAC connection. A DAC connection is a stored set of login details that enable you to log into the DAC client and connect to the DAC repository. a. To start the DAC client, select Start > Programs > Oracle Business Intelligence > Oracle

    DAC > DAC Client. b. In the Login dialog box, select Configure. c. In the Configuring dialog box, select Create Connection, and then click Next. d. Enter the appropriate connection details as specified in the table:

    Name DAC Connection type Oracle (Thin) Instance orcl Database Host Database Port 1521

    e. Click Test Connection. f. Enter dac as the Table owner name and password. g. Click Test and verify that the connection was successfully established. h. Click Close. i. Select Apply. j. Click Finish to save the connection details and return to the login dialog box. k. If necessary, select the DAC connection from the Connection list, enter dac as the table

    owner name and password, and click Login. The DAC client opens. Note: Typically, when you log into DAC and connect to a DAC repository for the first time, the DAC detects that the DAC schema does not exist in the database and you are asked whether you want to create a repository. For this training, the DAC schema and repository tables have already been created in your training environment, so you are not prompted to create the DAC repository.

    11. Importing DAC metadata. Typically, the next step would be to use the DAC client to import DAC metadata into the DAC repository schema. As part of this process, you would specify the source system applications (Oracle 11.5.10, Siebel 8.0, and so on) for which you import the ETL metadata. Because importing DAC metadata is a time-consuming process, this step has been omitted from the training. The DAC metadata for the Oracle 11.5.10 source systems has already been imported into the DAC repository in your training environment. For more information on

  • Lesson 4: Installing Oracle BI Applications

    20 Oracle BI Applications 7.9: Implementation for Oracle EBS

    this process, please refer to the section on importing the DAC Metadata in the Oracle Business Intelligence Applications Fusion Edition Installation and Configuration Guide.

    12. Create the Oracle Business Analytics Warehouse tables. Before starting this procedure, you must create a database schema with a role named SSE_ROLE for the data warehouse. A database schema named OBAW with the role SSE_ROLE has already been created for you in this training environment. The Oracle Business Analytics Warehouse tables are created by the DAC client. The DAC client uses ODBC connections to the Oracle Business Analytics Warehouse database for this procedure. An ODBC connection named OBAW has already been created for you in this training environment. a. In the DAC client, select Tools > ETL Management > Configure. b. In the Sources dialog box, select Oracle as the database platform for both the target data

    warehouse and source transactional database. c. Click OK to display the Data Warehouse Configuration Wizard. d. Select the Create Data Warehouse Tables check box. e. Click Next. The Data Warehouse tab becomes active. f. Enter the appropriate details of the database schema in which you want to store the data

    warehouse as specified in the following table. Leave the Container field blank. If you leave the Container filed blank, DAC creates a container by default for the source business applications (Oracle 11.5.10, Siebel 8.0, and so on) that you selected when you imported the seed data into the DAC metadata repository. Container leave empty for all containers Table Owner obaw Password obaw ODBC Data Source obaw Data Area obaw_data Index Area obaw_index

    g. Click Start. The Run Status tab displays information about the process. h. After a minute or two, verify that a Success message is displayed, indicating that the data

    warehouse tables have been created. If you want to see log information about the process, use the following log files: \OracleBI\DAC\config\generate_ctl.log A log of the schema definition process, including details of any conflicts between containers. \OracleBI\DAC\config\createtables.log A log of the ddlimp process. If a Failure message is displayed, the data warehouse tables have not been created. Use the log information in \OracleBI\DAC\config\generate_ctl.log to diagnose the error. The createtables.log is not generated. Ask your instructor if you need assistance.

    i. Click Finish.

    13. Configure the connection between the DAC server and the DAC repository. Because the training environment uses Windows, you can use the DAC client to configure a DAC server that runs in the same \DAC folder. a. In the DAC client, select Tools > DAC Server Management > DAC Server Setup. The

    DAC repository that you connect to using the DAC client is the one that stores the DAC server repository connection information that you specify in this procedure.

  • Lesson 4: Installing Oracle BI Applications

    Oracle BI Applications 7.9: Implementation for Oracle EBS 21

    b. Click Yes in the Server Setup message to display the Server Configuration dialog box. c. In the Repository Connection Information tab, enter the appropriate information. Because the

    DAC server is running on the same machine as the DAC client, click Populate from preconfigured client connection to populate the fields with connection details from the DAC client.

    d. Click OK and verify the server configuration information. Connection type Oracle (Thin) Instance orcl Database Host Database Port 1521 Table owner name dac Password dac

    e. Click Test Connection to make sure the DAC repository connection works. You should receive a message Connection was successfully established!

    f. Click Close. g. Click Save. (For this training, skip the Email Configuration.)

    14. Set DAC system properties. You need to set these properties to ensure proper integration between the DAC client, the DAC server, and Informatica. a. In the DAC client, click the Setup button to display the Setup view. b. Display the DAC System Properties tab. c. Set values for the following properties:

    InformaticaParameterFileLocation C:\Informatica\PowerCenter8.1.1\server\infa_shared\SrcFiles

    Main Informatica Repository Oracle_BI_DW_Base Repository Name DAC DAC Server Host

    d. Click Save.

    15. Register the Informatica Services in the DAC. a. Click the Informatica Servers tab. b. Register the Informatica Integration Services service, by modifying the record with Name =

    Oracle_BI_DW_Server. Select Oracle_BI_DW_Server in the top pane and then modify the fields in the Edit subtab. Accept all defaults except for the following: Server Hostname Password Administrator

    c. Click Save. d. Register the Informatica repository service, by modifying the record with Name =

    INFORMATICA_REP_SERVER. Accept all defaults except for the following: Server Hostname Password Administrator

  • Lesson 4: Installing Oracle BI Applications

    22 Oracle BI Applications 7.9: Implementation for Oracle EBS

    e. Click Save.

    16. Start the DAC server, restart the DAC client, and test the Informatica connections. a. Close the DAC client. b. Restart the Informatica Services 8.1.1 SP4 service. c. Start the DAC server by selecting Start > Programs > Oracle Business Intelligence >

    Oracle DAC > Start DAC Server. The command window flashes. d. Restart the DAC client by selecting Start the DAC server by selecting Start > Programs >

    Oracle Business Intelligence > Oracle DAC > DAC Client. e. Log in to the DAC connection as dac with the password dac. f. Confirm that the DAC client is connected to the DAC server by looking at the DAC server

    monitor icon in the upper-right corner of the DAC client. The icon color should be orange, indicating that the DAC client is connected to the DAC server and the DAC server is idle. When you mouse over the icon, you should see the message DAC Server is idle. It may take a moment for the connection to be established. Wait until the icon turns orange before proceeding to the next step.

    g. Click Setup to open the Setup view. h. Click the Informatica Servers tab. i. Select Oracle_BI_DW_Server in the upper pane. j. Click Test Connection in the lower pane to test the connection. You should receive a

    message Connection to Oracle_BI_DW_Server successfully established! k. Click OK. l. Select INFORMATICA_REP_SERVER. m. Click Test Connection to test the connection. You should receive a message Connection to

    INFORMATICA_REP_SERVER successfully established! n. Click OK.

    17. Set the transactional and data warehouse physical data sources in the DAC. a. Click the Physical Data Sources tab. The Physical Data Sources tab displays a pre-created

    record for the data warehouse with name DataWarehouse and one or more records for the OLTP sources. The records that are created by DAC for the OLTP sources depend on the business application source systems you selected when importing the DAC metadata. In this training environment you should see ORA_11_5_10 and SEBL_80 sources.

    b. Select DataWarehouse in the top pane. c. Select the Edit subtab and accept all defaults except for the following:

    Instance orcl Table Owner obaw Table Owner Password obaw DB Host Port 1521 Default Index Space OBAW_INDEX

    d. Test the connection. You should receive the message Connection to DataWarehouse successfully established!

    e. Click OK.

  • Lesson 4: Installing Oracle BI Applications

    Oracle BI Applications 7.9: Implementation for Oracle EBS 23

    f. Click Save. g. Select ORA_11_5_10. h. Select the Edit subtab and accept all defaults except for the following:

    Connection type Oracle (Thin) Instance orcl Table Owner biapps Table Owner Password biapps DB Host Port 1521

    i. Test the connection. You should receive the message Connection to ORA_11_5_10 successfully established!

    j. Click OK. k. Click Save. l. Leave the DAC client open for the next practice.

    18. Configure the relational connections in the Informatica Workflow Manager. a. Verify that the Informatica Services 8.1.1 SP4 service is started. b. To log in to Workflow Manager, select Start > Programs > Informatica PowerCenter

    8.1.1 > Client > PowerCenter Workflow Manager. c. In the Welcome window, deselect Show this message at startup and click OK. d. Select Repositories in the Repository Navigator. e. In the menu, select Repository > Add to display the Add Repository dialog box. f. In the Add Repository dialog box, enter Oracle_BI_DW_Base in the Repository field, and

    Administrator in the Username field. g. Click OK to save the details. h. Select Repository > Connect to display the Connect to Repository dialog box. i. Enter Administrator as the password. j. If the Connection Settings area is not displayed, click More. k. Use the Domain list to select the domain (Domain_).

    Please note: If no domain is visible in the list, click Add to display the Add Domain dialog box. At the Add Domain dialog box, specify the name of the domain that was created when you installed Informatica PowerCenter Services (for example, Domain_), and the fully qualified host name for the gateway host (for example, ) and port for the gateway port (for example, 6001).

  • Lesson 4: Installing Oracle BI Applications

    24 Oracle BI Applications 7.9: Implementation for Oracle EBS

    l. Click Connect. The Repository Navigator in the left pane should look similar to the screenshot.

    m. Select Connections > Relational to display the Relational Connection Browser. You need to

    create a connection for each transactional (OLTP) database, and a connection for the Oracle Business Analytics Warehouse (OLAP) database.

    n. Click New to display the Select Subtype dialog box, select Oracle, and click OK. o. Enter the details for the DataWarehouse connection object as specified in the following

    table. You must specify DataWarehouse exactly as it appears in the Physical Data Sources tab in the DAC Setup view. Name DataWarehouse User Name obaw Password obaw Connect String orcl

    p. Click OK. q. Click New again and repeat the steps to create the ORA_11_5_10 connection object. Again,

    you must specify the OLTP connection ORA_11_5_10 exactly as it appears in the Physical Data Sources tab in the DAC Setup view. Name ORA_11_5_10 User Name biapps Password biapps

  • Lesson 4: Installing Oracle BI Applications

    Oracle BI Applications 7.9: Implementation for Oracle EBS 25

    Connect String orcl r. Click OK. s. Click Close. t. Select Repository > Exit to close Workflow Manager.

  • Lesson 4: Installing Oracle BI Applications

    26 Oracle BI Applications 7.9: Implementation for Oracle EBS

  • Lesson 5: Understanding the ETL Process

    Oracle BI Applications 7.9: Implementation for Oracle EBS 27

    Practice 5-1: Exploring Oracle BI ETL Metadata

    Goals To explore some of the prebuilt Oracle Business Intelligence ETL metadata to gain a high-level understanding of some of the key elements, processes, and naming conventions

    Scenario You have installed and configured the software components required to run ETL for the Oracle Business Analytics Warehouse. Before loading and customizing the data warehouse, you explore some of the prebuilt metadata used to perform ETL.

    Outcome You will be able to relate the fundamental steps of the Oracle Business Analytics Warehouse ETL process to prebuilt metadata in the Oracle Informatica Repository and the DAC repository.

    Time 2030 minutes

    Instructions:

    In this exercise, you use Informatica tools and the DAC client to explore some of the prebuilt metadata used in the Oracle Business Analytics Warehouse ETL process. At this point, do not concern yourself with specific details about the metadata, the Informatica tools, or the DAC client, which are all covered in more detail in subsequent lessons. Rather, focus on the metadata objects and their general use in the ETL process.

    1. Start the Informatica Designer tool and connect to the Informatica Repository. a. Verify that the service Informatica Services 8.1.1 SP4 is started. b. Select Start > Programs > Informatica PowerCenter 8.1.1 > Client > PowerCenter

    Designer. c. If the Welcome dialog box appears, deselect Show this message at startup and click OK. d. Double-click Oracle_BI_DW_Base. e. Enter Administrator as the username and password and click Connect.

    2. Explore an SDE adaptor folder. a. Expand the SDE_ORA11510_Adaptor folder in the Repository Navigator. This folder

    contains the Informatica repository source dependent extract (SDE) metadata for the Oracle E-Business Suite application, version 11.5.10.

  • Lesson 5: Understanding the ETL Process

    28 Oracle BI Applications 7.9: Implementation for Oracle EBS

    b. Expand the Sources folder. c. Expand the OLTP and OLAP subfolders. These subfolders contain the Informatica

    repository source definition objects for the transactional (OLTP) and data warehouse (OLAP) databases for this adaptor. Source definition objects provide detailed descriptions of tables or files that provide source data in mappings. (For this training, you can ignore the other subfolders in the Sources folder.)

    d. Expand the Targets folder. The Targets folder contains the Informatica repository target definition objects for this adaptor. Target definition objects provide detailed descriptions of objects or files that contain target data in mappings.

    e. Expand the Transformations folder. The Transformations folder contains the Informatica repository transformation objects for this adaptor. Transformation objects are used in mappings to generate, modify, or pass data.

    f. Expand the Mapplets folder. The Mapplets folder contains the Informatica repository mapplet objects for this adaptor. Mapplets are reusable objects that are used in mappings in the same way as transformations to generate, modify, or pass data.

    g. Expand the Mappings folder. The Mappings folder contains the Informatica repository mapping objects for this adaptor. Mappings contain a set of mapplets, source definitions, target definitions, and transformations used to extract, transform, and load data.

    3. Explore an SDE mapping. a. Expand the Mappings folder and locate the mapping SDE_ORA_GLRevenueFact. Based

    on the name of this mapping, what do you surmise is the purpose of this mapping?

    b. Expand the mapping SDE_ORA_GLRevenueFact. What is the target table for this mapping?

    c. Is this table located in the transactional database or the data warehouse?

  • Lesson 5: Understanding the ETL Process

    Oracle BI Applications 7.9: Implementation for Oracle EBS 29

    d. What type of table is this?

    e. Notice that there are no source instances for this mapping. Non-Siebel SDE adapter folders typically do not expose sources directly in the mappings. Instead, they use the concept of Business Component mapplets. These are extract mapplets that may contain relational, application, or flat file sources. You learn more about this in the next lesson, Working with Informatica Designer, and Lesson 8, Exploring SDE and SIL Mappings.

    f. Expand the Transformation Instances folder and notice that there are two mapplets defined for this mapping: mplt_BC_ORA_GLRevenueFact and mplt_SA_ORA_GLRevenueFact. These mapplets are transformation objects in the SDE mapping. They are used to extract data from an Oracle source, make any necessary transformations to the data, and output the data to the next transformation object in the SDE mapping. You learn more about this in the next lesson, Working with Informatica Designer, and Lesson 8, Exploring SDE and SIL Mappings.

    4. Explore SDE mapplets. a. Expand SDE_ORA11510_Adaptor > Mapplets to examine the two mapplets for the

    SDE_ORA_GLRevenueFact mapping. b. Scroll to locate the mapplet mplt_BC_ORA_GLRevenueFact. c. Expand the Source Instances folder and notice there are four source definitions for this

    mapplet: RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST_ALL, and RA_SALESREPS_ALL. Are these sources located in the transactional database or the data warehouse database?

    d. Expand the Transformation Instances folder. This folder contains the additional transformation objects for this mapplet.

    e. Locate and expand the mapplet mplt_SA_ORA_GLRevenueFact. f. Notice there are no source instances for this mapplet. That is because this mapplet contains

    lookup transformations, which can look up data in a flat file or a relational table, view, or synonym.

    g. Expand the Transformation Instances folder. Notice that there are two lookup transformations for this mapplet: LKP_CUSTLOC_CUST_LOC_ID and LKP_LOC_CURRENCY.

    5. Explore the SILOS folder. a. Expand Oracle_BI_DW_Base > SILOS. This folder contains the Informatica Repository

    source independent load (SIL) metadata. Notice that the SILOS folder contains all of the

  • Lesson 5: Understanding the ETL Process

    30 Oracle BI Applications 7.9: Implementation for Oracle EBS

    same subfolders contained in an SDE_*_Adapter folder.

    b. Expand the Sources folder. Are the sources listed here in the transactional database or the

    data warehouse?

    6. Explore an SIL mapping. a. Expand the Mappings folder and locate the mapping SIL_GLRevenueFact. Based on the

    name of this mapping, what do you surmise is the purpose of this mapping?

    b. Expand SIL_GLRevenueFact > Target Instances. What is the target table for this mapping?

    c. Is this table located in the transactional database or the data warehouse?

    d. What type of table is this?

    e. Expand SIL_GLRevenueFact > Source Instances. Notice that one of the sources for this mapping is W_GL_REVN_FS. Is this table located in the transactional database or the data warehouse?

    f. What type of table is this?

    g. Which SDE mapping populates this table?

    h. Expand the Transformation Instances folder and notice that there are many more transformation objects associated with an SIL mapping than with an SDE mapping. You explore these transformations in more detail in Lesson 8: Exploring SDE and SIL Mappings.

    i. Can you think of any instances where a Source Independent Loading mapping would include a source table in the transactional database?

  • Lesson 5: Understanding the ETL Process

    Oracle BI Applications 7.9: Implementation for Oracle EBS 31

    7. Explore workflows in Informatica Workflow Manager. a. In Informatica PowerCenter Designer, select Tools > Workflow Manager. b. In the Repository Navigator, expand SDE_ORA11510_Adapter > Workflows >

    SDE_ORA_GLRevenueFact to view the components of the SDE_ORA_GLRevenueFact workflow. Notice there are two tasks for this workflow: a Start task and a task named SDE_ORA_GLRevenueFact.

    c. Right-click the SDE_ORA_GLRevenueFact task (not the workflow) and select Properties. d. If necessary, click the Object tab. e. Notice that the mapping for this task is SDE_ORA_GLRevenueFact. This workflow

    contains instructions on how to execute the task for the mapping SDE_ORA_GLRevenueFact, which extracts and moves data from source tables to the W_GL_REVN_FS fact staging table.

    f. Click Cancel to close the Properties dialog box. g. Notice that there is another workflow named SDE_ORA_GLRevenueFact_Full. This

    workflow also contains instructions on how to execute the task for the SDE_ORA_GLRevenueFact mapping, which extracts and moves data from source tables to the W_GL_REVN_FS fact staging table. A table can be loaded in full mode or incremental mode. Full mode refers to data loaded for the first time or data that is truncated and then loaded. Incremental mode refers to new or changed data being added to the existing data.

  • Lesson 5: Understanding the ETL Process

    32 Oracle BI Applications 7.9: Implementation for Oracle EBS

    h. In the Repository Navigator, expand SILOS > Workflows > SIL_GLRevenueFact to view the components of the SIL_GLRevenueFact workflow. Notice that there are two tasks for this workflow: a Start task and a task named SIL_GLRevenueFact.

    i. Right-click the SIL_GLRevenueFact task (not the workflow) and select Properties. j. If necessary, click the Object tab. k. Notice that the mapping for this task is SIL_GLRevenueFact. This workflow contains

    instructions on how to execute the task for the SIL_GLRevenueFact mapping, which loads data from the fact staging table and other data warehouse tables into the W_GL_REVN_F fact table.

    l. Click Cancel to close the Properties dialog box. m. Notice that there is another workflow named SIL_GLRevenueFact_Full. n. Select Repository > Exit to close Workflow Manager. o. Select Repository > Exit to close Designer.

    8. Return to the DAC client, which should still be open from the previous set of practices. If not, follow the instructions below to start the DAC client. a. Select Start > Programs > Oracle Business Intelligence > Oracle DAC > DAC Client. b. Log in to the DAC connection with table owner name dac and password dac (these should be

    the default login values). It may take a few seconds for the DAC client to open.

    9. Explore DAC SDE tasks. a. If necessary, click Design in the upper-left corner of the DAC client to open the Design view. b. If necessary, select the Oracle 11.5.10 container in the list. c. Click the Tasks tab in the upper-right corner (not the Tasks subtab).

  • Lesson 5: Understanding the ETL Process

    Oracle BI Applications 7.9: Implementation for Oracle EBS 33

    d. Click the Query button. e. In the Name field, enter SDE_ORA_GLRevenueFact. f. Click Go and verify that the SDE_ORA_GLRevenueFact task is returned by the query and

    is the only task visible in the upper window. g. If necessary, click the Edit subtab. h. Notice that the task phase for this task is Extract Fact, which uses SDE workflows and

    mappings to extract data from source transactional tables and to load fact staging tables in the Oracle Business Analytics Warehouse (OBAW).

    i. Notice that the execution type for this task is Informatica. Most DAC tasks are Informatica task types, which call and run Informatica workflows in the Informatica repository. Based on your exploration of workflows in Informatica Workflow Manager, which Informatica workflows are called and run by this DAC task?

    j. Which Informatica mapping is executed by the workflows that are called and run by this DAC task?

    k. Based on your exploration of this SDE_ORA_GLRevenueFact mapping in Informatica Designer, what is the target table for this DAC task?

    l. To verify your answer, click the Target Tables subtab. m. Click the Source Tables subtab to view the source tables for this DAC task.

    10. Explore DAC SIL tasks. a. Click the Query button. b. In the Name field, enter SIL_GLRevenueFact. c. Click Go and verify that the SIL_GLRevenueFact task is returned by the query and is the

    only task visible in the upper window. Recall that this is the SIL mapping you explored in Informatica Designer earlier in this practice.

    d. If necessary, click the Edit subtab. e. Notice that the task phase for this task is Load Fact, which uses SIL workflows and

    mappings to load data from fact staging tables into fact tables in the OBAW. f. Notice that the execution type for this task is Informatica. Most DAC tasks are Informatica

    task types, which call and run Informatica workflows in the Informatica repository. Based on your exploration of workflows in Informatica Workflow Manager, which Informatica workflows are called and run by this DAC task?

    g. Which Informatica mapping is executed by the workflows that are called and run by this DAC task?

  • Lesson 5: Understanding the ETL Process

    34 Oracle BI Applications 7.9: Implementation for Oracle EBS

    h. Based on your exploration of this SIL_GLRevenueFact mapping in Informatica Designer, what is the target table for this DAC task?

    i. To verify your answer, click the Target Tables subtab. j. Click the Source Tables subtab to view the source tables for the SIL_GLRevenueFact DAC

    task. k. What is the primary source table for the SIL_GLRevenueFact task?

    l. What type of table is this?

    m. Which DAC task loads this table?

    n. Select File > Close to close the DAC client.

  • Lesson 5: Understanding the ETL Process

    Oracle BI Applications 7.9: Implementation for Oracle EBS 35

    Solutions 5-1: Exploring Oracle BI ETL Metadata

    Answers:

    3.a. Expand the Mappings folder and locate the mapping SDE_ORA_GLRevenueFact. Based on the name of this mapping, what do you surmise is the purpose of this mapping? This source dependent extract (SDE) mapping extracts Oracle source data that is used to load the general ledger revenue fact table.

    3.b. Expand the mapping SDE_ORA_GLRevenueFact. What is the target table for this mapping? W_GL_REVN_FS

    3.c. Is this table located in the transactional database or the data warehouse? Data warehouse

    3.d. What type of table is this? Fact staging table

    4.c. Expand the Source Instances folder and notice there are four source definitions for this mapplet: RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST_ALL, and RA_SALESREPS_ALL. Are these sources located in the transactional database or the data warehouse database? Transactional database

    5.b. Expand the Sources folder. Are the sources listed here in the transactional database or the data warehouse? Data warehouse

    6.a. Expand the Mappings folder and locate the mapping SIL_GLRevenueFact. Based on the name of this mapping, what do you surmise is the purpose of this mapping? The purpose of this mapping is to load the general ledger revenue fact table in the data warehouse.

    6.b. Expand SIL_GLRevenueFact > Target Instances. What is the target table for this mapping? W_GL_REVN_F

    6.c. Is this table located in the transactional database or the data warehouse? Data warehouse

    6.d. What type of table is this? Fact table

    6.e. Expand SIL_GLRevenueFact > Source Instances. Notice that one of the sources for this mapping is W_GL_REVN_FS. Is this table located in the transactional database or the

  • Lesson 5: Understanding the ETL Process

    36 Oracle BI Applications 7.9: Implementation for Oracle EBS

    data warehouse? Data Warehouse

    6.f. What type of table is this? Fact staging table

    6.g. Which SDE mapping populates this table? SDE_ORA_GLRevenueFact

    6.i. Can you think of any instances where a Source Independent Loading mapping would include a source table in the transactional database? Source Independent Loading mappings are used to process data in the staging tables and other data warehouse tables and load it into the ultimate target tables, so typically these mappings would not include a source table in transactional database.

    9.i. Notice that the execution type for this task is Informatica. Most DAC tasks are Informatica task types, which call and run Informatica workflows in the Informatica repository. Based on your exploration of workflows in Informatica Workflow Manager, which Informatica workflows are called and run by this DAC task? SDE_ORA_GLRevenueFact and SDE_ORA_GLRevenueFact_Full

    9.j. Which Informatica mapping is executed by the workflows that are called and run by this DAC task? SDE_ORA_GLRevenueFact

    9.k. Based on your exploration of this SDE_ORA_GLRevenueFact mapping in Informatica Designer, what is the target table for this DAC task? W_GL_REVN_FS

    10.f. Notice that the execution type for this task is Informatica. Most DAC tasks are Informatica task types, which call and run Informatica workflows in the Informatica repository. Based on your exploration of workflows in the Informatica Workflow Manager, which Informatica workflows are called and run by this DAC task? SIL_GLRevenueFact and SIL_GLRevenueFact_Full

    10.g. Which Informatica mapping is executed by the workflows that are called and run by this DAC task? SIL_GLRevenueFact

    10.h. Based on your exploration of this SIL_GLRevenueFact mapping in Informatica Designer, what is the target table for this DAC task? W_GL_REVN_F

    10.k. What is the primary source table for the SIL_GLRevenueFact task? W_GL_REVN_FS

    10.l. What type of table is this? Fact staging table

  • Lesson 5: Understanding the ETL Process

    Oracle BI Applications 7.9: Implementation for Oracle EBS 37

    10.m. Which DAC task loads this table? SDE_ORA_GLRevenueFact

  • Lesson 5: Understanding the ETL Process

    38 Oracle BI Applications 7.9: Implementation for Oracle EBS

  • Lesson 6: Working with Informatica Designer

    Oracle BI Applications 7.9: Implementation for Oracle EBS 39

    Practice 6-1: Working with Informatica Designer

    Goal To use Informatica Designer tools to build a source dependent extract mapping

    Scenario The primary goal of this practice is to become familiar with Informatica Designer and its tools. To accomplish this, you create a source dependent extract (SDE) mapping that extracts data from a source table and moves the data into a fact staging table. Thus, the secondary goal of this practice is to become familiar with some ETL mapping components and the steps to create them. In this set of practices, you use custom tables provided specifically for this training. These tables have very small datasets, so you can focus less on the data being moved by ETL and more on Informatica Designer tools and the steps for building mappings. In the practices for the next lesson, you use Informatica Workflow Manager to run the mapping and to verify the results. Later in this course, in lessons 14 and 15, you build custom SDE and SIL mappings and use the DAC to run the mappings and to verify the results.

    Outcome When you complete this practice, you will have an SDE mapping that extracts data from the REVN table and loads it into the WC_REVN_FS staging table.

    Time 3040 minutes

    Instructions:

    1. Open Informatica Repository Manager and create a custom Informatica repository folder. All modifications to the Oracle_BI_DW_Base repository should be done in custom folders. a. Select Start > Programs > Informatica PowerCenter 8.1.1 > Client > PowerCenter

    Repository Manager. b. If the Welcome dialog box appears, deselect Show this message at startup and click OK. c. Double-click Oracle_BI_DW_Base. d. Enter Administrator as the username and password and click Connect. e. Select Folder > Create. f. Name the new folder CUSTOM_SDE and click OK. g. Click OK to confirm that the folder has been successfully created.

    2. Import the source for the SDE mapping. a. Select Tools > Designer to open the Informatica PowerCenter Designer. b. Right-click the CUSTOM_SDE folder and select Open. Alternatively, you can double-click the

    CUSTOM_SDE folder to open it. c. Verify that the CUSTOM_SDE folder is bolded and that the toolbar displays CUSTOM_SDE

    (Oracle_BI_DW_Base) in the drop-down field in the upper-left corner. d. Source Analyzer should already be open in the workspace. If not, select Tools > Source

    Analyzer.

  • Lesson 6: Working with Informatica Designer

    40 Oracle BI Applications 7.9: Implementation for Oracle EBS

    e. Select Sources > Import from Database. The Import Tables dialog box appears. f. Select ETL_LAB_OLTP (Oracle in OraDb11g_home1) from the ODBC data source list.

    This ODBC data source has already been created for your training environment. g. Enter etl_lab_oltp for username, owner name, and password, and click Connect. Use

    lowercase for all three values. h. Expand ETL_LAB_OLTP > TABLES. i. Select the REVN table. j. Click OK. REVN is displayed in the Source Analyzer workspace. k. In the Navigator, expand CUSTOM_SDE > Sources and verify that the ETL_LAB_OLTP

    source appears and contains the REVN table. l. Select Repository > Save. m. In the Output window, verify there is a message indicating that the source

    ETL_LAB_OLTP:REVN is inserted.

    3. Preview the source data. a. In the Source Analyzer window, right-click the REVN table and select Preview Data. b. Select ETL_LAB_OLTP (Oracle in OraDb11g_home1) for the ODBC data source, enter

    etl_lab_oltp for the username, owner name, and password, and click Connect. Use lowercase for all three values. The Preview Data window appears.

    Note that REVN has five rows of revenue data with a primary key (ROW_ID), foreign keys for product and person data, and a LAST_UPDATE_DATE column. Recall that LAST_UPDATE_DATE is used in incremental loads to identify changed records. LAST_UPDATE_DATE is compared to the DAC parameter $$LAST_EXTRACT_DATE to determine which records have been updated since the last ETL run.

    c. Click Close to close the Preview Data window.

    4. Import the target for the SDE mapping. a. Select Tools > Target Designer. b. Select Targets > Import from Database. c. Select the ETL_LAB_DW (Oracle in OraDb11g_home1) ODBC data source to connect to

    the target database.

  • Lesson 6: Working with Informatica Designer

    Oracle BI Applications 7.9: Implementation for Oracle EBS 41

    d. Enter etl_lab_dw for the username, owner name, and password, and click Connect. Use lowercase for all three values.

    e. Expand ETL_LAB_DW > TABLES. f. Select the WC_RVF_FS table. g. Click OK. WC_RVF_FS is displayed in the Target Designer workspace. h. In the Navigator, expand CUSTOM_SDE > Targets and verify that the WC_RVF_FS

    target is visible. i. Select Repository > Save. j. In the Output window, verify there is a message indicating that the target WC_RVF_FS is

    inserted. k. In the Target Designer window, examine the WC_RVF_FS table definition. Notice that this

    staging table has the following required columns: - INTEGRATION_ID: Stores the primary key or the unique identifier of a record as in the source table. - DATASOURCE_NUM_ID: Stores the data source from which the data is extracted. It also has placeholders for the source columns that will be mapped to this target when you build the SDE mapping.

    5. In the steps that follow, you create a source dependent extract mapping named SDE_C_RevenueFact. This mapping extracts and moves data from the source table, REVN, to the target fact staging table, WC_RVF_FS. The data does not undergo any major transformations in this mapping as it is moved from the source to the target fact staging table. The C in the naming convention indicates that this is a custom mapping. The completed mapping will look similar to this screenshot:

    At all times, ensure that you are working in the CUSTOM_SDE Folder. Verify that the CUSTOM_SDE folder is bolded and the Designer toolbar displays CUSTOM_SDE - (Oracle_BI_DW_Base) in the drop-down field in the upper-left corner.

    6. Create a mapplet to extract the revenue data from the source. a. Select Tools > Mapplet Designer. b. Select Mapplets > Create. c. Name the mapplet mplt_BC_C_RevenueFact and click OK.

    7. Create parameters to pass values for the last extract date and the initial extract date to the mapplet. These parameters are used to identify records that have changed since the last ETL run. The values for these parameters are passed from the DAC during ETL run time. Because you will use Informatica Workflow Manager, and not the DAC, to run and verify the SDE mapping in the next practice, you hard code the value for the $$LAST_EXTRACT_DATE parameter. Please note that hard-coding the value is for training purposes only and is not the recommended practice.

  • Lesson 6: Working with Informatica Designer

    42 Oracle BI Applications 7.9: Implementation for Oracle EBS

    a. Select Mapplets > Parameters and Variables. b. Click the Add a new variable to this table button. c. Enter the following values:

    Name: $$LAST_EXTRACT_DATE Type: Parameter

    Data type: Date/time

    Initial Value 05/02/2003 21:02:44 d. Click the Add a new variable to this table button again. e. Enter the following values:

    Name: $$INITIAL_EXTRACT_DATE Type: Parameter

    Data type: Date/time

    Initial Value

    f. Click OK.

    8. Add a source definition to the mapplet. a. In the Repository Navigator, expand CUSTOM_SDE > Sources > ETL_LAB_OLTP. b. Drag the REVN source into the Mapplet Designer. By default, a source qualifier

    transformation named SQ_REVN is created. c. If desired, select Layout > Zoom Percent to change the layout of the mapplet in the Mapplet

    Designer.

    9. Add a mapplet output transformation to the mapplet. a. Select Transformation > Create to open the Create Transformation dialog box. b. In the list, select Mapplet Output. c. Name the transformation MAPO_REVN_EXTRACT. d. Click Create. e. Click Done. f. Drag MAPO_REVN_EXTRACT to the right of SQ_REVN. g. Drag each column from SQ_REVN to a blank row in MAPO_REVN_EXTRACT. h. Check your work. Your mapplet should look similar to the screenshot:

    10. Generate the default SQL query for the source qualifier. a. Double-click the SQ_REVN source qualifier. b. Click the Properties tab.

  • Lesson 6: Working with Informatica Designer

    Oracle BI Applications 7.9: Implementation for Oracle EBS 43

    c. For the Sql Query transformation attribute, in the Value field, click the down arrow to open the SQL Editor.

    d. Click inside the SQL: field. e. Click Generate SQL to display the default query. f. Modify the default SQL query to include a WHERE clause that compares the

    LAST_UPDATE_DATE column to the $$LAST_EXTRACT_DATE parameter. Hint: You can enter the port and variable manually, or double-click the corresponding objects in the left pane to add them to the query: WHERE (REVN.LAST_UPDATE_DATE > TO_DATE('$$LAST_EXTRACT_DATE', 'MM/DD/YYYY HH24:MI:SS'))

    g. Click OK to close SQL Editor. h. Click Apply in the Edit Transformations dialog box. i. Click OK to close the Edit Transformations dialog box.

    11. Validate the mapplet. a. Select Layout > Arrange. b. In the Select Outputs dialog box, verify that MAPO_REVN_EXTRACT is selected and

    click OK. c. If necessary, select View > Output to view the Output window. d. Click the Validate tab of the Output window e. Select Mapplets > Validate. You should receive the message Mapplet

    mplt_BC_C_RevenueFact is VALID. f. If your mapplet is valid, select Repository > Save to update the repository. If you receive a

    message that the mapplet is not valid, review the steps in this practice and try to troubleshoot. If you need assistance, ask your instructor.

    12. Create an SDE mapping. a. Select Tools > Mapping Designer. b. Select Mappings > Create. c. Name the mapping SDE_C_RevenueFact, and click OK.

    13. Create a parameter to pass a value for the DATASOURCE_NUM_ID to the mapping. DATASOURCE_NUM_ID is a unique number assigned by the DAC to a data source so that the data can be identified in the data warehouse. By default, the unique number assigned to the Oracle E-Business Suite source is 4. This value is passed from the DAC during ETL run time. Because you will use Informatica Workflow Manager and not the DAC to run and verify the SDE mapping in the next practice, you hard code the value for the $$DATASOURCE_NUM_ID

  • Lesson 6: Working with Informatica Designer

    44 Oracle BI Applications 7.9: Implementation for Oracle EBS

    parameter. Please note that hard-coding this value is for training purposes only and is not the recommended practice. a. Select Mappings > Parameters and Variables. b. Click the Add a new variable to this table button. c. Enter the following values:

    Name: $$DATASOURCE_NUM_ID Type: Parameter

    Data type: integer

    Initial Value 4 d. Click OK.

    14. Add the mapplet to the mapping. a. In the Repository Navigator, expand CUSTOM_SDE > Mapplets. b. Drag mplt_BC_C_RevenueFact from the Navigator into the Mapping Designer workspace.

    15. Create a new Expression transformation and add it to the mapping. An Expression transformation is used to calculate values in a single row before writing to the target. In this step, you use the $$DATASOURCE_NUM_ID parameter that you created in an earlier step to place a value of 4 in DATASOURCE_NUM_ID. a. Select Transformation > Create. b. Select Expression from the transformation type list. c. Enter EXPTRANS as the transformation name. d. Click Create. e. Click Done. f. In mplt_BC_C_RevenueFact, use Shift-click to select all five ports, ROW_ID, PROD_ID,

    PERSON_ID, REVF, and LAST_UPDATE_DATE, and drag them to the EXPTRANS transformation.

    g. Double-click EXPTRANS. h. Click the Ports tab. i. Click the Add a new port to this transformation button. j. Give the new port the following attributes:

    Name: DATASOURCE_NUM_ID

    Data type: Decimal

    Prec 10

    Port Type Output k. If necessary, select the DATASOURCE_NUM_ID port and use the up arrow to move it to

    the top of the port list. l. For the DATASOURCE_NUM_ID port, click the down arrow button in the Expression

    column to open Expression Builder. m. Delete the existing formula (DATASOURCE_NUM_ID). n. Click the Variables tab in the left pane.

  • Lesson 6: Working with Informatica Designer

    Oracle BI Applications 7.9: Implementation for Oracle EBS 45

    o. Expand the Mapping Parameters folder and double-click the $$DATASOURCE_NUM_ID variable to add it to the expression. When you run ETL in the next practice, the DATASOURCE_NUM_ID port will be populated with the initial value (4) defined for the $$DATASOURCE_NUM_ID variable.

    p. Click OK. q. Click Apply and OK.

    16. Add and link the target definition. Target definitions vary by mapping. In this practice, the target for data extracted from the REVN source is the WC_RVF_FS fact staging table in the ETL_LAB_DW database. a. In the Repository Navigator, expand CUSTOM_SDE > Targets and select WC_RVF_FS. b. Drag WC_RVF_FS into the Mapping Designer and place it to the right of EXPTRANS. c. Drag ROW_ID from EXPTRANS to INTEGRATION_ID in the WC_RVF_FS target

    definition. INTEGRATION_ID stores the primary key or the unique identifier of a record. d. Drag DATASOURCE_NUM_ID, PROD_ID, PERSON_ID, REVF, and

    LAST_UPDATE_DATE from EXPTRANS onto their corresponding ports in the WC_RVF_FS target definition.

    17. Validate the mapping. a. Select Layout > Arrange. b. Select WC_RVF_FS as the target and click OK. The mapping should look similar to the

    screenshot:

    c. If necessary, select View > Output to view the Output window. d. Click the Validate tab of the Output window e. Select Mappings > Validate. You should receive the message Mapping

    SDE_C_RevenueFact is VALID. f. If your mapping is valid, select Repository > Save. If you receive a message that the

    mapping is not valid, review the steps in this practice and try to troubleshoot. If you need assistance, ask your instructor.

    g. Leave Informatica Designer open for the next practice.

  • Lesson 6: Working with Informatica Designer

    46 Oracle BI Applications 7.9: Implementation for Oracle EBS

  • Lesson 7: Working with Informatica Workflow Manager

    Oracle BI Applications 7.9: Implementation for Oracle EBS 47

    Practice 7-1: Creating and Running an Informatica Workflow

    Goals To use Informatica Workflow Manager to create a workflow for the SDE mapping you created in the previous practice

    Scenario In the practice for the previous lesson you created a source dependent extract (SDE) mapping that extracts data from a source table and moves the data into a fact staging table. Now you use Informatica Workflow Manager to create a workflow to run the mapping. Please note that the DAC is used to run ETL mappings in production environments; whereas Informatica client tools are used for testing. Again, as in the practice for the previous lesson, you use custom tables provided specifically for this training.

    Outcome You have a workflow associated with the SDE mapping and have loaded the WC_RVF_FS fact staging table.

    Time 2030 minutes

    Instructions:

    1. Verify that the Informatica Services 8.1.1 SP4 service is started.

    2. Start the Informatica Workflow Manager. If the Informatica Designer is still open from the previous practice, select Tools > Workflow Manager. If the Informatica Designer is not open, follow these steps: a. Select Start > Programs > Informatica PowerCenter 8.1.1 > Client > PowerCenter

    Workflow Manager. b. Double-click Oracle_BI_DW_Base. c. Enter Administrator as the username and password and click Connect.

    3. Add a database connection to the target database. a. Select Connections > Relational to open the Relational Connection Browser. b. Click New. c. In the Select Subtype dialog box, select Oracle and click OK. d. In the Connection Object Definition dialog box, enter the following values:

    Name etl_lab_dw

    User Name etl_lab_dw

    Password etl_lab_dw

    Connect String ORCL e. Click OK to return to the Relational Connection Browser.

  • Lesson 7: Working with Informatica Workflow Manager

    48 Oracle BI Applications 7.9: Implementation for Oracle EBS

    4. Add a database connection to the source database. a. Click New in the Relational Connection Browser. b. In the Select Subtype dialog box, select Oracle and click OK. c. In the Connection Object Definition dialog box, enter the following values:

    Name etl_lab_oltp

    User Name etl_lab_oltp

    Password etl_lab_oltp

    Connect String ORCL d. Click OK to return to the Relational Connection Browser. e. Click Close to close the Relational Connection Browser.

    5. Create a workflow for the SDE mapping you created. This workflow contains instructions on how to execute the session task for the mapping SDE_C_RevenueFact, which extracts and moves the data from the source table REVN to the target fact staging table WC_RVF_FS. a. Verify that the CUSTOM_SDE folder is open. If it is not open, double-click

    CUSTOM_SDE to open it or right-click CUSTOM_SDE and select Open. b. Select Tools > Workflow Designer. c. Select Workflows > Create. d. In the Create Workflow dialog box, enter the name s_SDE_C_RevenueFact. e. Click OK. f. Select Tasks > Create to add a session task to the workflow. g. In the Create Task dialog box, select the Session task type. h. Enter the name s_SDE_C_RevenueFact. i. Click Create. j. In the Mappings dialog box, select the SDE_C_RevenueFact mapping and click OK. k. Click Done. l. In the Workflow Designer window, drag the s_SDE_C_RevenueFact session off of the Start

    task. m. Select Tasks > Link Task, then click the Start task, and drag the link to the

    s_SDE_C_RevenueFact session task.

    6. Edit the session task properties. a. In the Workflow Designer workspace, double-click the s_SDE_C_RevenueFact session

    task. b. In the General tab, select Fail parent if this task fails and Fail parent if this task does not

    run. c. Click the Properties tab. d. For the $Source connection value attribute, click the down arrow in the Value field to open

    the Connection Browser. e. In the Connection Browser, select ETL_LAB_OLTP and click OK. f. For the $Target connection value attribute, click the down arrow in the Value field to open

    the Connection Browser.

  • Lesson 7: Working with Informatica Workflow Manager

    Oracle BI Applications 7.9: Implementation for Oracle EBS 49

    g. In the Connection Browser, select ETL_LAB_DW and click OK. Note: As you will see in subsequent practices, in a production environment you would use connection variables generated by the DAC to designate source and target connections. Because you are in a test environment, you are manually selecting the relational connections you created earlier.

    h. Click the Config Object tab of the Edit Tasks dialog box. i. In the Error handling section, for the Stop on errors attribute, enter a value of 1. j. Click the Mapping tab. k. In the left pane, select the mplt_BC_C_RevenueFact.SQ_REVN source. l. In the Connections setting in the right pane, click the down-arrow button in the Value field

    to edit the source connection. m. In the Relational Connection Browser, select ETL_LAB_OLTP, and then click OK. n. In the left pane, select the WC_RVF_FS target. o. In the Connections setting in the right pane, click the down-arrow button in the Value field

    to edit the target connection. p. In the Relational Connection Browser, select ETL_LAB_DW, and then click OK. q. In the Properties section, change the Target load type attribute from Bulk to Normal. r. In the Properties section, scroll down and select Truncate target table option. s. Click Apply. t. Click OK.

    7. Validate the workflow. a. Select Layout > Arrange > Horizontal. b. If necessary, select View > Output to view the Output window. c. Click the Validate tab of the Output window. d. Select Workflows > Validate. You should receive the message Workflow

    s_SDE_C_RevenueFact is VALID. e. If your workflow is valid, select Repository > Save. If you receive a message that the

    workflow is not valid, review the steps in this practice and try to troubleshoot. If you need assistance, ask your instructor.

    8. Before running the workflow, use SQL*Plus to query the WC_RVF_FS target table and confirm that there is no data. WC_RVF_FS is the staging table in the ETL_LAB_DW database that will be populated by running the s_SDE_C_RevenueFact workflow you just created. a. Select Start > Programs > Oracle OraDb11g_home1 > Application Development >

    SQL Plus. b. Enter ETL_LAB_DW as the username and click Enter. c. Enter ETL_LAB_DW as the password and click Enter. d. At the SQL> prompt, execute the following query:

    SELECT COUNT(*) FROM WC_RVF_FS; e. Verify that the query returns a count of zero. f. Leave SQL*Plus open.

    9. Execute the s_SDE_C_RevenueFact workflow to load the data into WC_RVF_FS. a. Return to Informatica Workflow Manager.

  • Lesson 7: Working with Informatica Workflow Manager

    50 Oracle BI Applications 7.9: Implementation for Oracle EBS

    b. In the Repository Navigator, expand CUSTOM_SDE > Workflows, right-click s_SDE_C_RevenueFact, and select Start Workflow. Informatica PowerCenter Workflow Monitor should open when you start the workflow.

    10. Monitor the progress of the workflow in Workflow Monitor. a. Monitor the progress and verify that the workflow and the session task both have a status of

    Succeeded before continuing. If the workflow returns a status of Failed, right-click the s_SDE_C_RevenueFact workflow object in Workflow Monitor, select Get Workflow Log and try to troubleshoot. If the session task returns a status of Failed, right-click the s_SDE_C_RevenueFact session task object in Workflow Monitor, select Get Task Log and try to troubleshoot. Troubleshooting may require changes to the workflow in Workflow Manager or changes to the SDE mapping in Designer. If you troubleshoot successfully, try re-running the workflow. If you need assistance, ask your instructor.

    b. When the both the workflow and session complete successfully, close Workflow Monitor, Workflow Manager, and Designer.

    11. Use SQL*Plus to query the WC_RVF_FS table to verify that the data has been loaded. a. Return to SQL*Plus, which should still be open. b. At the SQL> prompt, execute the following query:

    SELECT COUNT(*) FROM WC_RVF_FS; c. Verify that the query returns five rows of data. d. Close SQL*Plus.

  • Lesson 8: Exploring SDE and SIL Mappings

    Oracle BI Applications 7.9: Implementation for Oracle EBS 51

    Practice 8-1 Exploring a Prebuilt SDE Mapping

    Goals To explore a prebuilt source dependent extract (SDE) mapping in the Oracle Informatica repository

    Scenario The main goal of this practice is to explore the anatomy of a typical prebuilt SDE mapping in the Informatica repository. Extract mappings generally consist of a source table or business component, an expression transformation, and a staging table. Business components are packaged as mapplets, which reside in source-specific folders within the repository. Business components are used to extract data from the source system. An understanding of the anatomy of prebuilt mappings will assist you in the configuration and customization of ETL mappings. This practice explores the function and components of a typical SDE mapping. Note that individual mappings may differ substantially from the examples provided here.

    Time 1015 minutes

    Instructions:

    1. Open Informatica Repository Manager and create a new Informatica repository folder. a. Select Start > Programs > Informatica PowerCenter 8.1.1 > Client > PowerCenter

    Repository Manager. b. Double-click Oracle_BI_DW_Base. c. Enter Administrator as the username and password and click Connect. d. Select Folder > Create. e. Name the new folder Explore_SDE and click OK. f. Click OK to confirm that the folder has been successfully created. g. Select Explore_SDE in the Repository Navigator. h. Select Tools > Designer to open Designer. i. Verify that the new Explore_SDE folder is visible in the Repository Navigator in Designer. j. Close Repository Manager.

    2. Copy a mapping to the new folder. a. Verify that the Explore_SDE folder is open in Designer. The folder is open if it is bolded

    and appears as Explore_SDE (Oracle_BI_DW_Base) in the list in the upper-left corner of the Designer toolbar.

    b. Expand the Explore_SDE folder. Notice that at this point it contains empty subfolders. c. Expand SDE_ORA11510_Adaptor > Mappings. d. Select the mapping SDE_ORA_GLRevenueFact. e. Select Edit > Copy. f. Select the Explore_SDE folder. g. Select Edit > Paste.

  • Lesson 8: Exploring SDE and SIL Mappings

    52 Oracle BI Applications 7.9: Implementation for Oracle EBS

    h. Click Yes to confirm that you want to copy SDE_ORA_GLRevenueFact. You are copying this mapping to a custom folder as a precaution to ensure that you do not inadvertently make changes to the mapping in the SDE_ORA11510_Adaptor folder while you explore it.

    i. Expand Explore_SDE > Mappings and confirm that the SDE_ORA_GLRevenueFact mapping is copied to the Explore_SDE folder.

    j. Expand the subfolders under Explore_SDE and notice that all of the related repository

    objects for this mapping were also copied to the folder: sources, targets, transformations, and mapplets.

    k. Select Repository > Save.

    3. Explore the SDE_ORA_GLRevenue mapping. a. Select Tools > Mapping Designer to open Mapping Designer in the workspace. b. If necessary, expand Explore_SDE > Mappings. c. Drag SDE_ORA_GLRevenueFact into Mapping Designer. This mapping extracts revenue

    data from tables in the Oracle E-Business Suite source system and stores the data in the W_GL_REVN_FS fact staging table in the Oracle Business Analytics Warehouse.

    d. If desired, select Layout > Zoom Percent and select a percent to modify the mapping layout in the Mapping Designer workspace.

    e. Note that there are four components in the mapping and that the data flow is from left to right. The following table provides a high-level explanation of the function of each component in the mapping. You explore each component in detail later in this practice. mplt_BC_ORA_GLRevenueFact Mapplet Extracts revenue transactions from the source

    system Exp_W_GL_REVN_FS_Integration_Id Expression

    Calculates values in a single row before writing to the target

    mplt_SA_ORA_GLRevenueFact Mapplet Converts source-specific data elements into standard formats and then stores them in a staging table

    W_GL_REVN_FS Target Definition Stores revenue transactions extracted from the source system

    4. Explore the parameters and variables for the mapping.

  • Lesson 8: Exploring SDE and SIL Mappings

    Oracle BI Applications 7.9: Implementation for Oracle EBS 53

    a. Select Mappings > Parameters and Variables to open the Declare Parameters and Variables dialog box.

    b. Notice there are two parameters listed for this mapping: $$DATASOURCE_NUM_ID and $$TENANT_ID. Values for these parameters are passed by the DAC during run time. As you will see, these parameters are included in expressions for ports in the Exp_W_GL_REVN_FS_Integration_Id expression transformation.

    c. Click Cancel to close the Declare Parameters and Variables dialog box without making any changes.

    5. Explore the mplt_BC_ORA_GLRevenueFact mapplet. a. Right-click mplt_BC_ORA_GLRevenueFact and select Open Mapplet to open it in the

    Mapplet Designer. This mapplet extracts revenue data from tables in the Oracle E-Business Suite source system.

    b. If desired, select Layout > Zoom Percent and select a percent to modify the layout in the Mapplet Designer workspace.

    c. Note that there are three component types in the mapplet and that the data flow is from left to right. The three component types are: source definition, source qualifier, and mapplet output transformation.

    d. Notice that there are four source definitions for this mapplet. Recall that source definitions represent tables or files that provide source data. Source definitions are imported into the Informatica repository via the Source Analyzer. In this example, there are four tables imported from the Oracle E-Business Suite source: RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST_ALL, RA_CUSTOMER_TRX_ALL, and RA_SALESREPS_ALL.

    e. Double-click RA_CUSTOMER_TRX_ALL to open the Edit Transformations dialog box. f. Click the Ports tab. Notice that all ports are output ports, which means they pass data to the

    next object in the mapplet. Source definitions provide data, so they contain only output ports. g. Click Cancel to close the Edit Transformations dialog box. h. Double-click the SQ_GL_REVENUE_EXTRACT source qualifier to open the Edit

    Transformations dialog box. When you add a relational or a flat file source definition to a mapplet or mapping, you need to connect it to a source qualifier transformation. The source qualifier transformation represents the rows that the Informatica Integration Service reads when it runs a session. In this example, all four source definitions connect to a single source qualifier.

    i. Click the Ports tab. Notice that all ports are input/output. Input/output ports receive data and pass it unchanged.

    j. Click the Properties tab. k. For the Sql Query transformation attribute, click the down arrow in the Value field to open

    the SQL Editor to display the SQL statement that is used to retrieve the data from the sources. You can use the SQL Editor to view, modify, or validate the SQL.

    l. Scroll to the bottom of the SQL statement and notice that the SQL contains the $$LAST_EXTRACT_DATE parameter. Recall that this parameter is used to identify records that have changed since the last ETL run and that the value for this parameter is passed from the DAC during run time. (You define parameters and variables for mapplets similar to how you define them for mappings: by selecting Mapplets > Parameters and Variables to open the Declare Parameters and Variables dialog box.)

  • Lesson 8: Exploring SDE and SIL Mappings

    54 Oracle BI Applications 7.9: Implementation for Oracle EBS

    m. Click Cancel to close the SQL Editor. n. Click the Sources tab. Notice that this tab lists the source definitions associated with this

    source qualifier. o. Click Cancel to close the Edit Transformations dialog box. p. Double-click MAPO_GL_REVENUE_EXTRACT to open the Edit Transformations dialog

    box. q. Click the Ports tab. Notice that all ports are input. Input ports receive data. In this example,

    the MAPO_GL_REVENUE_EXTRACT mapplet output transformation is the target of this mapplet and receives data from the SQ_GL_REVENUE_EXTRACT source qualifier. The MAPO_GL_REVENUE_EXTRACT mapplet output transformation passes output from the mapplet to the next transformation in the mapping (Exp_W_GL_REVN_FS_Integration_Id Expression in this example).

    r. Click Cancel to close the Edit Transformations dialog box.

    6. Explore the Exp_W_GL_REVN_FS_Integration_Id expression transformation. An expression transformation is used to calculate values in a single row before writing to the target. a. Select Tools > Mapping Designer. Alternatively, you can click the Mapping Designer icon

    on the toolbar. The SDE_ORA_GLRevenueFact mapping should still be open. b. Double-click the Exp_W_GL_REVN_FS_Integration_Id expression transformation to

    open the Edit Transformations dialog box. c. Click the Ports tab. Notice that port type varies by port. While most of the ports are

    input/outpu