Search Results update_approval_action

Overview

The APPS.LNS_APPROVAL_ACTION_PUB_W package is a public PL/SQL wrapper that exposes the approval action transactions of the Oracle Loans (LNS) module within Oracle E-Business Suite 12.1.1 and 12.2.2. In the Loans business flow, an approval action represents the recorded decision taken against a loan or loan-related object as it moves through the underwriting and authorization lifecycle. Each action captures the decision date, the acting approver, the associated loan identifier, and a set of status and descriptive attributes that together define the outcome and sequencing of the approval step.

This package is the published, externally callable surface through which application logic creates and maintains those approval action records. It is declared as AUTHID CURRENT_USER, meaning the procedures execute with the privileges of the invoking session rather than the definer, so the calling applications must themselves hold the necessary object privileges. The package header carries the signature LNS_APACT_PUBJ_S.pls, version 120.0.12010000.3, last updated in April 2010, confirming its presence across both the 12.1.1 and 12.2.2 code lines. The _W suffix and the presence of a companion specification indicate that this is the wrapper layer of the Loans approvals public API, delegating business validation and persistence to the underlying private implementation.

Key Procedures and Functions

The documented API surface consists of two procedures:

• CREATE_APPROVAL_ACTION — Creates a new approval action record. It accepts a message-list initialization flag, a set of typed positional parameters (p1_a0 through p1_a31) that carry the date, numeric, and character attributes of the action, and returns the generated action identifier through x_action_id along with the standard API status trio x_return_status, x_msg_count, and x_msg_data.
• UPDATE_APPROVAL_ACTION — Updates an existing approval action. It takes the same message-list flag and positional attribute parameters, and additionally accepts p_object_version_number as an in-out parameter to enforce optimistic locking, returning the same standard status trio.

Both procedures follow the Oracle Application Object Library (AOL) API conventions: callers initialize the message list, inspect x_return_status for FND_API.G_RET_STS_SUCCESS, and drain messages with the standard FND_MSG_PUB routines when the status indicates an error. Parameter naming is positional and generic, reflecting a generated or signature-based wrapper rather than a hand-authored business API, so callers should rely on the recorded ETRM/technical documentation or the underlying validator to confirm the meaning of each positional slot.

Tables Accessed

The documented metadata does not enumerate the specific tables read or written through APPS synonyms, and the package is recorded as referencing no other packages. Based on its function, the procedures persist rows into the Loans approval action entity and read supporting Loans and approval setup data to validate the incoming attributes. Consumers requiring exact object-level lineage should confirm the base tables through the ETRM table-usage extract or by reviewing the package body in the target environment, since this information is not exposed in the supplied metadata.

Usage Notes

This package is a backend API and is not intended for direct end-user invocation. It is typically called from Oracle Forms-based Loans approval screens, from concurrent programs that process approval transactions in batch, and from custom extensions or integrations that need to record approval decisions programmatically. Because it is recorded as referenced by zero other packages, it is positioned as a leaf-level public entry point rather than a shared internal dependency. When invoking it from custom code, callers must respect AOL API conventions—initialize the message list, check the return status, and supply the correct object version number on updates to avoid stale-write errors.