Search Results lns_submit_for_approval_pub




Overview
Explore in AI Chat

Overview

APPS.LNS_APPROVAL_ACTION_PUB is a public PL/SQL package within the Oracle E-Business Suite Lease and Loan Management (LNS) module family. Its business purpose is to manage the approval actions recorded against lease and loan contracts managed in Oracle Leasing and Loans. In the ETRM (Enterprise Contracts and Transactional Management) 12.2.2 schema, the package carries the PUB API classification, indicating that its procedures are intended to be callable by external programs, forms, workflows, and other packages rather than being restricted to internal use. The package encapsulates the persistence and retrieval of approval action rows, and it also exposes logic for approving specific loan or lease related transactions such as receivables additions and loan amount adjustments. Because approval routing in EBS frequently depends on Oracle Approvals Management (AME), the package additionally provides a flag procedure to determine whether AME is enabled, plus a routine that translates a user interface interaction into the corresponding AME approval action. The object is documented with VALID status in the ETRM metadata, confirming it is the current generation of the API in the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

  • CREATE_APPROVAL_ACTION — Inserts a new approval action record, capturing the approval state associated with a lease or loan transaction.
  • UPDATE_APPROVAL_ACTION — Modifies an existing approval action, for example to advance its status or correct its attributes after a review.
  • DELETE_APPROVAL_ACTION — Removes an approval action record, typically when a transaction is withdrawn, cancelled, or re-routed.
  • GET_APPROVAL_ACTION_REC — Retrieves a single approval action record so callers can inspect the current approval state without querying the underlying table directly.
  • APPROVE_ADD_RECEIVABLE — Approves the addition of a receivable associated with a lease or loan, driving the downstream adjustment posting.
  • APPROVE_LOAN_AM_ADJ — Approves a loan amount adjustment, validating the adjustment and progressing it through the approval lifecycle.
  • IS_AME_ENABLED — Returns a Boolean-style indicator of whether Oracle Approvals Management is active for the current context, allowing callers to branch between AME-driven and native approval handling.
  • AME_APPROVAL_ACTION_FROM_UI — Maps a user interface action into the AME approval action representation, synchronizing front-end decisions with the AME engine.

Tables Accessed

The package reads and writes a broad set of lease, loan, and approval tables through APPS synonyms. The core transactional tables include LNS_APPROVAL_ACTIONS, LNS_LOAN_HEADERS and LNS_LOAN_HEADERS_ALL, LNS_LOAN_LINES, LNS_LOAN_AMOUNT_ADJS, LNS_LOAN_HISTORIES_H, LNS_DISTRIBUTIONS, LNS_AMORTIZATION_SCHEDS, LNS_FEE_ASSIGNMENTS, LNS_CONDITIONS, and LNS_COND_ASSIGNMENTS. Approval-related adjustments may also touch AR_ADJUSTMENTS_ALL. Setup and reference data come from FND_LANGUAGES, FND_PROFILE_OPTION_VALUES, and JTF_RS_RESOURCE_EXTNS, the latter supplying resource and approver identity information. Collectively these tables provide contract header, line, distribution, fee, condition, and historical context needed to determine and record approval outcomes.

Usage Notes

LNS_APPROVAL_ACTION_PUB is invoked from Oracle Forms when users perform approval actions on lease and loan records, and from Oracle Workflow, which references the package to drive routing decisions. It is also referenced by the sibling packages LNS_APPROVAL_ACTION_PUB_W (the wrapper) and LNS_SUBMIT_FOR_APPROVAL_PUB, meaning custom code that submits a lease or loan for approval will indirectly exercise this API. The ETRM dependency documentation confirms the package is referenced by three other packages in the APPS schema, and that it itself depends on SYS.STANDARD and, indirectly, on the LNS_APPROVAL_ACTION_PUB object body. Developers extending approval logic should call the published procedures rather than issuing DML against LNS_APPROVAL_ACTIONS directly, since the API enforces AME integration and keeps approval history consistent.