Search Results has_contract_access

Overview

OKC_REP_UTIL_PVT is a private (PVT) utility package in the APPS schema that supports the Oracle E-Business Suite Contract Management (OKC) repository modules. Unlike public APIs such as OKC_API, packages classified as PVT are internal implementation utilities intended for use by other OKC packages rather than direct external invocation. The package consolidates common repository operations — contract access validation, status changes, approval and signature history maintenance, party and contact validation, import validation, and CSV/error handling — into a single shared library. It serves the Contract Repository feature set supporting repositories, closeout, import, signing workflow, and term-related processing. Because OKC_REP_UTIL_PVT is referenced by nine other packages, it functions as a foundational dependency within the OKC repository layer.

Key Procedures and Functions

The package exposes 31 documented procedures and functions. Access-control routines include CHECK_CONTRACT_ACCESS, CHECK_CONTRACT_ACCESS_EXTERNAL, HAS_CONTRACT_ACCESS, HAS_CONTRACT_ACCESS_EXTERNAL, and CAN_UPDATE, which determine whether a user may view or modify a contract. Status and history routines include CHANGE_CONTRACT_STATUS, ADD_APPROVAL_HIST_RECORD, and ADD_SIGNATURE_HIST_RECORD, which manage lifecycle transitions and audit trails. Validation routines include VALIDATE_CONTRACT_PARTY, VALIDATE_PARTY_CONTACT, VALIDATE_IMPORT_PARTIES, VALIDATE_IMPORT_DOCUMENTS, and VALIDATE_IMPORT_CONTRACTS, ensuring data integrity during entry and import. Import-oriented routines include VALIDATE_AND_INSERT_CONTRACTS and DELETE_IMPORT_CONTRACT. Output and utility routines include GET_CSV_ERROR_STRING, GET_CSV_HEADER_STRING, GET_EXTERNAL_USERLIST, OK_TO_COMMIT, and PURGE_RECENT_CONTRACTS, which support reporting, external user resolution, transaction commit checks, and cleanup of recently imported contracts.

Tables Accessed

Through APPS synonyms, the package reads and writes a range of reference and transactional tables. Supplier data is read from AP_SUPPLIERS, while quote linkage uses ASO_QUOTE_HEADERS_ALL. Currency and lookup definitions come from FND_CURRENCIES and FND_LOOKUP_VALUES. Security and access checks reference FND_GRANTS, FND_OBJECTS, and FND_USER. Document categorization uses FND_DOCUMENT_CATEGORIES and its translation table FND_DOCUMENT_CATEGORIES_TL. Party, contact, site, and relationship validation draws on HZ_PARTIES, HZ_PARTY_SITES, HZ_CONTACT_POINTS, and HZ_RELATIONSHIPS. Organization and resource data are sourced from HR_ALL_ORGANIZATION_UNITS and JTF_RS_GROUPS_DENORM.

Usage Notes

OKC_REP_UTIL_PVT is invoked indirectly rather than through direct customer calls. Its documented callers include OKC_API, OKC_PURGE_PVT, OKC_REP_CLOSEOUT_PVT, OKC_REP_CONTRACT_IMP_PVT, OKC_REP_CONTRACT_PROCESS_PVT, OKC_REP_SEARCH_UTIL_PVT, OKC_REP_SIGN_WF_PVT, OKC_REP_WF_PVT, and OKC_TERMS_UTIL_GRP, indicating use across contract entry forms, import concurrent programs, purge jobs, search, and workflow-driven signing and approval processing. Custom extensions should call the public OKC_API rather than this internal utility, since its signature and behavior are not part of the supported public interface and may change between releases such as 12.1.1 and 12.2.2.