Search Results jtf_brm_expression_lines_u1

Overview

The JTF.JTF_BRM_EXPRESSION_LINES table stores the atomic, line-level components of simple business rule definitions consumed by the Business Rule Monitor (BRM) within Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a single predicate or connective fragment — a left operand, an operator, a right operand, and the surrounding parentheses and boolean connectors — that together compose the conditional logic of a business rule. The table is owned by the JTF schema, is registered under FND Design Data as JTF.JTF_BRM_EXPRESSION_LINES, and resides in the APPS_TS_SEED tablespace with a status of VALID.

While BRM expression lines persist the individual rule fragments, the fully assembled and generated complex view definition derived from these lines is stored separately in JTF_BRM_RULES_B. From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is link, suggesting this entity primarily resolves relationships between a rule and its constituent expression components, anchored by a surrogate key and connected to parent rule and security metadata.

Key Information Stored

The physical schema documents 37 columns. The most significant, business-relevant columns are:

• EXPRESSION_LINE_ID — surrogate primary key and sole unique-index column (JTF_BRM_EXPRESSION_LINES_U1), uniquely identifying each expression line. Because it is the only documented unique index, it is also the business-key candidate.
• RULE_ID — foreign key linking the line to its parent business rule (JTF_BRM_RULES_B); non-unique indexed via JTF_BRM_EXPRESSION_LINES_N1.
• LEFT_VALUE and RIGHT_VALUE — the operands of the predicate. Values are provided but not validated through lookups against AK_ATTRIBUTES_VL; both are indexed (_N6, _N7).
• BRM_OPERATOR_CODE — the comparison operator (e.g., equals, greater-than), validated through FND_LOOKUPS.
• BRM_BOOLEAN_OPERATOR_CODE — the AND/OR connector joining predicates, validated through FND_LOOKUPS.
• BRM_LEFT_PARENTHESIS_CODE and BRM_RIGHT_PARENTHESIS_CODE — grouping tokens that control evaluation precedence, validated through FND_LOOKUPS.
• BRM_LEFT_PARENTHESIS_TYPE, BRM_OPERATOR_TYPE, BRM_RIGHT_PARENTHESIS_TYPE, BRM_BOOLEAN_OPERATOR_TYPE — type discriminators, each non-unique indexed.
• SORT_SEQUENCE — determines evaluation order of lines within a rule.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data segregation.
• OBJECT_VERSION_NUMBER, APPLICATION_ID, the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), and ATTRIBUTE_CATEGORY plus ATTRIBUTE1–ATTRIBUTE15 for extensibility.

Common Use Cases and Queries

The principal use case is reconstructing and auditing the logic behind a business rule. Because expression lines carry ordering and grouping metadata, they are read in SORT_SEQUENCE order and joined to lookup meanings to render human-readable rule conditions.

Retrieve all expression lines for a rule in evaluation order:

• SELECT expression_line_id, sort_sequence, brm_left_parenthesis_code, left_value, brm_operator_code, right_value, brm_boolean_operator_code FROM jtf.jtf_brm_expression_lines WHERE rule_id = :rule_id ORDER BY sort_sequence;

Decode operators and connectors to their lookup meanings for reporting:

• SELECT el.expression_line_id, fl1.meaning operator_meaning, fl2.meaning boolean_meaning FROM jtf.jtf_brm_expression_lines el LEFT JOIN fnd_lookups fl1 ON fl1.lookup_code = el.brm_operator_code LEFT JOIN fnd_lookups fl2 ON fl2.lookup_code = el.brm_boolean_operator_code WHERE el.rule_id = :rule_id;

Additional scenarios include identifying rules referencing a particular attribute value (querying LEFT_VALUE/RIGHT_VALUE indexed columns), validating that expression lines exist for every active rule, and migrating or cloning rule definitions between environments alongside JTF_BRM_RULES_B.

Related Objects

• JTF_BRM_RULES_B — parent rules table; joined via JTF_BRM_EXPRESSION_LINES.RULE_ID = JTF_BRM_RULES_B.RULE_ID. Stores the generated complex view definition.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, governing row-level security.
• FND_LOOKUPS — supplies and validates the parenthesis, operator, and boolean operator codes.
• AK_ATTRIBUTES_VL — conceptually the source of LEFT_VALUE and RIGHT_VALUE attribute references, though not enforced by validation.
• FND_USER — referenced by the WHO columns CREATED_BY and LAST_UPDATED_BY.