Search Results check_function

Overview

APPS.PER_US_EEO4_PKG is a US-specific Oracle HRMS reporting package that supports the "EEO4 Report (XML)" concurrent program in Oracle E-Business Suite 12.1.1 and 12.2.2. The EEO4 report is the annual Employer Information Report (Standard Form 100, commonly called the EEO-1) that covered US employers must file with the Equal Employment Opportunity Commission. The report classifies an organization's workforce by job category, gender, race and ethnicity, and salary band, and the package assembles the aggregated counts required for each report line.

The package was created on 27-JUN-2006 (version 115.0) and subsequently patched. Version 115.2 (28-JUL-2006) introduced the CHECK_FUNCTION and GET_FUNCTION_NUMBER functions under bug numbers 5409988 and 5415136 respectively. Version 115.6 (31-JUL-2006, bug 5414756) added a p_dynamic_where parameter to GENERATE_SQL to handle employees earning more than 70,000 per annum. The package is declared AUTHID CURRENT_USER and its header source file is peruseeo4.pkh.

The package defines PL/SQL record and collection types that shape the report data, including emp_rec (job function, lookup code, salary range, and consolidated male and female counts across white, black, Hispanic, Asian and Indian categories), func_rec (job function and description), and the table types function_data, full_time_emp_data, other_full_time_emp_data, and new_hire_emp_data.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions:

• CHECK_FUNCTION and GET_FUNCTION_NUMBER — added in version 115.2; they validate and resolve job function/EEO category classifications used to group employees on the report.
• POPULATE_FT_EMP_DATA, POPULATE_OFT_EMP_DATA, POPULATE_NH_EMP_DATA — populate the internal collections for full-time employees, other full-time employees, and new hires respectively.
• GENERATE_SQL — builds the dynamic query used to extract employee data; the p_dynamic_where parameter allows callers to inject filtering logic, such as isolating salaries above 70,000.
• GENERATE_XML_DATA, GENERATE_HEADER_XML_DATA, GENERATE_JURIS_CERT_XML_DATA, GENERATE_FOOTER_XML_DATA, GENERATE_FT_XML_DATA, GENERATE_OFT_XML_DATA, GENERATE_NH_XML_DATA — produce the XML fragments for the report body, header, jurisdiction certificate, footer, and the three employee population sections.
• CONVERT_INTO_XML and CREATE_XML — convert the collected data into XML and assemble the final document.
• CREATE_REPORT and WRITE_TO_CONCURRENT_OUT — assemble the completed report and write it to the concurrent program output file.
• GET_LOOKUP_MEANING — retrieves the display meaning of lookup codes used for job function and salary range.

Tables Accessed

The package references two HRMS tables through APPS synonyms: HR_ALL_ORGANIZATION_UNITS and HR_ORGANIZATION_INFORMATION. These supply the organization and classification information used to identify the reporting establishment and its attributes for the EEO4 submission. DBMS_SQL is used to execute dynamically constructed SQL, consistent with the GENERATE_SQL procedure and its p_dynamic_where parameter. PLITBLM is an Oracle-supplied PL/SQL table-to-index conversion utility used for array processing within the package. No application tables outside these are documented as being written by the package; it functions primarily as a read-and-aggregate reporting component.

Usage Notes

PER_US_EEO4_PKG is invoked by the EEO4 Report (XML) concurrent program rather than by a data-entry form. A user submits the concurrent request from the US HRMS responsibility, supplying the required organization and reporting parameters, and the package populates its collections, generates the XML, and writes the result to the concurrent manager output. Because it is declared AUTHID CURRENT_USER, it executes with the privileges of the invoking user and is normally run from the APPS schema.

The package is not referenced by any other package, so its interfaces are effectively internal to the concurrent program. The addition of CHECK_FUNCTION and GET_FUNCTION_NUMBER indicates that report correctness depends on valid job function classification; implementers extending or troubleshooting the report should verify the lookup values and organization classification data that these functions rely upon.