Results for “okc_review_upld_terms”

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

Overview

OKC_REVIEW_UPLD_TERMS is a transactional staging and staging-history table within the Oracle Contracts Core (OKC) module, owned by the OKC schema. Its documented purpose is to store the details generated during the upload of a Microsoft Word document into structured contract terms. In other words, when a user uploads a Word document so that its clauses, articles, and sections can be parsed into structured dealer or customer contract terms, this table captures the intermediate row-by-row representation of what the upload process detected, how each detected object maps to an article or article version, and what errors or warnings were raised during the conversion.

Because the table carries both foreign-key relationships to OKC_ARTICLES_ALL and OKC_ARTICLE_VERSIONS, it sits at the boundary between external document content and the native OKC structured term model. The heuristic Data Vault classification supplied in the metadata is standalone; from a modeling perspective, this suggests the table behaves as an independent staging or work entity rather than as a strict hub or link. It does, however, exhibit link-like behavior through its ARTICLE_ID and ARTICLE_VERSION_ID references, so it can reasonably be treated as a link-style association table in a Data Vault representation.

Key Information Stored

The table is documented with 28 columns. The most operationally significant are listed below. The surrogate primary key is REVIEW_UPLD_TERMS_ID, enforced by the unique index OKC_REVIEW_UPLD_TERMS_U1. The metadata does not document any additional business-key unique index on this table, so REVIEW_UPLD_TERMS_ID should be treated as the sole documented unique identifier.

• REVIEW_UPLD_TERMS_ID — Surrogate primary key; uniquely identifies each upload term row.
• DOCUMENT_ID / DOCUMENT_TYPE — Identify the source Word document and its type being processed.
• OBJECT_ID / OBJECT_TYPE — The parsed object instance and its classification (e.g., clause, section, term) detected in the document.
• OBJECT_TEXT / OBJECT_TITLE — The textual content and title extracted for the object.
• PARENT_OBJECT_TYPE / PARENT_ID / NEW_PARENT_ID — Hierarchy information for parent-child relationships among parsed objects, including any re-parenting applied during upload.
• ARTICLE_ID — Foreign key to OKC_ARTICLES_ALL, linking the row to a structured contract article.
• ARTICLE_VERSION_ID — Foreign key to OKC_ARTICLE_VERSIONS, tying the row to a specific article version.
• LABEL / DISPLAY_SEQ — Display label and ordering sequence for the term within the structured output.
• ACTION — The action applied to the object during upload (for example insert, update, or ignore).
• ERROR_MESSAGE_COUNT / WARNING_MESSAGE_COUNT — Counts of errors and warnings recorded for the row during processing.
• NON_STANDARD_FLAG / MANDATORY_FLAG / LOCK_TEXT — Flags indicating non-standard content, mandatory terms, and locked text.
• UPLOAD_LEVEL / OLD_REVIEW_UPLD_TERMS_ID — The depth of the upload traversal and a self-referencing pointer to a prior version of the same row.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OKC framework.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — Standard EBS WHO columns.

Common Use Cases and Queries

Typical usage centers on diagnosing and auditing Word-to-structured-term uploads. Support and implementation teams query the table to confirm which objects were parsed, whether errors occurred, and how detected objects mapped to articles. A common pattern retrieves rows for a given document with their error/warning posture:

• SELECT REVIEW_UPLD_TERMS_ID, OBJECT_TYPE, OBJECT_TITLE, ACTION, ERROR_MESSAGE_COUNT, WARNING_MESSAGE_COUNT FROM OKC.OKC_REVIEW_UPLD_TERMS WHERE DOCUMENT_ID = :p_doc_id ORDER BY DISPLAY_SEQ;
• Join to OKC_ARTICLES_ALL on ARTICLE_ID and to OKC_ARTICLE_VERSIONS on ARTICLE_VERSION_ID to reconcile uploaded terms against structured articles.
• Filter on ERROR_MESSAGE_COUNT > 0 or WARNING_MESSAGE_COUNT > 0 to identify failed or partial uploads for troubleshooting.
• Aggregate by ACTION or UPLOAD_LEVEL to summarize the shape of an upload session.

Reporting use cases include auditing mandatory versus non-standard term insertions, and reconstructing the original document hierarchy using PARENT_ID, NEW_PARENT_ID, and UPLOAD_LEVEL.

Related Objects

The following objects are most significant in relation to OKC_REVIEW_UPLD_TERMS, based on documented foreign-key relationships and OKC module knowledge:

• OKC_ARTICLES_ALL — Referenced via ARTICLE_ID; the master structured article definition.
• OKC_ARTICLE_VERSIONS — Referenced via ARTICLE_VERSION_ID; versioned article content.
• OKC_REVIEW_UPLD_TERMS (self) — Referenced via OLD_REVIEW_UPLD_TERMS_ID for prior-row tracking.
• OKC_TERMS and associated OKC term tables — the structured terms ultimately produced by the upload process.
• OKC_CONTRACTS and contract document tables — provide the contract context for the uploaded document.

Together these references confirm that OKC_REVIEW_UPLD_TERMS functions as an intermediate, link-style entity connecting external Word document content to the structured article and term model in Oracle Contracts Core.