Search Results rhs_char_tl_const

Overview

ASO_APR_RULE_STEPS_VL is a view in the Oracle E-Business Suite Order Capture (ASO) module. It exposes the individual rule steps that comprise the condition logic of Oracle Advanced Pricing and Order Capture rules stored in the ASO_APR_RULE_STEPS family of tables. Each row in the view represents a single operand-operator-operand step within a rule, where the left-hand side and right-hand side of the comparison may be an attribute, a function, or a constant value. The _VL suffix indicates that the view joins the base (_B) and translated (_TL) tables and applies a language filter, returning translated descriptive text for the current session language. In practice the view is used to inspect and report on rule definitions, to trace how an attribute or function participates in rule evaluation, and to support integration or diagnostic work where the logic behind a pricing or order-capture rule must be exposed without navigating the EBS user interface.

Underlying Base Objects

The documented view text joins the following base objects:

• ASO_APR_RULE_STEPS_B — the base table holding the rule step records and their operand, operator, and constant metadata.
• ASO_APR_RULE_STEPS_TL — the translation table supplying the translated character constant (RHS_CHAR_TL_CONST).
• ASO_APR_RULES_B and ASO_APR_RULES_TL — the parent rule headers, providing the rule name and description.
• AK_OBJECT_ATTRIBUTES — the AK (Application Object Library) attribute dictionary, used twice (aliases AOA and AOA1) to resolve the left- and right-hand attribute column, table, and base-table column names.
• AK_ATTRIBUTES_VL — the attribute translation/view, again used twice (AA and AA1), to supply the attribute display name and data type.
• ASO_APR_FUNCTION_VL — the function view, used twice (F and F1), to resolve package name, function name, return datatype, and user function name.

Because the view spools AK dictionary data, it depends on the AK object definitions being present and correctly registered for the application. ETRM records no separately documented materialized or base table ownership for the view itself.

Key Columns

• ASO_APR_RULE_STEP_ID, ASO_APR_RULE_ID — primary key of the step and foreign key to the parent rule.
• LOGICAL_OPERATOR, PREFIX, SUFFIX, RELATIONAL_OPERATOR — control how the step is assembled into the rule expression.
• LHS_OPERAND_TYPE, RHS_OPERAND_TYPE — indicate whether the operand is an ATTRIBUTE, FUNCTION, or constant.
• LHS_ATTRIBUTE_FUNCTION, RHS_ATTRIBUTE_FUNCTION — DECODE-derived display of the resolved column or package.function.
• LHS_DATA_TYPE, RHS_DATA_TYPE — the datatype of each operand, derived from the AK attribute or the function return type.
• LHS_AK_OBJECT, LHS_AK_ATTRIBUTE_CODE, LHS_AK_ATTR_APPLIC_ID, RHS_AK_OBJECT, RHS_AK_ATTRIBUTE_CODE, RHS_AK_ATTR_APPLIC_ID — the AK identifiers that link each operand to its object-attribute definition.
• RHS_NUM_CONST, RHS_DATE_CONST, RHS_CHAR_CONST, RHS_CHAR_TL_CONST — typed constant values on the right-hand side.
• CASE_SENSITIVE_FLAG, creation and update audit columns, and the ATTRIBUTE1..15/CONTEXT DFF columns.
• AK_OBJECT, NAME, DESCRIPTION — rule identity from the parent rules tables.

Common Use Cases and Queries

The view is typically queried to review rule logic, to search for every step referencing a given AK object or attribute, or to diagnose why a rule behaves unexpectedly. A representative query for the RHS AK object follows:

• List all steps for a rule, ordered by step: SELECT aso_apr_rule_step_id, lhs_attribute_function, relational_operator, rhs_attribute_function FROM aso_apr_rule_steps_vl WHERE aso_apr_rule_id = :rule_id ORDER BY aso_apr_rule_step_id;
• Find steps using a particular right-hand object: SELECT apr.name, s.rhs_ak_object, s.rhs_ak_attribute_code, s.rhs_attribute_function FROM aso_apr_rule_steps_vl s, aso_apr_rules_vl apr WHERE s.aso_apr_rule_id = apr.aso_apr_rule_id AND s.rhs_ak_object = :object_name;
• Report function-based operands: SELECT aso_apr_rule_step_id, rhs_function_id, rhs_attribute_function FROM aso_apr_rule_steps_vl WHERE rhs_operand_type = 'FUNCTION';

Because the view resolves dictionary references on the fly, queries against it are best used for reporting and investigation rather than high-volume processing.