Search Results delete_approval_action

Overview

LNS_APPROVAL_ACTION_PUB is a public PL/SQL package within the Oracle E-Business Suite Lease Management (formerly Loans) module. It encapsulates the business logic governing approval actions taken against lease and loan records, and it functions as the supported programmatic interface for creating, modifying, retrieving, and removing approval action records. The package belongs to the APPS schema and is classified as a public API, meaning it is intended for invocation by both internal EBS components and external custom code, rather than being restricted to package-private use.

The header comment in the package body identifies a revision dating to 2008, with original authorship attributed to Bernice Lam in January 2004. The package supports integration with Oracle Approvals Management (AME), as evidenced by the presence of the IS_AME_ENABLED and AME_APPROVAL_ACTION_FROM_UI procedures, indicating that approval routing can be driven by AME rules where the relevant profile options are configured. Private helper routines, including a logging procedure that conditionally writes to FND_LOG.STRING based on the current runtime log level, provide internal diagnostics without exposing that machinery to callers.

Key Procedures and Functions

The package exposes eight documented procedures and functions:

• CREATE_APPROVAL_ACTION — Creates a new approval action record. Internally delegates to the private do_create_approval_action routine, which accepts an approval action record and returns the newly generated action identifier and a return status.
• UPDATE_APPROVAL_ACTION — Modifies an existing approval action. The private implementation accepts the action record, an object version number for optimistic locking, and a return status output.
• DELETE_APPROVAL_ACTION — Removes an approval action identified by its action identifier, returning a status indicator. This is the procedure most directly associated with the search term "delete_approval_action."
• GET_APPROVAL_ACTION_REC — Retrieves an approval action record for a given action, typically used to populate a record structure prior to update or display.
• APPROVE_ADD_RECEIVABLE — Performs the approval processing required to add a receivable, linking the approval action to receivable generation.
• APPROVE_LOAN_AM_ADJ — Executes approval logic for loan amount adjustments.
• IS_AME_ENABLED — Returns an indicator of whether Oracle Approvals Management is active for the current context.
• AME_APPROVAL_ACTION_FROM_UI — Handles approval action processing initiated from the user interface when AME integration is in effect.

Tables Accessed

The package reads and writes a broad set of Lease Management and shared EBS tables through APPS synonyms. The central transactional table is LNS_APPROVAL_ACTIONS, which stores the approval action records manipulated by the create, update, delete, and get procedures. Loan context is derived from LNS_LOAN_HEADERS, LNS_LOAN_HEADERS_ALL, LNS_LOAN_LINES, LNS_LOAN_HISTORIES_H, and LNS_LOAN_AMOUNT_ADJS, reflecting the package's role in approving loan amount adjustments. Supporting financial structures include LNS_DISTRIBUTIONS, LNS_FEE_ASSIGNMENTS, LNS_AMORTIZATION_SCHEDS, and AR_ADJUSTMENTS_ALL, the last used in the receivable approval flow. Conditions and their assignments are held in LNS_CONDITIONS and LNS_COND_ASSIGNMENTS. Shared EBS reference data is drawn from FND_LANGUAGES, FND_PROFILE_OPTION_VALUES (for profile-driven behavior such as AME enablement and logging), and JTF_RS_RESOURCE_EXTNS (for resource information associated with approvals).

Usage Notes

LNS_APPROVAL_ACTION_PUB is typically invoked from Lease Management forms, from concurrent programs performing batch approval processing, and from custom extensions requiring controlled manipulation of approval actions. Three other packages reference it, indicating reuse across the module. Callers should invoke the public procedures rather than the private do_* helpers, and should always inspect the returned status indicator before committing. The presence of object version numbers in the update path means callers must supply or preserve the correct version to avoid concurrent update conflicts. Because AME behavior is conditional, implementations should call IS_AME_ENABLED before assuming AME-driven approval routing applies.