Results for “okr_combinations_b”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKR_COMBINATIONS_B is a base table historically associated with the Oracle E-Business Suite product OKR — Contracts for Rights, a module that has since been classified as obsolete. The table functions as a foundational entity that stores combination-level identifiers for intellectual property and publishing rights records. Within the standard Oracle EBS 12.1.1 and 12.2.2 footprint, the object is documented in the Oracle E-Business Suite Technical Reference Manual (ETRM) but is explicitly annotated as "Not implemented in this database," indicating that no physical implementation or seeded data is present in a default installation. Any deployment presence would result from a legacy customization, an upgraded historical schema, or a specialized licensing configuration.
From a Data Vault modeling perspective, the heuristic classification for OKR_COMBINATIONS_B is hub-leaning. This means the table is best understood as a candidate hub: it carries a distinct business identifier (CBN_ID) that is referenced by dependent tables, serving as the anchor for relationships rather than as a transactional satellite holding changing descriptive attributes. This classification is a modeling suggestion derived from the foreign-key structure, not a prescriptive design from Oracle.
Key Information Stored
The documented metadata for this table is intentionally minimal, reflecting its obsolete and non-implemented status. The principal columns documented are:
- CBN_ID — The combination identifier. This column constitutes the primary key through the constraint OKR_COMBINATIONS_B_PK, and it is the single business-key candidate documented. It acts as the surrogate-to-business identifier anchor that dependent tables reference.
Because the ETRM excerpt provides no additional column inventory, no further attribute-level facts (descriptive names, effective dates, status codes, or audit columns) can be asserted from the source documentation. In a typical base-table companion pattern, a corresponding _TL translation table might exist for multilingual descriptive columns, but this is not confirmed by the provided metadata. Practitioners should treat CBN_ID as the sole documented key and verify any remaining columns directly against the deployed schema via ALL_TAB_COLUMNS.
Common Use Cases and Queries
Given its obsolete status, practical query activity centers on impact analysis, data-migration validation, and cleanup rather than operational reporting. Typical scenarios include determining whether orphaned child rows exist in dependent tables, and identifying whether legacy rights combination data must be retained for archival or statutory reasons.
- Presence check — confirm whether the object exists in a given environment:
SELECT COUNT(*) FROM all_tables WHERE table_name = 'OKR_COMBINATIONS_B'; - Referential audit — identify child records whose parent combination no longer exists:
SELECT c.cbn_id FROM okr_ip_combinations c WHERE NOT EXISTS (SELECT 1 FROM okr_combinations_b b WHERE b.cbn_id = c.cbn_id); - Usage summary — count dependent rows per combination:
SELECT cbn_id, COUNT(*) FROM okr_ip_combinations GROUP BY cbn_id;
Because the table is not implemented in standard environments, these patterns are primarily diagnostic and should be executed only where the object is confirmed to be deployed.
Related Objects
The documented foreign-key relationships establish OKR_COMBINATIONS_B as a parent reference for at least two dependent child tables:
- OKR_IP_COMBINATIONS — references OKR_COMBINATIONS_B via OKR_IP_COMBINATIONS.CBN_ID → OKR_COMBINATIONS_B.CBN_ID.
- OKR_IP_PUB_MEDIA — references OKR_COMBINATIONS_B via OKR_IP_PUB_MEDIA.CBN_ID → OKR_COMBINATIONS_B.CBN_ID.
These two objects form the immediate dependency surface around the hub. Any archival, purge, or migration activity targeting OKR_COMBINATIONS_B must account for these inbound foreign keys to preserve referential integrity. No views, PL/SQL APIs, or additional dependent objects are documented in the ETRM excerpt beyond these two relationships.
-
Table: OKR_COMBINATIONS_B 12.2.2
Not implemented in this database·Explore OKR module →
-
Table: OKR_COMBINATIONS_B 12.1.1
Not implemented in this database·Explore OKR module →
-
Table: OKR_IP_PUB_MEDIA 12.1.1
PUBLICATION MEDIUM table
Not implemented in this database·Explore OKR module →
-
Table: OKR_IP_COMBINATIONS 12.2.2
Not implemented in this database·Explore OKR module →
-
Table: OKR_IP_COMBINATIONS 12.1.1
Not implemented in this database·Explore OKR module →
-
Table: OKR_IP_PUB_MEDIA 12.2.2
PUBLICATION MEDIUM table
Not implemented in this database·Explore OKR module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
View: OKR_COMBINATIONS_V 12.2.2
Not being used
Not implemented in this database·Explore OKR module →
-
View: OKR_COMBINATIONS_V 12.1.1
Not being used
Not implemented in this database·Explore OKR module →