Results for “okc_condition_lines_v”

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

Overview

OKC_CONDITION_LINES_V is a concurrent-safe, language-aware view in the Oracle E-Business Suite Contracts Core (OKC) module, owned by the APPS schema. It exposes the condition line definitions that form the rule-based structure of Oracle Contracts and Oracle Trade Management conditions. In ETRM terminology, a "condition" is a logical expression evaluated at runtime against contract or transaction data — for example, determining whether a discount applies, whether an approval routing is triggered, or whether a term is eligible for a given party or product combination. The view consolidates the operational columns of the condition line base table with the descriptive text from the translation table, resolving the current session language automatically through USERENV('LANG').

Because the underlying records are protected and multilingual, direct queries against the base tables are discouraged. OKC_CONDITION_LINES_V provides a stable, read-only reporting and integration surface for both EBS 12.1.1 and 12.2.2, making it suitable for BI Publisher reports, custom OAF pages, and inbound/outbound interface extracts that must present condition logic in the user's language.

Underlying Base Objects

The view is defined over two documented base objects:

• OKC_CONDITION_LINES_B — the base (language-independent) table holding condition line identifiers, relational and logical operators, parentheses, tolerances, sort sequence, and the FK references to the parent condition header (CNH_ID) and to AAE/PDF/contract master entities.
• OKC_CONDITION_LINES_TL — the translation table supplying the language-specific DESCRIPTION and SFWT_FLAG (the "seed with translation" indicator). The join is CNLB.ID = CNLT.ID AND CNLT.LANGUAGE = USERENV('LANG').

The view is an equi-join of the two, therefore returning exactly one row per condition line for the session language, provided a translation exists for that language. It is a synonym in APPS referencing the same definition visible to other EBS schemas through grants.

Key Columns

• ROW_ID — the physical ROWID of the base-table row; useful for row-level updates in custom code.
• ID / OBJECT_VERSION_NUMBER — the primary key and optimistic-locking version; required for any DML or REST-style update.
• CNH_ID — foreign key to the condition header, linking lines back to the parent condition definition.
• CNL_TYPE — the condition line type (e.g., operand type or arithmetic/logical role).
• LEFT_COUNTER_ID / RIGHT_COUNTER_ID — the counter (variable) identifiers used on each side of an expression.
• LEFT_CTR_MASTER_ID / RIGHT_CTR_MASTER_ID — master counter references, typically to OKC_COUNTER_MASTER, providing the semantic meaning of the counters.
• LEFT_PARENTHESIS / RIGHT_PARENTHESIS — parentheses indicators controlling expression nesting.
• RELATIONAL_OPERATOR / LOGICAL_OPERATOR — the comparison (e.g., =, >, <) and boolean (AND/OR) operators.
• RIGHT_OPERAND, TOLERANCE, START_AT — the literal or tolerance value applied when the right side is a constant rather than a counter.
• DESCRIPTION (from TL) — the user-facing text of the condition line, resolved for the current language.
• ATTRIBUTE1..15, SEEDED_FLAG, APPLICATION_ID — DFF columns and Oracle-seeded indicators, used to distinguish customer-defined lines from seeded ones and to support descriptive flexfield reporting.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — standard WHO columns.

Common Use Cases and Queries

Typical scenarios include auditing which conditions apply to a contract template, extracting condition logic for a data-warehouse feed, and troubleshooting why a rule did not fire at runtime. A representative query joins the view to the condition header and counter master to reconstruct readable logic:

• List all lines for a condition: SELECT id, cnh_id, sortseq, cnl_type, relational_operator, logical_operator, description FROM okc_condition_lines_v WHERE cnh_id = :p_cnh_id ORDER BY sortseq;
• Identify customer-defined lines: SELECT id, description FROM okc_condition_lines_v WHERE seeded_flag = 'N';
• Audit recent changes: SELECT id, last_updated_by, last_update_date FROM okc_condition_lines_v WHERE last_update_date >= :since;

Because the view enforces the USERENV('LANG') predicate, callers should confirm that a translation row exists for the runtime language; otherwise the line will not be returned. Reports intended for multi-language audiences should either set the session language explicitly or join the translation table independently when all languages are required.