Results for “rgp_type”

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

Overview

OKC_RG_BLK_V is a reporting view owned by the APPS schema within the Oracle Contracts Core (OKC) module. It exposes rule group data that drives the rule-based behavior of contract documents in Oracle E-Business Suite 12.1.1 and 12.2.2. Rule groups associate a set of contract rules with a specific contract template or document type, and they govern clause selection, deviation handling, and other conditional logic applied during contract authoring in the Contracts Core (OKC) and related modules.

The view serves as a flattened, presentation-ready source for rule group records. Rather than requiring reports or integrations to join the underlying rule group view against the lookup table for a readable group name, OKC_RG_BLK_V performs that join internally, exposing a denormalized result set suitable for inquiry screens, concurrent program outputs, and third-party integration extracts. As with most APPS-owned dictionary views in EBS, it should be queried rather than updated directly; DML is performed through the underlying base entities.

Underlying Base Objects

The documented definition of OKC_RG_BLK_V is a join of two objects:

• OKC_RULE_GROUPS_V — the primary source of rule group records, supplying the contract identifier, rule group type, clause and template references, status and definition codes, comments, and standard WHO audit columns.
• FND_LOOKUPS — the Oracle Application Object Library lookup view, joined on RG.RGD_CODE = LKP.LOOKUP_CODE with the filter LKP.LOOKUP_TYPE = 'OKC_RULE_GROUP_DEF'. This join converts the stored rule group definition code into its user-facing meaning.

The view therefore depends on the OKC rule group data model and on the shared FND lookup infrastructure. Because FND_LOOKUPS is language-sensitive, the GROUP_NAME returned reflects the language of the querying session. Metadata also lists FND_GLOBAL as a referenced object, consistent with standard EBS views that derive session context (such as language or user) at runtime.

Key Columns

• DNZ_CHR_ID — the contract document or template identifier associated with the rule group; a denormalized key linking the rule group to its owning contract entity.
• RGP_TYPE — the rule group type, distinguishing the functional category of the group (for example, rules applied to a template versus a specific document).
• CHR_ID — the contract header identifier to which the rule group applies.
• CLE_ID — the clause identifier linked to the rule group, where applicable.
• SAT_CODE — the status or applicability code attached to the rule group record.
• RGD_CODE — the rule group definition lookup code, the value joined to FND_LOOKUPS.
• ID — the unique system identifier for the rule group row.
• OBJECT_VERSION_NUMBER — the optimistic locking version number, incremented on each update.
• GROUP_NAME — the translated meaning of RGD_CODE, obtained from FND_LOOKUPS; this is the human-readable label for the rule group definition.
• COMMENTS — free-text descriptive comments entered for the rule group.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording creation and last-modification context.

Common Use Cases and Queries

Typical uses include auditing which rule groups are attached to contract templates, diagnosing why a particular rule fired during contract authoring, and extracting rule group configuration for migration or reporting. A simple inquiry listing all rule groups with their readable definitions:

• SELECT id, chr_id, rgp_type, group_name, sat_code, comments FROM okc_rg_blk_v ORDER BY chr_id, id;
• SELECT group_name, COUNT(*) FROM okc_rg_blk_v GROUP BY group_name ORDER BY 2 DESC; to profile which rule group definitions are most widely used.
• SELECT * FROM okc_rg_blk_v WHERE chr_id = :p_chr_id; to retrieve all rule groups for a specific contract.
• SELECT * FROM okc_rg_blk_v WHERE last_update_date > SYSDATE - 30; to identify recently modified rule group configuration.

Because GROUP_NAME depends on FND_LOOKUPS, queries run in a session whose language has no lookup translation may return a null or defaulted name; operators should confirm lookup setup under the OKC_RULE_GROUP_DEF lookup type when the name appears blank.