SQL Override: Mapping Reusability in Informatica

.

In a not so remote past, one of the biggest frustrations for ETL designers was having to replicate a job many times in order to accommodate slight differences depending on the data source. Whether it’s a change in the source table definition or a different clause in the extract SQL, today’s ETL tools have embed capabilities that allow for the reuse of metadata objects to save time and improve maintainability of the workflows.

In this post, I will describe with simple examples how to best reuse ETL mappings in Informatica PowerCenter using the SQL override capability.

Continue reading this post >

Combining Measure with Filter on an Unrelated Dimension

.

Sometimes we need to combine measures from two fact tables in the same report and apply a filter to one of them. If the filter is on a dimension shared by both fact tables; that’s great. However, if the dimension is only related to one of the facts, then we have a problem: Oracle BI would show null values for a measure that’s not related to the dimension.

Imagine that we have two fact tables: Revenue and Budget. Revenue is recorded for Product but also contains information about General Ledger (GL) Account. Budget is defined for Product but not for GL Account so there’s no relationship between them. Our business model is shown in the image below. Of course in a normal repository there would be more dimensions and facts but they have been left out to clarify the example.

Continue reading this post >

Implementing Multiple Hierarchies in a Dimension Mapped to Essbase with Oracle BI

.

If you are using an Essbase data source, you may be interested in learning more about the relationship between Essbase cubes and your Oracle BI EE platform.

It is quite common to find a dimension with multiple hierarchies in a BI project. This is managed in Oracle BI by creating a Dimension object with multiple child levels at a point that converges into the same leaf level.

This looks quite easy when the physical data source is a relational database. However, when the physical data source is an Essbase cube, the process is a bit more complex.

Continue reading this post >

privacy policy - Copyright © 2000-2010 ClearPeaks

topnav