Search Results validate_change_request

Overview

The APPS.OKC_CHANGE_REQUEST_PUB package is the public application programming interface for Oracle Contract Management (OKC), the contracts module within Oracle E-Business Suite. It exposes the change request entity to external callers—forms, concurrent programs, workflow, and custom extensions—so that change requests raised against contracts can be created, maintained, validated, and removed through supported API calls rather than through direct table manipulation.

The package header carries a AUTHID CURRENT_USER declaration, meaning that external routines execute with the privileges of the invoking schema; grants on the package are therefore used to control which database accounts may call the API. The $Header line indicates the file OKCPCRTS.pls at version 120.0, dated 2005, which is consistent with a stable API surface carried forward across the 12.1.1 and 12.2.2 releases. The package defines local subtype aliases (crtv_rec_type, crtv_tbl_type, corv_rec_type, corv_tbl_type, cprv_rec_type, cprv_tbl_type) inherited from OKC_CHANGE_REQUEST_PVT, giving callers strongly typed record and table structures for change requests, change definitions, and change party roles. Global variables of these types are also declared at package level.

Key Procedures and Functions

ETRM documents 34 procedures and functions on this package. The entity-level operations are:

• CREATE_CHANGE_REQUEST, UPDATE_CHANGE_REQUEST, DELETE_CHANGE_REQUEST — the core maintenance verbs for a contract change request header.
• LOCK_CHANGE_REQUEST, VALIDATE_CHANGE_REQUEST — concurrency and business-rule verification entry points. VALIDATE_CHANGE_REQUEST is the packaged validator that callers invoke to confirm a change request satisfies the module's mandatory attribute and referential rules before it is committed or pushed into approval.
• CREATE_CHANGE, UPDATE_CHANGE, DELETE_CHANGE, LOCK_CHANGE, VALIDATE_CHANGE — the equivalent lifecycle verbs for individual change lines attached to a request.
• CREATE_CHANGE_PARTY_ROLE, UPDATE_CHANGE_PARTY_ROLE, DELETE_CHANGE_PARTY_ROLE, LOCK_CHANGE_PARTY_ROLE, VALIDATE_CHANGE_PARTY_ROLE — maintenance of the parties and roles participating in a change request.
• PUT, GET, RESET — generic accessors that move records into and out of the package's global state and reinitialize it.
• ADD_LANGUAGE — the standard multi-language installation hook used to seed translated lookup rows.

Each maintenance procedure follows the EBS API convention of accepting p_api_version and p_init_msg_list, and returning x_return_status, x_msg_count, and x_msg_data, with the payload supplied and returned through the typed record or table parameters. Callers should inspect x_return_status against OKC_API.G_RET_STS_SUCCESS and drain x_msg_count before proceeding.

Tables Accessed

The excerpted source does not enumerate the OKC tables directly; the documented references exposed through APPS synonyms in the package body are DBMS_LOB (used for large-object manipulation of descriptive or clause content) and PLITBLM (the PL/SQL table-to-database index-by manipulation utility). The change request, change, and party role tables themselves are reached indirectly through the private package OKC_CHANGE_REQUEST_PVT, which owns the base-table DML. In practice this means the public package reads and writes the OKC change request schema while delegating the low-level statements to its private counterpart.

Usage Notes

This package is referenced by three other packages in the ETRM inventory, confirming its role as a shared public entry point rather than a leaf routine. It is normally invoked from the Contract Management change request forms layer, from workflow or approval processes that need to validate a request before advancing it, and from custom PL/SQL extensions integrated through the standard API with p_init_msg_list => OKC_API.G_TRUE, an explicit p_api_version, and full error-stack handling. Because the package runs with invoker's rights, the calling schema must hold execute privilege on OKC_CHANGE_REQUEST_PUB; custom code should never bypass it to update the underlying OKC tables directly, as validation and concurrency logic reside inside the API and its private package.