Search Results delete_contact

Overview

OKL_CONTRACT_PARTY_PUB is the public application programming interface for managing the party and contact associations attached to an Oracle Lease Management (OKL/ETRM) contract. In Oracle EBS 12.1.1 and 12.2.2, the package exposes a controlled, API-layer entry point through which external callers can create, maintain, and remove the contact and role records that link a lease or loan contract to the parties involved — lessees, lessors, vendors, and related business contacts. The package is declared with AUTHID CURRENT_USER and delegates its core processing to the private implementation package OKL_CONTRACT_PARTY_PVT, whose complex entity object subtypes (ctcv_rec_type/ctcv_tbl_type for the contract-contact view and cplv_rec_type/cplv_tbl_type for the contract-party link view) are re-exposed as public subtypes. This design follows the standard Oracle EBS PL/SQL API pattern, in which sensitive validation and DML logic reside in a private package and a thin public wrapper provides the supported interface, message stack handling, and API-version governance.

Key Procedures and Functions

• CREATE_CONTACT — The primary entry point associated with the user search term. It inserts a new contact association for a contract, accepting either a single contact record (record-based overload operating on the ctcv_rec_type) or a set of records (table-based overload operating on the ctcv_tbl_type) and returning the created record(s) with system-populated attributes.
• UPDATE_CONTACT — Modifies existing contact records for a contract, again offered in both a single-record and a table (bulk) overload so that multiple contacts can be maintained in one call.
• DELETE_CONTACT — Removes a contact association from a contract, exposed as a record-based operation matching the create and update signatures.
• CREATE_K_PARTY_ROLE — Establishes a party role (for example, a lessee or lessor role) for a contract, using the cplv entity structures exposed by the public subtype declarations.
• UPDATE_K_PARTY_ROLE — Maintains the attributes of an existing contract party role.
• DELETE_K_PARTY_ROLE — Removes an existing party role assignment from the contract.

All procedures follow the standard EBS API signature convention: an API version, an optional message-list initialization flag, the three standard OUT parameters (return status, message count, and message data), and the entity record or table. Return status values are governed by the OKC_API constants.

Tables Accessed

The documented table reference for the public package is PLITBLM, accessed through an APPS synonym. In this context the base table stores the persistent rows representing contract contacts, party roles, and their associated descriptive or relationship attributes. The public package performs only the API-level interaction with this structure; the substantive inserts, updates, deletes, and validations are issued from OKL_CONTRACT_PARTY_PVT. Because the object operates on the OKL contract party model, the underlying columns correspond to the contract identifier, party identifier, contact attributes, and role qualifying information managed by the Lease Management data model.

Usage Notes

OKL_CONTRACT_PARTY_PUB is invoked rather than calling DML against the underlying tables directly, so that standard validations, message-stack accumulation, and API versioning are preserved. Typical callers include the OKL contract entry and maintenance forms, which route contact and party-role changes through the API layer, and Lease Management concurrent programs that import or synchronize contract party data in bulk — the table-based overloads exist specifically for these bulk processing cases. It is also the supported interface for custom extensions and third-party integrations that must attach contacts or party roles to a lease contract. Only the CREATE, UPDATE, and DELETE operations listed in the documentation are guaranteed public; the package maintains global g_ctcv_rec and g_cplv_rec variables for internal session consistency, and callers must always inspect x_return_status, x_msg_count, and x_msg_data before assuming success.