Search Results okc_rep_imp_contacts_t_s

Overview

The APPS.OKC_REP_CONTRACT_IMP_PVT package body is a private (PVT-classified) API within the Oracle Contracts (OKC) module of Oracle E-Business Suite, purpose-built to support bulk import of contracts from external sources into the ETRM (Enterprise Contracts) repository. It is the engine behind the contract import concurrent program in releases 12.1.1 and 12.2.2. The package consumes rows staged in the OKC_REP_IMP_* interface tables, validates them, and materializes them as native contract records in the OKC_REP_CONTRACTS_ALL and OKC_REP_CONTRACT_VERS operational tables, along with related usages, parties, contacts, risks, and documents.

Although the PL/SQL API is classified as a private package and is not referenced by any database object, it is invoked internally by the import concurrent program and by the OKC_REP_CONTRACT_PROCESS_PVT driver. It orchestrates the import lifecycle: run ID registration, contract header and party population, contract version creation, deliverable and task assignment, and error reporting through the OKC_REP_IMP_ERRORS_T staging table.

Key Procedures and Functions

The package exposes approximately twenty documented procedures and functions that collectively define the import contract lifecycle:

• CREATE_CONTRACT — Creates a new contract record from staged interface data, establishing the contract header, business document type, and initial version.
• POPULATE_CONTRACT_HDR — Populates header-level attributes such as contract number, type, dates, currency, and status on the target contract record.
• POPULATE_CONTRACT_PARTIES — Transfers party role information (buyer, seller, etc.) from OKC_REP_IMP_PARTIES_T into the contract's party relationships.
• POPULATE_PARTY_CONTACTS — Populates contacts associated with each contract party, sourcing OKC_REP_IMP_CONTACTS_T.
• POPULATE_CONTRACT_RISKS — Moves staged risk records from OKC_REP_IMP_RISKS_T into the contract's risk structure.
• DELETE_CONTRACT — Removes a previously imported contract and its dependent rows, typically used to support re-import or rollback scenarios.
• VALIDATE_AND_INSERT_CON_CP — Validates contract usages and inserts valid rows into OKC_REP_CONTRACT_USAGES and OKC_REP_CONTRACT_USAGES_S.
• DELETE_PARTY_CONTACTS and DELETE_PARTIES — Clean up staged or previously imported party and contact data to prevent duplication.
• CREATE_NEW_CONTRACT_VERSION — Generates a new version of an existing contract, preserving prior versions in OKC_REP_CONTRACT_VERS.
• CHECK_CONTRACT_EXISTS — Determines whether a contract already exists for a given external reference, supporting update vs. insert decisions.
• ACTIVATE_TASKS_CLOSEOUT — Activates downstream tasks and closeout actions associated with imported contracts.
• CANCEL_CONTRACT and DELETE_CANCEL_CONTRACT — Handle cancellation of imported contracts and their cleanup.
• MIGRATE_CONTRACT_RELATIONS — Migrates relationship data into OKC_REP_CONTRACT_RELS, linking contracts to related agreements.

Tables Accessed

The package reads from the OKC_REP_IMP_* interface tables, including OKC_REP_IMP_CONTRACTS_T, OKC_REP_IMP_CONTRACTS_T_S, OKC_REP_IMP_PARTIES_T, OKC_REP_IMP_PARTIES_T_S, OKC_REP_IMP_CONTACTS_T, OKC_REP_IMP_CONTACTS_T_S, OKC_REP_IMP_RISKS_T, OKC_REP_IMP_RISKS_T_S, OKC_REP_IMP_DOCUMENTS_T, and OKC_REP_IMP_ERRORS_T. It writes to the operational tables OKC_REP_CONTRACTS_ALL (contract headers), OKC_REP_CONTRACT_VERS (versions), OKC_REP_CONTRACT_RELS (relationships), OKC_REP_CONTRACT_USAGES and OKC_REP_CONTRACT_USAGES_S (usage and usages history), and OKC_REP_IMPORT_RUN_ID_S (import run sequencing). HR_ALL_ORGANIZATION_UNITS is joined to resolve internal party organizations. The OKC_REP_CONTRACT_USAGES_S table is a key search target because it stores the usage history surfaced by the import validation routine.

Usage Notes

This package is not intended for direct invocation. It is called internally by the OKC contract import concurrent program and by OKC_REP_CONTRACT_PROCESS_PVT. It depends on the FND_API, FND_MSG_PUB, FND_LOG, FND_GLOBAL, FND_FILE, FND_MESSAGE, and FND_PROFILE standard EBS utilities for error handling, logging, and profile resolution, and on OKC_API and OKC_DELIVERABLE_PROCESS_PVT for contract and deliverable creation. Custom concurrent programs should stage data in the OKC_REP_IMP_* tables and invoke the import driver rather than calling these procedures directly. Diagnosing import failures requires querying OKC_REP_IMP_ERRORS_T and reviewing FND_LOG output generated under the calling run ID.