Search Results call_lease_approval_wf




Overview
Explore in AI Chat

Overview

PN_AM_WF is a PL/SQL package in the APPS schema that supports Oracle Property Manager's lease approval workflow processing. Its name reflects its role as the workflow and approval-management bridge for Property Manager (PN) lease-related transactions. In Oracle EBS 12.1.1 and 12.2.2, Property Manager lease records often require formal approval routing before they become active, and this package contains the server-side logic that initiates, evaluates, and tracks those approval cycles. It subscribes to Oracle Workflow as well as Oracle Approvals Management (AME), as evidenced by references to AME_CALLING_APPS and AME_TEMP_OLD_APPROVER_LISTS, allowing lease approval hierarchies to be derived from AME-based approver list generation.

The package operates primarily against lease data stored in PN_LEASES_ALL and supplementary detail records in PN_LEASE_DETAILS_ALL, and it works in tandem with PN_LEASE_PVT, the private API layer that performs the underlying lease validation and processing logic. It is classified in the ETRM repository as an OTHER API, meaning it is not a publicly documented open interface but rather an internal support package used by Property Manager's own forms and workflow processes.

Key Procedures and Functions

  • CALL_LEASE_APPROVAL_WF — Initiates the lease approval workflow for a lease request, launching the Oracle Workflow process used to route the document to the appropriate approvers.
  • GET_APPROVER — Determines the approver (or approver set) for a given lease approval request, typically by consulting AME or workflow routing rules.
  • GET_NOTIFICATION_AGENT — Retrieves the notification agent, that is the user or role to whom approval notifications should be sent.
  • RAISE_BUSINESS_EVENT — Publishes the relevant Oracle Workflow business event when an approval or status change occurs, enabling downstream integrations to react.
  • SET_APPROVAL_STATUS — Writes the current approval state (for example pending, approved, or rejected) back to the associated lease record.
  • SET_STATUS_ON_EXIT — Sets the final status of the approval workflow as the process completes, ensuring the lease reflects the terminal approval outcome.
  • UPDATE_STATUS — Performs the general update of the lease approval status field in the underlying lease table, used by both workflow callbacks and manual status transitions.
  • VALIDATE_LEASE_REQUEST — Verifies that a lease request is eligible for the approval workflow before it is submitted, guarding against invalid or incomplete submissions.
  • SUBMIT_PROGRAM — Submits the concurrent program associated with the lease approval process, useful for background processing of approval-related jobs.
  • WF_DEBUG — Provides workflow debugging output, a diagnostic aid when troubleshooting approval routing and notification failures.

Tables Accessed

  • PN_LEASES_ALL — The core Property Manager lease table; the package reads lease attributes and writes approval status values back to it.
  • PN_LEASE_DETAILS_ALL — Stores the detail lines associated with leases, consulted during submission and approval processing.
  • AME_CALLING_APPS and AME_TEMP_OLD_APPROVER_LISTS — Used with Oracle Approvals Management to obtain and apply approver list information for the lease transaction.
  • FND_APPLICATION and FND_USER — Reference application registration and user identity data, supporting notification agent and approver resolution.
  • PN_WF_ITEM_S — Holds workflow item keys and activity status for lease approval workflow instances.
  • WF_PARAMETER_LIST_T (SYS/STANDARD) — Supplies the Oracle Workflow parameter list type used when launching workflow processes.
  • DUAL and PLITBLM — Standard Oracle helper objects used for singleton selects and PL/SQL table manipulation.

Usage Notes

PN_AM_WF is an internal component rather than a formally published API. It is invoked primarily through the Property Manager lease approval workflow, from lease entry forms when a user submits a lease for approval, and through workflow callbacks such as SET_APPROVAL_STATUS and SET_STATUS_ON_EXIT that update the lease as the approval progresses. The concurrent program submission path (SUBMIT_PROGRAM) indicates it also participates in background approval-related processing. Customizations that need to query or drive lease approval status should ideally use supported Property Manager APIs such as PN_LEASE_PVT, but forms and workflow definitions that reference PN_AM_WF rely on its procedures directly. Because the package references AME objects, approvals require AME configuration for the Property Manager application context to resolve approvers correctly. Given its dependence on FND_WF and AME configuration data, changes to approval hierarchies or workflow definitions can affect its behavior without any change to the package itself.