Search Results okr_ip_rgts_txn_terr




Overview
Explore in AI Chat

Overview

The table OKR_IP_RGTS_TXN_TERR is a data object within the Oracle E-Business Suite (EBS) modules for Contracts for Rights (OKR). Specifically, it is part of the "Contracts for Rights" product family, which the provided ETRM metadata explicitly marks as "Obsolete." The table's name suggests its role was to manage the association between Intellectual Property Rights Transactions (IP_RGTS_TXN) and specific geographic territories (TERR). This linking was crucial for defining the territorial scope of rights granted or managed under a contract. Critically, the documentation states this table is "Not implemented in this database," indicating it is a defined but inactive object within the standard EBS 12.1.1 and 12.2.2 installations, likely a remnant from earlier development or a placeholder for functionality that was never fully deployed.

Key Information Stored

Based on the table's name and the provided foreign key metadata, the primary data stored would have been mapping records. The documented primary key, OKR_IP_RGTS_TXN_TERR_PK, is on a column named ID, which would serve as a unique system identifier for each mapping record. Two critical foreign key columns define the relationship: IP_RGTS_TXN_ID, linking to a parent rights transaction record, and TERRITORY_ID, linking to a specific territory definition in the JTF_LOC_AREAS_B table. This structure implies that for a single rights transaction, multiple territory associations could exist, allowing a contract to cover numerous geographic regions.

Common Use Cases and Queries

As the table is documented as not implemented, there are no active operational use cases. However, its intended purpose informs potential analytical queries. Had it been active, common use cases would include reporting on the territorial distribution of licensed rights or validating territory assignments during transaction entry. A typical query would join this table to the transaction header and territory master to list all territories for a given contract. For example:

  • SELECT terr.territory_id, loc.area_name FROM okr_ip_rgts_txn_terr terr, jtf_loc_areas_b loc WHERE terr.territory_id = loc.location_area_id AND terr.ip_rgts_txn_id = :p_txn_id;

Given its obsolete and unimplemented status, encountering this table typically indicates a data model investigation, a customization analysis, or a cleanup activity rather than daily reporting.

Related Objects

The primary related objects are defined by its foreign key constraints. The most significant relationship is with the JTF_LOC_AREAS_B table, which is the master table for geographical areas and territories within the EBS Trading Community Architecture. This connection grounds the territory mapping in the standard EBS geography model. The self-referencing foreign key on the IP_RGTS_TXN_ID column indicates a relationship to another table, likely named OKR_IP_RGTS_TXN or similar, which would be the parent transaction header table. Since the OKR module is obsolete, associated application programming interfaces (APIs), forms, and reports are also likely deprecated or removed from active use.