Oracle BI Applications 7.9: Implementation for Oracle EBS Student Guide Dss4096011 Editon 1.1 February 2010 65505 ORACLEAuthor Jim Sarokin Technical Contributors and Reviewers Dan Hilldale Mitravinda Kolachalam Manmohit Saggi Phillip Scott Kasturi Shekhar Albert Walker Jr. Publisher Jayanthy Keshavamurthy Copyright ©2010, Oracle andlor its affiliates. All rights reserved. Disclaimer ‘This document contains proprietary information and is protected by copyright and other intellectual propery laws. You may copy ane print this document solely for your ‘own use in an Orace taining course. The document may not be modified or alteree inary way, Except where your use constitutes “fa use" Under copyright law, you ‘may not use, share, download, upload, copy, prin, display. perform, reproduce, publish, ieense, post, transmit, or distribute fis document in whole orn pat without the express authorization of Oracle ‘The information contained in his document is subject to change without notice If you find any problems inthe document, lease repor them in wring to: Orace Unversity, 500 Oracie Parkway, Redwood Shores, Cafomia 84085 USA. This document isnot warranted to be evrortre. Restricted Rights Notice \( this documentation is delivered tothe United States Government or anyone using the documentation on behalf ofthe United Slates Government, the following notice is applicable U.S, GOVERNMENT RIGHTS. ‘The US. Governments rights to use, modify, reproduce, release, perform, display, or disclose these Vaining materials are restricted by the tems afte applicable Oracle license agreement andlor the applicable U.S. Gavemment contract. ‘Trademark Notice Oracle is a registered trademark of Oracle Corporation ancor its afiates. Ober ames may be vademarks oftheir espectve owners Oracle Internal & Oracle Academy Use OnlyContents 1 Course Introduction Lesson Agenda 1-2 Instructor and Class Participants 1-3 Training Site Information 4 Course Audience 1-5 Course Prerequisites 1-6 Course Goal I-7 Course Objectives I-8 Course Methodology I-98 Course Materials 1-10 Course Agenda [+11 Summary -15 1 Oracle Business Intelligence Applications Overview Objectives 1-2 The Evolving Role of Business Intelligence 1-3 Enterprise Performance Management System 1-4 Oracle BI Applications: Overview 1-5 Oracle BI Applications: Multisource Analytics 1-6 Sales Analytics 1-7 Service Analytics 1-8 Contact Center Telephony Analytics 1-9 Marketing Analytics 1-10 Supply Chain and Order Management Analytics 1-11 Financial Analytics 1-12 Human Resource Analytics 1-13 Procurement and Spend Analytics 1-15 Oracle BI Applications Components 1-16 Common Enterprise Information Model 1-17 Analytic Workflows 1-18 Speeds Time to Value and Lowers TCO 1-20 Application Integration: Security 1-21 Application Integration: Action Links 1-22 Guided Navigation 1-23 Deployment Options 1-24 Summary 1-25 2 Oracle Business Intelligence Applications Architecture Overview Objectives 2-2 Oracle BI Applications Components 2-3 Oracle BI Applications Architecture 2-5ETL Overview 2-6 Data Extraction and Load Process 2-7 Universal Business Adaptor 2-9 Data Warehouse Administration Console (DAC) 2-10 Physical Data Model: Overview 2-11 Server Repository: Overview 2-12 Metrics and Calculations 2-13 Presentation Catalog: Overview 2-14 Oracle BI Enterprise Edition Platform Architecture 2-15 Oracle BI Applications Architecture 2-16 Data Warehouse Load Process 2-17 ETL: Process Flow 2-18 DAC Architecture 2-19 Deployment Considerations 2-20 ETL Servers Component 2-21 The OBAW Database Component 2-22 ETL Repositories Component 2-23 ETL Clients Component 2-24 ETL Client Component Contents 2-25 Deployment Summary 2-26 Summary 2-27 Practice 2-1: Matching Oracle Business Analytics Warehouse Components 2-28 Practice 2-2: Locating the Oracle Business Analytics Warehouse Components 2-29 Oracle Business Analytics Warehouse Content Objectives 3-2 The Oracle Business Analytics Warehouse (OBAW) Content 3-3, Star Schema 3-4 Selected Star Schemas of the OBAW 3-5 Star Schema Example: General Ledger Revenue 3-6 OBAW Tables 3-7 Fact Tables 3-9 Types of Fact Tables 3-10 Dimension Tables 3-11 Conforming Dimension Tables 3-12 Minidimension Tables 3-13 Subset Dimension Tables 3-14 Hierarchy and Helper Tables 3-15 Staging Tables 3-17 Aggregate Tables 3-18 Internal Tables 3-19 Standardized Codes 3-20 Standardized Codes: Accounts Receivable Process Example 3-22Currency and Multitenancy Support 3-25 Summary 3-26 Installing Oracle BI Applications Objectives 4-2 Oracle Business Intelligence Applications Installation and Configuration Tasks 4-3, Verify Preinstallation Requirements 4-5 Satisfy Mandatory Preinstallation Requirements 4-6 Complete Mandatory Preinstallation Tasks 4-7 Install Oracle BI Applications Software 4-8 Install Informatica PowerCenter Software 4-9 Restore the Oracle Bl Prebuilt Repository 4-10 Copy Source Files and Lookup Files 4-11 Set Code Page Validation 4-12 Set PowerCenter Integration Services Custom Properties 4-13 Install the DAC Client 4-14 Copy Hibemate Libraries 4-15, Install JDBC Drivers 4-16 Verify DAC Connection Configuration 4-17 Enable DAC Client Communication with Informatica 4-18 PMcMD Command 4-19 Create a DAC Connection 4-20 Create the DAC Repository Schema 4-21 Import DAC Metadata 4-22 Create the Data Warehouse Tables 4-23 Configure Connection Between DAC Server and DAC Repository 4-24 Set DAC System Properties 4-25 Register the Informatica Services in the DAC 4-26 Set Physical Data Sources in the DAC 4-27 Configure Relational Connections in Informatica Workflow Manager 4-28 Oracle BI Applications Topology 4-29 Summary 4-31 Practice 4-1 Overview: Configuring the Training Environment 4-32 Understanding the ETL Process Objectives 5-2 ETL Process: Overview 5-3 ETL Process Steps 5-5 Data Extraction and Load Process: Extract 5-6 Universal Adaptors 5-7 Data Extraction and Load Process: Load 5-8ETL Mappings 5-9 Full and Incremental ETL 5-10 DAC Tasks 5-11 DAC Task Phases 5-12 Internal Tables 5-14 Change Capture 5-15 Restart Mechanisms 5-16 Unspecified Mappings 5-17 Executing ETL 5-18 ETL Process: Summary 5-19 Summary 5-20 Practice 5-1: Exploring Oracle BI ETL Metadata 5-21 Working with Informatica Designer Objectives 6-2 Informatica Designer 6-3 Informatica Designer User Interface 6-4 Key Terms 6-5 Folder 6-6 Source Definition 6-8 Target Definition 6-9 Mapping 6-10 Transformation 6-11 Transformation Type 6-12 Mapplet 6-13 Port 6-14 Port Type 6-15 Informatica Designer Tools 6-16 Source Analyzer 6-17 Example: Importing a Source Definition 6-18 Target Designer 6-19 Mapping Designer 6-20 Mapplet Designer 6-21 Linking Components 6-22 Validating Mappings 6-23 Copying Existing Objects 6-24 Saving the Repository 6-25 Summary 6-26 Practice 6-1: Working with Informatica Designer 6-27 Working with Informatica Workflow Manager Objectives 7-2 Informatica Workflow Manager 7-3 Workflow 7-4 Session 7-5Creating and Running Workflows 7-6 Connect to the Repository 7-7 Open Workflow Designer 7-8 . Create a Workflow 7-9 ‘Add a Session to the Workflow 7-10 Link Workflow Tasks 7-14 . Edit Session Properties 7-12 . Validate the Workflow 7-13, Start the Workflow 7-14 9. Monitor the Workflow 7-15 10. Check Log File 7-16 Summary 7-17 Practice 7-1: Creating and Running an Informatica Workflow 7-18 PNOaRENS Exploring SDE and SIL Mappings Objectives 8-2 Anatomy of a Typical SDE Mapping 8-3 Business Component Mapplet 8-4 Source Qualifier Transformation 8-5 Expression Transformation 8-6 Source Adapter Mapplet 8-7 Target Definition 8-8 Anatomy of a Typical SIL Mapping 8-9 SIL Source Definitions 8-10 SIL Source Qualifier 8-11 MPLT_GET_ETL_PROC_WID Mapplet 8-12 ‘Lkp_W_GL_REVN_F Lookup Procedure 8-13 Exp_W_GL_REVN_P_Update_Flg Expression 8-14 W_GL_REVN_F Filter 8-16 'y_Conversion_Rates Mapplet 8-17 EXP_Custon Expression 8-18 1 PIN_PROFL_DMapplet 8-19 RevenueFact Mapplet 8-20 |_GL_REVN_F_Ins_Upd Update Strategy 8-21 SL_REVN_F Target Definition 8-22 Unspecified Mappings 8-23 Summary 8-24 Practice 8-1 Overview: Exploring a Prebuilt SDE Mapping 8-25 Practice 8-2 Overview: Exploring a Prebuilt SIL Mapping 8-26 Working with the Data Warehouse Adm Objectives 9-2 Data Warehouse Administration Console 9-3 DAC Application-Specific Capabilities 9-4 istration Console10 DAC Features 9-5 Source System Containers 9-6 DAC Repository Objects 9-7 DAC Repository Object Hierarchy 9-9 DAC Repository Object Hierarchy with Examples 9-10 DAC Client User Interface 9-11 DAC Client Tools Menu 9-12 DAC Views 9-13 Design View: Subject Areas Tab 9-14 Design View: Tables Tab 9-15 Design View: Source System Parameters Tab 9-16 Design View: Source System Folders Tab 9-17 Design View: Tasks Tab 9-18 Design View: Source Tables Subtab 9-20 Design View: Target Tables Subtab 9-21 Design View: Phase Dependency Subtab 9-22 Setup View 9-23 Setup View: DAC System Properties Tab 9-24 Setup View: Informatica Servers Tab 9-25 Setup View: Physical Data Sources Tab 9-26 Setup View: Refresh Dates 9-27 Setup View: Email Recipients Tab 9-28 Execute View 9-29 Execute View: Execution Plans Tab 9-30 Execute View: Parameters Subtab 9-31 Execute View: Prune Days 9-32 Execute View: Current Run Tab 9-33 Execute View: Run History Tab 9-34 Execute View: Scheduler Tab 9-35 Resetting the Data Warehouse 9-36 Object Ownership in the DAC 9-37 Summary 9-38 Practice 9-1: Exploring the DAC. 9-39 Configuring Analytical Applications Objectives 10-2 Configuration Required Before a Full Load 10-3 Initial Extract Date 10-4 Global Currencies 10-5 Exchange Rate Types 10-6 Fiscal Calendars 10-7 DATASOURCE_NUM_ID 10-8 Setting General Ledger Account Hierarchies Using Flexfield Value Sets Definitions 10-9" 12 Mapping Oracle GL Natural Accounts to Group Account Numbers 10-11 Creating a New Metric Based on a New Group Account Number 10-12 Create a New Group Account Number 10-13 Duplicate an Existing Measure 10-14 Rename the Measure and Modify the Filter. 10-15 Add the Measure to the Presentation Layer 10-16 Summary 10-17 Practice 10-1 Overview: Configuring Common Areas and Dimensions Before Running a Full Load 10-18 Practice 10-2 Overview: Configuring General Ledger Account Hierarchies 10-19 Practice 10-3 Overview: Mapping Oracle GL Natural Accounts to Group Account Numbers 10-20 Practice 10-4 Overview: Creating a New Metric Based on a New Group Account Number 10-21 Customizing DAC Metadata and Running an Execution Plan Objectives 11-2 Customizing DAC Metadata and Running an Execution Plan 11-3 Creating or Copying a Source System Container 11-4 Creating a Subject Area 11-5 Assembling a Subject Area 11-6 Creating an Execution Plan 11-7 Generating Execution Plan Parameters 11-8 Building an Execution Plan 11-9 Verifying DAC Server Is Started 11-10 Running an Execution Plan 11-11 Monitoring an Execution Plan 11-12 Viewing Run History for an Execution Plan. 11-13 Viewing Predefined Reports 11-14 Verifying Data. 11-15 Summary 11-16 Practice 11-1 Overview: Customizing DAC Metadata 11-17 Customizing Oracle Business Analytics Warehouse Objectives 12-2 Customization 12-3, Customization Scenarios. 12-4 Upgrade Considerations 12-5 Type | Customization: Adding Columns to Existing Tables 12-6 Type | Customization: Extending Mappings 12-7 Type | Customization: Safe Path 12-8 Type | Customization: Extension Categories 12-9 Type | Customization: Impact of Customization on Upgrade 12-10 Type | Customization: Points to Remember 12-1113 14 Type | Customization: Typical Steps to Extend Mappings 12-12 Type Il Customization: Adding Additional Tables 12-13 Type Il Customizations: Considerations 12-14 Type Il Customization: Required Columns 12-15 Type Il Customization: DATASOURCE _NUM ID 12-16 Type Il Customization: Custom Folders 12-17 Type Il Customization: Custom Workflows 12-18 Additional Customization Considerations 12-19 Table Definitions in Oracle Format 12-20 Update Strategy 12-21 ETL Process 12-22 Truncating Target Tables 12-23 BTL_PROC_WID 12-24 DATASOURCE_NUM_1D 12-25 Creating Indices 12-26 Naming Conventions 12-27 Configuring DAC 12-28 Summary 12-29 Adding Columns to an Existing Dimension Table Objectives 13-2 Type | Customization: Adding Columns to Existing Tables 13-3, Type | Customization Scenario 13-4 Type | Customization Steps 13-5 Step 1: Creating Custom SDE and SIL Folders in Informatica 13-6 Step 2: Copying SDE and SIL Mappings and Workflows to Custom Folders 13-7 Step 3: Building Custom SDE and SIL Mappings 13-8 Step 4: Editing Workflows 13-9 Step 5: Using DAC to Add New Column Objects to Data Warehouse 13-10 Step 6: Registering Custom Folders in DAC 13-11 Step 7: Modifying Existing DAC Tasks to Use Custom Mappings and Workflows 13-12 Step 8: Creating a Custom Subject Area in DAC 13-13 Step 9: Creating and Running a Custom Execution Plan in DAC 13-14 Verifying Results 13-15 Summary 13-16 Practice 13-1: Creating a Custom SDE Mapping 13-17 Practice 13-2: Creating a Custom SIL Mapping 13-18 Practice 13-3: Adding DAC Tasks and Running Customized ETL 13-19 Adding a New Dimension in OBAW Objective 14-2 Type Il Customization: Adding Additional Tables 14-3 Type Il Customization Scenario 14-415 16 Type Il Customization Steps 14-5 Step 1: Creating and Running DDL for New Tables 14-6 Step 2: Registering New Tables in DAC 14-7 Step 3: Setting Table Properties 14-8 Step 4: Importing Table Columns 14-9 Step 5: Adding a Foreign Key Column to the Fact Table 14-10 Completing the Remaining Steps 14-11 Summary 14-12 Practice 14-1: Adding a New Dimension in OBAW 14-13 Practice 14-2: Creating an SDE Mapping to Load the Dimension Staging Table 14-14 Practice 14-3: Creating an SIL Mapping to Load the Dimension Table 14-15 Practice 14-4: Creating an SDE Mapping to Load the Fact Staging Table 14-16 Practice 14-5: Creating an SIL Mapping to Load the Fact Table 14-17 Practice 14-6: Adding DAC Tasks and Running Customized ETL 14-18 Integrating Security for Oracle Business Intelligence Applications Objectives 15-2 Oracle BI Security Options 15-3 Oracle BI Application Security 15-4 Security Manager 15-5 Synchronizing BI Server Groups 15-6 Oracle BI Presentation Services Administration Page 15-7 ‘Synchronizing Presentation Catalog Groups 15-8 Authorization 15-9 Data Security Integration 15-10 Ledger Data Security in Oracle EBS 15-11 Ledger Security in Oracle BI Applications 15-12 Ledger Security: use System Variable 15-13 Ledger Security: EBS Single Sign-On Integration Session Variable 15-14 Ledger Security: EBS Security Context Initialization Block 15-15 Ledger Security: Ledgers Initialization Block 15-16 Summary 15-17 Managing OBAW Performance Objectives 16-2 Maximizing the OBAW Performance 16-3 Common Performance Bottlenecks 16-4 Performance Overview 16-5 Informatica Server Throughput 16-6 ETL Parallel Processing 16-7 ETL Parallel Processing: Example 16-8 ETL Performance Troubleshooting 16-9 ETL Performance Leading Practices 16-10 OBAW Database Server Throughput 16-11OBAW Database: Indices 16-12 OBAW Database: Optimizer Statistics 16-13 OBAW Database: Aggregate and Subdimension Tables 16-14 Aggregate Tables: Examples 16-15 Subdimension Tables: Examples 16-16 Summary 16-17 Appendix A: Exploring the Date Dimension Date Dimension A-2 wDAY_D AS Star Schema with Date Dimension: Example A-4 Source System Parameters A-5 Considerations A-6 ademy Use Only Ci ternal & Oracle A OracCourse Introduction Copyright © 2010, Oracle andlor its alates. Al rights reserved. Oracle Internal & Oracle Academy Use OnlyLesson Agenda This lesson provides an introduction to: + Instructor and class participants + Training site information * Course: — Audience — Prerequisites — Goal — Objectives — Methodology — Materials — Agenda ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-2Instructor and Class Participants + Who are you? — Name — Company — Role + What is your prior experience? — Business intelligence — Data warehouse design — Database design + How do you expect to benefit from this course? ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-3Training Site Information ele + Bathrooms vit * Class duration and breaks Bw * Telephones Re , + Meals and i 2 refreshments = + Fire exits * Questions? } Copyright © 2010, Oracle andlor is affliates. Al rights reserved, ternal & Oracle Academy Use Only Oracle Oracle BI Applications 7.9: Implementation for Oracle EBS 1-4Course Audience This course is designed for: * Technical architects + Technical business analysts + Configurators or developers + Application administrators * Database administrators ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-5Course Prerequisites Recommended: + Working knowledge of Informatica PowerMart or PowerCenter + Basic knowledge of SQL + Domain experience in business intelligence, data warehouse design, dimensional modeling, and database design ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-6Course Goal To enable students to install, design, customize, and configure Oracle Business Intelligence (BI) Applications and Oracle Business Analytics Warehouse ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-7Course Objectives + Explore Oracle Business Intelligence Applications and the Oracle Business Analytics Warehouse (OBAW) foundational concepts and architecture. + Install and configure Oracle BI Applications + Explore the prebuilt extract, transform, and load (ETL) metadata for Oracle BI Applications + Use the Data Warehouse Administration Console (DAC) to run ETL routines to populate the OBAW * Customize DAC metadata * Customize and extend the OBAW + Manage the security and performance of Oracle BI Applications ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-8Course Methodology Subject matter is delivered by: + Lecture and slide presentations + Software demonstrations + Class discussions + Hands-on practices ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-9Course Materials * Student Guide — All slides presented during lecture — Student notes - Activity Guide — Hands-on practices and solutions ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS | - 10Course Agenda Day One: + Lesson I: Course Introduction + Lesson 1: Oracle Business Intelligence Applications Overview + Lesson 2: Oracle Business Intelligence Applications Architecture Overview + Lesson 3: Oracle Business Analytics Warehouse Content + Lesson 4: Installing Oracle Business Intelligence Applications ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-11Course Agenda Day Two: + Lesson 5: Understanding the ETL Process + Lesson 6: Working with Informatica Designer + Lesson 7: Working with Informatica Workflow Manager + Lesson 8: Exploring SDE and SIL Mappings + Lesson 9: Working with the Data Warehouse Administration Console ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS | - 12Course Agenda Day Three: + Lesson 10: Configuring Analytical Applications + Lesson 11: Customizing DAC Metadata and Running an Execution Plan + Lesson 12: Customizing the Oracle Business Analytics Warehouse + Lesson 13: Adding Columns to an Existing Dimension Table ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS | - 13Course Agenda Day Four: + Lesson 14: Adding a New Dimension in the Oracle Business Analytics Warehouse + Lesson 15: Integrating Security for Oracle Business Intelligence Applications + Lesson 16: Managing OBAW Performance ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-14Summary This lesson provided an introduction to the: + Instructor and class participants + Training site information * Course: — Audience — Prerequisites — Goal — Objectives — Methodology — Materials — Agenda ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS | - 15AluQ asp Awapeoy ajeo 9 [eWau] [92/0Oracle Business Intelligence Applications Overview ‘Copyright © 2010, Oracle andior its alate. Al rights reserved.Objectives After completing this lesson, you should be able to: + Describe Oracle Business Intelligence (Oracle Bl) Applications + Explain the key components of Oracle BI Applications + Describe Oracle BI Applications integration with transactional applications ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-2The Evolving Role of Business Intelligence From: To: Analysts Pervasive use Historical data Real-time, predictive data Fragmented view Unified, enterprise view Reporting results Insight-driven business process optimization {UUs Unified infrastructure and prebuilt Analytic tools analytic solutions ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. The Evolving Role of Business Intelligence The role of business intelligence in an enterprise is undergoing a change: + Usage is moving from a few analysts to pervasive use across many organizational functions. This is supported by the use of prebuilt applications that support multiple roles. + Data storage is moving from purely historical information to up-to-the-minute analysis, and even predictive data that allows analysis into the future + Organizations want to bring together formerly fragmented silos of information, often stored in transactional systems, into a unified enterprise view of their organization. + There is a trend toward using prebuilt BI Applications that offers packaged value instead of building individual reports on an as-needed basis using Analytics tools, Oracle BI Applications 7.9: Implementation for Oracle EBS 1-3Enterprise Performance Management System Performance Management Applications PMCs em Ll) PTT ETC eB @ WF S to OLTP&.ODS Data Warchouse _—Essbase SAP, Oracl, Siobo, Excel Business, Systoms Bata Mart PeopleSoft, Custom ccs Process Copyright © 2010, Oracle andlor its alates. Al rights reserved. Enterprise Performance Management System Oracle’s Enterprise Performance Management system is a portfolio of technology and applications that include management applications for category-leading financial performance, operational BI applications, BI foundation, and tools. It also leverages Oracle’s Fusion Middleware technologies, such as Oracle Application Server and Oracle Identity Management. The top layer is the information delivery layer. This pervasive access layer allows information to be personalized and delivered based on individual needs and roles in the organization through Web-based dashboards or Microsoft Office products. Additionally, alerts can be pushed to mobile devices to notify managers of emerging issues or growing variance: Financial Performance Management Applications are a modular suite of integrated applications that support the entire financial management cycle of goal setting, modeling, planning, monitoring, analysis, and reporting Business Intelligence Foundation is the core technology of Oracle’s EPM system. It uses a common enterprise information model as the consistent semantic layer. Fusion Middleware provides an open, comprehensive, standards-based approach for deploying service-oriented architectures (SOAs) using Web services, an enterprise service bus, and the Oracle BPEL (Business Process Execution Language) Process Manager. Its portfolio includes products for integration, business process management, business intelligence and data management, developer tools for applications, and many other components. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-4 Oracle Internal & Oracle Academy Use OnlyOracle BI Applications: Overview ‘Oracle BI Applications ORACLE, PeopleSoft > Siebel IVR, ACD, CTI oe OL = er. Ee ee ETL maps adaptors | Copyright © 2010, Oracle andlor its alates. Al rights reserved. Oracle BI Applications: Overview Oracle BI Applications is a complete, prebuilt Business Intelligence solution that both delivers intuitive, role-based intelligence for everyone in an organization, from frontline employees to senior management, and enables better decisions, actions, and business processes. Oracle BI Applications is a complete, end-to-end BI environment that includes the Oracle BI EE platform and the prepackaged analytic applications. ‘The platform includes a server and end-user tools such as dashboards, query and analysis, enterprise reporting, and disconnected access to data, all supported by a unified, model-centric server architecture. On top of this platform, Oracle BI Applications consumes transactional operational data sources via packaged extract, transform, and load (ETL) mappings, and metadata, which load a data warehouse for analysis. Analyzing the data warehouse, Oracle BI Applications delivers role- based analysis via prebuilt reports, dashboards, alerts, briefing books, and other channels provided by the platform, Oracle BI Applications 7.9: Implementation for Oracle EBS 1-5 Oracle Internal & Oracle Academy Use OnlyOracle BI Applications: Multisource Analytics Sales ST ec ee Contact Center ets co Died Pipeline ‘Chum ‘Campaign | Order Supplier Employee Analysis_| Propensity | Scorecard Linearity _| Performance Productivity Triangulated | Customer | Response ‘Orders ‘Spend | GL/Balance | Compensation Forecasting | Satisfaction Rates vs. Available Analysis Sheet Analysis] Analysis Inventory Sales Team Resolution Product | Cycle Time Analysis | Procurement Effectiveness Rates Propensity Cycle Times Customer [HR Complance| &Product | Reporting Profitability Pal Analysis | Workforce Profle Upsel) | Service Rep | Loyaltyand | Backog Analysis | inventory Etectiveness | _Alttion Availabilty Cycle Time | Service Cost | Market Basket | Fulfilment Status | Empoyee | Expense | Tumover Analysis Analysis Analysis Expenses | Management | Trends Lead | Service Trends | Campaign ROI| Customer BOM | CashFlow | Retumon Conversion Receivables _|_Anaiysis_| Analysis _| Human Capital Probuilt adaptors: CIWACLE PeopleSoft Siebel SAP Other Operational & Analytic Sources ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Multisource Analytics Oracle BI Applications covers everything in the enterprise: from demand chain—including sales, service, and marketing—to supply chain, and also the important back-office capabilities. In many cases, financial analytics combine with other applications to offer a breadth of analysis. For example, financial analytics may be combined with supply chain analytics to analyze performance with regard to procurement. Oracle BI Application families take advantage of the strengths of the Oracle BI EE platform to deliver packaged analytics content, Prebuilt ETL consumes information from multiple transactional sources—including Oracle eBusiness Suite (EBS), Peoplesoft, Siebel, SAP, and other operational systems—to deliver broad business insight into these applications. Applications include the general, role-based analytical application families as well as a number of specific, vertical applications tailored to specific industries —for example, automotive, high technology, and life sciences industries Each Oracle BI application is discussed in detail in the slides that follow. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-6Sales Analytics Improves the effectiveness of a sales organization: + Analyze pipeline opportunities to determine actions required to meet sales targets + Determine which products and customer segments generate the most revenue + Understand which competitors are faced most often and how to win against them + — Identify up-sell and cross-sell opportunities within existing accounts ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Sales Analytics Oracle Sales Analytics provides hundreds of key performance indicators and more than 130 prebuilt reports in five customizable dashboards. These analytics solutions dramatically improve the effectiveness of a sales organization by providing real-time, actionable insight into every sales opportunity at the point of customer contact. With more accurate sales forecasts and enhanced identification of potential problems and opportunities, Oracle Sales Analytics helps close business faster and increase overall sales revenue. Sales Analytics analyzes pipeline opportunities and forecasts to determine the actions required to meet sales targets. The application determines which products and customer segments generate the most revenue and how to effectively cross-sell and up-sell to them. It also evaluates which competitors are faced most often and how to win against them. Oracle Sales Analytics provides the following benefits: + Analyzing pipeline opportunities to determine actions required to meet sales targets + Determining which products and customer segments generate the most revenue + Understanding which competitors are faced most often and how to win against them + Identifying up-sell and cross-sell opportunities within existing accounts Oracle BI Applications 7.9: Implementation for Oracle EBS 1-7Service Analytics Provides a comprehensive customer service solution: * Monitor, analyze, and manage the service center based on key performance metrics * Track customer service representative performance + Provide customer service representatives a more complete view of a customer's account ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Service Analytics Oracle Service Analytics provides a comprehensive customer service solution, with hundreds of key performance indicators and more than 102 reports delivered in eight interactive dashboards. This consolidated view of customer service effectiveness leads to improved service levels while lowering service costs, and increased customer satisfaction that translates into higher revenue per customer. Oracle Service Analytics provides the following benefits: + Service Effectiveness: Monitor, analyze, and manage the service center based on key performance metrics such as service request aging and average resolution time, increasing customer satisfaction and reducing costs. + Employee Effectiveness: Understand customer service representative performance to enable improvements in employee productivity, effectiveness, training programs, and retention, + Customer Insight: Provide customer service representatives a more complete view of a customer's account, potential value, and propensity to buy more products, enabling faster resolution of issues and increased cross-selling rates. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-8Contact Center Telephony Analytics Provides the ability to analyze all aspects of contact center performance: + Optimize performance across multiple service channels to maximize service effectiveness + Optimize staffing levels for anticipated call volumes and service request types + Gain insight into how training, tenure, and rewards impact agent performance * Track and measure initial incident-to-issue resolution rates. + Maximize cross-sell and up-sell rates ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Contact Center Telephony Analytics Oracle Contact Center Telephony Analytics provides organizations with powerful insight that enables them to analyze all aspects of contact center performance. Contact Center Telephony Analytics provides more than 72 reports in five interactive dashboards with hundreds of best- practice metrics, alerts, and key performance indicators (KPIs), enabling companies to take targeted action to improve employee productivity, reduce costs, and increase customer satisfaction. Oracle Contact Center Telephony Analytics provides the following benefits + Customer Service: Optimize performance across multiple service channels to achieve greater process efficiency and maximize service effectiveness and customer satisfaction. + Agent Performance: Increase service effectiveness while minimizing costs, optimize staffing levels for anticipated call volumes and service request types, and gain insight into how training, tenure, and rewards impact agent performance. + Service and Delivery Cost: Track and measure initial incident-to-issue resolution rates, measure service costs by customer, channel, and product type to reduce overall service costs, and maximize customer satisfaction. + Contact Center Sales: Increase revenue per agent, maximize cross-sell and up-sell rates, and maximize revenue performance across customer, product, service, and regions. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-9Marketing Analytics Provides a complete, up-to-the-minute picture of customer preferences, buying behavior, and profitability: + Achieve better campaign response rates + Profile customers for more effective event-based promotion + Allocate resources more effectively by identifying what drives campaign results + Track and measure campaign effectiveness in real time + Compare individual campaign results to target metrics + Gain better insight into segmentation characteristics ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Marketing Analytics Oracle Marketing Analytics provides the ability to obtain maximum results from marketing investments by providing the entire marketing team with a complete, up-to-the-minute picture of customer preferences, buying behavior, and profitability, Oracle Marketing Analytics helps you to develop closer, more valuable customer and prospect relationships and improve marketing effectiveness. Oracle Marketing Analytics provides the following benefits: + Marketing Planning: Achieve better campaign response rates, profile customers for more effective event-based promotion, and allocate resources more effectively by identifying what drives campaign results. + Campaign Performance: Track and measure campaign effectiveness in real time, understand factors that drive campaign results and lead conversion rates, and compare individual campaign results to target metrics. + Customer Insight: Understand product affinity for targeted promotions, profile customers’ buying behavior for more effective promotions, and gain better insight into segmentation characteristics. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-10Supply Chain and Order Management Analytics Provides insight into order and inventory data so you can make better decisions in each stage of the order lifecycle: + Improve revenue recognition with faster order to booking conversion and fewer bottlenecks in the order-to-cash cycle + Improve inventory management for those products that consistently fall into backlog due to a lack of appropriate stock levels + Gain visibility into inventory activities to minimize unnecessary expenditures and optimize inventory to conserve working capital ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Supply Chain and Order Management Analytics Oracle Supply Chain and Order Management Analytics delivers deep customer insight into order and inventory data so you can make better decisions in each stage of the order lifecycle. Oracle Supply Chain and Order Management Analytics enables you to assess inventory level: determine likely product fulfillment needs before the order has been booked, quickly identify potential order backlog issues, and stay on top of critical accounts receivable (A/R) and days sales outstanding (DSO) issues. By leveraging actionable and fact-based insights, you can transform your current Supply Chain and Order Management processes to improve financial performance and customer satisfaction Oracle Supply Chain and Order Management Analytics provides the following benefits: + Better Business Performance: Improve revenue recognition with faster order to booking conversion and fewer bottlenecks in the order-to-cash cycle. + Better Order Fulfillment: Improve inventory management for those products that consistently fall into backlog due to a lack of appropriate stock levels. + Better Inventory Management: Gain visibility into inventory activities to minimize unnecessary expenditures and optimize inventory to conserve working capital Oracle BI Applications 7.9: Implementation for Oracle EBS 1-11Financial Analytics Provides the ability to improve financial performance with complete, up-to-the-minute information on expenses and revenue contributions: + Assess cash-management + Monitor operational effectiveness of the payables department to ensure the lowest transaction costs + Monitor DSOs and cash cycles to manage working capital + Manage financial performance across locations, customers, products, and territories + Identify the most profitable customers, products, and channels + Understand profitability drivers across regions, divisions, and profit centers ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Financial Analytics Understand and manage the key drivers of shareholder value and profitability, Oracle Financial Analytics helps frontline managers improve financial performance with complete, up-to-the- minute information on their department's expenses and revenue contributions, Hundreds of key performance indicators and more than 200 reports enable financial managers to improve cash flow, lower costs, and increase profitability while maintaining more accurate, timely, and transparent financial reporting that helps ensure Sarbanes-Oxley compliance, Oracle Financial Analytics provides the following benefits + Payables: Assess cash-management and monitor operational effectiveness of the payables department to ensure the lowest transaction costs. + Receivables: Monitor DSOs and cash cycles to manage working capital, manage collections, and control receivables risk. + General Ledger: Manage financial performance across locations, customers, products, and territories, and receive real-time alerts on events that may impact the financial condition. + Profitability: Identify most profitable customers, products, and channels, and understand profitability drivers across regions, divisions, and profit centers. Oracle BI Applications 7.9: Implementation for Oracle EBS 1 - 12Human Resource Analytics Provides the ability to improve overall workforce performance and managerial effectiveness: + Understand how compensation impacts performance + Align incentive compensation with objectives and company goals + Assess HR performance against recruitment and retention goals + Understand drivers of employee turnover + Reduce time and cost of compliance reporting ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Human Resource Analytics Oracle Human Resources Analytics helps organizations improve overall workforce performance and managerial effectiveness while reducing costs. With numerous key performance indicators, more than 85 reports, and four dashboards, Oracle Human Resources Analytics provides human resources (HR) professionals and frontline managers with the tools to gain up-to-the-minute insight into productivity levels across an organization. The resulting benefits help reduce workforce costs, increase employee productivity, effectively manage employee compensation, improve retention, and reduce voluntary turnover. Oracle Human Resources Analytics provides the following benefits: + Compensation: Understand how compensation impacts performance, ensure compensation is equitable and consistent across roles, and align incentive compensation with objectives and company goals. + HR Performance: Assess HR performance against recruitment and retention goals, monitor and improve employee productivity, and assess compensation competitiveness to attract top talent. + Retention: Understand drivers of employee tumover, proactively identify top performers who are likely to be recruited by competitors, and reduce recruiting and involuntary termination costs. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-13Human Resource Analytics (continued) + Workforce Profile and Compliance: Reduce time and cost of compliance reporting, increase employce satisfaction and retention, and manage overall profile and background of workforce. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-14Procurement and Spend Analytics Provides the ability to optimize supply-side performance by integrating data from across the enterprise value chain: + Gain detailed visibility into direct and indirect spending + Identify opportunities to consolidate spending and reduce costs + Monitor price, delivery, and product quality to determine best- and worst-performing suppliers ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Procurement and Spend Analytics Oracle Procurement & Spend Analytics provides the ability to optimize supply-side performance by integrating data from across the enterprise value chain and enables executives, managers, and frontline employees to make more informed decisions, Oracle Procurement and Spend Analytics increases visibility into the complete procure-to-pay process, including comprehensive spend- and-procurement analysis, supplier performance analysis, and supplier payables analysis. Through complete end-to-end insight into the factors that impact company performance, you can significantly reduce costs, enhance profitability, increase customer satisfaction, and gain competitive advantage, Oracle Procurement and Spend Analytics provides the following benefits: + Improved Procurement and Spend: Gain detailed visibility into direct and indirect spending, and identify opportunities to consolidate spending and reduce costs. + Better Supplier Performance: Monitor price, delivery, and product quality to determine best- and worst-performing suppliers Oracle BI Applications 7.9: Implementation for Oracle EBS 1-15Oracle BI Applications Components Oracle BI Applications includes four key components: + Prebuilt data warehouse with conforming dimensions + Prebuilt ETL to extract data from Oracle and non-Oracle sources + Premapped metadata embedding best practices for metrics and KPIs + Best practice library of dashboards and reports ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. BI Application Components Oracle BI Applications includes the same four key components A prebuilt data warehouse data model that is optimized for the various supported databases, This data model incorporates the best practices that have been used in BI, decision support, and data warehousing. For example, there are more than 15 star schemas designed for analysis and reporting on Financial Analytics Prebuilt ETL logic that extracts and transforms data using a source-specific understanding of the supported transactional system before loading it into the data warehouse data model. The prebuilt ETL extracts data from over 3,000 operational tables and loads it into the data warehouse, sourced from SAP, Peoplesoft, Siebel, Oracle E-Business Suite, and other sources. Premapped metadata, which connects the physical data sources, provides logical models defining all the key performance indicators (KPI) and metrics, and finally defines the presentation of data in a role-based way to the users of the system. For example, there are different prebuilt presentations for roles such as Finance Managers, Procurement Managers, Call Center Agents, Sales Representatives, and so on, A library of metrics, reports, and alerts that are embedded in Interactive Dashboards and presented to users on the basis of individual roles, such as CFO, Finance Controller, Financial Analyst, AR/AP Managers, and Executives, Oracle BI Applications 7.9: Implementation for Oracle EBS 1-16Common Enterprise Information Model Unified metadata model provides consistent information across the enterprise PRESENTATION LAYER |< _ Role-based views of the information relevant to users. ear role rfarances 1S [: Simplified vow « fegleel SL nertace ‘SEMANTIC OBJECT LAYER 4 Consistent definition of business measures, metrics, and calculations + Dimensions + Hierarchies |: Measures + Calculations + Aggregation Rules + Time Series PHYSICAL LAYER ~\ Model once, deploy everywhere Te —_- a. "Bhs ~ Ross any dt sources ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Common Enterprise Information Model Oracle BI Applications is built on the Oracle Business Intelligence Foundation, At the heart of the Oracle Business Intelligence Foundation is a key technology differentiator for Oracle—the Common Enterprise Information Model. This is a unified metadata model, which is accessed by all the end user tools, so every end user and every department across the enterprise has the same consistent view of information, tailored to their role. As a result, organizations no longer need to maintain multiple metadata environments for different types of users. Oracle provides the ability to “model once, deploy everywhere.” The metadata model consists of three tiers: + The physical layer enables you to import the table structures of your existing data sources. + The semantic layer enables you to create a simplified representation of multiple data sources, creating a logical model of your business in ways your managers think about it dimensions, hierarchies, and metric: + The presentation layer further simplifies this model making the data appear to end users as a single data source with a single table structure of dimensions, measures, and derived measures, This common enterprise information model enables you to define key metries and calculations in one place, assuring that everyone has a consistent view of information (tailored to their role) and assuring alignment across departments. Oracle BI Applications 7.9: Implementation for Oracle EBS 1 - 17Analytic Workflows Business Function: Receivables Who are the Customers Role: and Covectors? Director, Credits and Collections Drillto . Objects 1) Maximize Cash Flow. 2) Control Recei Portfolio, Copyright © 2010, Oracle andlor its alates. Al rights reserved. Analytic Workflows Analytic workflows are built around standard paths of discovery for business issues. In this example, a Director of Credits and Collections in the Receivables function of Finance and Accounting is monitoring the “Maximize Cash Flow” objective. This objective is composed of several key questions and KPIs around Days Sales Outstanding (DSO), Days Payable Outstanding (DPO), and others. Each one of these subsequently leads to more questions about the core components of the KPI—for example, DSO being on target requires overdue balances to be on target, customers to be paying in line with their terms, and so on. These workflows are supported in Oracle BI Applications as standard exploration paths. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-18 Oracle Internal & Oracle Academy Use OnlyAnalytic Workflows ‘Ak Omens = __}pritl to Detail Who are the Customers? Drillto Overdue Invoice Detail Linc sou ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Analytic Workflows (continued) Continuing with the example from the previous slide, following one branch of the “Maximize Cash Flow” analytic workflow, each part of the flow is supported by prebuilt reports and navigation that allow users to easily drill down to further levels of detail as required. Because the application and the supporting data warehouse model, and ETL are built to capture information at the transaction-line level, users can easily drill down from the summary information to the most atomic level of information. Ultimately this allows the user to not only monitor progress on an objective, but also to easily navigate to the right information, so that in the end any required corrective action can be proactively taken. Notice, for example, that in the “Take Action” area of the workflow, the user is drilling down from the BI Application’s transactional invoice level report back to the originating transactional application to take action in the operational system. Oracle BI Applications 7.9: Implementation for Oracle EBS 1-19 ademy Use Only Ci transactional while maintaining e Data Warahouse! e sume content 6 Direct Alerts 2 ccess]| _Loed Process + Scheduled and Coneitonal Bots & Highlighting 3 Source ng Area aie aa + Conditional highighting that > Extraction Process provides context on matics (sit E {00d or bad?) 5 + FE sg Gs Ey Gi Bi me 2 8 Oracle SAPRIO. Sicbel PSFT EDW gif py < Federated Data Sources _" Stner 2 o © Copyright ©2010, Oracle andlor ts affliates. Allights reserved. 6 & Presentation Catalog: Overview ~ Oracle BI Applications delivers role-based Interactive Dashboards supporting organizational 5 roles spanning from executives to line managers and individual contributors. Included in the dashboards, which contain tabular as well as graphical interactive elements and reports, are analytic workflows and guided analytics that help to drive critical business decisions and insight. ‘Action Links, as described in the lesson titled “Oracle Business Intelligence Application Overview,” can drive the user from analytical reports and dashboards back to the transactional application in context to take action on the results of their analysis. Alerts and conditional highlighting provide ways to alert users to business-critical conditions, good and bad, and drive insight and action. Orac Oracle BI Applications 7.9: Implementation for Oracle EBS 2-14Oracle BI Enterprise Edition Platform Architecture Does not include the OBAW or [cient] BI Applications Return results Copyright © 2010, Oracle andlor its alates. Al rights reserved. Oracle BI Enterprise Edition Platform Architecture The diagram in the slide represents the logical relationship between the components of Oracle BI Enterprise Edition (EE). The physical architecture may vary, but a typical instance is described in this lesson. This logical architecture does not account for all utilities required to administer and extend the data warehouse. Oracle BI EE is offered in two major architecture options: Oracle Business Intelligence Platform and Oracle Business Intelligence Applications. Oracle Business Intelligence Platform provides the following: An infrastructure to model data so that users can understand it A server to generate SQL and access, merge, and sort data from multiple sources A simple, highly interactive, Web-based analysis tool, and the ability to construct dynamic reports and alerts Oracle BI Applications 7.9: Implementation for Oracle EBS 2-15 Oracle Internal & Oracle Academy Use OnlyOracle BI Applications Architecture Includes infrastructure components and the following: + The OBAW and ETL components to load it + Informatica, DAC, and BI server metadata [cum] Return Analytics Transactional database Read Copyright © 2010, Oracle andlor its alates. Al rights reserved. Oracle BI Applications Architecture The diagram in the slide represents the logical relationship between the components of Oracle BI Applications. The physical architecture may vary, but a typical instance is described in this module. This logical architecture does not account for all utilities required to administer and extend the data warehouse. Oracle BI Applications provides all that the platform does, plus: + Prebuilt Oracle BI repository containing all the mappings, logic, metrics, and KPIs required for the deployed applications + Prebuilt Presentation catalog with role-based Interactive Dashboards and reports to support the needs of line managers to chief executive officers + Prebuilt OBAW database designed for analytical processing with prebuilt routines to extract, load, and transform data from transactional databases, and the DAC components and a repository used to configure and execute the ETL process Oracle BI Applications 7.9: Implementation for Oracle EBS 2-16 Oracle Internal & Oracle Academy Use OnlyData Warehouse Load Process + The DAC generates a metadata-driven ETL plan and executes ETL tasks. Informatica Integration Services performs ETL using source-to- target mappings and transformations. — Extraction: Sources are transactional databases. — Transformation: Cleansing, translations, aggregation (facts) — Load: Target is the OBAW star schemas. DAC repository |**| DAC server t Informatica Integration |_Load Services ,x — = [een] Workflow Informatica repository DAC client Transactional database ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Data Warehouse Load Process The Informatica repository is a small relational database containing metadata necessary for ETL processing, The DAC repository stores metadata about the ETL process, including source and target information, Informatica and other ETL tasks, warehouse and source tables, and other information, All Informatica mappings and workflows are stored in the Informatica repository. Metadata about these mappings are stored in the DAC repository for use by the DAC server in issuing ETL requests to Informatica Integration Services. ETL Tasks ‘A majority of the tasks are of the Informatica type, in which case the DAC server communicates with Informatica Integration Services. Oracle BI Applications 7.9: Implementation for Oracle EBS 2-17ETL: Process Flow + Administrator initiates ETL in the DAC client, + The DAC server issues ETL tasks. = Informatica ETL tasks are issued against Informatica Integration Services. + Informatica Integration Services accesses workflows in the Informatica repository. + Informatica Integration Services processes the workflows + Data is extracted from the transactional databases. + Data is transformed and then loaded into the OBAW. > 3 Metadata about ETL © processing, source and target | Gnformath 28 tables Integration ~ Services — (ETL) G Transactional LEN So B database < 2 o © Copyright ©2010, Oracle andlor ts affliates. Allights reserved. 6 & ETL: Process Flow 3 Extraction: Source Dependent Extract (SDE) routines extract data. Ee Transformation and Load: Source Independent Load (SIL) routines transform and load data. into star schemas within the OBAW. Oracle BI Applications 7.9: Implementation for Oracle EBS 2-18DAC Architecture Informatica client DAC client Client tier pec Informatica pac repository TOPIP. repository _ > 3 Information onc ewe ° Server tier pare ‘ 3s Native DB | JDBC = libraries > 3 3 Database tier g 2 3 gs Copyrgn'© 2010, Orel andlor ts anes AI gh reserved 5 DAC Architecture 3 The DAC client is a command and control interface for the data warehouse to allow for the 5 setup, configuration, administration, and monitoring of data warehouse processes. The DAC Server executes instructions from the DAC client and manages data warehouse processes, including scheduling, loading of the ETL, and configuring the subject areas to be loaded. It dynamically adjusts its actions based on information in the DAC repository. The DAC Server issues its ETL commands against Informatica Integration Services, which in tum accesses the Informatica repository for workflow metadata. Informatica client utilities are used to configure and customize the Informatica repository metadata, and are covered in later lessons, JDBC drivers are required for DAC database connectivity. You must install the appropriate JDBC driver in the DAC\1ib directory to enable DAC database connectivity. Installation is covered in detail in the lesson titled “Installing Oracle BI Applications.” The DAC is covered in detail in the lesson titled “Working with Data Warehouse Administration Console.” Oracle BI Applications 7.9: Implementation for Oracle EBS 2-19Deployment Considerations To maximize ETL performance, it is recommended that four component machines are set up. + These are in addition to any transactional databases. — ——=, — i ETL clients Copyright © 2010, Oracle andlor its alates. Al rights reserved. Deployment Considerations The above represents a recommended physical deployment of the architecture, ETL Repositories Depending on performance and requirements, the components of ETL repositories can also reside on the same component machine as the OBAW database. Oracle BI Applications 7.9: Implementation for Oracle EBS 2 - 20 Oracle Internal & Oracle Academy Use OnlyETL Servers Component + Supports the ETL process * Contains: — DAC server: Organizes ETL tasks for processing — Informatica Integration Services: Processes ETL — Informatica Repository Service: Accepts connections to the Informatica repository from Informatica servers and clients _— [= | =] __ Copyright © 2010, Oracle andlor its alates. Al rights reserved. ETL Servers Component All servers used in the ETL process reside on this machine. These include the DAC server, Informatica Integration Services, and the Informatica Repository Service Informatica Integration Services Informatica Integration Services is the third-party software used to populate the OBAW from the source transactional database using ETL routines. You can also install Informatica Integration Services on other machines to increase performance. The other ETL servers can also be hosted on other machines. Oracle BI Applications 7.9: Implementation for Oracle EBS 2-21 Oracle Internal & Oracle Academy Use OnlyThe OBAW Database Component * Contains the OBAW database + Stores the data accessed from the Oracle BI client + Is a database instance whose requirements are entirely dependent on your usage and performance requirements — Aunique database instance allows instantiation of optimized parameters [| =| =] — Copyright © 2010, Oracle andlor its alates. Al rights reserved. The OBAW Database Component Single Database These components are all part of the OBAW and are contained in a single database. It is recommended that the OBAW Database machine should be a dedicated machine with its own instance of a supported RDBMS platform. Supported Platforms Supported RDBMS platforms include: + Oracle + IBM DB2 Universal Server + Microsoft SQL Server + Teradata Oracle BI Applications 7.9: Implementation for Oracle EBS 2 - 22 Oracle Internal & Oracle Academy Use OnlyETL Repositories Component + Supports ETL processing + Isa database instance whose requirements are entirely dependent on your usage and performance requirements = Aunique database instance allows instantiation of optimized parameters + Contains: — The Informatica repository: Stores mappings and workflows specifying data transformation and flow used by Informatica Integration Services in ETL processing — The DAC repository: Is unique to each database warehouse, stores metadata representing warehouse objects and processes, and is used by the DAC client and server to configure and schedule ETL execution plans ETL servers ETL nts, Copyright © 2010, Oracle andlor its alates. Al rights reserved. ETL Repositories Component The Informatica and DAC repositories store metadata information about the source and target databases, mappings that dictate data flow, and information about processing performed by the DAC and Informatica Integration Services. Although the OBAW database and the repository databases can exist on one machine, you should separate the repositories onto their own machines, or at least into different databases or schemas on the same machine to maintain the integrity of data. Mappings ‘They provide a set of instructions for retrieving data, performing computations, and loading data. Oracle BI Applications 7.9: Implementation for Oracle EBS 2 - 23 Oracle Internal & Oracle Academy Use OnlyETL Clients Component Contains the clients used to create and administer the OBAW, the DAC repository, and the Informatica repository * DAC client: — Used to run, configure, and customize the OBAW ETL objects and processes + Informatica clients: — Used to configure and customize the Informatica repository [| = | =] — Copyright © 2010, Oracle andlor its alates. Al rights reserved. ETL Clients Component This machine is used to manage and extend the Informatica repository and to administer ETL. The DAC client is used to run, schedule, and configure the ETL execution. Oracle BI Applications 7.9: Implementation for Oracle EBS 2-24 Oracle Internal & Oracle Academy Use OnlyETL Client Component Contents DAC client: — ls used to schedule, monitor, configure, and customize the OBAW ETL — Accesses metadata about ETL mappings, dependencies, and tables in the DAC repository Informatica Workflow Manager and Designer: — Is.used to customize and test mappings, workflows, and other objects in the Informatica repository Informatica Repository Manager: — ls used to administer the Informatica repository Informatica Repository Service Administration Console: — ls used to administer the Repository Service ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 2 - 25Deployment Summary Recommended configuration for the OBAW components: ETL clients DAC and Informatica clients Copyright © 2010, Oracle andlor its alates. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 2-26 Oracle Internal & Oracle Academy Use OnlySummary In this lesson, you should have learned how to: + Describe the Oracle Business Intelligence Applications logical architecture + Explain the process flow of building the data warehouse + Employ the recommended deployment options to maximize data warehouse performance + List the components supporting the Oracle Business Analytics Warehouse and the functions performed by each core component ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 2 - 27Practice 2-1: Matching Oracle Business Analytics Warehouse Components This practice covers matching definitions with their corresponding components. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Practice 2-1: Matching Oracle Business Analytics Warehouse Components In this practice, you match the core OBAW components with their corresponding functions Oracle BI Applications 7.9: Implementation for Oracle EBS 2 - 28Practice 2-2: Locating the Oracle Business Analytics Warehouse Components This practice covers matching components with their setup locations. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Practice 2-2: Locating the Oracle Business Analytics Warehouse Components In this practice, you determine the recommended location for each core component of the OBAW, Oracle BI Applications 7.9: Implementation for Oracle EBS 2 - 29AluQ asp Awapeoy ajeo 9 [eWau] [92/0Oracle Business Analytics Warehouse Content ‘Copyright © 2010, Oracle andior its alate. Al rights reserved.Objectives After completing this lesson, you should be able to: + Describe the contents of the Oracle Business Analytics Warehouse + Explain the warehouse tables ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 3-2The Oracle Business Analytics Warehouse (OBAW) Content + Data stored in prebuilt star schemas + Supporting tables used for staging and processing ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 3-3Star Schema + Is adenormalized format that is more effective for query processing + Is populated by ETL processes * Is composed of: — One fact table — Aset of dimension tables — The joins that relate the dimension tables to the fact table ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Star Schema The OBAW data model was designed using dimensional modeling techniques to support the analysis requirement of Oracle Business Intelligence (BI) Applications. Because complex queries run slowly on transactional databases, the database requirements for Oracle BI are different from those of transactional applications. In Oracle BI, you modify data much less frequently than in transactional systems, but you need quick results when viewing new analyses, drilling down to detailed charts and graphs, and creating new briefings. The star schema is optimized for these uses. Oracle BI Applications 7.9: Implementation for Oracle EBS 3-4Selected Star Schemas of the OBAW Sates [Cal Center + Opportunies + ACD Events + Customer + Quotes + Rep Activities + Products + Pipeline + Contact-Rep Snapshot + Suppliers Jocder Management + Targets and Benchmark + Cost Centers + Sales Order Lines + IVR Navigation History + Profit Centers + Sales Schedule Lines [service + Internal Organizations + Bookings + Service Requests + Customer Locations. + Piek Lines + Activities + Customer Contacts + Billings + Agreements + GL Accounts + Backiogs IWorktorce + Employee Marketing + Compensation + Sales Reps + Campaigns + Employee Profle + Service Reps + Responses + Employee Events + Partners + Marketing Costs JPharma + Campaign [Supply Chain + Prescriptions + Offers + Purchase Order Lines + Syndicated Market Data + Purchase Requisition Lines | JFinancials + Purcnase Order Receipts | |» Financial Assets + ventory Balance + Insurance Claims + Inventory Transactions JPubiic Sector Finance + Benefits + Receivables + Cases + Payables + Incidents + General Ledger + Leads + Goes ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Selected Star Schemas Oracle BI Applications offers a breadth of analysis, spanning sales, service, and marketing to back-office functions, and include several verticalized areas. To meet the analytical requirements, the OBAW contains a number of horizontal as well as vertical star schemas, shown in the slide. This is just a sample of the total number of star schemas available. For example, in the pharmaceutical industry, specific star schemas are included to store information about prescriptions and industry syndicated market data. The star schemas listed in the slide can be deployed in the OBAW depending on the applications that are selected, and the use of conforming dimensions allows consistent analysis across different subject areas, applications, and areas of analysis. Conforming dimensions are discussed in detail later in the lesson. Oracle BI Applications 7.9: Implementation for Oracle EBS 3-5Star Schema Example: General Ledger Revenue W_GL_REVN_F stores all the revenue transaction amounts in document and local currency and maintains three global currency exchange rates. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 3-6OBAW Tables * Fact tables + Dimension tables * Minidimension tables * Subset dimension tables + Hierarchy and helper tables + Staging tables + Aggregate tables * Extension tables + Internal tables ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 3-7OBAW Tables + Staging tables + Aggregate tables * Extension tables + Internal tables ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 3-8Fact Tables + Are central tables in star schemas * Typically contain numeric measurements * Can be aggregated — Examples: Revenue and units + Also store the most atomic transactional grain = Allows drilling to transactional details during analysis + Are surrounded by dimension tables — Each dimension table related to the fact table by a single join + Are identified with the suffix _F ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Fact Tables Ina star schema, the central table is a fact table, It usually contains numeric measurements and has multiple joins to dimension tables surrounding it. Dimension tables are related to the fact table by a single join. Oracle BI Applications 7.9: Implementation for Oracle EBS 3-9Types of Fact Tables All base facts are based on a single business function—for example, Sales Order Lines, Sales Cycle Lines, and so on. Types of fact tables + Transactional — Mirror of transactional data from the source — Lowest atomic grain of each transactional record — Examples: Order Lines Fact, Account Receivable Transactions + Snapshot — Snapshot of balances across time = Examples: Inventory and Account Balances, Accounts Receivable and Accounts Payable aging snapshots, and Opportunity Pipeline + Cycle Lines = Derived from multiple fact tables, typically store process cycle times = Sales Order Cycle Lines, Purchase Cycle Lines + State Transition — Required for specialized transition count metrics, - a State transitions (# New, # Inactive, # Dormant customers, and so on + Aggregate — Performance enhancement on key metrics ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Types of Fact Tables Transactional fact tables provide the lowest granularity of transactional information available in the source transactional system and can be thought of as mirroring the transactional data from the source. Snapshot fact tables store totals—for example, theinventory and account balance for a specific point in time. Cycle Lines fact tables provide time-series aggregations—for example, storing the amount of time that passed between different stages in a sales cycle. State Transition fact tables store specialized transition count metri segmentation. that are used in customer Aggregate fact tables aggregate detail data at one or more higher levels to aid in query performance. Oracle BI Applications 7.9: Implementation for Oracle EBS 3 - 10Dimension Tables + Store descriptions of the characteristics of a business * Contain fewer records with many columns + Are identified with the suffix _D + Have columns that represent attributes of the dimension + Have a single primary key joined to the fact table — Unique numeric key (ROW_WID) for each dimension table is generated during the load process — Key is used to: — Join each dimension table with its corresponding fact tables Join the dimension with any associated hierarchy or extension table + Examples: Date, account, and product ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Dimension Tables The dimension tables in a star schema store descriptions of the characteristics of a business. A dimension is descriptive information that qualifies a fact. For example, each record in a product dimension represents a specific product. Typically, dimension tables are wide and short because they contain fewer records with many columns. The columns of a dimension table are also called attributes of the dimension, Each dimension table in a star schema has a single primary key joined to the fact table, Oracle BI Applications 7.9: Implementation for Oracle EBS 3-11Conforming Dimension Tables + Are common dimension tables shared by fact tables + Enable cross-fact analysis + Are used by the OBAW + Ensure a consistent view across the OBAW — Provides enterprisewide business analysis ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Conforming Dimensions Conforming dimension tables are shared by multiple fact tables allowing consistent analys across multiple star schemas, > 3 % 8 a > E 5 3 S : \OracleBI\) ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Install Oracle BI Applications Software The Oracle Business Intelligence Applications installer runs on Windows and requires the Oracle Business Intelligence infrastructure to be installed. When you run the Oracle Business Intelligence Applications Installation Wizard, the Oracle Business Intelligence Applications files are installed in the existing Oracle Business Intelligence infrastructure directory (for example, : \OracleBI\). If you have a previous version of Oracle Business Intelligen: Applications installed, you must uninstall this version before you run the installer for Oracle Business Intelligence Applications Version 7.9.5. If you do not uninstall the old version, some Version 7.9.5 directories will not be correctly installed. Be sure to make a backup of your RPD, presentation catalog, and DAC and dwrep directories before you uninstall the old version. Oracle BI Applications 7.9: Implementation for Oracle EBS 4-8Install Informatica PowerCenter Software + Install Informatica PowerCenter Client Tools. — It must be installed on Windows. — Oracle recommends that you co-locate the DAC client with the PowerCenter Client Tools. + Install Informatica PowerCenter Services. — Itcan be installed on UNIX or on Windows. — Oracle recommends that you co-locate the PowerCenter Services with the DAC Server. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Install Informatica PowerCenter Services Software Follow the installation wizards to install the Informatica PowerCenter software. Informatica PowerCenter Client Tools must be installed on Windows, and you must install the SP4 patch, Informatica PowerCenter Client Tools consists of Workflow Manager, which is used to customize mappings, workflows, and other objects in the Informatica repository; Repository Manager, which is used to restore and manage the Informatica repository; and Designer, which is used to configure and update mapplets, mappings, transformations, and other metadata. You will learn more about Informatica Client Tools in the lessons titled “Working with Informatica Designer” and “Working with Informatica Workflow Manager.” Informatica PowerCenter Services can be installed on Windows or Unix and must include the SP4 patch for Oracle BI Applications 7.9. Informatica PowerCenter 8.1.1 has significant architecture changes from previous versions. Before installing Oracle Business Intelligence Applications, Oracle recommends that you read the Informatica PowerCenter documentation to familiarize yourself with the new architecture, components and features. Informatica PowerCenter 8.1.1 SP 4 documentation is included on the Informatica PowerCenter DVD provided with Oracle Business Intelligence Applications. Oracle recommends that you install Informatica PowerCenter Client Tools on the same machine as the DAC client, and install Informatica PowerCenter Services on the same machine as the DAC Serv Oracle BI Applications 7.9: Implementation for Oracle EBS 4-9Restore the Oracle BI Prebuilt Repository + Copy the file Oracle_BI_DW_Base.rep from the OracleBI\dwrep\Informatica\Repository directory to the \InformaticaPowerCenter8.1.1\server\infa_sh ared\Backup directory. + Use the Restore option in the Informatica PowerCenter Administration Console to load the prebuilt > Oracle _BI_DW_Base repository. Oo ne oe o 8 5 Rectare contents for Oracle #1 DW s2ce ca 2 Seloctbadeup fle = elec Bacup fet evra vapothory contents o [[Gracte 81 OW Bace.rop 1 3 ° § Pastors az new z 2 3° s Copyright © 2010, Oracle andlor ts afates, lights reserved, 5 os Restore the Oracle BI Prebuilt Repository a An Informatica repository file named Oracle _BI_DW_Base. rep is installed into the £ OracleBI\dwrep\Informatica\Repository directory during the Oracle Business 2 Intelligence Applications installation. You use the Restore option in Informatica PowerCenter Administration Console to load this prebuilt Oracle_BI_DW_Base repository. To load the prebuilt Oracle _BI_DW_Base.. rep repository into Informatica: 1. Copy the file Oracle _BT_DW_Base. rep from the OracleBI\dwrep\ Informat ica\Repository directory on the machine where the Oracle Business Intelligence Applications installer was run to the following folder on the machine where Informatica PowerCenter Services has been installed: on Windows, to the \Informatica PowerCenter8.1.1\server\infa_shared\Backup directory; on UNIX or Linux, to the $Informatica/PowerCenter8.1.1/server/infa_shared/Backup directory. 2. In the Informatica PowerCenter Administration Console, select the Repository Service that was created during the installation process (for example, Oracle_BI_DW_Base), and restore the contents, Detailed steps are provided in the practice for this lesson Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 10Copy Source Files and Lookup Files Copy source files and lookup files from the Oracle Business Intelligence Applications installation directory to the Informatica directory on the Informatica PowerCenter Services machine. pies: (Ecnoansnorcintawseavcnis [Bc yremicvorcatees isenetnia sacs! Ore martina eer Ghee roenre repeats sea Bact stanus.cy acer stamus.cov arene Shei pete er rnc te ceo > Bl awctcatcrivanatten ov ee ey goo ents 5 © jas | chorsanameanicnarauene |e! adins [Ea Giromntaponari | aera LORE 8 vane awe 2 feces apa ac Bos) Shersraniaerg Bavtpe Bethe aap > Ssroices foe esis oa og Socruict ee penne beatae co pale = Esonanaine orton cote pecs ShmrvaerErebentpeso conc 5 Bhsransiec top tore ne pote 8 ‘Eisner nee. DiS el S Aponte tye ne cowie py 8 Micra nsec alc z Sonos nase 2 3° s Copyright © 2010, Oracle andlor ts afates, lights reserved, 5 os Copy Source Files and Lookup Files a You need to copy source files and lookup files from the Oracle Business £ Intelligence Applications installation directory to the Informatica 2 directory on the Informatica PowerCenter Services machine. To copy source files and lookup files on Windows: 1. Copy the source files in \OracleBI\dwrep\Informatica\SrcFiles to g \Informatica PowerCenter8.1.1\server\infa_shared\SrcFileson O the Informatica PowerCenter Services machine. 2. Copy the lookup files in \Oracl eBI\dwrep\Informatica\LkpFiles to Informatica PowerCenter8.1.1\server\infa_shared\LkpFiles on the Informatica PowerCenter Services machine. Oracle BI Applications 7.9: Implementation for Oracle EBS 4-11Set Code Page Validation Configure code page validation for Informatica PowerCenter Integration Services. ee Fie ES Forma: ow “Hep File reader buffered records max target tales ins session max writer buters-100 OM shared memory. Configuration Properties > Edit, and change the value for the ValidateDataCodePages property from Yes to No, The data code page is disabled here because the code page is identical for both the source and target databases. It is not necessary to validate the code page when data is moved between the compatible source and the target databases. Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 12Set PowerCenter Integration Services Custom Properties Log in to the PowerCenter Administration Console and create and set custom properties for PowerCenter Integration Services as needed. custom Propartion oe ree a [overademonvenvnneapver ] SSS P romove | [siebeltnicodane [bispesGorcl chantgorl a [a | ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Set PowerCenter Integration Services Custom Properties Log in to the PowerCenter Administration Console and create and set custom properties as, needed. For each custom property, add a new custom property with an appropriate value, Internal & Oracle Academy Use Only Examples: Create a custom property named ServerPort with a value of an available port number to configure Informatica PowerCenter Services to listen on that port number. The DAC communicates with the PowerCenter Integration Services service using this port. Create a custom property named SiebelUnicodeDB and set OLTP (biapps@orcl) and OLAP (obaw@orel) values for SiebelUnicodeDB if your data movement is from Unicode to Unicode. 8 3° Oracle BI Applications 7.9: Implementation for Oracle EBS 4-13Install the DAC Client The DAC client is installed by the Oracle Business Intelligence Applications installer. + Runs only on a Windows platform + Should be installed on the same machine that runs Informatica PowerCenter Client tools ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Install the DAC Client The DAC client is installed by the Oracle Business Intelligence Applications installer. The DAC client only runs on a Windows platform. Oracle recommends that you run the DAC client on the ‘Windows machine that runs the Informatica PowerCenter Client tools. Oracle BI Applications 7.9: Implementation for Oracle EBS 4-14Copy Hibernate Libraries Copy Hibernate libraries to the appropriate DAC directories. Files Copy from Copy ta ‘jar hibernate-3.2\lib DAC hibernate3,jar hibernate 3.2 DAC\lib hibemate.configur ion-3.0.dtd |\hibernate.3.2\src\org hibernate \DAC hibemate-mapping3.0.dtd__|\hibernate.3.2'srciorg\hibernate DAC ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Copy Hibernate Libraries 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 Core Package 3.2 are now generally available (for example, Hibernate Core Package Version 3.2.5 GA). DAC is supported on the libraries of these versions also. You can download Hibernate Core Package from http://www hibernate. org, Internal & Oracle Academy Use Only For the purposes of this training, the Hibernate libraries have already been downloaded to your training environment. In the practice for this lesson, you copy the Hibernate libraries to the appropriate DAC directories as indicated in the table in this slide. Oracle BI Applications 7.9: Implementation for Oracle EBS 4-15Install JDBC Drivers Install JDBC drivers in the \OracleBI\DAC\1ib directory for DAC database connectivity. (B CiloracleBn\OACtlib ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Install JDBC Drivers Il the appropriate JDBC driver in the DAC\1b directory to enable DAC database connectivity. If the required JDBC drivers are not already installed, you need to install the JDBC driver on the machines where the DAC client is installed. You must Oracle BI Applications 7.9: Implementation for Oracle EBS 4-16Verify DAC Connection Configuration Open the DAC config.bat file in the \oracleBI\DAC directory and verify the connection configuration for the DAC. repository. Cee Tie Edt Femest ew Hels new REM Configure the following two lines. REM SAVA_RONE should be set toa directory where et oc Yene"shou'g pesne. te rhe Te JAVA HOME variable points to REM where Dic 1s" installed (na, the directory where the Java SDK is installed, DAC_HOME variable points to the directory where DAC is installed. FEM DAC_HOME-C:\or ec leDT\DAC ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Verify DAC Connection Configuration The connection information in the DAC config.bat file is configured during Oracle BI Applications installation. To verify or change the connection information, open the DAC config.bat file in the \OracleBI\DAC directory. Verify that the JAVA_HOME variable points to the directory where Java SDK is installed. In this example, it is set to JAVA_HOME= jdk1.5.0_11. Make sure there are no spaces in the path reference. Verify that the DAC_HOME variable points to the directory where DAC is installed. In this example, it is set to DAC_HOME= C:\OracleBI\DAC. Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 17Enable DAC Client Communication with Informatica * The DAC client uses the Informatica PMREP and PMCMD command-line programs to communicate with the 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. + In order for the DAC client to be able to use the PMREP and PMCMD programs, create a system variable that defines the path of the Informatica domain file. CiInformaticatPowerCenter3.1,t\clentibin Sas ce va ce coed CruMNOOWSysenerdse renee otce Hike [Bcinvemsiopomctco identi | NRC OS None ES E ee ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Enable DAC Client Communication with Informatica ‘The PMREP program is installed in the Informatica PowerCenter Client and the Informatica PowerCenter Services bin directories. Because of the recommendation to co-locate the DAC client with the PowerCenter Client, the PMREP program is available on the machine for the DAC client to use. The PMCMD program is installed in the PowerCenter Services bin directories. In this training environment, PowerCenter Services has been installed on the same machine as the DAC client and PowerCenter Client 8.1.1 SP4. Therefore, all that is needed is to copy the pmomd . exe program from the C: \Informat ica\PowerCenter8.1.1\server\bin directory to ¢:\Informatica\PowerCenter8.1.1\client \bin directory. In order for the DAC client to be able to use the PMREP and PMCMD programs, you need to create a system variable that defines the path of the Informatica domain file domains .infa. Although it is not shown in the slide, the path should include the name of the file. You also need to add the directory path to Informatica PowerCenter binaries to the path environment variable (not shown here). Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 18PMCMD Command + The Informatica PMCMD command is used by the DAC server to initiate workflows in the Informatica repository. + Syntax: Calls PMcMD User name variable Password variable — “[PATHvariable] \PMcMD" start *INFA_USER¥INFA_PASSWORD 4001 Oracle BI_DW Base:SDE AssetFact 0 0 Portnumber | { Repository folder |[ Workflow name | | Indicates workfiow | | Nowait option ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. PMCMD Command This slide details the use and syntax of the PMCMD command-line utility, which is used by the DAC server to submit ETL workflows on the Informatica server for execution, Oracle BI Applications 7.9: Implementation for Oracle EBS 4-19Create a DAC Connection Create a DAC connection, which is a stored set of login details that enable you to log in to the DAC client and connect to the DAC Repository. Cama. ORACLE ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Create a DAC Connection Before you can connect to the DAC client, you need to create a DAC connection. A DAC connection is a stored set of login details that enable you to log in to the DAC client and connect to the DAC repository. To create a DAC connection, start the DAC client and select Configure > Create Connection in the DAC client Login screen, Provide the appropriate connection details in the Configuring dialog box, as shown in the screenshot, and then test the connection. Oracle BI Applications 7.9: Implementation for Oracle EBS 4-20 Oracle Internal & Oracle Academy Use OnlyCreate the DAC Repository Schema When you log in to DAC and connect to a DAC repository for the first time, the DAC detects that the DAC repository tables do not exist in the database and you are asked whether you want to create a repository. Copyright © 2010, Oracle andlor its alates. Al rights reserved. Create the DAC Repository Schema When you log in to DAC and connect to a DAC repository for the first time, the DAC detects that the DAC schema does not yet contain repository tables and you are asked whether you want to create a repository, Enter the tablespace name (optional) and click Yes. The DAC creates the repository tables and the DAC client opens. This assumes that a user/schema and tablespace have already been created in the database. Oracle BI Applications 7.9: Implementation for Oracle EBS 4-21 Oracle Internal & Oracle Academy Use OnlyImport DAC Metadata In the DAC client, select Tools > DAC Repository Management > Import to import the DAC metadata for selected source systems into the DAC repository schema. om dg ifr a Chae meats sons Select desired "Loge source eae systems. eee eostony fis ocormentet thay back 0p Inybeparing the XML hes Sau thor athe ain. Dy we 0 conan trenoose a patent eration pleasa Fete tet Delo as a caiman to proce: ea Confirm 7 I import. rca opto tes rot ise (itt setchrnie oanigs:t Check log file. 5 on rie astais CuomaesNDK Hepa ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Import DAC Metadata After you create the DAC repository schema, you use the DAC client to import the DAC metadata. Select Tools > DAC Repository Management > Import to import DAC metadata for selected source systems into the DAC repository schema Verify that the Logical check box and the System check box are selected (this is the default). Logical imports all information contained in the DAC Design view and the execution plan information for the DAC Execute view. System imports all information contained in the DAC Setup view, except passwords for servers and database connections. Run Time (not selected here) imports ETL Run History and the last refresh date information, This option is not necessary when you first import DAC metadata because no ETL has been run yet. In the Applications List table, use the check boxes in the Selected column to specify the source system applications (Siebel 8.0 and Oracle 1.5.10 in this example) for which you want to import the ETL metadata, Be sure to select Universal (selected by default). To avoid possible ETL errors in other applications (for example, missing tasks), you must import the Universal application. The import process may take a long time, depending on the selected source systems. When the process is complete, the DAC displays a status box containing a success or failure message. If the process fails, use the \DAC\1og\ import . 1og file to diagnose the errors, Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 22Create the Data Warehouse Tables Select Tools > ETL Management > Configure in the DAC client to create tables in the OBAW database. 1, Set source and target, database platforms. Tat ia warns database (race ~ Seures rassctonl dias plform: (Gera pir Sonor owe 3. Enter the details of the Passwaid database where you want to create the data warehouse tables. Bae = Data Aree 2, Select Create Data Ei nd Warehouse Tables. Rares ‘ate Werehouse Conga oto: [rate Dato Worchowse Tees aati sues red Loven isting Data Wares Tales Greeting DotoWoretnise abs Success 4, Check log file [Tears Delos tages Transaction Datanso chek Yi ro het ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Create the Data Warehouse Tables You use the DAC client to create tables in the Oracle Business Analytics Warehouse database. The DAC client uses an ODBC connection to the Oracle Business Analytics Warehouse database for this procedure. You must create the ODBC connection and a schema to hold the OBAW tables before you create the OBAW tables using the DAC. To create the OBAW tables, select Tools > ETL Management > Configure, select the target and source database platforms, select Create Data Warehouse Tables, and enter data warehouse details in the Data Warehouse Configuration Wizard. If you leave the Container field blank, the DAC creates a container by default for all of the source business applications that you selected when you imported the seed data into the DAC metadata repository earlier. Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 23 ademy Use Only Ci DAC Server Management > DAC Server Setup to configure the connection between the DAC Server and the DAC repository. FepostoryConnesontnormeon | Eat Confition pat wn pontoon connoin.. Ccomection ye Ovact tum ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Configure Connection Between DAC Server and DAC Repository ‘You must configure the connection between the DAC Server and the DAC repository. In Windows, you can use the DAC client to configure a DAC Server that runs in the same \DAC folder. If the DAC Server is co-located with a configured DAC client in the same \DAC folder, you can set the connection between the DAC Server and DAC repository using the DAC client, 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 will store the DAC Server repository connection information that you specify in this procedure. In the Repository Connection Information tab, enter the appropriate information, In this, example, because the DAC Server is running on the same machine as the DAC client, you can click “Populate from preconfigured client connection” to populate the fields with connection details from the DAC client. Click Test Connection to make sure that the DAC repository connection works. Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 24Set DAC System Properties Set DAC system properties to ensure proper integration between the DAC client, the DAC Server, and Informatica. DADS Pr Maia Sos Malone. nace | smo ejumo| Damn] Ghee ane vive eas Frauen tas) i F Dinpinacreenoene fue (non Tau Coreen i. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Set DAC System Properties ‘You need to set DAC system properties to ensure proper integration between the DAC client, the DAC Server, and Informatica. You set DAC system properties in the DAC System Properties tab in the Setup view in the DAC client. For example, you need to set the: + Location of the Informatica parameter files + Name of the main Informatica repository + Name of the DAC repository + Name of the DAC Server host and so on. Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 25, > 3 % 8 a > E 5 3 S Setup view > Informatica Servers tab, register the Informatica Integration Services service and the Informatica Repository Service. an {now | El Save | 5] Unio ff Delete | 70 ouery| 2 Retresn]| ‘ama Tye [Sener Hechame Sener Pot Tea Oracle ALOW Sarvar ___[rformatea frachine_nare 4006 Banistran INFORWATICALREP_SERVER [Repository |machine_name | 2001 Administrator ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Register the Informatica Services in the DAC In the DAC client, display the Setup view, and then display the Informatica Servers tab. Register the Informatica Integration Services service by modifying the record with Name = Oracle BI_DW_ Server. Accept all defaults except for Server Hostname and Password. > 3 % 8 a > E 5 3 S 3 % 8 a > E 5 3 S 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 (OBAW) database. Click New to add a new connection, and then enter the details for the connection object. You must specify the DataWarehouse exactly as it appears in the Physical Data Sources tab in the DAC Setup view. Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 28Oracle BI Applications Topology Copyright © 2010, Oracle andlor its alates. Al rights reserved. Oracle BI Applications Topology Oracle Business Intelligence Applications and Informatica PowerCenter can be deployed flexibly across a wide range of topologies on different platforms and combinations of platforms. The figure in this slide shows a typical deployment topology. Machine A is a machine that has Oracle Business Intelligence Enterprise Edition or Oracle Business Intelligence Standard Edition One installed, on which you run the Oracle Business Intelligence Applications installer to install the Oracle Business Intelligence Applications files. Note: The instance of the Oracle Business Intelligence Enterprise Edition or Oracle Business Intelligence Standard Edition One does not need to be the functional version of the Oracle Business Intelligence Enterprise Edition that you will use to deploy dashboards in your live system. This instance is only required to enable the Oracle Business Intelligence Applications installer to install the Oracle Business Intelligence Applications files on a machine. After the Oracle Business Intelligence Applications files have been installed on Machine A, the DAC client is deployed to Machine B, and the DAC Server is deployed to Machine C. In addition, the following files are copied from the installation machine (Machine A) to the Business Intelligence Deployment Tier (Machine Group F) as follows: Oracle BI Applications 7.9: Implementation for Oracle EBS 4-29 Oracle Internal & Oracle Academy Use OnlyOracle BI Applications Topology (continued) The OracleBI\Server\Repository\EnterpriseBusinessAnalytics.rpd file is copied from Machine A to the machine that runs the BI Server in Machine Group F. + The OracleBr! cs\*.* files are copied from Machine A to the machine that runs the BI Presentation Services Catalog in Machine Group F. a\Web\Catalog\EnterpriseBusinessAn: Machine B is a machine that runs the DAC client and the Informatica PowerCenter Client Tools. Machine C is a machine that runs the DAC Server and the Informatica PowerCenter Services. Machine D is a machine that hosts the transactional (OLTP) database. Machine E is a machine that hosts the Oracle Business Analytics Warehouse database. ‘Machine Group F is a group of machines that runs the Oracle Business Intelligence Enterprise Edition components. For example, one machine might run the BI Server and BI Applications RPD, and another machine might run the BI Presentation Services and the Oracle Business Analytics Warehouse You can also run Oracle Business Intelligence Applications on a single machine installation of Oracle Business Intelligence Standard Edition One. Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 30Summary In this lesson, you should have learned how to install and configure Oracle Business Intelligence Applications and related components. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 4-31Practice 4-1 Overview: Configuring the Training Environment This practice covers postinstallation tasks to configure the training environment before you populate and customize the Oracle Business Analytics Warehouse. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Practice 4-1 Overview: Configuring the Training Environment The Oracle Business Intelligence platform and Oracle BI Applications have already been installed in your training environment, This includes the 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 the additional, postinstallation configuration of the DAC and Informatica in your environment. Performing these tasks is a convenient debugging technique, as most configuration issues arise from the steps performed in this practice. Oracle BI Applications 7.9: Implementation for Oracle EBS 4 - 32Understanding the ETL Process ‘Copyright © 2010, Oracle andior its alate. Al rights reserved.Objectives After completing this lesson, you should be able to: + Explain the extract, transform, and load (ETL) process used to load the Oracle Business Analytics Warehouse (OBAW) * Describe the differences between a full load and an incremental load of the OBAW + — Identify the applications and mechanisms used to support the ETL process ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 5-2ETL Process: Overview Data is loaded from the transactional database into the OBAW by the ETL process. — Run using the DAC client Running an ETL initiates: — Tasks run by the DAC server to prepare internal tables — Aseries of Informatica mappings and transformations executed by the Informatica server as requested by the DAC server The Informatica server accesses metadata in the Informatica repository to define how the data moves between the transactional database and the OBAW. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 5-3ETL Process: Overview At a high level, the ETL process is completed in three steps. + The DAC server executes as many steps in parallel as possible. Reads the data necessary for analysis Loads the rearranged data into the fact from transactional databases and dimension tables in OBAW Cleans the data and rearranges as required for the star schema ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. ETL Process: Overview The main point to note here is that ETL is a parallel process, The graphics and the callouts in the slide define the ETL process Oracle BI Applications 7.9: Implementation for Oracle EBS 5-4ETL Process Steps + Step 1: Extract and load staging tables. — Extracts and consolidates data from the transactional system and writes to the OBAW staging tables + Step 2: Transform data. — Transforms data in staging tables in preparation for load — Computes calculated fields * Step 3: Load dimension and fact tables. — Generates and maintains warehouse primary keys — Loads hierarchy tables — Loads dimension and fact tables ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. ETL Process Steps ‘You can identify the tables used during the phases in the data warehouse by the suffix of their names (for example, _F for fact, _D for dimension, and so on). Note that transformation is performed on the data warehouse to save impact on the transactional database during ETL. Oracle BI Applications 7.9: Implementation for Oracle EBS 5-5Data Extraction and Load Process: Extract + Uses source-specific and Universal Adaptors © staging tables + Exposes simplified <= business entities from Extract complex source systems { + Converts source-specific Extract data to a universal staging table format for B Ci PeopleSoft SAP ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Data Extraction and Load Process: Extract Extract Extract mappings encapsulate the complexity of the source and expose a simplified view of the business entities. > 3 % 8 a > E 5 3 S 3 % 8 a > E 5 3 S Seed Data > Task Phases. It is recommended that you use existing packaged task phases. Although it is possible to define and assign custom phases and associated priorities, this can have important repercussions on task precedence when building execution plans. Oracle BI Applications 7.9: Implementation for Oracle EBS 5 - 12DAC Task Phases + Load Fact: — Use SIL mappings to load data from fact staging tables into fact tables. + Dimension Hierarchy: — Use SIL mappings to load dimension hierarchy tables. - Aggregate: — Use SIL mappings to load aggregate tables. * Post Load: — Use post-load processing (PLP) mappings to update and load tables, including hierarchy and aggregate tables. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 5-13Internal Tables Are located in the OBAW Assist in the load process and contain metadata for the data warehouse including parameters used in the ETL process Examples: — W_ETL_RUN_S stores a record per ETL run. — W_EXCH_RATE_G stores exchange rates. — W_COSTLST_G stores costlist data. — W_DUAL_G is used to generate calculated values. — W_LST_OF_VAL_G stores a list of values used in the ETL process. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Internal Tables The internal tables store some static values, for example, language and currency, which are not updated incrementally. General tables end with a suffix of _G. Oracle BI Applications 7.9: Implementation for Oracle EBS 5-14Change Capture Change capture logic is included in the SQL of the SDE mapping. + The LAST_UPDATE_DATE column is compared to the $$LAST_EXTRACT_DATE parameter to detect changed records. + Records are loaded if LAST_UPDATE_DATE is greater than the value for the $$LAST_EXTRACT_DATE parameter. + The $$LAST_EXTRACT_DATE parameter value is passed from the DAC during ETL run time. SELECT TABLE. ROW_ID TABLE. PROO_TO, TABLE! PERSOWLID, TAELE:REVF, TABLE, LAST_UPDATE_DATE FROWN TABLE WaERE CABLE. LAST_UPDATE_DATE > TO_DATEC’SSLAST_EXTRACT DATE", "RM/DD/YYYY HH24:ME:SS' 3) ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Change Capture Change capture logic is included in the SQL WHERE clause of source qualifier transformation of the SDE Informatica mapping. (You learn more about source qualifier transformations in the lesson titled “Working with Informatica Designer.”) ‘The LAST_UPDATS_DATE column in Oracle source databases is used in incremental loads to identify changed records. LAST_UPDATE_DATS is compared to the DAC parameter $$LAST_EXTRACT_DATE to determine which records have been updated since the last ETL run, Records are loaded if LAST_UPDATE_DATE is greater than the value for the $$LAST_EXTRACT_DATE parameter. The value for the $$LAST_EXTRACT_DATE parameter is passed from the DAC during ETL run time. The TO_DATE function is used to convert the value to the proper format. Oracle BI Applications 7.9: Implementation for Oracle EBS 5-15Restart Mechanisms + Restart mechanisms are built into all mappings. « Rows that have been loaded or updated in the same ETL run are not reprocessed. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 5-16Unspecified Mappings + During a full load, the SDE mappings include logic to insert unspecified values. + All fact rows from source transactional system tables that do not have a matching row in their dimension tables are defaulted to the unspecified value. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 5 - 17Executing ETL In the DAC client: — Run the ETL execution plan. The DAC server runs tasks based on the ETL phase and task precedence. — Most ETL tasks call Informatica workflows. — Workflows are run in parallel on Informatica servers 2 snus sino Bes Tate =~ @ tas BB sexions ‘SDE workflows * © sexo SIL workflows load fact e Bo ‘vores / load staging tables. e eo = /_and dimension tables. Ye SIL acnewerse < SL_AGEemiF act Full sep iemonn é SD=_O4_APTemmaDirensen E_ORA AP Texmstirensin Ful Ee Dee APtansactonrsee Ditrbuton pray 6 50 ORA AP Transaction et Enpeneaticinbaticn P__50E_ORA_APTrensactionF ct, Espenssdisinbuten_ Ful [SL ACDCemF at, fohelete Si AcieDinenscn ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 5 - 18 > 3 % 8 a > E 5 3 S (TET Workspace cote. | (eee ee =f] Is used to view repositories o@eo & ruPE Ww Ohi aie) ees Repoton Never * eater) ; and folders | |g Seiec 5) 2 aa UB) woes re Boas acon bn Eee eed transformations Output Status Bar 2 Provides task , Displays . deiails, such as status of - saving work, of 5 prea aero SUE ORL BALD Valdatng 2 operations [SADE DRRRS) oe Tae Soa RT —|__ mapping ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Informatica Designer User Interface This slide introduces the Informatica Designer user interface. Refer to the callouts in the slide for details about the different user interface components. Oracle BI Applications 7.9: Implementation for Oracle EBS 6-4Key Terms + Folder + Source definition + Target definition + Mapping * Transformation « Mapplet * Port ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Key Terms This slide introduces the key Informatica Designer terms covered in this lesson, Each is presented in detail in the slides that follow. Oracle BI Applications 7.9: Implementation for Oracle EBS 6-5Folder FRepesionHasigatoy Organizes and stores Informatica repository metadata + Prebuilt SDE and SILOS folders should not be modified. — Folders may be overwritten during upgrades. ftston-aucs = Custom Powe soe folders cae |_folders | Seomusw sce Oracle SELOnALISD ir Beeraues oe SDE folder eo eS é Z 2 é 2 : é é 2 é Z 2 Be > + Create and use custom < folders for new or modified ° Informatica repository 8 g objects. ie 2 = Customizations are 5 € preserved during upgrades. a sg 2 s 2 < 2 o & Copyright © 2010, Oracle andor ts afates, Al rghs reserved § o Folder 3 Informatica repository folders provide a way to organize and store all metadata in the repository. 5 Prebuilt SDE and SILOS folders ship with the Oracle Business Analytics Warehouse (OBAW) = = and contain prebuilt Informatica repository objects. The SDE folders are organized by their respective source applications and versions. For example, the folder SDE_ORA11510_Adaptor contains the Informatica SDE repository objects for Oracle 11.5.10; the folder SDE_SBL_80_Adaptor contains the Informatica SDE repository objects for Siebel 8.0, and so on. If you want to make changes to the Oracle Business Analytics Warehouse, you must create a custom folder and make the changes in it. Do not change objects in any of the shipped folders unless explicitly directed by Oracle. The shipped folders and the objects within them may be overwritten in future upgrades. The deployed repository does not include any custom folders; you must create your own. You should create a custom folder for each SDE folder you have deployed that will have customizations. These folders hold the extract mappings to various sources. You should also create a separate custom folder for the customizations you want to make to the SILOS folder. Do not store customized extract and load mappings in the same folder. Oracle BI Applications 7.9: Implementation for Oracle EBS 6-6Folder (continued) The easiest way to modify an object is to copy an existing object from the shipped folder into the corresponding custom folder and to reuse existing business components, source and target definitions, transformations, mapplets, and mappings. ‘You use another Informatica tool, Repository Manager, to create custom folders. You lea how to create custom folders in the practices for this lesson. Oracle BI Applications 7.9: Implementation for Oracle EBS 6-7Source Definition Repository object containing a detailed description of database objects or files that provide source data Fleposkory Navigator = @ SDE_ORALIS10 Adaptor Source definitions B sora sag & ou 1 Ae HEADERS AL aeons AL 1 AP BAK ACCOUNTS AL me pan ANCES B woes a B manors AL ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Source Definition Source definitions provide detailed descriptions of tables or files that provide source data in mappings and mapplets. To extract data from a source, you must first define sources in the repository. ‘The main purpose of this slide is to identify where the sources are located in the Designer user interface. An example of how source definitions are used in mappings and mapplets is provided later in this lesson, Oracle BI Applications 7.9: Implementation for Oracle EBS 6-8Target Definition Repository object containing a detailed description of database objects or files that contain target data Flepockony Navigater =~ {9} SDE_ORAIISi0 Adaptor WB) Assness Compenents e~ Qf sume a wang waracr re want woos Target definitions | Sheeacee ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Target Definition Target definitions provide detailed descriptions of objects or files that contain target data in mappings. Target definitions typically represent data warehouse tables. ‘When you create a mapping, you must add a target definition to it, Typically, each mapping is designed to load one target table. This slide identifies where the targets are located in the Designer UI. An example of how target definitions are used in mappings is provided in another slide later in this module. Oracle BI Applications 7.9: Implementation for Oracle EBS 6-9Mapping Repository object representing the data flow between sources and targets used to extract, transform, and load data Repasioy Nevicetor = ED SDL ORALTSTO_Adapor Dusen Consents B sores B too B Gam tieraons B Vawtortors Breen e Mappings * ‘SDE_ORA_APTermnsDananon foo) De ont Wawaderted Dott Fy 1 2B Soe oangonmcnterted_Preoeastn fo Bh son ou arnaeasorreaweuncnutevane 1 2B Soeonapenarcatureatjuttynentin foo) soe ou prnaasorrea Fame jeter, pomercwdia lunbusloobveloabs soe ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Mapping A mapping is a set of source and target definitions linked by transformation objects that define the rules for data transformation, Mappings represent the data flow between sources and targets. ‘When the Integration Service runs a session, it uses the instructions configured in the mapping to read, transform, and write data. Every mapping must have the following components: + "Source definition: Describes the characteristics of a source table or file + Transformation: Modifies data before writing it to targets. Use different transformation objects to perform different functions. + Target definition: Defines the target table or file + Links: Connect sources, targets, and transformations so that the Integration Service can move the data as it transforms it Source definitions, target definitions, transformations, and links are described in more detail in subsequent slides. A mapping can also contain one or more mapplets. A mapplet is a set of transformations that you build in the Mapplet Designer and can use in multiple mappings. When you add an object to a mapping, you configure the properties according to the way you want the Integration Service to transform the data. You also connect the mapping objects according to the way you want the Integration Service to move the data, You connect the objects through ports. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 10Transformation Repository object that generates, modifies, or passes data Flepoctory Navigator = SDE_ORAZIS1O Adaptor fursness Components BB saucer ° 8 me cer Transformations B Crerscns oe DES GENERIC -EUSTGC_GUETONER ID UP _CUSTLOC_AST_L0C ID LF eROUP ACCOUNT CAT.cODE LP _ROUP_ACCOLNT FDL STATENENT LF sROUP ACCOUNT NUMA uP A. NETHOD. CODE FILE papene ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Transformation ‘Transformations are used in mappings to generate, modify, or pass data. Transformations in a mapping represent the operations that the Integration Service performs on the data. Data passes through transformation ports that you link in a mapping or mapplet, ‘Transformations can be active or passive. An active transformation can change the number of rows that pass through it, such as a Filter transformation that removes rows that do not meet the filter condition. A passive transformation does not change the number of rows that pass through it, such as an Expression transformation that performs a calculation on data and passes all rows through the transformation. Transformations can be connected to the data flow, or they can be unconnected. An unconnected transformation is not connected to other transformations in the mapping. An unconnected transformation is called within another transformation and retums a value to that transformation. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 11 ademy Use Only Ci ternal & Oracle A OracTransformation Type + Performs a distinct function in transforming data + Examples: Transformation Type Function Brings data into the mapping process from one Source qualifier or more related tables in the same data source Expression Performs simple calculations Aggregator Performs aggregate calculations Filter Adds a conditional filter Update strategy Allows inserts, updates, deletes, and rejects Lookup Looks up values and passes to other objects ‘Allows joins between tables in different data Joiner sources ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Transformation Type Different transformation types are used in mappings. Transformations can be used, for example, to aggregate or cleanse data during ETL. This is not a comprehensive list, but the major transformation types are listed. A comprehensive list can be found in the Informatica documentation, Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 12Mapplet Repository object that contains a set of transformations whose logic can be reused in multiple mappings ERE =) SDE ORALISIO_Adaptor Defeat cranes force anes coe Dera Tags PLT ADI coves Mapplets Ingk_EC_ORa APemaDinensen gk. 608A APTraneacionFac FaymertPrinary Ingk_ 6-08 APiranasenenFn_seeck tear ase0ec2GUGUTES Frereres ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Mapplet A mapplet is a reusable object that you create in the Mapplet Designer. It contains a set of transformations and enables you to reuse that transformation logic in multiple mappings. Examples of mapplet logic include logic to obtain currency conversion rates or logic to obtain the ETL_PROC_WID, which is the unique identifier for an ETL run. ‘When you use a mapplet in a mapping, you use an instance of the mapplet. Like a reusable transformation, any change made to the mapplet is inherited by all instances of the mapplet. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 13 ademy Use Only Ci gpl beiper + Mapplet Designer 2 SINED tia Dein — Use to create and modify mapplets. + Mapping Designer — Use to create and modify mappings. this course ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Informatica Designer Tools This slide identifies the Informatica Designer tools that you use throughout the course to configure source definitions, target definitions, mappings, mapplets, and transformations. You learn how to use these tools in the practices in this course, For reference, the Transformation Developer is listed, but it is not used in this course, Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 16Source Analyzer Used to import, create, or modify source definitions sntorms oe ere) P Resesory Eat ew Teds Layout tetsoang. Sauces indo He UCN S0e uate 85 2 tock | eoloo Gls FepostoryNevewst a reps x : — TG Oral BD Boe * @ aso = B cimrom sor Te) © sre Cnpets 5 Nae Taste a B Few ivashed 15 Tue iP frog mace 18 Fensail faee 18 Kan Dotape Loge OW. ares fa PARTRER, NA. th ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Source Analyzer Before creating a mapping, sources must be defined in the repository. Use the Source Analyzer to import or create source definitions for flat file, XML, COBOL, Application, and relational sources for mappings. Source definitions include properties such as column names and data types. ‘You can create source definitions for file and relational sources in the following ways: + Import definition. + Create a source definition based on a target definition. + Manually create a source definition. + Copy an existing source. If you want to use existing sources for custom mappings, they must be copied from the shipped SDE and SILOS folders to a custom folder. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 17Example: Importing a Source Definition (Pkepetay EAE an Teak Lae seeing ESI vnc tp (CUSTOM. E-free Bow 5 [6 lene ipertonFe ooo Gla see a __2. Select Import Repostiory Nexigat_ = peeaenesenseg, from Database. [A Selectfolder. =” SBE cowie” frre 2B sae tree 3, Select ODBC | [sn data source. Lode Fear awn ate |) ene Trommcees LTT freee credentials. | |) == stati fp fecar ———— govmer + Sones are ea 5. Select tables --—— Siay forimport and (TTT Sear click OK 6. Source definition is displayed in Source Analyzer. UU upoaTe DATE ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Example: Importing Source Definition Sources needed to build mappings can be imported from data sources. Connections to external data sources are made via Open Database Connectivity (ODBC) data sources. The callouts in the slide show the steps for importing a source from a databa Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 18 ademy Use Only Ci ternal & Oracle A OracTarget Designer Used to import, create, and modify target definitions ee acle_BI_DW_Aase]) Pesestry Est Yaw Tos Lave versanng Tass rdsu Noe CUSTOM SOE nck BLOW Gor [ETSI | 2 Qe eooo Ble 4 Raposloy Never Ss aa nie fae Fo seamen ED Busnes Components bo Bi sures [DATASOURCE WUND rumipal 10 | oa WIEGRATOND ached a0 | PARINER.NJE van? 50 PARTNER-LOC aca? 5 | ee Cape @ TATASOURCE MLMLIOurbmips] 18 @ cinensoe Soo Mteseamion io oe an 2B tmtirnaine | mee wwe 20 2. BD taxi | Asoo mrowte? 30 oo |) Bee rurbaips) 18 = @ astm me | USturoate nate dae 3 ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Target Designer Before creating a mapping, targets must be defined in the repository. Use the Target Designer to import, create, and maintain target definitions for mappings. Target definitions include properties such as column names and data types. Create target definitions for file and relational sources in the following ways: + Import definition. “reate a target definition based on a source definition, + Manually create a target definition, opy an existing target, If you want to use existing targets for custom mappings, they must be copied from the shipped SDE and SILOS folders to a custom folder The steps for importing target definitions are identical to importing source definitions and are not repeated here. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 19 ademy Use Only Ci Copy. Then select the Mappings folder in the custom folder you created and select Edit > Paste. The Informatica prompts you to confirm the copy. To create a new mapping, select Mappings > Create. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 20Mapplet Designer Used to create and modify mapplets pier -[Mapplet Designer -CUSIOM.SDL-[Orecle DW Darel eceaony eft Wow Tear Lovet sesomg Monee Tantra rey Hee OUSTON SOE Hae Bows ® (ISIE | is S QA ~ > OMOo FeAeoF FA ws oe nbb Rei ennr ea SES a oy Ape > eB [] se | aro HC Romer aan rea Source qualifier |" transformation Modify mapplets, jin the workspace. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Mapplet Designer Use the Mapplet Designer to create, copy, and modify, if necessary, mapplets. You can reuse existing mapplets in the prebuilt ETL mappings to add their processing in your custom mappings. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 21Linking Components Drag the ports to create links between components. Copyright © 2010, Oracle andlor its alates. Al rights reserved. Linking Components Create links between source definitions, mapplets, transformations, and target definitions by dragging ports between the desired components. A blue line indicates a link. To delete a link, click the blue line and select Edit > Delete, or press Delete, Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 22 Oracle Internal & Oracle Academy Use OnlyValidating Mappings Select Mappings > Validate to validate a mapping. Se eT TB sonar tat vey Teas Les sere aang Teor ry eb porns noes ove [SID 88 Am + |g ODO0 RFAewF FAs ws Oh ah bbw $s epost Newgeior ff S06 (Reve 5 2 me DL Wage fo var SDE_C_Revema ava => : Saison TE atigat EE "=i Validation message appears — inthe Output window, —— ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Validating Mappings Mappings must be configured correctly and then validated so that the Informat read and execute the entire mapping without any errors. Mappings are marked invalid (with a red X) when errors are detected that prevents the Informatica server from executing the mapping successfully. To determine whether a mapping is valid, the Informatica Designer checks the following: + The required ports are connected. + Allport connections are valid. + All expressions parse successfully and are valid. + The independent object definition matches the instance of the object definition in the mapping Mappings are validated automatically when you save the repository. You can also validate mappings manually by selecting Mappings > Validate. server can Validation results appear in the Output window. If a mapping is invalid, review the validation message in the Output window to determine the reason. Follow the same procedures to validate mapplets. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 23Copying Existing Objects Existing objects can be used as a starting point to build new objects in custom folders. epactinyy Navigancr @ recoskorks = @ Och or ow oaee © BCom = custom soe Baines Compares Saunese Tels aes Cinersine Tranernatlone oppets Mapping copied from the Meopinge SDE_ORA11510_Adaptor of SDE Custer Parreromenson / folder tothe YS Stet RavanaFact | _ CUSTOM_SDE folder. FEO ERRUBUBES: ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Copying Existing Objects ‘You can use existing objects from the shipped SDE and SILOS folders as a starting point to create new objects in custom folders. To copy an object, first open the custom folder. Copy the existing object and paste into the custom folder. Alternatively, drag the desired object from the existing folder into the custom folder. Informatica prompts you to confirm the copy. When you copy an object, all objects contained within that object are also copied. For example, when you copy a mapping, all sources, targets, mapplets, and transformations associated with the mapping are copied as well. Informatica provides a dialog box that enables you to determine which versions of objects to copy and which to discard. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 24Saving the Repository Select Repository > Save to save changes to the Informatica repository. (EEE cat iw tat Decco & oe Configure Doris. seen anid 1) ese Al Tole uence Compensres af Import copes. ee on ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Saving the Repository Be sure to save your work as you build and modify repository objects. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 25Summary In this lesson, you should have learned how to: + — Identify the Informatica repository objects used to configure the Oracle Business Analytics Warehouse + Navigate the set of tools in the Informatica Designer used to configure Informatica repository objects. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 26Practice 6-1: Working with Informatica Designer This practice covers the following topics: + Navigating Informatica Designer and its set of tools + Building an SDE mapping ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Practice 6-1: Working with the Informatica Designer The primary goal of this practice is to become familiar with the 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 data sets, 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 lesson titled “Working with Informatica Workflow Manager,” you use the Informatica Workflow Manager to run the mapping and verify the results. Later in this course, in the lessons titled “Adding a New Dimension in OBAW” and “Integrating Security for Oracle Business Intelligence Applications,” you build custom SDE and SIL mappings and use the DAC to run the mappings and verify the results. Oracle BI Applications 7.9: Implementation for Oracle EBS 6 - 27AluQ asp Awapeoy ajeo 9 [eWau] [92/0Working with Informatica Workflow Manager ‘Copyright © 2010, Oracle andior its alate. Al rights reserved.Objectives After completing this lesson, you should be able to: + Navigate Informatica Workflow Manager + Run workflows and sessions using the Informatica Workflow Manager + Monitor workflows using the Informatica Workflow Monitor ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Objectives In the lesson titled “Working with Informatica Designer,” you learned the steps to build mappings using the Informatica Designer tools. In this lesson, you learn how to use the Informatica Workflow Manager to add those mappings to sessions, and then run and monitor the sessions to load data, Oracle BI Applications 7.9: Implementation for Oracle EBS 7-2Informatica Workflow Manager Is an Informatica client tool used to build workflows to execute mappings ee eee eee entation Tet Sener Greate sib fh GOsIALe-Onksovie [Di] w+ Gl aeosaos g 4\@ 222.282 5 \oos)o genni a Designer: EE ey Create and 3 ae See otis ©, run workflows. San os. =» bg wma) | BS = ae View, select, Ig Bote an, (2 ORIOWEMN = $20 cent caretncro cane eee * SxqaniaatieDinerson Custones Ful View messages from the Informatica Integration Service, 1 ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Informatica Workflow Manager This slide explains the purpose of the Informatica Workflow Manager. In the Workflow Manager, you define a set of instructions to execute tasks, such as sessions. This set of tructions is called a workflow. When you create a workflow in the Workflow Designer, you add tasks to the workflow. The Session task is based on a mapping you build in the Designer. You then connect tasks with links to specify the order of execution for the tasks you created, ‘When the workflow starts, the Integration Service retrieves the metadata from the repository to execute the tasks in the workflow. You can monitor the workflow status in the Workflow Monitor. You used Workflow Manager to register Informatica servers in the lesson titled “Installing Oracle BI Applications.” This lesson focuses on the steps needed to create, run, and monitor s ssions and workflows. Oracle BI Applications 7.9: Implementation for Oracle EBS 7-3Workflow + Is aset of instructions that tells the Informatica Integration Service how to execute tasks + Contains a session and any other tasks needed to execute a session ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Workflow A workflow is a set of instructions that tells the Integration Service how to run tasks such as sessions. A workflow is made up of tasks. The most common types of tasks used in the Oracle Business Analytics Warehouse (OBAW) are Start and Session ta The Start task represents the beginning of the workflow. The Session task is used to execute the mapping. The workflows are called by the Data Warehouse Administration Console (DAC) server during extract, transform, and load (ETL) based on how their respective DAC tasks are prioritized for execution Oracle BI Applications 7.9: Implementation for Oracle EBS 7-4Session + Is aset of instructions that tells the Informatica Integration Service how and when to move data from sources to targets + Is configured in the Workflow Manager by creating a session task + Is executed as a task within a workflow ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Session A session is the mechanism by which mappings move data from sources to targets. Mappings are added to sessions. When the Informatica server runs a session, it uses the instructions configured in the mapping to read, transform, and write data Oracle BI Applications 7.9: Implementation for Oracle EBS 7-5Creating and Running Workflows Connect to the repository. Open Workflow Designer. Create a workflow. Add a session to the workflow. Link workflow tasks. Edit session properties. Validate the workflow Start the workflow. Monitor the workflow. 0. Check log files. BOEPNOAARYONS ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Creating and Running Workflows These are the high-level steps for creating and running workflows. Each step is presented in detail in the slides that follow. Oracle BI Applications 7.9: Implementation for Oracle EBS 7-61. Connect to the Repository Open Workflow Manager and connect to the repository. See ee Double-click the repository. Enter username ‘and password and click Connect. 5) (a Krai at Kaan Svc ae 7 Copyright © 2010, Oracle andlor its alates. Al rights reserved. 1. Connect to the Repository To open Workflow Manager: If Informatica Designer is open, select Tools > Workflow Manager; otherwise select Start > Programs > Informatica PowerCenter 8.1.1 > Client > PowerCenter Workflow Manager. Afier the Workflow Manager is open, connect to the repository as you would in other Informatica tools: double-click the repository, enter the username and password, and click Connect. Oracle BI Applications 7.9: Implementation for Oracle EBS 7-7 Oracle Internal & Oracle Academy Use Only2. Open Workflow Designer Open the appropriate custom folder and Select Tools > Workflow Designer to open the Workflow Designer workspace. oiteeceeen eee SB Revostory at wow Bena Layout versoong Wi TeskDeveoper (@OUSIO_—_worket Cesirer Select Workflow Designer. eee G8 ete 9229 O29 wow Raposilon Navigator [i Woildor Mensoe Dict, Hebntie Bam |S Bere 8B Gunton ogtens PB TO Cee Open folder. | (2 senire TO Bias ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. 2. Open Workflow Designer Open the appropriate custom folder and select Tools > Workflow Designer to open the Workflow Designer workspace. Oracle BI Applications 7.9: Implementation for Oracle EBS 7-83. Create a Workflow Select Workflows > Create to create a new workflow. Name the workflow and click OK. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 7-94. Add a Session to the Workflow Select Tasks > Create to add a session to a workflow. Select Session type. ee Game z te Name the task. |_| Bii2eometorthsts Select a mapping to associate with the session, ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. 4, Add a Session to the Workflow To add a session to a workflow, perform the following steps: 1, Select Tasks > Create, Select the Session type from the list. Name the session, Associate a mapping with the session. Re Oracle BI Applications 7.9: Implementation for Oracle EBS 7 - 105. Link Workflow Tasks Select Tasks > Link Task to link workflow tasks. [EG sees correetane ware Click the Start icon and then the session task to 2 create the link ae Start SDE_C_Aevenu, ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. 5. Link Workflow Tasks To link tasks, select Tasks > Link Task, and then click the Start task and then the session task. Oracle BI Applications 7.9: Implementation for Oracle EBS 7-116. Edit Session Properties Double-click the session in the Workflow Designer workspace to open the Edit Tasks dialog window. Use the Edit — ‘Tasks dialog box to edit session properties. eae a ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. 6. Edit Session Properties Session properties include source and target database connections, transformation source, bulk load options, session file names, and the option to truncate the target table. Oracle BI Applications 7.9: Implementation for Oracle EBS 7 - 127. Validate the Workflow Select Workflows > Validate to validate the workflow. EEE = een © co Pas 3 Com be Feposten Nsdgear $d Stine parce 4 semester © yoieom G2 Re oun Saree 7 bet tel da SE, pre MES eee con cond hv ae Tae racic veins [So Rea tanks Kae Copyright © 2010, Oracle andlor its alates. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 7-13 Oracle Internal & Oracle Academy Use Only8. Start the Workflow Right-click the workflow and select Start Workflow. 46, SOE_Ciston PatnerDinerson 2 He Gukon Pattern Fa | SERA, ciReverueFact SOE ORO clever act Ful SDE ORD OrgarstionDmersion Custer SBE_ Cha orgarzatiorbwnerson_custorer Ful > in Navigator. | valosDecioa e ite 5 ‘en 2 - A Selec Start Worktow a 3 Shee Woon 2 Uncen 5 3 s < 2 S s Copyright© 2010, Oracle andor ts alates, Al gh eserves. § 8. Start the Workflow i Aer session properties are set and the workflow is validated, you can start the workflow or £ session from the appropriate folder in the Repository Navigator. Start workflows by right- 2 clicking the workflow and then selecting Start Workflow. Alternatively, you can right-click a task in the Workflow Designer workspace and select Start Workflow From Task. Oracle BI Applications 7.9: Implementation for Oracle EBS 7 - 149. Monitor the Workflow Use the Workflow Monitor to monitor workflows. ee Repostny Ee Med Took Tak tas 6 Rape 1 cra 5p Fane = @ crate. sen tena secs g (2 e_onents0 Pore Bats [tle] wave Wallen a8 State Carpet Tre Stabe SSE CReenefat — SUAS IDSSISAN SIUMOMIOIEEDIM Sued [5 eSDEE hovenaroe srvemeTIRRanaM SIREN IRIOSRAR oxen Workflow Start time | Completion time | Status ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. 9. Monitor the Workflow When you start a workflow, the Informatica Workflow Monitor opens and provides information about the workflow run, including the start time, completion time, and status. Oracle BI Applications 7.9: Implementation for Oracle EBS 7 - 1510. Check Log File + For the workflow log, right-click workflow in the Workflow Monitor and select Get Workflow Log. + For the task log, right-click task in the Workflow Monitor and select Get Task Log. SHAME BIN 27 LSE Steg nederdel [eaE? Feeenaf act ni oe (Gusta Sbelon svete tee aes) Hoe civawnsnaeman we uate atl Boe, ¢ Aree ee (BiPiea st0bpalisiTiren 00 treads snmmyaenan man Shr nti ner consort cha| when sormmsrosesnaN 2975 UML Sin pane ial Emin oe SUE-C Revewefat ene ca Rm Fates ‘Soi sce TE ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. 10. Check Log File Use log files to verify the success of a session or to troubleshoot sessions that fail. If the workflow retums a status of Failed, right-click the workflow object in the Workflow Monitor, select Get Workflow Log and try to troubleshoot. If the session task returns a status of Failed, right-click the session task object in Workflow Monitor, select Get Task Log and try to troubleshoot, Troubleshooting may require changes to the workflow in the Workflow Manager or changes to the mapping in the Designer Log files include information about: + Allocation of system shared memory + Execution of presession commands + Session initialization + Creation of SQL commands for reader and writer threads + Start and end times for target loading + Errors encountered during session + Execution of postsession commands + Load summary of reader, writer, and Data Transformation Manager (DTM) statistics Oracle BI Applications 7.9: Implementation for Oracle EBS 7 - 16Summary In this lesson, you should have learned how to: + Navigate in the Informatica Workflow Manager + Run workflows and sessions using the Informatica Workflow Manager + Monitor workflows using the Informatica Workflow Monitor ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 7 - 17Practice 7-1: Creating and Running an Informatica Workflow This practice explains how to use the Informatica Workflow Manager to create and run a workflow for an SDE mapping. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Practice 7-1: Creating and Running an Informatica Workflow In the practice for the lesson titled “Working with Informatica Designer,” 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 the 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 lesson titled “Working with Informatica Designer,” you use custom tables provided specifically for this training. Oracle BI Applications 7.9: Implementation for Oracle EBS 7 - 18Exploring SDE and SIL Mappings ‘Copyright © 2010, Oracle andior its alate. Al rights reserved.Objectives After completing this lesson, you should be able to: + Describe the differences between Source Dependent Extract (SDE) and Source Independent Load (SIL) mappings + — Identify typical objects and their mechanics in SDE and SIL mappings ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Oracle BI Applications 7.9: Implementation for Oracle EBS 8-2Anatomy of a Typical SDE Mapping SDE mappings select from source transactional tables and load warehouse staging tables. Business. Expression Source adapter Target component mapplet transformation ‘mapplet definition ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Anatomy of a Typical SDE Mapping A typical SDE mapping generally consists of source tables or a business component, an expression transformation, and a staging table, Most SDE adapter folders use the concept of business component mapplets. These are extract mapplets that may contain relational, application, or flat file sources. The Siebel adaptor folders do not use business component mapplets; the sources are exposed directly in the mapping. The source objects of SDE mappings are transactional tables, whose data is retrieved, processed by mapping transformations, and loaded into an OBAW staging table, which is the typical target object of an SDE mapping This slide provides an overview of the function and major components of a typical SDE mapping in an Oracle adaptor folder (for example, SDE_ORA11510_Adaptor). This mapping, SDE_ORA_GLRevenueFact, extracts revenue data from tables in an Oracle E-Business Suite source system and loads the data into the W_GL_REVN_FS fact staging table in the Oracle Business Analytics Warehouse. Note that there are four components in the mapping and the data flow is from left to right. Each of these components is discussed in detail in the slides that follow, Please note that individual mappings may differ substantially from the examples provided on this and the following slides, which examine a typical mapping, SDE_ORA_GLRevenueFact. The main goal is to illustrate the typical objects and data flow in an SDE mapping. Oracle BI Applications 7.9: Implementation for Oracle EBS 8-3Business Component Mapplet Extracts data from tables in the source system > O° © & 3 > € G = oO S Source: Source Output ° definitions qualifier * transformation < © o © Copyright ©2010, Oracle andlor ts affliates. Allights reserved. 6 & Business Component Mapplet 3 ‘This mapplet, mp1t_BC_ORA_GLRevenueFact, extracts revenue data from tables in the 5 Oracle E-Business Suite source system. Notice that there are three component types in the 2 mapplet and the data flow is from left to right. The three component types are source definition, source qualifier, and mapplet output transformation. Recall that source definitions represent tables or files that provide source data, Source definitions are imported into the Informatica repository via the Source Analyzer. The screenshot shows only a partial view of the source definitions for this mapplet. 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. The source qualifier is discussed in more detail in the next slide 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_SXTRACT source qualifier. The MAPO_GL_REVENUE_EXTRACT mapplet output transformation passes output from the mapplet to the next transformation in the mapping (Bxp_W_GL_REVN_FS_Integrat ion_Id expression in the example for this lesson). Oracle BI Applications 7.9: Implementation for Oracle EBS 8-4Source Qualifier Transformation + Represents the rows that the Informatica Integration Service reads when it runs a session * Contains the SQL statement used to retrieve data 7 USI_UFDAED AY decal + GRESTON tore nine + TREATED EN Sema HL GUST TRLIYPE IO. deeret [I sheen eA ‘recente: Fare ao SELECT RA_CUSTONER TRE ALLLAST UPDATES BY: RA_CUSTONER TRH ALLCREATION DATE FA CUSTOMER TRA ALL CREATED BY Ra CUSTOMER TR ALLTFX NUMER, PALCUSTOMERLTRAALLCUST.TRXLT PEO. RA CUSTOMER TAX ALL TRO DATE FRCALLBLL_ TO. Pa CUSTOMER TR ALLSOLT._TO_CONTAGT ID RA GUSTONER. THX ALL SOLD-TO_SINE USED Pa CUSTOMER TR ALLSIL 79. CUSTOWERIO. AA CUSTOMER. TR ALLBUL TD ST USED, PACGUSTOMERLTRACALL SHPL_TO_CUSTOMER|D.RA, CUSTOMER. TP ALL SHiP_TO_CON TACO, FALSUSTOMERCTRACALL SHP_TO_SITE_USE_O. FA CUSTOMER. TF ALL TEFMID. oC CUSTOMERCTOCALLPAMAY SaLESP=P PAC SALESREPS ALL PERSON ID. PA CUSTOMER TRLALL PURCHASE ORDER. RA CUSTOMER THX ALL PURCHASE ORDER DATE Pe CUSTOMER TRH ALLEXCHANDE RATE TYRE,RA CUSTOMER TR ALL ENCHANISE OATE, NTAGT.IO. RA CUSTOMER. TPAC ALL SOLD_TO_CUSTOMER.IO. ademy Use Only Ci ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Source Qualifier Transformation ‘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 row set retrieved from source objects before undergoing subsequent transformations, It is often used to perform necessary data manipulation, which can include joining source objects, filtering rows, specifying custom joins such as an outer join and an inner join, and data cleansing. ‘The SQL Query transformation attribute contains the SQL statement that is used to retrieve the data, To view or modify the SQL statement, double-click the source qualifier transformation to open the Edit Transformations dialog box, click the Properties tab, and then click the SQL Query value’s down-arrow icon. The source qualifier SQL also contains the $$LAST_EXTRACT_DATE parameter (not shown here). 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 ternal & Oracle A Orac Oracle BI Applications 7.9: Implementation for Oracle EBS 8-5Expression Transformation Is used to calculate values in a single row before writing to the target a ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Expression Transformation An expression transformation is used to calculate values in a single row before writing to the target. Expression transformations perform necessary processing on data retrieved by the source qualifier, Notice that port types in an expression transformation vary by port. Though most of the ports are input/output ports that receive data and pass it unchanged, there are also input ports, variable ports, which are used to store values across rows, and output ports with expressions. For example, notice the value in the Expression field for DATASOURCE_NUM_LD port. Recall that DATASOURCE_NUM_TD is the unique identifier of the source system from which data is extracted. DATASOURCE_NUM_ID forms part of the unique key in the data warchouse and is referenced in all SDE mappings. Here DATASOURCE_NUM_ID is an output port that gets its value from the $$DATASOURCE_NUM_ID parameter, whose value is passed by the DAC during run time, Recall that variables and parameters can be declared for mappings and mapplets using the Declare Parameters and Variables dialog box. Notice that other ports are also transformed by expressions, such as TENANT_ID, which is calculated using an IIF conditional expression. You build expressions using the Expression Editor, which is accessed by clicking the down arrow in the Expression field for a port. Oracle BI Applications 7.9: Implementation for Oracle EBS 8-6Source Adapter Mapplet Converts source-specific data elements into standard formats and then stores them in a staging table. Lookup Input _,| Expression _,! Output transformations | | transformation | transformation [~) transformation ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Source Adapter Mapplet The Source Adapter mapplet converts source-specific data elements into standard formats and then stores them in a staging table. The Source Independent Load (SIL) mapping then uses an Analytic Data Interface (ADI) mapplet to pick up these records, which are already transformed into a standard format, Note that there are five components in the mapplet and the data flow is from left to right. The components are: two unconnected lookup procedures, a mapplet input transformation, an expression transformation, and a mapplet output transformation. LKP_LOC_CURRENCY and LKP_CUSTLOC_CUST_LOC_ID are unconnected lookup transformations. An unconnected lookup transformation is a stand-alone transformation that is not linked to other transformations in a mapping or mapplet. A lookup transformation is called in an expression using the :LKP reference qualifier. ‘The input transformation in this mapplet receives the output of the expression transformation in the SDE_ORA_GLRevenueFact mapping and passes the data to the expression transformation in this mapplet. The expression transformation performs any necessary processing on the data and then passes it to the output transformation. Notice that all ports in the output transformation have the EXT_prefix. These ports exactly match the input ports of an Analytic Data Interface (ADI) mapplet in the corresponding SIL mapping. You explore this mapplet in more detail in the practice for this lesson. Oracle BI Applications 7.9: Implementation for Oracle EBS 8-7Target Definition Represents the target table object senior Trrwomaton Pers [rou] mnt tere some nattunaten [9 6A | Toroaton tes FTO Required columns are loaded into the staging table. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Target Definition The target definition represents the target table object in the mapping. For an SDE mapping, this is a staging table in the OBAW. In this example, the target definition is the fact staging table W_GL_REVN_FS. The EXT_*output ports of the mplt_SA_ORA_GLRevenueFact mapplet are used to populate the ports in the W_GL_REVN_FS target definition. This table is one of the source definitions in the corresponding SIL mapping, SIL_GLRevenueFact. Recall that target definitions are defined using the Target Analyzer in Informatica Designer. The required staging table columns, DATASOURCE_NUM_ID and INTEGRATION_ID, are loaded into the staging table. INTEGRATION_LD stores the primary key or the unique identifier of a record in the source table and DATASOURCE _NUM_D stores the data source from which the data is extracted, These required columns are used by the SIL mapping to generate the surrogate key for the OBAW. Oracle BI Applications 7.9: Implementation for Oracle EBS 8-8Anatomy of a Typical SIL Mapping SIL mappings select data from OBAW tables, perform transformations, and load data into OBAW tables. Source qualifier ‘Mapplet Mappiat || Update ea FS [=m As BL Magplet ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Anatomy of a Typical SIL Mapping SIL mappings select data from OBAW staging and dimension tables, perform transformations, and load data into OBAW tables. SIL mappings differ from SDE mappings with regard to source and target tables, SIL mappings are source independent in that they do not select data from a transactional source, but rather from the warehouse staging and dimension tables. The targets of SDE mappings are OBAW staging tables; whereas the targets of SIL mappings are the final OBAW tables. Also, SIL mappings are typically more complex than SDE mappings, because the data undergoes more transformation before being passed to the target. This slide provides an overview of major components of a typical SIL mapping. An SIL mapping has many of the same transformation objects as an SDE mapping: source definition, source qualifier, mapplet, lookup procedure, expression, and target definition. In addition, an SIL mapping contains the following transformation objects: filter and update strategy. In the remainder of this lesson, you explore the general flow of an SIL mapping and the objects that are unique to an SIL mapping, Please note that individual mappings may differ substantially from the examples provided on this and the following slides, which examine the SIL_GLRevenueFact mapping. The main goal is to illustrate the typical objects and data flow in an SIL mapping Oracle BI Applications 7.9: Implementation for Oracle EBS 8-9SIL Source Definitions SIL source definitions include dimension tables loaded by dimension SIL mappings and staging tables loaded by SDE esse ; ‘ mappings. Dimension Pping ‘ane | Staging table mone Dimension table ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. SIL Source Definitions Source definitions for SIL mappings are all located in the OBAW. They include dimension tables, which are populated by dimension SIL mappings, and staging tables, which are populated by SDE mappings. In this example, one of the source definitions is the W_GL_1 FS fact staging table, which is populated by the SDE_ORA_GLRevenueFact mapping discussed earlier in this lesson. The screenshot shows only a partial view of the source definitions for this mapping. > 3 % 8 a > E 5 3 S _ETL_PROC_WO-ETL_PROC.WID.%, WWr(REJECT FL, IrIeNULLtye ETL paocwio, rbaere tase Update E(HSERT_ONLY_FLG -'V’, flag” logic WrbeLeTe Pes WWF[UP_DELETE_FLG =" %.‘D}, lnF(SYSTEMS_GOLE.DIFF =". °U.) ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Exp_W_GL_REVN_F_Update_Flg Expression ‘This expression transformation evaluates the value of the “Update Flag” port, UPDATE_FLG, which is used to take actions such as insert and delete in the update strategy transformation, which is located downstream in this mapping. The possible values for the UPDATE_FLG port are: I (insert new record), B (insert new record and mark for soft delete), U (update existing record), D (update existing record and mark for soft delete), and X (reject). ‘The update flag is evaluated using the following logic: Basic Checks: If the current ETL Process Identifier is the same as the target record’s ETL Process Identifier, it is already loaded and, therefore, no processing is required (result X for Reject) - STOP. If the stage reject flag = Y, then no processing (result X for Reject) - STOP. TL Process Identifier is NULL): If the stage delete flag = Y, then insert the record and mark it for a soft-delete (result B for insert with a soft-delete) - STOP. If the stage delete flag <> Y, insert into target (result I for Insert) - STOP. Checks for existing records (where target’s ETL Process Identifier is NOT NULL): If INSERT_ONLY_FLG = Y, then no processing (result X for Reject) - STOP. Checks for new records (where target’s Oracle BI Applications 7.9: Implementation for Oracle EBS 8 - 14Exp_W_GL_REVN_F_Update_Flg Expression (continued) If the stage delete flag = Y and the target delete flag = Y, then no processing (result X for Reject) - STOP. If the stage delete flag = Y and the target delete flag <> Y, then update target and mark for a sofi-delete (result D for Updates with soft-delete) - STOP, If the stage delete flag <> Y, update the target if there is a difference in the comparison columns (result U for Update) - STOP. If there is no difference in the comparison columns, then no processing (result X for Reject) - STOP. Oracle BI Applications 7.9: Implementation for Oracle EBS 8 - 15Fil_W_GL_REvN_F Filter Uses an IIF formula to filter out records that have an UPDATE_FLG value of 'X' and are, therefore, rejected Hane Dat 7) SERVICE REP_ID sung 7 ACC REP ID na + PRODUCTID ing +) PROD SALES ID song =| Tatton | pots Pte | wade enine slo rengornetin [PESTS ee ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. Fil_W_GL_REVN _F Filter A filter transformation filters out rows based on one or more conditions. The filter transformation allows only those rows that meet the filter condition. The rows that do not meet the filter criteria are not processed. In this example, the filter transformation uses an IIF formula to filter out records that have an UPDATE_F'LG value of ‘X’ and are, therefore, rejected. Oracle BI Applications 7.9: Implementation for Oracle EBS 8 - 16the three possible global currencies is involved. ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. mplt_Curcy Conversion_Rates Mapplet This mapplet is responsible for getting the correct exchange rates for a given date, where a currency conversion to any of Nate Dalaipe i — /DOE_CURR cone sting ot sing Earnreayrs tina 056 70 LOC EHH RATE ecina eri oT fatetine » DATASOURCE MUM_ID ‘ecm TENANT ID) sting a Bet_OOC CURR. CODE sting = CURR CODE sting (LTO_L OL ExcH_RaTE ecm EAODOCTOTGLORAL EA RATE cena EXTIDOCTO“GLOBALZECH RATE — decing| BOCPOE TO GLORY PCH RATE decks) mplt_Curcy_Conversion_Rates Mapplet This mapplet is responsible for getting the correct exchange rates for a given date, where a currency conversion to any of the three possible global currencies is involved. Currency night have transactions involving multiple conversions are required because your business currencies. The OBAW stores amounts in the document currency (the currency of the transaction), local currency (the currency in which accounting entries are recorded), and global currencies. Out of the box, Oracle Business Intelligence Applications provides three global currencies, which are the common currencies used by the OBAW. For every monetary amount extracted from the source, the load mapping loads the document currency and local currency amounts into the target table. It also loads the exchange rates required to convert the document amount into each of the three global currencies. Thus, in the target table, there are two amount columns and three exchange rate columns. You will learn more about configuring global currencies in the lesson titled “Configuring Analytical Applications.” Oracle BI Applications 7.9: Implementation for Oracle EBS 8 - 17 ademy Use Only Ci ‘Copyright © 2010, Oracle andior its alate. Al rights reserved. mplt_SIL_GLRevenueFact Mapplet This mapplet is responsible for transforming specific types of columns in the target table W_GL_REVN_F. Jobs done in this mapplet include code-name pair resolution, dimension surrogate key resolution, currency conversion (if required), date to date_wid conversion, stamping of system columns such as W_INSERT_DT, W_UPDATE_DT, and so on. Please note that the mapplet is too complex to display ina slide. You explore the mapplet in the practice for this lesson. Internal & Oracle Academy Use Only 8 3° Oracle BI Applications 7.9: Implementation for Oracle EBS 8 - 20