Some ADF applications have custom properties defined on the ApplicationModule such as EFFECTIVE_DATE or TREE_VERSION.
You can include these custom properties in your application queries, and the Oracle BI Server passes them to the Oracle ADF application.
You cannot use this feature to pass any custom property to your Oracle ADF application. Only certain custom properties, like
TREE_VERSION, are supported.
'PARAM_EFFECTIVE_DATE, ApplicationIdBind, KeyFlexfieldCodeBind'
After you register the custom properties as a repository variable, you can include these variables in queries. For example:
set variable PARAM_EFFECTIVE_DATE=2001-01-01 : SELECT c1 FROM t1;
set variable ApplicationIdBind = '0', KeyFlexfieldCodeBind = 'KFF1' : select_physical ApplicationID, KeyFlexfieldCode, DataSecurityObjectName, SegmentLabelCode from adfdb..."AppModule.KFFHierFilterVO1";
When you are including a custom property of type
PARAM_EFFECTIVE_DATE, the date format for the property value must use the format, yyyy-mm-dd.