Results for “okr_ip_pub_media”

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

Overview

OKR_IP_PUB_MEDIA is a table within the Oracle E-Business Suite product family designated OKR – Contracts for Rights. The ETRM metadata classifies the OKR product as obsolete, and the table itself is explicitly documented as “Not implemented in this database.” Its declared purpose is to store publication medium information — the channel or format through which intellectual property rights are published or exploited (for example print, electronic, or broadcast media). In the historical OKR data model, this table served as a child of the intellectual property header and acted as the parent of the release records that monetize a given medium.

The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. This should be treated as a modeling suggestion rather than a documented fact: the table carries descriptive attributes about a publication medium attached to a parent entity, and it is referenced by downstream transaction tables (OKR_IP_RELEASES), which is consistent with a satellite role in a Data Vault construct. Practically, the table behaves as a dependent detail table in a third-normal-form EBS schema rather than as an independent hub.

Key Information Stored

The documented metadata exposes a limited but meaningful set of columns and constraints:

• PMM_ID — The surrogate primary key, enforced by constraint OKR_IP_PUB_MEDIA_PK. The metadata lists this column under both the OKR_IP_PUB_MEDIA_PK and OKR_PUB_MEDIA_PK constraint definitions.
• CBN_ID — Foreign key to OKR_COMBINATIONS_B. This links publication media to an accounting flexfield combination, indicating that media-level attributes can carry an accounting or cost-code association.
• IP_ID — Foreign key to OKR_IP_COMMON_B. This ties the publication medium to the intellectual property header record, identifying which right or title the medium belongs to.

No additional columns are documented in the supplied metadata. In the standard OKR pattern, a table of this shape would typically also carry a medium code or name, language, territory, effective dates, and audit columns (creation/update WHO columns), but these are not enumerated in the available documentation and should be verified against the actual data dictionary if the table is present in a given instance. The primary key is clearly the surrogate PMM_ID; no separate unique business-key index is documented.

Common Use Cases and Queries

Because the object is obsolete and not implemented, the principal use cases are historical reporting, data migration, and reverse-engineering of legacy OKR installations. Typical patterns include:

• Enumerating media for a title: joining OKR_IP_PUB_MEDIA to OKR_IP_COMMON_B on IP_ID to list all publication media associated with an intellectual property record.
• Release analysis: joining OKR_IP_RELEASES to OKR_IP_PUB_MEDIA on PMM_ID to trace which releases were generated for each medium.
• Accounting reconciliation: joining CBN_ID to OKR_COMBINATIONS_B to reconcile media-level activity against a flexfield combination.

A representative query would take the form: SELECT m.pmm_id, m.ip_id, m.cbn_id FROM okr_ip_pub_media m WHERE m.ip_id = :ip_id; with optional joins to the two parent tables for descriptive context. In migration scenarios, this table is usually a source for mapping legacy medium assignments into the current rights or royalty schema.

Related Objects

The FK metadata identifies the following significant relationships:

• OKR_IP_COMMON_B — Referenced via OKR_IP_PUB_MEDIA.IP_ID; the intellectual property header and the primary parent of the medium record.
• OKR_COMBINATIONS_B — Referenced via OKR_IP_PUB_MEDIA.CBN_ID; supplies the accounting flexfield combination.
• OKR_IP_RELEASES — References this table via OKR_IP_RELEASES.PMM_ID; the child table where releases are recorded against a publication medium.

These three objects form the complete documented dependency set. Because OKR is flagged obsolete and the table is not implemented, no APIs, concurrent programs, or views are documented against it; any integration effort should be validated against the target instance before relying on these relationships.