Results for “longlist_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_XPRT_BUS_VARIABLES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC - Contracts Core product. It exposes the set of contract expert business variables that are eligible for use by the Contract Expert rules engine. The view's defining characteristic is its filtering logic: it returns only those business variables that are flagged as contract expert enabled (CONTRACT_EXPERT_YN = 'Y'), are of variable type 'S', and are not of datatype 'D'. Because the view is limited to this curated subset, it provides consuming processes with a ready-made list of variables that can be referenced when authoring, evaluating, or validating Contract Expert rules and conditions.

In the context of EBS 12.1.1 and 12.2.2, the view functions as a metadata access point rather than a transactional one. It is commonly used by Contract Expert configuration screens, extensions, and custom reports that need to enumerate the permissible contract expert variables and their associated value set characteristics without interrogating the underlying business variable definitions directly.

Underlying Base Objects

The view is defined over two documented base objects. The primary source is OKC_BUS_VARIABLES_V, itself a view over the business variables maintained for Contracts Core. The second source is FND_FLEX_VALUE_SETS, referenced through a synonym and joined using an outer join (XPRT_VALUE_SET_NAME = FLEX_VALUE_SET_NAME(+)). The outer join ensures that a variable is still returned even when no matching flex value set exists, in which case the value set attributes resolve to null. The join is used to enrich each variable with its value set properties, such as the longlist flag, validation type, and flex value set identifier.

Key Columns

• VARIABLE_CODE — the internal code that uniquely identifies the business variable; used programmatically in rules and expressions.
• VARIABLE_NAME — the user-facing name of the variable presented in Contract Expert configuration.
• DESCRIPTION — descriptive text explaining the purpose or intended use of the variable.
• VALUE_SET_NAME — the name of the associated flex value set (aliased from XPRT_VALUE_SET_NAME), defining the permissible values for the variable.
• VARIABLE_DATATYPE — the datatype of the variable; datatype 'D' (date) variables are excluded by the view filter.
• LONGLIST_FLAG — indicates whether the value set supports a longlist presentation of values.
• VALIDATION_TYPE — the validation method applied by the value set.
• FLEX_VALUE_SET_ID — the internal identifier of the associated flex value set.

Common Use Cases and Queries

The view is typically queried to list available contract expert variables, to inspect their value set configuration, or to drive downstream logic that depends on the value set. A representative query retrieves the variables and their validation characteristics:

• SELECT variable_code, variable_name, value_set_name, validation_type FROM okc_xprt_bus_variables_v WHERE variable_datatype = 'N';
• SELECT variable_code, variable_name FROM okc_xprt_bus_variables_v ORDER BY variable_name;
• Joining to FND_FLEX_VALUES by FLEX_VALUE_SET_ID to enumerate the permissible values for a given contract expert variable.

Typical scenarios include building custom Contract Expert validation reports, validating rule conditions against configured variables, and integrating contract expert variable metadata into external rule authoring tools.