Search Results sync_review_tables

Overview

OKC_REVIEW_UPLD_TERMS_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module. It supports the uploading, staging, review, and approval of contract terms during a bulk document upload and review cycle. When contract documents, such as Microsoft Word files or other externally authored documents, are uploaded into Oracle Contracts, the extracted terms and sections are placed into staging tables for user review before they are committed to the live contract repository. This package provides the backend programmatic infrastructure for that review process, allowing users to insert, lock, update, delete, validate, accept, and reject the staged uploaded terms. The package also manages review messages, business variables, and article references associated with uploaded content. Because it is classified as PVT, it is not intended as a public integration API; it is invoked internally by the Contracts Terms and Conditions review user interface and related internal logic rather than by external callers.

Key Procedures and Functions

The package exposes eleven documented procedures and functions, each serving a distinct role in the review lifecycle.

• INSERT_ROW — Inserts a new uploaded terms review record, capturing contract document identity, object details, article references, display sequencing, error and warning counts, and the upload level.
• LOCK_ROW — Obtains a row-level lock on an uploaded terms record using its identifier and object version number, supporting optimistic concurrency control.
• UPDATE_ROW — Updates an existing uploaded terms record; many parameters default to NULL so only supplied attributes are modified.
• DELETE_ROW — Removes an uploaded terms review record from the staging tables.
• VALIDATE_ROW — Validates an uploaded terms record before commit or acceptance.
• GET_REC — Retrieves a single uploaded terms record for display or processing.
• ACCEPT_CHANGES — Commits accepted uploaded terms into the live contract structure.
• REJECT_CHANGES — Discards changes associated with an uploaded terms record.
• DELETE_UPLOADED_TERMS — Removes uploaded terms, typically when a document upload session is abandoned or reinitiated.
• SYNC_REVIEW_TABLES — Synchronizes the review staging tables, keeping review messages and variable values consistent with the uploaded terms.
• CREATE_UNASSIGNED_SECTION — Creates an unassigned section record. This procedure is the object matched by the search term "create_unassigned_section." It is used when uploaded content cannot be automatically mapped to an existing contract section, so an unassigned placeholder section is generated to hold the material for manual assignment during review.

Tables Accessed

The package reads and writes several staging and reference tables through APPS synonyms. OKC_REVIEW_UPLD_TERMS and its sequence OKC_REVIEW_UPLD_TERMS_S1 are the primary staging tables for uploaded term records. OKC_REVIEW_UPLD_HEADER stores header-level upload session data, while OKC_REVIEW_MESSAGES and OKC_REVIEW_MESSAGES_S1 hold validation messages. OKC_REVIEW_VAR_VALUES and OKC_REVIEW_VAR_VALUES_S1 store variable values captured during review. Contract structure references come from OKC_ARTICLES_ALL, OKC_ARTICLE_VERSIONS, OKC_K_ARTICLES_B, and OKC_K_ART_VARIABLES. Business document and variable definitions are drawn from OKC_BUS_DOC_TYPES_B, OKC_BUS_VARIABLES_B, and OKC_BUS_VARIABLES_TL. FND_NEW_MESSAGES is referenced for message lookup, likely during ACCEPT_CHANGES.

Usage Notes

As a PVT package, OKC_REVIEW_UPLD_TERMS_PVT is not exposed as a supported public API. It is invoked internally by the Contracts Terms and Conditions review forms and by the logic that orchestrates document upload and term extraction. It is generally called when a user reviews, edits, accepts, or rejects staged contract terms in the upload review UI, and may also be driven by concurrent programs or internal packages that manage the review cycle. Custom code should avoid calling it directly, because its procedures are private and subject to change across releases; supported integrations should use public Contracts APIs instead. The 11 procedures are referenced by three other packages, indicating it functions as a shared internal service within the contract terms review framework.