Data Validation with BI Applications and Siebel

The Informatica based BI Applications Version (from 7.8.x) were shipping a dedicated DAC (DataWarehouse Administration Console) Execution Plan to validate the data within the Siebel Application that could be used to ensure the data consistency when/before loading the data into the Warehouse.

DAC flatfiles conn

However, this was only available for the Siebel Data Source and not for any other of the Oracle Business Applications.

In general, this was always something customers wanted to have for their other Oracle Business Applications, but was never made available. Probably with the reason that a Standard Application (even if customized) should not make any data inconsistency’s possible.

However, most Projects could benefit from an out-of-the-box available data validation.

So, what did the Exception Reports check within the standard Source?

  • List of Values – Identifies gaps and overlaps for certain LOV types
  • Exchange Rates – Currency Exchange rates that do not change over a period of time
  • Hierarchies -that have circular references are flagged as exceptions. Additionally, since the Data Warehouse supports only a certain number of levels for hierarchies. If there are Hierarchies that have more than that defined, they are flagged as exceptions.

(The Official PDF Documentation can be found here). As can be seen from above, these checks were focused on Application Administration areas or technical limitations. Thus, areas were mistakes can happen more easily.

For the new ODI based Version these standard checks are not available anymore – also for Siebel. The new mechanism to write and perform these checks is called “Flow Control”.

A Full feature Implementation would probably not only check the source for the purpose of loading the Business Warehouse, but the source in general. Within Oracles offering, this is the Oracle Enterprise Data Quality.