Results for “rule_information15_dsc”

14 results




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

Overview

OKC_RULES1_BLK_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, and is shipped as a valid object within the OKC (Contracts Core) product. Its purpose is to present the business rules stored against contract documents in a fully descriptive, human-readable form. Whereas the underlying contract rules tables store rule attributes as coded identifiers, this view resolves those identifiers into displayed values and descriptions at query time, so that reporting tools, forms, and integrations can consume meaningful text without invoking the Contracts Core public APIs themselves.

The view is particularly relevant to the Contracts Core descriptive flexfield mechanism. The RULE_INFORMATION attributes are flexfield segments, and the view exposes each segment value alongside its translated value and description. This makes OKC_RULES1_BLK_V a convenient source for extracting rule definitions in reporting and integration scenarios where the caller cannot or does not wish to call the flexfield resolution APIs directly.

Underlying Base Objects

Per the documented ETRM metadata for release 12.2.2, the view references two objects:

  • OKC_RULES_V (VIEW) — the primary contract rules view, supplying the rule rows, identifiers, object references, and raw RULE_INFORMATION column values that this view projects and enriches. It is aliased RLE in the view definition.
  • OKC_RULE_PUB (PACKAGE) — the Contracts Core public package supplying the helper functions used to derive the resolved values and descriptions: GET_OBJECT_VAL, GET_OBJECT_DSC, GET_FLEX_VAL, and GET_FLEX_DSC.

The view therefore sits one layer above OKC_RULES_V, adding no new persisted data; every derived column is computed through the package, generally at row-fetch time.

Key Columns

The view exposes identifying columns, three object-reference triplets, and the flexfield-based rule information attributes. Important columns include:

  • ID, DNZ_CHR_ID, RGP_ID, OBJECT_VERSION_NUMBER — the rule's primary identifier, its owning contract/document identifier, rule group identifier, and the optimistic locking version.
  • RULE_INFORMATION_CATEGORY — the descriptive flexfield context used to resolve the RULE_INFORMATION* segments.
  • JTOT_OBJECT1_CODE/OBJECT1_ID1/OBJECT1_ID2, with corresponding columns for OBJECT2 and OBJECT3 — coded object references. For each, the view adds JTOT_OBJECTn_VAL and JTOT_OBJECTn_DSC, resolved via GET_OBJECT_VAL and GET_OBJECT_DSC and truncated to 240 bytes.
  • RULE_INFORMATION1 through RULE_INFORMATIONn — the raw flexfield segment values, each accompanied by a _VAL (translated value) and _DSC (description) column resolved through GET_FLEX_VAL and GET_FLEX_DSC. This is the structure that answers a search such as "rule_information15": the segment RULE_INFORMATION15 is exposed as RULE_INFORMATION15, RULE_INFORMATION15_VAL, and RULE_INFORMATION15_DSC.

Common Use Cases and Queries

The view is typically used to report rule configurations on contracts, to reconcile coded object references against their descriptions, and to extract flexfield rule attributes for downstream systems. A representative query filtering on a specific rule information segment is:

  • SELECT id, dnz_chr_id, rule_information_category, rule_information15, rule_information15_val, rule_information15_dsc FROM okc_rules1_blk_v WHERE rule_information15_val IS NOT NULL;
  • SELECT id, dnz_chr_id, jtot_object1_val, jtot_object1_dsc FROM okc_rules1_blk_v WHERE dnz_chr_id = :contract_id;

Because value resolution occurs through OKC_RULE_PUB, queries returning large row sets can be costly; filtering by DNZ_CHR_ID or RULE_INFORMATION_CATEGORY is advisable. The view should be treated strictly as a reporting and integration source, not as a target for DML.