Asian free trial phone chat - Oracle bi updating session variables

To do that, go to the load plan component to which the variables are to be hardcoded, select the Overwrite checkbox and provide the hardcode values for the variables.The screenshot below shows examples of hardcoding DOMAIN_CODE and LOOKUP_TYPE.

oracle bi updating session variables-7

Be sure to set the order in which the session variables should be loaded: This variable we can use for a data restriction on the Logical Table Source of our address table.

Values in repository and session variables are not secure, because object permissions do not apply to variables.

In the Variables tab, right click on the variables and select ‘Refresh Variable Definition’ so that the variable definition in the LP is synchronized with its real definition.

Once this is done, verify that the logical schema is showing CM_BIAPPS11G, and the select statement is showing the embedded SQL in the getcmparam() function.

Parameters can be configured by customers, pre-seeded in the ETL code, or maintained internally: To ensure correct values to be used in ETL, variables are refreshed at run time.

A variable can be refreshed in either a package or a load plan.

They will still inherit the value refreshed in the parent step.

Overriding Rule (2) (unlikely to happen but it exists) If a variable is refreshed both in a package and in a load plan, then the value refreshed from the package will override the value refreshed from the load plan.

ODI fails to interpret QUALIFY at load plan level in some cases.) Examples: IS_INCREMENTAL, LAST_EXTARCT_DATE Definition: Variables whose values are configured in BIACM by customers.

(In other words, the values of these variables come from BIACM.

The refreshing logic of such a variable uses a UDF to extract its value from BIACM.) Examples: UPDATE_ALL_HISTORY, TYPE2_FLG For a complete list of ODI variables, please refer to this post.

Tags: , ,