Search Results get_doc_eit

Overview

APPS.PAY_US_EMPLOYEE_PAYSLIP_WEB is a PL/SQL package that implements the server-side logic behind the Oracle E-Business Suite Online Payslip Views, the self-service pages through which employees view their payroll payslips. The package encapsulates the queries, formatting rules, and legislation-specific calculations required to render a payslip and the associated "Choose Payslip" selection list. Its source header identifies it as pyusempw.pkh, with the last notable version recorded at 120.12 (2010/11/16). Although the name carries the US prefix, the change history shows the package was progressively extended to support non-US legislation, including Arabic Hijrah calendar display and Japanese payslip performance improvements. It is a supporting (non-API) package and is referenced by 49 other packages, making it a foundational component of the payroll self-service stack.

Key Procedures and Functions

The package exposes twenty documented procedures and functions. The payslip data retrieval group includes GET_DOC_EIT, which resolves the assignment's date of commencement EIT (extra information type) content for display; GET_FORMAT_VALUE, which returns a formatted value for a payslip field; GET_MEANING_PAYSLIP_LABEL, which resolves the display label for a given payslip element from the lookup meanings; and FORMAT_TO_DATE, a utility that converts a value into a display-ready date string.

The employment and assignment group includes GET_PROPOSED_EMP_SALARY, GET_EMP_ANNUALIZATION_FACTOR, and GET_ASGN_ANNUAL_HOURS, which together derive salary and annualization attributes used to present earnings consistently on a payslip. GET_TERM_INFO returns termination-related details where applicable.

The legislative and jurisdiction group includes GET_LEGISLATION_CODE, GET_JURISDICTION_NAME, and GET_FULL_JURISDICTION_NAME, which identify the payroll legislation and resolve jurisdiction labels for display. GET_SCHOOL_DSTS_NAME resolves school district naming, supporting jurisdiction-specific localization requirements.

The payment and distribution group includes GET_CHECK_NUMBER, GET_NETPAYDISTR_SEGMENT, CHECK_EMP_PERSONAL_PAYMENT, and CHECK_US_EMP_PERSONAL_PAYMENT. The two check functions determine whether an employee has personal payment method data available, a prerequisite for rendering payment information on the payslip. The Arabic Hijrah support is provided by GET_DISPLAY_LIST, added under version 115.26 to drive the Choose Payslip list.

Tables Accessed

The package reads primarily from payroll and assignment tables via APPS synonyms. The core selection and processing tables are PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS, PAY_ACTION_INFORMATION, and PAY_ACTION_INTERLOCKS, which together define payroll runs and their action-level details. Assignment context is drawn from PER_ALL_ASSIGNMENTS_F, with payroll definitions from PAY_ALL_PAYROLLS_F. Earnings and deduction values come from PAY_RUN_RESULTS and PAY_RUN_RESULT_VALUES, with input definitions in PAY_INPUT_VALUES_F. Payment method and type lookups are sourced from PAY_ORG_PAYMENT_METHODS_F, PAY_PAYMENT_TYPES, and PAY_PRE_PAYMENTS. Legislative configuration is read from PAY_LEGISLATIVE_FIELD_INFO. Organizational and location attributes are supplied by HR_ORGANIZATION_INFORMATION and HR_LOCATION_EXTRA_INFO. Most access is read-only, consistent with a reporting and display package.

Usage Notes

The package is invoked through the Online Payslip Views self-service flow rather than directly by end users. It is called by the payslip rendering logic within Oracle iRecruitment-style self-service pages, the payslip action information view (pay_perf_payslip_action_info_v), and by other packages — the reference count of 49 reflects its role as a shared utility. Customizations that extend payslip content typically call the formatting and lookup functions (GET_FORMAT_VALUE, GET_MEANING_PAYSLIP_LABEL, GET_FULL_JURISDICTION_NAME) rather than modifying the package itself, since it is an Oracle-owned, non-API object. Any direct call should respect the AUTHID CURRENT_USER declaration noted in the header and avoid relying on internal cursors such as get_choose_payslip or get_jp_choose_payslip, which are implementation details subject to change across releases.