Informatica SDE and SIL mapping

Source Dependent extract(SDE) and Source Independent loading mappings(SIL)? 
you know they are informatica mappings used for specific requirements. 
SDE loads data to stage area, whereas bulk load is used, 
SIL loads data from srage area to target area, whereas normal load is used. 
Have you guys ever worked with these types of mapping? What are the key transformations used in these mappings?  

SDE_* - Workflow loads data into the staging table.Staging table will 
not have any index defined on them and always the load into the staging 
table will be a truncate and load.Since there are no index defined "Bulk" 
load mode is being used. 

SIL_* - You can find two SIL_* workflows in the Workflow Manager.During 
a full load the workflow (SIL_*_Full) will be invoked from DAC and the 
target table is truncate ,indexes are dropped ,data is loaded in 'Bulk' mode 
and then the indexes are rebuild.Durring incremental load , the workflow 
(SIL_*) will be invoked which would just insert/update the incremental 
data.Since the amount of data during incremental load is minimal compared to 
full load this would run in 'Normal' mode.If indexes are present on a table 
"BULK" mode does not work. 


SDE 
During ETL, the preconfigured Informatica workflows/mappings, identified as the SDE (Source Dependent Extract) mappings, extract data from source OLTP database tables by querying views created by DAC with names starting with V_* and load the data into staging tables on the SRMW database. The view definition will change depending on whether the ETL run is a full load or incremental load run. In case of a full load, it would be a SELECT * FROM <base table>”. While in the case of an incremental load, the view definition joins the base table with the Image tables. This is done to minimize the impact and duration of the ETL process on the OLTP database. 
DAC drops and creates these views during each run (unless specified explicitly in one of the System properties called Drop Create Views Always . These views can be dropped any time and DAC will create them when necessary. 
SIL 
Query data from the staging tables, perform final transformations, and load the dimension and fact tables. Because these processesare independent of the original OLTP database, they are used for data loading from any sources when the staging tables have been populated.  


"Are both types of mapping predefined? Or we have to create mappings in informatica, if so, what are the key transformations?" 

All of these mappings are pre-built as part of the Oracle BI Apps. The BI Apps provides a complete data warehouse data model and the ETL routines to load this data model plus the logical content in OBI EE to query and present this data to users. The only reason you would create your own mappings is to map to sources that are not already supported by the BI Apps to load into the existing data warehouse tables or to load into brand new data warehouse tables that you may build to meet gaps in the BI Apps. 

Very Basic of OBIA

ANSWERS

1) What are the Oracle Business Intelligence Applications (BI Apps)?
It is a complete, end-to-end BI environment covering the BI platform and pre-packaged analytic applications.

The platform includes a server and end user tools such as dashboards, query and analysis, enterprise reporting, disconnected access to the data -- all supported by a unified, model-centric server architecture.

On top of this platform, we have a set of analytic applications consuming the operational data sources and delivering greater insight to larger user communities across the organization via dashboards, query and analysis, and alerts.


2) What technology components do I need to buy to run the BI Apps?
- A database to host the Datawarehouse
- Oracle BI Suite EE Plus or Oracle BI Suite SE1 (OBIEE)
- ETL component options to OBIEE, either Oracle Data Integrator* or Informatica
- Application content per application

*Oracle Data Integrator (ODI) is currently only available for certain release against a specific release of a source system. Future plans are to have ODI fully available.


3) What Application content is available for the BI Apps?

ERP Analytics  - Oracle Financial Analytics - Oracle Procurement and Spend Analytics - Oracle Human Resources Analytics - Oracle Supply Chain and Order Management Analytics - Oracle Spend Classification Analytics - Oracle Project Analytics CRM Analytics - Oracle Sales Analytics - Oracle Service Analytics - Oracle Marketing Analytics - Oracle Contact Center Analytics - Oracle Loyalty Analytics - Oracle Price Analytics Industry Applications - Oracle US Federal Financial Analytics 4) Which systems can BI Apps source its data from? Oracle provides pre-built adapters for Oracle eBusiness Suite, Peoplesoft, JD Edwards, SAP and Siebel. In additional to these pre-built adapters Oracle provides the Universal adapters that enable any other source system to be a source for the Datawarehouse. 5) I have customised my source system; can I extend the BI Apps for these customisations? Oracle has designed the BI Apps to be extendable, from the source system mappings, the warehouse model, the BI Modelling layer to the Presentation objects. Oracle provides a methodology for extensions in the supplied guides. One of the most common extensions is the inclusion of descriptive flexfields for eBusiness suite sources. 6) How do I deploy the BI Apps? The BI Apps can be deployed as follows - Standalone mode - Integrated with Portal via JSR-168/WSRP - Embedded with the transaction system within a dashboard view - Embedded with the transaction system contextually within a transactional view 7) Can I have the same security as my transactional system? The BI Apps can be integrated with the source system to enable a smooth transition for users maintaining the user’s security context as they move from the transactional system to BI Apps and back into the transactional system. 8) Does a BI Apps implementation take as long as a traditional Datawarehouse implementation? A traditional Datawarehouse implementation will typically take in the region of 18 months + to deliver, because much of the time consuming effort has already been developed. A BI Apps project will usually have release cycles every 100 days or so. A minimal configuration implementation can have a development system up and running in a few weeks. 9) What is the DAC? DAC stands for Data Warehouse Application Console. It is an essential component of Oracle BI application architecture. DAC serves the following purposes: - DAC is a metadata driven administration and deployment tool for ETL and data warehouse objects - It is used by warehouse developers and the ETL Administrator - Manages Application Configuration - Manages the execution of warehouse loads - Provides a monitoring facility 10) Where can I get some more information about the content of the BI Applications? The following links on the Oracle support site are a good starting point: Content Guide: https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=832690.1 Oracle® Business Intelligence Applications Metrics Reference Guide Release 7.9.6 https://metalink3.oracle.com/od/faces/secure/km/DocumentDisplay.jspx?id=846917.1 Oracle® Business Intelligence Applications ETL Data Lineage Guide Release 7.9.6,7.9.6.1 (Doc ID 829385.1) https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=829385.1

11) How is BI Apps made aware of my source system configurations?
During the configuration of the BI Apps configurations are entered as parameters in the DAC and by completing CSV files that define your source system configs. These CSVs are then picked up during the ETL run and used to populate the warehouse.


12) Does my warehouse have to be an Oracle database?
No, the BI Apps are certified against many databases including DB2 and Terradata.


13) Can I view my data indifferent currencies?
The BI Apps hold both the transactional and local currency amounts. In addition there is the possibility to have up to 3 reporting currencies with basic configuration. The data model stores five currency versions in each fact as follows:

- Group Amount (x3) : Corporate Currency Amount
- Local Amount : Local Country / Region Currency Amount
- Document Amount : Actual Transaction Currency Amount

Support for different exchange rate types through ETL configuration

- Corporate
- User


14) I am a multi-country organisation and would like to have the ability to display the BI Apps in the local language, is this possible?
Yes, there is the facility to have the OBIEE components displayed in multi-language and the BI Apps can be configured to display the objects in multi-language. To display the data in multi-language is a customisation effort that will require extending the warehouse to include translation tables.

Configuration Steps for Financial Analytics for Oracle EBS

Configuration Steps for Financial Analytics for Oracle EBS

This section contains configuration steps before you do a full data load that apply to Oracle EBS. It contains the following topics:

• Section 5.2.2.1, "About Configuring Domain Values and CSV Worksheet Files for Oracle Financial Analytics"
• Section 5.2.2.2, "How to Configure Transaction Types for Oracle General Ledger and Profitability Analytics (for Oracle EBS R12)"
• Section 5.2.2.3, "How to Configure Transaction Types for Oracle General Ledger and Profitability Analytics (for Oracle EBS R11i)"
• Section 5.2.2.4, "How to Specify the Ledger or Set of Books for which GL Data is Extracted"
• Section 5.2.2.5, "Oracle EBS Currency Balance Types"

Basic of Oracle Financial Analytics

Why use Oracle Financial Analytics?
In additon to the above benefits, Financial Analytics integrates with Oracle E-Business Suite (EBS), Peoplesoft, JD Edwards, and SAP, which allows companies to implement the technology, filled with years of research and best practices, quickly and with a LOT less risk.

What is Oracle Financial Analytics comprised of?
By listing some of the content of the BI module, without going into too much detail, you will be able to get a sense for the type of information and see the vast amount of content included.

————————
6 Dashboards
————————
General Ledger: provides information about the key areas of required for financial management including balance sheet, cash flow, liquidity, expenses, working capital and liquidity.

Payables: provides information about how effectively and efficiently the company is meeting its payment obligations.

Receivables: provides information about effectively and efficiently the company is collecting payment from sales.

Projects: provides financial information about projects.

Profitability: provides imformation for the key areas for profitability including margins by customer and product, profit and loss statements, revenues, and the various “Return-On metrics” such as ROA, ROI, ROE.

US Federal Financial Performance: provides information about budgets and payments

————————
36 dashboard pages – broken out by dashboard below:
————————
General Ledger: Overview, Balance Sheet, Cash Flow, Budget vs Actual, Asset Usage, Liquidity, Financial Structure, GL Balance, Trial Balance

Payables: Overview, AP Balance, Payments Due, Effectiveness, Payment Performance, Supplier Report, Invoice Details, All AP Transactions

Receivables: Overview, AR Balance, Payments Due, Effectiveness, Payment Performance, Customer Report, Invoice Details, All AR Transactions

Projects: Project Invoices

Profitability: Overview, P&L, Margins, Revenue, Products, Customers

US Federal Financial Performance: Budget Summary, Budget Details, Budget Spending, Payables

————————
255 Reports – A small sampling of the reports include:
————————
Cash Flow Summary
Monthly & Quarterly Cash Flow
Net Working Capital Summary
Operating Cycle and Cash Cycle
Monthly & Quarterly Balance Sheet
Budget vs Actual – Current & YTD Operating Expenses
Top 10 Categories by Expense Variance -and- Top 10 Cost Centers by Expense Variance
Payables Turnover -and- Receivables Turnover
Cash Ratio
Days Cash in Hand
Quick Ratio -and- Current Ratio
Debt Coverage
Debt to Asset -and- Debt to Equity
GL Account Balance -and- Trial Balance

————————
488 Metrics – A small sampling of the metrics include:
————————
Receivables 
AR Balance: • DSO • Closing Group Amt • Credit Limit Used % • Total AR Overdue Amt
AR Aging: • AR Aging 1-30 Amt • AR Due 1-30 Amt • AR Overdue 1-30 Amt
Payment Performance: • AR Payment Days • AR Weighted Days • Times Paid Before Due
AR Transactions: • AR Avg Invoice Amt • AR Credit Memo Amt

Payables 
AP Balance: • DPO • Closing Group Amt • Total AP Overdue Amt • Overdue Amt to Total %
AP Aging: • AP Aging 1-30 Amt • AP Due 1-30 Amt • AP Overdue 1-30 Amt
Payment Performance: • AP Payment Days • AP Weighted Days • Times Paid Before Due
AP Transactions: • AP Avg Invoice Amt • AP Avg Payment Amt

General Ledger 
Balance Sheet: • Cash • Accounts Receivable • Debt to Equity Ratio • Current Ratio
Asset Turnover: • AR Turnover • AP Turnover • Inventory Turnover • Cash Cycle • Fixed Assets Turnover
Cash Flow: • Operating Cash Flow • Investing Cash Flow • Financing Cash Flow • Net Cash Flow

Profitability 
Profitability Returns: • Return on Equity • Return on Assets • Return on Capital
Margins: • Gross Margin % • Operating Margin % • EBT Margin % • Net Income Margin %
Product Profitability: • Revenue • Product Gross Profit • Product Operating Profit
Customer Profitability: • Revenue • Customer Gross Margin

Who will use and benefit from Financial Analytics?
CFOs, Controllers, Accounting Managers, Finance Analysts, Department Heads, Payables and Receivables Managers, Payables & Receivables Analysts, Project Managers, Project Accountants, and much more.

Where can I find more information?
More information about Oracle Financial Analytics can be found here:
http://www.oracle.com/us/solutions/business-analytics/analytic-applications/business-role/financial-analytics/overview/index.html
And more information about Oracle Business Intelligence in general can be found here:
http://www.oracle.com/us/solutions/business-analytics/overview/index.html

Customizing the Oracle Business Analytics Warehouse

• Section 17.1, "Overview of Customization in Oracle Business Intelligence Applications"
• Section 17.2, "Oracle Business Analytics Warehouse Customization Scenarios"
• Section 17.3, "Category 1 Customizations: Adding Columns to Existing Fact or Dimension Tables"
• Section 17.4, "Other Types of Customizations Requiring Special Handling"
• Section 17.5, "Category 2 Customizations: Adding Additional Tables"
• Section 17.6, "Category 3 Customizations: Adding New Data as a Whole Row into a Standard Dimension Table"
• Section 17.7, "Configuring Extracts"
• Section 17.8, "Configuring Loads"
• Section 17.9, "Configuring Slowly Changing Dimensions"
• Section 17.10, "About Stored Lookups"
• Section 17.11, "Codes Lookup"
• Section 17.12, "About Resolving Dimension Keys"
• Section 17.13, "About Domain Values"
• Section 17.14, "Configuring the Domain Value Set with CSV Worksheet Files"
• Section 17.15, "Configuring the Domain Value Set Using Informatica PowerCenter Designer"
• Section 17.16, "Configuring Conformed Dimensions"

High-Level Installation and Setup Task List (OBIA, Informatica,OBIEE & DAC)

 High-Level Installation and Setup Task List

This section describes the high-level tasks that you must complete in the specified order to install and set up Oracle BI Applications.

Note: The tasks in the following list form Step 2 in Section 2.4, "Roadmap to Installing, Setting Up, and Configuring Oracle BI Applications".

You must complete these tasks in the order listed below.

1. Before you start, do the following:
   1. Follow the appropriate preinstallation steps in Chapter 3, "Preinstallation and Deployment Requirements for Oracle BI Applications."
   2. On the target installation machine, make sure that you have a valid Oracle Middleware Home (MW_HOME) that contains a valid Oracle BI EE Infrastructure Home (ORACLE_HOME). For more information about Home locations, see Section 4.2.1, "Summary of Oracle Home Locations Used in this Guide.".
      You must make sure that:
      - The BI EE system is installed and configured using the Simple or Enterprise installation type from the Oracle BI EE installation.
      - The WebLogic Administration Server and NodeManager needs to be running. The Oracle BI Applications installer validations check that the WebLogic Administration Server and NodeManager are running. If these two processes are not running, then the Oracle BI Applications installation will not proceed.
   3. Make sure that you satisfy the Informatica PowerCenter requirements that are specified in Section 4.3.2, "Informatica PowerCenter Requirements."
   4. Make sure that you satisfy the Code Page requirements that are specified in Section 4.3.3, "Code Page and Data Movement Requirements."
   5. Make sure that you perform the mandatory preinstallation tasks that are specified in Section 4.5, "Setup Task: Preinstallation Tasks." The preinstallation tasks are the following:
      - Section 4.5.1, "Create Databases for Oracle BI Applications and Informatica PowerCenter Components"
      - Section 4.5.2, "Install and Configure Database Connectivity Software"
      - Section 4.5.3, "Perform Prerequisites for Informatica PowerCenter Installation"
2. Run the Oracle BI Applications 7.9.6.4 installer on a Windows machine that contains a valid Oracle BI EE Infrastructure Home (ORACLE_HOME). For more information, see Section 4.6, "Setup Task: Installing the Oracle BI Applications files."
   1. Make sure that a complete installation of Oracle Business Intelligence Enterprise Edition is installed on the machine on which you want to install Oracle BI Applications. For more information, see Section 4.3.1, "Oracle Business Intelligence Infrastructure Requirements for the Oracle BI Applications Installer."
      Note: This instance of Oracle Business Intelligence Enterprise Edition does not need to be the functional version that you will use to deploy dashboards in your live system. This instance is only required to enable the Oracle BI Applications installer to install the Oracle BI Applications files on a machine.
3. Install Informatica PowerCenter Services and Client Version 9.0.1 Hotfix 2 software and set up the Informatica components for use with Oracle BI Applications. For more information, see Section 4.7, "Setup Task: Installing and Setting Up Informatica PowerCenter."
   Note:

   Informatica PowerCenter Client must be co-located with DAC Client. Informatica PowerCenter Server must be co-located with DAC Server.
   Note:

   See the System Requirements and Supported Platforms for Oracle Business Intelligence Applications for information about additional hot fixes or emergency bug fixes that might be required to support the current version of Informatica.
   1. Install Informatica PowerCenter Client as described in Section 4.7.1, "Installing Informatica PowerCenter Client Tools (Windows)."
   2. Install Informatica PowerCenter Services as described in Section 4.7.2, "Installing Informatica PowerCenter Services."
      During the installation, you are prompted to create an Informatica Domain using a suitable database account. For information about creating a suitable database account, see Section 4.5.1, "Create Databases for Oracle BI Applications and Informatica PowerCenter Components".
   3. Create the Informatica Repository Service as described in Section 4.7.3, "Creating the Informatica Repository Service."
   4. Create the Informatica Integration Service as described in Section 4.7.4, "Creating the Informatica Integration Service."
   5. Restore the Pre-built Informatica Repository as described in Section 4.7.5, "Restoring the Pre-built Informatica Repository."
   6. Configure the Informatica PowerCenter components as described in Section 4.7.6, "Configuring Informatica PowerCenter Components."
4. Restore the pre-built Informatica Repository file provided with Oracle BI Applications. This file includes ETL repository objects, such as mappings, sessions, and workflows. For more information, see Section 4.7.5, "Restoring the Pre-built Informatica Repository."
5. Install the DAC Client and Server Platform. The DAC Platform is installed by the Oracle Data Warehouse Administration Console (DAC) installer. For more information, see Section 4.8, "Setup Task: Installing and Setting Up the DAC Platform."
   Note:

   Informatica PowerCenter Client must be co-located with DAC Client. Informatica PowerCenter Server must be co-located with DAC Server.
   1. (On Windows) Install DAC as described in Section 4.8.1, "Installing DAC on Windows Using the DAC Installer."
   2. (On UNIX) Install DAC as described in Section 4.8.3, "Deploying the DAC Server on Linux or UNIX."
   3. Install JDBC Drivers for DAC as described in Section 4.8.4, "Installing a JDBC Driver for DAC Database Connectivity."
   4. (Siebel-specific) Create ODBC Connections for the DAC Client as described in Section 4.8.5, "(Siebel specific) Creating an ODBC Database Connection for a Siebel Source System."
   5. Install Informatica pmcmd and pmrep as described in Section 4.8.6, "Setting Up pmcmd to Enable Communication Between Informatica PowerCenter and DAC."
   6. Install DAC Metadata files as described in Section 4.8.7, "Installing DAC Metadata Files."
6. Log into DAC and Import Metadata into the DAC Repository. For more information, see Section 4.9, "Setup Task: Log into DAC for the First Time, Configure DAC Server, and Import Metadata into the DAC Repository."
7. Create the Oracle Business Analytics Warehouse tables. For more information, see Section 4.10, "Setup Task: Creating the Oracle Business Analytics Warehouse Tables."
8. Configure the DAC Server. For more information, see Section 4.11, "Setup Task: Configuring the DAC Server."
9. Configure DAC Integration Settings. For more information, see Section 4.12, "Setup Task: Configuring DAC Integration Settings."
10. Create Relational Connections in Informatica Workflow Manager, as specified in Section 4.13, "Setup Task: Configuring Relational and Application Connections in Informatica Workflow Manager."
11. Configure the Oracle BI Repository connections, as specified in Section 4.16, "Setup Task: Configuring the Oracle BI Repository Connections."
12. Copy the Oracle BI Applications RPD and BI Presentation Catalog to a suitable Oracle BI EE Machine and deploy them. For more information, see Section 4.17, "Setup Task: Deploying the Metadata Repository and Presentation Catalog."
13. Configure the SiebelUniCodeDB Custom Property, as specified in Section 4.14, "Setup Task: Configuring the SiebelUnicodeDB Custom Property."
14. Set up DAC to receive email notification. For more information, see Section 4.15, "Setup Task: Setting Up DAC to Receive Email Notification."
15. If your deployed BI EE system with Oracle BI Applications is different from the BI EE system used to install Oracle BI Applications, then you must apply the security policy to the BI Domain on the deployed BI EE system by following the steps in Section 4.18, "Setup Task: Applying the Oracle BI Applications Security Policy to the BI Domain.".
    If your deployed BI EE system with Oracle BI Applications is the same as the BI EE system used to install Oracle BI Applications, then the Oracle BI Applications installer performs this configuration automatically.
16. Perform required post-installation tasks that are specific to your deployment, as follows.
    • Section 4.19.1, "Configuring Security-Related Initialization Blocks."
    • Section 4.19.2, "Setting DAC Source System Parameters."
    • Section 4.19.3, "Creating Stored Procedures for DB2-UDB."
    • Section 4.19.4, "Siebel-Specific Configuration Tasks."
    • Section 4.19.5, "Teradata-Specific Configuration Tasks."
    For more information, see Section 4.19, "Setup Task: Additional Configuration Tasks."

First Oracle Cloud Conference@Dubai

Application Services

Oracle’s application services are best-in-class and span numerous mission-critical business functions such as sales and marketing, customer experience, human capital management, and enterprise resource planning.

·         Enterprise Resource Planning Try

·         Planning and Budgeting Preview

·         Human Capital Management Try

·         Talent Management Try

·         Oracle and SelectMinds

·         Sales and Marketing Try

·         Customer Service and Support Try

Social Services

Oracle Social Relationship Management (SRM) services helps organizations use social data and channels to drive greater customer understanding, make better business decisions, and strengthen relationships.

·         Social Network Learn more

·         Social Marketing Learn more

·         Social Engagement and Monitoring Learn more

Platform Services

Oracle’s platform services enable rapid and effective development, testing, and deployment of enterprise-class business applications on the industry’s #1 database and #1 application server.

·         Java Try

·         Database Try

·         Developer Preview

Common Infrastructure Services

Oracle's infrastructure services provide proven, reliable, secure infrastructure for all platform, application, and social services.

·         Storage Preview

·         Messaging Preview

Other Cloud Solutions

Oracle also provides comprehensive products for cloud providers to build and manage private clouds, and managed cloud services to help customers fully manage and/or host their clouds.