Results for “okc_mrv_t”

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

Overview

OKC_MRV_T is a valid table owned by the OKC schema within the Oracle Contracts Core (OKC) product family. In Oracle EBS 12.1.1 and 12.2.2, the OKC module provides the foundation for contract authoring, contract terms, and contract repositories used across Procurement, Order Management, and Service Contracts. OKC_MRV_T is a standalone repository table that stores document content associated with contract master records, holding large binary (BLOB) payloads in addition to classification columns such as document identifier and document type.

The ETRM documentation records OKC_MRV_T as a standalone object with no foreign-key dependencies on other tables. A heuristic Data Vault classification mined from the FK structure therefore suggests this table behaves as an isolated satellite, carrying descriptive and large-object payload data keyed by its own surrogate identifier. Because it has no parent link or hub relationship documented, it is best modeled as a self-contained satellite that is joined to other contract objects through shared business keys rather than enforced referential constraints.

Key Information Stored

The documented physical schema for OKC_MRV_T contains six columns in the OKC schema. The most important columns and their contents are:

• ID — the surrogate primary key, enforced by the OKC_MRV_T_PK constraint. It uniquely identifies each row in the table.
• DOC_ID — the document identifier that associates the stored content with a contract document record.
• DOC_TYPE — the classification of the document, distinguishing the type of content held in the row.
• BLOB_DATA — the binary large object column that stores the raw document or media content.
• BLOB_OUTPUT — a secondary BLOB column that stores the rendered or generated output of the document content.
• ACTION — a processing or state indicator describing the action applied to the stored content.

Two unique indexes are documented, SYS_IL0000523171C00004$$ and SYS_IL0000523171C00005$$, which are the internal LOB indexes automatically created for the BLOB_DATA and BLOB_OUTPUT columns respectively. These are not business-key candidates; the only true uniqueness enforcement documented is the surrogate primary key OKC_MRV_T_PK on ID. The pairing of DOC_ID and DOC_TYPE functions as the practical business reference by which rows are located.

Common Use Cases and Queries

Because the table stores binary document payloads, typical usage centers on retrieving and auditing contract document content rather than transactional processing. Common scenarios include extracting the binary payload for archival or migration, identifying documents by type, and validating that a document record has an associated stored content row.

• Retrieving document content by business reference: SELECT ID, DOC_ID, DOC_TYPE, ACTION FROM OKC.OKC_MRV_T WHERE DOC_ID = :doc_id AND DOC_TYPE = :doc_type;
• Enumerating stored documents by type: SELECT DOC_TYPE, COUNT(*) FROM OKC.OKC_MRV_T GROUP BY DOC_TYPE;
• Orphan analysis, checking for stored content with no matching contract record: SELECT m.ID, m.DOC_ID FROM OKC.OKC_MRV_T m LEFT JOIN OKC.OKC_K_DOCUMENTS d ON d.DOCUMENT_ID = m.DOC_ID WHERE d.DOCUMENT_ID IS NULL;
• Examining the size of binary payloads for storage planning: SELECT ID, DBMS_LOB.GETLENGTH(BLOB_DATA) AS data_len, DBMS_LOB.GETLENGTH(BLOB_OUTPUT) AS output_len FROM OKC.OKC_MRV_T;

Reporting use cases typically join DOC_ID to the contract document header to produce listings of documents that have stored binary content, sorted by document type and action.

Related Objects

Although ETRM classifies OKC_MRV_T as standalone, it participates in the wider contract document model through its DOC_ID and DOC_TYPE columns. Significant related objects include:

• OKC_K_DOCUMENTS — the contract document header table, joined on OKC_K_DOCUMENTS.DOCUMENT_ID = OKC_MRV_T.DOC_ID.
• OKC_K_LINES — contract line records linked to the parent document via DOC_ID.
• OKC_K_HEADERS — contract header records referenced by the document chain.
• OKC_K_ITEMS — contract line item details associated with the same document hierarchy.
• OKC_TERMS_TL and OKC_TERMS_VL — contract terms and their translations, related through the document type.
• OKC_K_PARTY_ROLES — party role assignments defined for the parent contract.
• OKC_MRV_MAP — mapping metadata often used alongside stored document content.
• OKC_QA_QUESTIONS and OKC_QA_ANSWERS — structured contract content frequently carried together with document payloads.

Integration is generally achieved through the OKC public APIs and views over OKC_K_DOCUMENTS rather than through enforced foreign keys on OKC_MRV_T itself.