Search Results delete_out_arg

Overview

The APPS.OKC_OUTCOME_PVT package body is the private implementation layer of the Oracle E-Business Suite Contracts (OKC) outcome API. It belongs to the ETRM (Enterprise Contracts) module and provides the procedural logic that creates, validates, updates, deletes, and locks outcome records and their associated arguments. Within Oracle EBS 12.1.1 and 12.2.2, outcomes represent the realized or anticipated results stored against a contract or contract line, and outcome arguments capture the detailed attribute-level values that qualify those results. The package is classified as a PVT (private) API, meaning it is not intended for direct invocation by external callers; instead, it exposes its behavior through the corresponding public wrapper package and related OKC APIs. The header comment ($Header: OKCCOCEB.pls 120.0) identifies the source as a Contracts module PL/SQL library unit shipped under the APPS schema.

Key Procedures and Functions

The package body implements 24 documented procedures and functions. The primary groupings are as follows.

• ADD_LANGUAGE — Registers or maintains language-specific seed data for outcome objects, delegating to okc_oce_pvt.add_language.
• CREATE_OUTCOMES_ARGS — Orchestrates a full outcome creation by first populating the master outcome record, propagating the generated identifier to the detail rows, and then populating the outcome arguments. It manages return status and message propagation across the subordinate calls.
• UPDATE_OUTCOMES_ARGS — Performs the corresponding master-and-detail update flow for an existing outcome and its arguments.
• VALIDATE_OUTCOMES_ARGS — Applies validation rules across both the outcome header and its argument collection.
• CREATE_OUTCOME / LOCK_OUTCOME / UPDATE_OUTCOME / DELETE_OUTCOME / VALIDATE_OUTCOME — The master-level operations that insert, lock, modify, remove, and validate an outcome record.
• CREATE_OUT_ARG / LOCK_OUT_ARG / UPDATE_OUT_ARG / DELETE_OUT_ARG / VALIDATE_OUT_ARG — The detail-level operations that manage individual outcome argument rows.

Each routine follows the standard EBS API convention, returning x_return_status, x_msg_count, and x_msg_data, and using OKC_API constants such as G_RET_STS_SUCCESS and G_RET_STS_UNEXP_ERROR to signal results. Notably, CREATE_OUTCOMES_ARGS invokes create_out_arg after establishing the foreign key link between the master outcome (oce_id) and its argument rows.

Tables Accessed

Per the documented ETRM metadata, the package references the table PLITBLM through APPS synonyms. This PL/SQL internal table is typically used by the language-handling routines invoked via ADD_LANGUAGE and related translation maintenance logic. The outcome and outcome-argument business data itself is manipulated through the ocev_rec_type and oatv_tbl_type record and table types passed between the package's procedures, which map onto the underlying OKC outcome and outcome-argument entities.

Usage Notes

Because OKC_OUTCOME_PVT is a private package, it is not intended for direct call from forms, concurrent programs, or custom code. It is referenced by one other documented package, which acts as the public entry point that a developer would invoke. Typical invocation patterns include the Oracle Contracts authoring forms, contract import or generation concurrent programs, and custom extensions that call the public OKC outcome API. Callers should always supply p_api_version and p_init_msg_list, check x_return_status against the OKC_API constants, and inspect x_msg_count and x_msg_data for validation failures before committing the transaction.