Results for “okc_rule_groups”

18 results




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

Overview

The view OKR_IP_RGTS_DV belongs to the OKR – Contracts for Rights product family, a module that Oracle has since marked as obsolete within the E-Business Suite. The suffix _DV follows Oracle's long-standing convention for a "detail view," indicating that the object consolidates logically related columns from a set of denormalized base tables into a single, readable result set. In the context of Oracle EBS 12.1.1 and 12.2.2, this view surfaces intellectual property (IP) right records together with the contract header, line, rule, and rule-group attributes that qualify each right. It exists primarily to support reporting, concurrent program extraction, and integration queries where a functional user or interface needs a flattened representation of an IP right without navigating the many normalized tables beneath it.

The view is significant because the OKC (Contracts Core) and OKR schemas store right-related data across line types distinguished by LSE_ID values. Reconstructing a single right requires joining several of these line entries and their associated rules. OKR_IP_RGTS_DV encapsulates that join logic so that consumers do not have to replicate it.

Underlying Base Objects

The ETRM metadata documents the view as a "complete view" defined over the following base tables:

  • OKC_LINES_B – the base table for contract lines, appearing multiple times with aliases (CLEB, CLEIP, CLERG) to traverse the line hierarchy.
  • OKC_K_LINES_TL – the translated (language) table for line names and descriptions.
  • OKC_RULES_B – the base table holding rule information, used three times for language (LAN), territory (TER), and exclusivity (EXC) rule categories.
  • OKC_K_ITEMS – the table linking lines to item/object identifiers; central to the "okc_k_items" search context, as it carries OBJECT1_ID1 used to associate the right with its parent IP record.
  • OKC_RULE_GROUPS (referenced as RGP from OKC_RULE_GROUPS_B) – groups the individual rules that apply to a given line.
  • OKC_K_HEADER_B – the contract header, supplying contract number, status, and template flag.
  • OKR_IP_COMMON_B – the OKR-specific table holding the IP identifier (IP_ID).

The join keys are notably driven by hard-coded line subtype identifiers: LSE_ID = 100 for the IP line, LSE_ID = 101 for the rule-group line, and LSE_ID = 104 for the right line itself. The IP identity is established by matching TO_CHAR(IPYB.IP_ID) = CIMIP.OBJECT1_ID1.

Key Columns

Common Use Cases and Queries

A frequent requirement is to list all active IP rights for a given contract, including their language, territory, and exclusivity terms. For example:

SELECT contract_number, rgt_name, start_date, end_date, lang_code, terr_id, exclusivity_yn FROM okr_ip_rgts_dv WHERE sts_code = 'ACTIVE' AND template_yn = 'N' ORDER BY contract_number, rgt_name;

Integration routines migrating rights data to a downstream licensing or royalty system commonly filter by ip_id to extract every right tied to a specific property. Auditors and reporting extracts frequently join this view back to OKC_K_ITEMS where additional object references are required, though the view already embeds that relationship through its CIM and CIMIP aliases. Because the module is obsolete and the view is documented as "not implemented in this database," administrators should confirm availability in their specific instance before relying on it in 12.2.2 environments.