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

Anatomy of a Typical SDE Mapping

SDE mappings select from source transactional tables and load warehouse staging tables.

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.
Business Component Mapplet
Extracts data from tables in the source system

Business Component Mapplet

1. This mapplet, mplt_BC_ORA_GLRevenueFact, extracts revenue data from tables in the
Oracle E-Business Suite source system.
2. Notice that there are three component types in the Mapplet and the data flow is from
left to right. The three component types are source definition, source qualifier, and
Mapplet output transformation.
3. 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.
4. 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.
5. The source qualifier transformation represents the rows that the Informatica
Integration Service reads when it runs a session.
6. 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.
7. In this example, the MAPO_GL_REVENUE_EXTRACT mapplet output transformation is
the “target” of this mapplet and receives data from the SQ_GL_REVENUE_EXTRACT
source qualifier.
8. The MAPO_GL_REVENUE_EXTRACT mapplet output transformation passes output
from the mapplet to the next transformation in the mapping
(Exp_W_GL_REVN_FS_Integration_Id expression in the example for this lesson).