Search Results okc_rule_atts_blk_v




Overview
Explore in AI Chat

Overview

OKC_RULE_ATTS_BLK_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It belongs to the OKC – Contracts Core product (Oracle Contracts), where it supports the rule-based attribute framework used by the Contract Terms and Conditions (Terms) authoring engine. Specifically, the view exposes the block-level attribute definitions attached to contract rules through the "OKC RULE DEVELOPER DF" descriptive flexfield. Each row describes a single attribute column that a rule may capture, together with the value set that governs how the attribute is validated and displayed.

The view serves as a metadata bridge between the Contracts rule definitions and the underlying Oracle Application Object Library (AOL) flexfield and value set infrastructure. It is read at runtime to determine which attributes belong to a given rule, whether they are mandatory, how they should be prompted to the user, and what validation or formatting rules apply. Integration and reporting consumers use it to enumerate rule attributes without directly navigating the flexfield usage and value set tables.

Underlying Base Objects

The view is defined over three documented base objects:

  • FND_DESCR_FLEX_COL_USAGE_VL (VIEW) — aliased COL, the descriptive flexfield column usage view that supplies the attribute column definitions, sequence numbers, prompts, required flags, and the associated descriptive flex context code (the rule code).
  • FND_FLEX_VALUE_SETS (SYNONYM) — aliased VST, the value set definition table, outer-joined on FLEX_VALUE_SET_ID to provide validation type, format, maximum size, number precision, and uppercase-only behavior.
  • OKC_RULE_DEFS_V (VIEW) — aliased RLD, the Contracts rule definition view, joined on rule code, application ID, and descriptive flexfield name to restrict the attribute list to defined contract rules.

The join is an inner join between the flexfield column usage view and the rule definitions, with an outer join to the value set table so that attributes without a value set are still returned. Only enabled flexfield columns (ENABLED_FLAG = 'Y') are included.

Key Columns

  • RLE_CODE — Descriptive flex context code derived from the column usage record; identifies the contract rule to which the attribute belongs.
  • COL_SEQ — Column sequence number, establishing the display order of the attribute within the rule block.
  • COL_NAME — Application column name of the attribute, with contract-specific names (JTOT_OBJECT1_CODE through JTOT_OBJECT3_CODE) normalized to JTOT_OBJECT1, JTOT_OBJECT2, and JTOT_OBJECT3.
  • REQUIRED_YN — Required flag indicating whether the attribute must be populated.
  • PROMPT — Left-hand prompt text presented to the user for the attribute.
  • VAL_TYPE — Validation type code derived by decoding the value set name and validation/format attributes: 'J' for a Java/default value, 'T' for OKC_TIMEVALUES, 'D' for FND_STANDARD_DATE, 'A' for OKC_AMOUNT-prefixed value sets, 'F' for table validation, or 'N' for numeric formatting.
  • MAXIMUM_SIZE — Maximum size constraint from the value set.
  • NUMBER_PRECISION — Numeric precision from the value set; nulled for the OKC_NUMBER value set.
  • UPPERCASE_ONLY_FLAG — Indicates whether values must be entered in uppercase.

Common Use Cases and Queries

Typical uses include generating rule attribute documentation, auditing which value sets back a given rule, and driving dynamic attribute rendering in contracts extensions. A representative query listing attributes for a specific rule is:

  • SELECT rle_code, col_seq, col_name, required_yn, prompt, val_type, maximum_size, number_precision, uppercase_only_flag FROM okc_rule_atts_blk_v WHERE rle_code = :rule_code ORDER BY col_seq;
  • SELECT rle_code, COUNT(*) attr_count FROM okc_rule_atts_blk_v GROUP BY rle_code; to inventory attribute counts per rule.
  • SELECT col_name, prompt FROM okc_rule_atts_blk_v WHERE required_yn = 'Y'; to identify mandatory attributes across rules.

Because the view reads AOL flexfield and value set metadata, query performance benefits from filtering on RLE_CODE. No DML should be issued against it.