Search Results is_employee_set

Overview

APPS.GL_WF_JE_APPROVAL_PKG is the Oracle General Ledger approval workflow engine package. It orchestrates the Journal Entry approval cycle within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments, providing the procedural logic that the Oracle Workflow engine invokes to route, validate, approve, reject, and forward journal entries submitted for authorization. It is the single integration point between the GL journal entry data model and the Workflow notification infrastructure.

Businesses use this package when they enable journal approval in the GL Journal Entries form, where the "Journal Approval" control must be set to "Yes." The package evaluates authorization limits, resolves the appropriate approver hierarchy, and generates workflow notifications to the responsible individuals according to the configured approval rules.

Key Procedures and Functions

The package exposes 26 documented procedures and functions. Its central entry point is START_APPROVAL_WORKFLOW, which initiates the approval workflow for a submitted journal entry. IS_EMPLOYEE_SET validates whether the preparer is a valid employee; the related person checks use PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F. GET_SOB_ATTRIBUTES and GET_JEB_ATTRIBUTES retrieve set of books and journal entry batch attributes needed to drive the workflow. IS_JE_VALID and SET_JE_INVALID manage journal validity flags, while DOES_JE_NEED_APPROVAL and SET_APPROVAL_NOT_REQUIRED determine whether approval is bypassed. CAN_PREPARER_APPROVE, SET_APPROVER_NAME, and SET_JE_APPROVER record the approver identity on the journal. APPROVE_JE and REJECT_JE apply the terminal decision to the journal entry. FIND_APPROVER and FIRST_APPROVER locate candidates from the authorization hierarchy; SET_CURR_APPROVER establishes the current approver; MGR_EQUALTO_APRV and GET_APPROVER_MANAGER handle manager-based routing. NOTIFYPREP_NOAPRVRESP notifies the preparer when no approver responds, and RECORD_FORWARD_FROM_INFO logs forwarding history.

Tables Accessed

The package reads and writes GL_JE_HEADERS, GL_JE_LINES, GL_JE_BATCHES, and GL_JE_APPROVAL_S to retrieve journal data and persist approval status. GL_LEDGERS and GL_LEDGERS_PKG supply ledger/Set of Books context via GET_SOB_ATTRIBUTES. GL_AUTHORIZATION_LIMITS provides the dollar thresholds that govern routing decisions. FND_USER, FND_PROFILE_OPTION_VALUES, and the FND_PROFILE packages resolve user identity and system profile options. PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F resolve employee and supervisor relationships. Workflow tables WF_LOCAL_ROLES, WF_NOTIFICATIONS, WF_PARAMETER_LIST_T, along with WF_CORE, WF_ENGINE, WF_EVENT, WF_DIRECTORY, WF_MONITOR, WF_ROLES, and WF_USERS, deliver notifications, manage roles, and record workflow events. DUAL and STANDARD are used for PL/SQL and SQL housekeeping.

Usage Notes

This package is invoked indirectly rather than being called by end users. It is triggered from the GL Journal Entry form when a user submits a journal for approval, and by the Oracle Workflow engine during the GL Journal Approval process. Concurrent and background workflow agents call it as notifications are delivered and responses recorded. The metadata confirms APPS.GL_WF_JE_APPROVAL_PKG is referenced by one other package and itself references GL_LEDGERS_PKG. Customizations should avoid modifying the package directly; extensions are typically built by subscribing to workflow events or by calling the package from custom code where approval state must be queried. Status is VALID in both 12.1.1 and 12.2.2, and no database object depends on it beyond the one referencing package, making it a stable integration surface.