Learn about the Endeca ODI package, interface, and procedures. Source and target data stores delivered with the BI Applications installation include all Oracle BI Applications repository (RPD) logical columns. These may be customized to add or remove mappings to meet business requirements.
New Flexfields
The flexfield properties in the ODI Data Store columns configure the Endeca Server column settings. For example, the Endeca properties define whether the value of a column is text searchable, value searchable, and so on. These properties all begin with the "Endeca Property" as a prefix.
Limitations
Some complex metadata from the RPD BMM layer cannot be extracted and loaded into Endeca Server, which includes:
The dimension
Aggregation rules
Complex expressions
Multiple Logical Table source
Content of Logical source
The reports with same logical columns in OBIEE and Endeca Studio have different query results because of the missing metadata. You can use Endeca EQL to imitate the features of the OBIEE model.
Packages
Each Subject Area (SA) has the following package design pattern:
ENDECA_DATADOMAIN variable: Name of SA Data Domain, for example, OEID_Project_Cost.
ENDECA_DATADOMAIN_PROFILE variable: Data Domain profile. If blank, the default Data Domain profile is used.
ENDECA_DATALOAD_LOG_FILE_PATH variable: Path/name for Log File, for example OEID_Project_Cost_ENDECA_DATALOAD.LOG.
ENDECA_OBIEE_SQL_PREFIX variable: Optional Oracle BI EE prefix, usually set for currency, for example, set variable PREFERRED_CURRENCY='Global Currency 4'.
ETL_PREDICATE_EXTRACT variable: Optional Oracle BI EE where clause (filter) condition. The default is 1=1.
TLP_OEID_SA_Load_Tgt_Schema interface, for example, TLP_OEID_Project_Cost_Load_Tgt_Schema
Interface does not load data (has filter set to 1=2).
Interface creates the Data Domain if it does not already exist.
Mapping contains all of the columns for the Subject Area and loads only the schema.
Caution:
If any columns are modified in the data loading interfaces, this load target schema interface's columns needs to be updated and maintained.
There is an IKM option to disable the "APPLY SCHEMA" option to preserve attribute configurations made in Studio.
TLP_OEID_SA_Fact Table Name interfaces, for example, TLP_OEID_Project_Cost_Fact_Project_Cost.
Interface or interfaces (some Subject Areas may have more than one) extracts data from Oracle BI EE and loads Endeca.
One interface exists per dataset collection name, for example, "Fact_Project_Cost"
Each interface loads a single denormalized fact star schema.
Each interface truncates the collection data before each load, so each load is a destructive load and not incremental.
Each interface uses the following:
LKM: LKM BIAPPS OBIEE to SQL BMMFETCH
IKM: IKM SQL to Endeca Server
Data Stores
Source: Oracle BI Applications\Oracle BI Applications Business Model\Core
Target: Oracle BI Applications\Oracle BI Applications Endeca\Core
Endeca Web Service Procedure
The procedure requires the same jars used by the SQL to Endeca Server IKM.
Only Subject Areas that are sample apps have the Endeca Web Service Procedure added to load views as the final step in the Package.
The Endeca Web Service Procedure can optionally be included in any Subject Area, or even be run standalone in its own ODI Package.