Search Results ap_web_db_hr_int_pkg




Overview
Explore in AI Chat

Overview

AP_WEB_DB_HR_INT_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Payables (AP) module. Its name reflects its central role: an HR integration layer for the Oracle iSupplier / Payables web-based supplier and expense entry flows ("AP_WEB") that surface human resources data to authenticated web users. The package bridges Payables web functionality with Oracle HRMS and the Workflow directory, resolving the relationship between an FND_USER login and the underlying HR person, employee, assignment, and supervisor records. In this capacity it supports security filtering, approver derivation, and the display of employee information such as job, organization, and management hierarchy within Payables web pages.

The package is classified as type OTHER in the ETRM catalog and holds a VALID status across Oracle EBS 12.1.1 and 12.2.2. It is a foundational utility object: ETRM documents that it is referenced by 25 other database objects, while it depends on AP_WEB_DB_UTIL_PKG, AP_WEB_DB_HR_INT_PKG itself (recursive internal calls), and numerous HR and Workflow views. It is not referenced by any database object outside its dependent set in the catalog sense, but its downstream consumer base confirms it as a shared runtime dependency for Payables web security and employee lookup logic.

Key Procedures and Functions

The ETRM metadata documents 26 procedures and functions. Representative members include:

  • GETUSERIDFOREMPCURSOR — returns a cursor of user IDs associated with a given employee, supporting reverse lookup from person to FND_USER.
  • GETEMPLOYEEID, GETEMPIDFORUSER — resolve the HR employee identifier from a user context and vice versa.
  • GETEMPLOYEEINFO, GETEMPLOYEEINFOCURSOR — return employee biographical and assignment data, either as a single record or a ref cursor.
  • GETALLEMPLISTFORWEBUSERCURSOR, GETEMPLISTFORWEBUSERCURSOR, GETNUMOFEMPFORWEBUSER — enumerate the employees visible to a web user, honoring manager and security scoping, with a count function for pagination.
  • GETSUPERVISORID, GETSUPERVISORNAME, GETSUPERVISORINFO, GETSUPERVISORDETAILS, GETMANAGERIDANDSTATUS — derive the management chain, used to populate approver defaults and routing in Payables web approval workflows.
  • GETEMPORGID — return the organization identifier for an employee.
  • ISPERSONACTIVE, ISPERSONCWK (contingent worker), ISPERSONTERMINATED, GETEMPINACTIVEDATE — status predicates and dates that gate whether a person may act as an approver or appear in workflow routing.
  • GETSECURATTRCOUNT — count security attributes, supporting the AK web user security model.
  • GETVENDORANDVENDORSITE — return the vendor and vendor site associated with a user, connecting HR identity to supplier records.

Tables Accessed

Per the documented table list, the package reads AK_WEB_USER_SEC_ATTR_VALUES (web user security attribute values that constrain data visibility), FND_USER (application user accounts), PER_ASSIGNMENT_STATUS_TYPES (assignment status categories used by the active/terminated predicates), and DUAL (syntax anchoring). Dependency metadata shows broader access through APPS synonyms and HR views, including HR_EMPLOYEES_CURRENT_V, PER_ASSIGNMENTS_F, PER_PEOPLE_F, PER_PEOPLE_X, PER_EMPLOYEES_X, PER_EMPLOYEES_CURRENT_X, PER_CONT_WORKERS_CURRENT_X, PER_WORKFORCE_X, PER_WORKFORCE_CURRENT_X, FND_PROFILE, WF_USERS, WF_DIRECTORY, HR_PO_INFO, and APP_EXCEPTION. These are read (with APP_EXCEPTION used to signal errors) to resolve identity, employment status, assignment, supervisor, and workflow directory information without duplicating that data in Payables.

Usage Notes

AP_WEB_DB_HR_INT_PKG is invoked at runtime by Payables web pages and their supporting PL/SQL, typically through AP_WEB_DB_UTIL_PKG. It is called when a user opens an iSupplier or Payables web function that must display employee names, validate whether a person is an active employee or contingent worker, filter records by the user's security attributes, or default an approver from the supervisor hierarchy. Because its procedures accept no documented parameter lists in the ETRM extract, signatures should be confirmed against the actual package specification in the target instance before reuse. Direct references by 25 dependent objects indicate that customizations and extensions should call the package rather than replicating its HR security logic, and any modification to HR views or the Workflow directory can affect its results.