12 validated Oracle Fusion HCM SQL queries for EEO-1 headcount, ACA FTE calculation, FLSA overtime eligibility, and SOX audit trails. Written for real environments, not demos.
Get the Compliance Pack ($499) →One-time purchase. Delivered within 24 hours. 30-day guarantee.
The right tables, race/ethnicity codes, and job category mappings take days to find without a guide.
Getting variable-hour employee status wrong creates IRS exposure. The PAY_ query logic is non-obvious.
Producing role change history, segregation of duties conflicts, and payroll approvals from HCM tables under time pressure.
Every query includes: table references, join conditions, date-effective filter pattern, and inline comments explaining each clause. Ready to run in BI Publisher or direct SQL access.
Maps PER_ALL_PEOPLE_F ethnicity codes to EEOC categories. Joins to per_persons_legislative_f for US-specific data. Handles multi-ethnicity respondents per EEOC 2007 instructions.
Cross-reference Oracle job codes to EEO-1 job categories (1.1 Executive, 1.2 Senior Professional, 2 Professional⦠9 Laborers). Includes unmapped job audit.
W-2 earnings bucketed into the 12 EEOC pay bands by job category and demographic. Joins PAY_PAYROLL_ACTIONS and element classification for W-2 wage elements only.
Counts FTEs using the monthly measurement method. Includes part-time FTE equivalents (hours Γ· 120). Aggregates to employer-level for ALEs and controlled group determinations.
Identifies employees crossing the 30-hour ACA threshold mid-measurement period. Pulls from PAY_RUN_RESULT_VALUES and PER_ALL_ASSIGNMENTS_M with averaging logic.
Validates offer-of-coverage code logic (1Aβ1J lines 14β16) against enrollment and benefit election data in BEN_* tables. Flags indicator mismatches before filing.
Identifies workers classified as exempt vs non-exempt. Cross-checks salary against DOL threshold ($684/week as of 2024). Flags potential misclassifications by job title and salary level.
Pulls hours worked from HWM_TIME_ENTRIES vs element results in PAY_RUN_RESULTS. Calculates regular rate of pay including non-discretionary bonuses for accurate 1.5x overtime base.
Identifies users with conflicting HCM role combinations (e.g., both Payroll Entry and Payroll Approval). Joins HCM security tables to produce conflict matrix by user and conflict type.
Lists all users with HCM super-user or sensitive data access roles. Includes last login date, role assignment date, and approver. Point-in-time snapshot for audit evidence.
Flags payroll runs where element totals vary more than 5% from prior period. Excludes approved variance reasons. Produces the management review evidence auditors expect.
Comprehensive action history from PER_ACTION_OCCURRENCES and PER_ASSIGNMENT_SUPERVISORS_F. Shows who changed what, when, and which supervisor approved. Standard SOX evidence package.
-- EEO-1 Category 1 Headcount -- Reports as of: snapshot date (typically Oct 15 or Dec 31) -- Tables: PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_M, -- PER_PERSONS_LEGISLATIVE_F, PER_JOBS_F, HR_LOCATIONS_ALL SELECT -- EEO-1 job category from Oracle job code mapping jm.eeo1_category, -- EEOC race/ethnicity codes mapped to standard labels CASE pl.ETHNIC_GROUP WHEN '2' THEN 'Hispanic or Latino' WHEN '1' THEN 'White (Not Hispanic)' WHEN '4' THEN 'Black or African American' WHEN '7' THEN 'Asian' WHEN '5' THEN 'American Indian or Alaska Native' WHEN '3' THEN 'Native Hawaiian or Other Pacific Islander' WHEN '6' THEN 'Two or More Races' ELSE 'Not Disclosed' END AS race_ethnicity, p.SEX AS gender, COUNT(*) AS headcount FROM PER_ALL_PEOPLE_F p JOIN PER_ALL_ASSIGNMENTS_M a ON a.PERSON_ID = p.PERSON_ID AND a.PRIMARY_FLAG = 'Y' AND a.ASSIGNMENT_TYPE IN ('E','C') AND :snapshot_date BETWEEN a.EFFECTIVE_START_DATE AND a.EFFECTIVE_END_DATE JOIN PER_PERSONS_LEGISLATIVE_F pl ON pl.PERSON_ID = p.PERSON_ID AND pl.LEGISLATION_CODE = 'US' AND :snapshot_date BETWEEN pl.EFFECTIVE_START_DATE AND pl.EFFECTIVE_END_DATE JOIN eeo1_job_category_map jm -- supplied mapping table ON jm.oracle_job_code = a.JOB_CODE WHERE :snapshot_date BETWEEN p.EFFECTIVE_START_DATE AND p.EFFECTIVE_END_DATE AND a.ASSIGNMENT_STATUS_TYPE = 'ACTIVE_PROCESS' GROUP BY jm.eeo1_category, pl.ETHNIC_GROUP, p.SEX ORDER BY jm.eeo1_category, race_ethnicity, gender
Each query in the pack includes the full version with all join conditions, date-effective filters, gotcha comments, and notes on which BI Publisher data source type to use.
12 production SQL queries β EEO-1 (3), ACA (3), FLSA (2), SOX (4)
EEO-1 job category mapping table β Oracle job codes β EEOC categories template
ACA measurement period cheat sheet β monthly vs lookback method explained
FLSA salary threshold table β current DOL thresholds by exemption type
BI Publisher data model setup notes β parameter binding, multi-dataset joins
Inline SQL comments β every clause explained for customization
Oracle Fusion 24B-compatible β tested against PER_ALL_ASSIGNMENTS_M patterns
30-day email support β we'll help adapt any query to your environment
All queries are written for Oracle Fusion Cloud HCM Release 13 (current cloud version) and tested through Oracle 24B. The assignment queries use the 24B-recommended PER_ALL_ASSIGNMENTS_M pattern instead of the deprecated _F table.
These are physical SQL queries β they require either BI Publisher with a direct database connection, a custom report with SQL data source, or BIP access through Oracle Fusion's built-in analytics layer. They will not run in OTBI (Logical SQL). Each query includes BI Publisher setup notes.
The queries produce the correct headcount breakdowns. Your legal or HR team should validate the job category mappings for your specific Oracle job codes before filing. We include a mapping template to simplify that validation step.
Email us with your Oracle version and the error. We include 30 days of email support to help adapt the query to your environment. If we can't get it working, full refund β no questions asked.
Yes. The OTBI Template Pack ($97) contains Logical SQL queries for OTBI/Oracle Analytics. This Compliance SQL Pack contains physical SQL for BI Publisher and direct database access β different technology, different use cases. Most compliance reporting requires physical SQL because OTBI subject areas don't expose the raw legislative data needed for EEO-1 and ACA calculations.