Search Results get_employee_certificate_xml

Overview

PAY_NO_EOY_ARCHIVE is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Norwegian End-of-Year (EOY) reporting and archiving process within Oracle Payroll. Its primary business function is to extract, collate, and archive payroll data required for statutory year-end reporting to Norwegian authorities. The package assembles employee, employer contribution, and reporting code information into a structured XML payload that can be retained for audit and regulatory compliance purposes. In the context of Oracle EBS 12.1.1 and 12.2.2, this package forms part of the localized Norwegian payroll legislative solution. ETRM classifies the package with an API classification of OTHER, indicating that it is an internal, non-public API not intended for general customer extension. The status is VALID, confirming that the package is compiled and available in the APPS schema. It depends on the SYS.STANDARD package and is not referenced by any other package, meaning it is typically invoked directly by concurrent programs or forms rather than through a layered dependency chain.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions that collectively drive the extraction workflow. The processing lifecycle is anchored by INITIALIZATION_CODE, ARCHIVE_CODE, and DEINITIALIZATION_CODE, which set up, execute, and tear down the archive operation. RANGE_CODE and ASSIGNMENT_ACTION_CODE manage the selection of payroll assignment actions and the applicable date or data ranges. Two collation routines, EXTRACT_REPORTING_CODE and COLLATE_REPORTING_CODE, gather and consolidate the reporting code values used to classify earnings and deductions for the year-end return.

Data retrieval is handled by GET_AUDIT_DATA, GET_EMPLOYER_CONTRIBUTION_DATA, and GET_EMPLOYEE_CERIFICATE_DATA (documented spelling), each collecting a distinct category of payroll information. Corresponding XML generation is performed by GET_EMPLOYER_CONTRIBUTION_XML and GET_EMPLOYEE_CERTIFICATE_XML, which render the retrieved data into the required reporting format. EMPLOYED_THROUGHOUT_YEAR evaluates whether an employee was continuously employed across the reporting period.

Supporting utility functions include GET_PARAMETER, GET_INFO_PROMPT, GET_INFO_DTYPE, GET_CODE_DESC, and GET_XML_ORID, which supply concurrent program parameters, prompt text, data type metadata, lookup code descriptions, and XML object identifiers respectively.

Tables Accessed

The package reads and writes a range of HRMS and Payroll tables through APPS synonyms. Payroll action data is sourced from PAY_ACTION_CONTEXTS, PAY_ACTION_INFORMATION, PAY_ASSIGNMENT_ACTIONS, and PAY_ASSIGNMENT_ACTIONS_S. Balance and classification information is drawn from PAY_BALANCE_CLASSIFICATIONS, PAY_BALANCE_DIMENSIONS, PAY_BALANCE_TYPES, and PAY_DEFINED_BALANCES, which determine how earnings and contributions are categorised for reporting. Organization and location details come from HR_ALL_ORGANIZATION_UNITS, HR_LOCATIONS_ALL, HR_ORGANIZATION_INFORMATION, and HR_SOFT_CODING_KEYFLEX, supporting employer identification and statutory reporting attributes. Fast Formula contexts and globals are accessed via FF_CONTEXTS and FF_GLOBALS_F, and reference values are resolved through FND_LOOKUP_VALUES. These tables provide the demographic, assignment, and balance inputs that feed the XML extraction.

Usage Notes

PAY_NO_EOY_ARCHIVE is typically invoked from a Norwegian year-end reporting concurrent program or a dedicated payroll form, rather than being called directly from custom code. The initialization, extraction, archive, and deinitialization procedures are executed in sequence to produce and store the EOY archive. As an OTHER-classified internal API with zero referencing packages, it should be treated as unsupported for direct customer invocation; any bespoke integration should instead call the standard concurrent program that wraps it. In both EBS 12.1.1 and 12.2.2 the package behaves identically, as the Norwegian legislative logic resides in the APPS schema rather than the file system. Administrators reviewing EOY runs should verify that INITIALIZATION_CODE completes before ARCHIVE_CODE executes, since parameter and context setup failures will otherwise abort the extraction.