Search Results ip_description

Overview

The OKX_IP_COMMON_V view belongs to the Oracle E-Business Suite OKX – Contracts Integration module, which provides the integration layer between Oracle Contracts (OKC) and Oracle Projects (PA/OKR) for intellectual property agreements, funding agreements, and associated contract terms. The view exposes a language-resolved, common-denominator projection of intellectual property (IP) records stored in the OKR (Oracle Contracts Core for Projects) tables. Its purpose is to present a uniform, denormalized IP record — combining the identifier, subject, and description fields with the active-date bounds and status flag — to downstream reports, integrations, and APIs that need to surface IP information in a single query without joining the base and translation tables explicitly.

In EBS 12.1.1 and 12.2.2, the view is documented in the ETRM (Oracle E-Business Suite Technical Reference Manual) as a Contracts Integration object, but the metadata explicitly records that it is not implemented in this database. As a result, the view is a documented interface rather than a deployed database object in the standard environment.

Underlying Base Objects

The ETRM states that no referenced base objects are documented in the 12.2.2 metadata, and the title block likewise lists no owner. The view text itself, however, is fully documented and shows that the view is defined over two OKR tables:

• OKR_IP_COMMON_B — the base (non-translatable) table holding the IP entity, including the primary key IP_ID, the IP_IDENTIFIER, the IP_TYPE, and the START_DATE_ACTIVE / END_DATE_ACTIVE columns.
• OKR_IP_COMMON_TL — the translation table holding the NAME, SUBJECT, and DESCRIPTION attributes per language.

The two tables are joined on IP_ID, with the translation row restricted by T.LANGUAGE = USERENV('LANG') so that the query returns only the session-language version of the descriptive attributes. No other base objects (e.g., status or type lookup tables) are joined; the STATUS column is a literal rather than a derived value.

Key Columns

• NAME — the IP identifier, sourced from B.IP_IDENTIFIER. This is the primary business key used to locate an IP record.
• DESCRIPTION — the translated IP description from T.NAME. (The view text maps the translation table's NAME column to the output column DESCRIPTION, while the translation table's DESCRIPTION column is exposed as IP_DESCRIPTION.)
• STATUS — a hard-coded literal 'A', indicating the view returns only "Active" rows.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range of the IP record from the base table.
• IP_ID — the numeric primary key of the IP record.
• IP_TYPE — the classification of the IP (e.g., patent, trademark, copyright).
• IP_IDENTIFIER — the raw identifier value; duplicates NAME in output.
• IP_NAME — the translated name from T.NAME.
• IP_SUBJECT — the translated subject from T.SUBJECT.
• IP_DESCRIPTION — the translated description from T.DESCRIPTION.
• ID1 / ID2 — synthetic columns (IP_ID as ID1, and the literal '#' as ID2), typically used to satisfy a generic ID-pair contract when the view is consumed by an integration framework.

Common Use Cases and Queries

Because the view returns translated, active-only IP records with both an identifier and a display name, it is useful for lookups and list-of-values queries in integrations, reports, and interfaces that communicate with external contract systems. Typical usage includes presenting IP identifiers in contract funding screens, populating interface staging tables, and resolving the session-language description for an IP.

To retrieve all active IP records in the current session language:

SELECT IP_ID,
       IP_IDENTIFIER,
       IP_NAME,
       IP_TYPE,
       START_DATE_ACTIVE,
       END_DATE_ACTIVE
FROM   OKX_IP_COMMON_V
ORDER  BY IP_IDENTIFIER;

To look up a specific IP by identifier, for example to feed an integration extract:

SELECT IP_ID,
       IP_IDENTIFIER,
       IP_NAME,
       IP_SUBJECT,
       IP_DESCRIPTION
FROM   OKX_IP_COMMON_V
WHERE  IP_IDENTIFIER = :ip_identifier;

To resolve the description text for a known IP_ID within an active date window:

SELECT IP_ID, IP_NAME, DESCRIPTION
FROM   OKX_IP_COMMON_V
WHERE  IP_ID = :ip_id
AND    SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);

Note that the view performs no filtering on IP_TYPE or on the active dates; callers that require a date-bound or type-restricted result set must add the predicate themselves. Because the metadata records the view as not implemented in the standard database, queries against it in a stock EBS 12.1.1/12.2.2 instance will typically fail with ORA-00942; it should be treated as a documented contract rather than a deployable object, and equivalent queries should be issued directly against OKR_IP_COMMON_B and OKR_IP_COMMON_TL.