Search Results per_eeo_mag_report




Overview
Explore in AI Chat

Overview

The APPS.PER_EEO_MAG_REPORT package is a PL/SQL package in the Oracle E-Business Suite (EBS) Human Resources (HR) module. Its name indicates that it supports reporting for EEO (Equal Employment Opportunity) and MAG (Minority Action Group / affirmative action) reporting, which are U.S. regulatory and compliance reporting requirements layered on top of core HR workforce data. In Oracle EBS 12.1.1 and 12.2.2, packages of this type assemble data from Human Resources foundation tables — organizations, locations, people, and assignments — to produce the structured workforce demographic and organizational detail that EEO/affirmative action reporting demands.

The package is owned by the APPS schema and currently holds a VALID status, confirming that the compiled package and package body are present and usable in the environment. Its ETRM classification is recorded as OTHER, meaning it is not a published public API but rather an internal/reporting utility. The documentation of the object confirms both a package specification and a package body, along with the embedded SQL statements that drive its data retrieval.

Key Procedures and Functions

The ETRM documentation lists a single documented program unit within this package:

  • EEO_MAG_REPORT — the package's primary (and only documented) procedure/function. Based on the package naming convention and the referenced tables, this unit is responsible for deriving or emitting the EEO/MAG report content — aggregating worker and organizational attributes into the report structure consumed by the corresponding report output. The documented metadata does not expose a parameter list, so the exact signature is not asserted here; only the purpose of the unit is described.

Because the package exposes one documented unit, the package is narrow in scope and functions essentially as a single-purpose reporting routine rather than a general-purpose toolkit.

Tables Accessed

The package reads from several HR tables through APPS synonyms. Each table contributes to a distinct aspect of EEO/MAG reporting:

  • PER_ALL_PEOPLE_F — the core person record (names, dates, personal attributes) needed to identify employees and applicants.
  • PER_ALL_ASSIGNMENTS_F — assignment/employment detail (organization, position, job, payroll) that establishes the worker's placement in the enterprise.
  • PER_ASSIGNMENT_STATUS_TYPES — assignment status classifications used to determine active versus inactive workforce membership for reporting inclusion.
  • PER_PEOPLE_EXTRA_INFO — person-level descriptive flexfield/extra information, frequently holding EEO-relevant attributes such as ethnicity, gender, or veteran status.
  • HR_ALL_ORGANIZATION_UNITS and HR_ORGANIZATION_INFORMATION — the organizational hierarchy and internal organization attributes that drive EEO categorization by unit.
  • PER_GEN_HIERARCHY_NODES — generic hierarchy node information supporting organizational roll-up and grouping in the report.
  • HR_LOCATIONS_ALL and HR_LOCATION_EXTRA_INFO — work location details and location-level extra information, used where reports require geographic or location-based breakdowns.

Together these tables allow the package to correlate people, their assignments, their organizational placement, and location/extra descriptive data into a consolidated regulatory report.

Usage Notes

PER_EEO_MAG_REPORT is an internal reporting package rather than a documented public API. According to the dependency data, it is referenced by no other packages, indicating it is not called as a service by other PL/SQL code. Its typical invocation is therefore more likely through the EBS reporting infrastructure — a concurrent program, an Oracle Reports/BI Publisher report definition, or a form-based report launch — that executes the EEO_MAG_REPORT unit to generate output. Customizations should treat it as a private implementation object: because it is classified as OTHER and not a published interface, direct calls from custom code are not recommended, and any reliance on it should be validated against the specific 12.1.1 or 12.2.2 release and patch level in use, since internal reporting packages can change between releases without API-level compatibility guarantees.