Search Results okc_rep_imp_errors_t_s

Overview

OKC_REP_UTIL_PVT is a private (PVT) PL/SQL package body in the APPS schema belonging to the Oracle E-Business Suite Contracts (OKC) reporting module. It provides the shared utility layer that supports the Contract Repository import, validation, and access-control operations for EBS 12.1.1 and 12.2.2. The package encapsulates the low-level logic that the Contract Repository UI and its concurrent programs invoke when they need to validate imported contract data, check whether a user may view or update a contract, record approval and signature history, generate CSV output for error reporting, and purge transient repository data. Because the API is classified as private, it is not intended as a public integration point; it is called internally by the Contract Repository pages and by sibling packages such as OKC_REP_CONTRACT_PROCESS_PVT. The package references OKC_REP_IMP_CONTRACTS_T, OKC_REP_IMP_DOCUMENTS_T, OKC_REP_IMP_PARTIES_T, and OKC_REP_IMP_ERRORS_T (with its OKC_REP_IMP_ERRORS_T_S sequence) — the interface and error staging tables that carry contract import data — which places it squarely in the repository import pipeline. The user search term "okc_rep_imp_errors_t_s" corresponds to the sequence underlying the import error staging table used by this package's validation routines.

Key Procedures and Functions

The documented API surface includes 31 procedures and functions organized around four functional areas.

• Access control: CHECK_CONTRACT_ACCESS_EXTERNAL, CHECK_CONTRACT_ACCESS, HAS_CONTRACT_ACCESS_EXTERNAL, HAS_CONTRACT_ACCESS, CAN_UPDATE, and OK_TO_COMMIT determine whether a user, including an external party, is permitted to view or modify a contract. GET_EXTERNAL_USERLIST returns the set of external users evaluated against FND_GRANTS security.
• Status and history: CHANGE_CONTRACT_STATUS transitions a contract's status; ADD_APPROVAL_HIST_RECORD and ADD_SIGNATURE_HIST_RECORD write audit rows into OKC_REP_CON_APPROVALS and OKC_REP_SIGNATURE_DETAILS respectively.
• Import validation: VALIDATE_CONTRACT_PARTY, VALIDATE_PARTY_CONTACT, VALIDATE_IMPORT_PARTIES, VALIDATE_IMPORT_DOCUMENTS, VALIDATE_IMPORT_CONTRACTS, VALIDATE_AND_INSERT_CONTRACTS, and DELETE_IMPORT_CONTRACT process rows staged by the Contract Repository import. Errors are captured through GET_CSV_ERROR_STRING and GET_CSV_HEADER_STRING, which format validation failures into CSV output for user download.
• Maintenance: PURGE_RECENT_CONTRACTS removes stale rows from OKC_REP_RECENT_CONTRACTS.

Tables Accessed

The package reads and writes across several EBS schemas. Contract data is read from OKC_REP_CONTRACTS_ALL (including indexes _S1 and _S2), OKC_REP_CONTRACT_VERS, OKC_REP_CONTRACT_PARTIES, OKC_REP_CON_STATUS_HIST, OKC_REP_DOC_VERSIONS_V, and OKC_REP_CON_APPROVALS. Import staging is handled through OKC_REP_IMP_CONTRACTS_T, OKC_REP_IMP_DOCUMENTS_T, OKC_REP_IMP_PARTIES_T, and OKC_REP_IMP_ERRORS_T (with sequence OKC_REP_IMP_ERRORS_T_S). Party and contact validation joins HZ_PARTIES, HZ_PARTY_SITES, HZ_CONTACT_POINTS, HZ_RELATIONSHIPS, and AP_SUPPLIERS/AP_VENDOR_PUB_PKG. Resource and security checks use JTF_RS_* and FND_GRANTS, FND_USER, FND_OBJECTS, and FND_LOOKUP_VALUES. Reference lookups against ASO_QUOTE_HEADERS_ALL, OE_ORDER_HEADERS_ALL, OE_BLANKET_HEADERS_ALL, PO_HEADERS_ALL, and PON_AUCTION_HEADERS_ALL allow the repository to associate contracts with upstream sourcing documents.

Usage Notes

OKC_REP_UTIL_PVT is invoked indirectly. The Contract Repository OAF pages and the Contract Repository import concurrent program call it through OKC_REP_CONTRACT_PROCESS_PVT and the OKC_API public wrapper. It is not referenced by any database object and, being a PVT package, should not be called directly from customer extensions; developers needing equivalent behavior should use the supported public OKC_API entry points. The presence of FND_MSG_PUB, FND_LOG, and WF_DIRECTORY dependencies indicates that errors are surfaced through the standard EBS message stack and that workflow/resource integration is supported for approval and signature history. Because the package honors MO_GLOBAL and MO_GLOB_ORG_ACCESS_TMP, all validations run within the caller's multi-org security context.