Search Results update_con_admin_manager




Overview

OKC_REP_UPD_CON_ADMIN_PVT is a private PL/SQL package in the Oracle Contracts (OKC) module of Oracle E-Business Suite. Its purpose is to provide the underlying implementation for a mass-update utility that reassigns the Contract Administrator on a selected set of contracts. The package name reflects its role: OKC (Contracts), REP (Repository), UPD (Update), CON_ADMIN (Contract Administrator), PVT (Private). The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the defining schema, and it carries a standard global package name constant plus a reference to OKC_API.G_FND_APP for the FND application identifier.

The business problem addressed is administrative continuity. Over the life of a contract, the employee designated as Contract Administrator may leave the organization, change roles, or be replaced. Rather than manually opening each contract and editing the administrator field, this package allows a controlled bulk reassignment across Blanket Sales Agreements, Sales Orders, Quotes, and Repository Contracts. The header comment explicitly limits the scope to Sell and Other intent contracts, so Buy-intent (procurement) documents are outside its remit. This makes the package a repository-side maintenance tool rather than a transactional document API.

Key Procedures and Functions

The package exposes a single documented procedure, UPDATE_CON_ADMIN_MANAGER. According to the embedded API comment block, it is classified as a Private API and its stated function is "API to update Contract Administrator of Blanket Sales Agreements, Sales Orders, Quotes and Repository Contracts (Sell and Other intent only)." It has no documented pre-requisites.

The procedure is designed as a concurrent-program-style entry point: it returns errbuf and retcode as OUT parameters, the standard signature used by Oracle EBS concurrent managers, and accepts a p_doc_type IN parameter that is marked Required. The p_doc_type value determines which class of contract is targeted, since the procedure handles several distinct document families. The remaining parameters are optional filters that narrow the population of contracts affected: p_cust_id restricts by customer, p_prev_con_admin_id restricts by the existing administrator, p_salesrep_id restricts by salesperson, p_sales_group_id restricts by sales group (noted as applying to quotes), and p_org_id restricts by operating unit. The administrator to be assigned is passed through the salesperson parameter, since contract administration in this context is tied to the JTF resource/salesrep model. The package also declares the E_Resource_Busy exception with PRAGMA EXCEPTION_INIT mapped to Oracle error -00054 (resource busy), indicating that the update path anticipates row-lock contention and surfaces it as a named exception rather than a generic failure.

Tables Accessed

The package touches a broad cross-section of tables, consistent with its multi-document scope. Contract repository records are read and updated in OKC_REP_CONTRACTS. Blanket Sales Agreements and Sales Orders are handled through OE_BLANKET_HEADERS and OE_ORDER_HEADERS respectively, with OE_TRANSACTION_TYPES_TL supplying translated transaction type names. Quotes are handled through ASO_QUOTE_HEADERS, and sales group descriptions come from JTF_RS_GROUPS_TL. Salesperson identity and validation draw on JTF_RS_SALESREPS and FND_USER.

Customer filtering joins to HZ_CUST_ACCOUNTS and HZ_PARTIES in the Trading Community Architecture model. Operating unit and organization lookups use HR_ALL_ORGANIZATION_UNITS and its TL translation table. Document type and intent classification, which enforce the Sell and Other intent restriction, derive from OKC_BUS_DOC_TYPES_B and OKC_BUS_DOC_TYPES_TL. Finally, FND_NEW_MESSAGES is referenced to surface user-facing notifications or error messages back through the concurrent request log.

Usage Notes

Because UPDATE_CON_ADMIN_MANAGER is a private package and reports errbuf/retcode, it is normally invoked from a concurrent program registered in the Contracts responsibility, allowing administrators to submit a mass contract administrator reassignment and review results in the concurrent request output. The documented metadata records zero dependent packages, confirming it sits at the bottom of the call stack and is not itself called by other documented APIs.

The Required p_doc_type means callers must explicitly state which document family is being processed; the procedure does not infer it. Users should also note the intent restriction, the row-lock sensitivity implied by E_Resource_Busy, and the fact that optional filters combine as narrowing predicates — omitting them widens the update population, so filters such as p_cust_id, p_prev_con_admin_id, p_salesrep_id, p_sales_group_id, and p_org_id should be supplied deliberately. Custom code may call the procedure directly, but must respect the AUTHID CURRENT_USER behavior and provide the correct OKC privileges. As a private implementation package, it is not part of the supported public API surface, and its signature may change between patch levels; reliance on it should be treated accordingly.