Introduction
In Oracle Fusion HCM, understanding backend tables is critical for reporting, integrations, and troubleshooting. One such foundational structure is the Legislative Data Group Table in Oracle Fusion HCM. If you’ve worked on payroll, workforce structures, or HDL/BIP reports, you’ve likely interacted with Legislative Data Groups (LDGs) either directly or indirectly.
From a consultant’s perspective, LDG is not just a configuration—it drives how legislative rules, payroll processing, and country-specific compliance are handled. At the database level, the LDG table acts as a central reference point connecting multiple HCM components.
This blog explains the LDG table in detail, including how it is used in real implementations, how to query it, and how it impacts integrations and reporting.
What is Legislative Data Group in Oracle Fusion?
A Legislative Data Group (LDG) represents a partition of payroll and legislative data based on country-specific requirements.
Think of LDG as:
- A legal boundary for payroll processing
- A container for legislative rules
- A link between legal employers and payroll definitions
Key Concept
Each LDG is tied to:
- A legislation (country)
- One or more legal employers
- Payroll configurations like:
- Payroll definitions
- Elements
- Balances
- Fast formulas
Example
| Country | LDG Name | Usage |
|---|---|---|
| India | India LDG | Payroll for India employees |
| US | US LDG | US payroll & tax compliance |
| UK | UK LDG | HMRC payroll processing |
Legislative Data Group Table Details
From a technical standpoint, LDG data is stored in the following table:
Core Table
PER_LEGISLATIVE_DATA_GROUPS
Key Columns
| Column Name | Description |
|---|---|
| LEGISLATIVE_DATA_GROUP_ID | Primary Key |
| NAME | LDG Name |
| LEGISLATION_CODE | Country Code (IN, US, UK) |
| BUSINESS_GROUP_ID | Enterprise reference |
| EFFECTIVE_START_DATE | Start date |
| EFFECTIVE_END_DATE | End date |
| OBJECT_VERSION_NUMBER | Used for concurrency |
Why LDG Table is Important in Oracle Fusion
From an implementation perspective, LDG impacts multiple areas:
1. Payroll Processing
- Payroll definitions are tied to LDG
- Elements are created per LDG
- Payroll runs cannot cross LDG boundaries
2. Security & Data Partitioning
- Data is segregated by LDG
- Prevents mixing of legislative rules
3. Reporting & Integrations
- Used in:
- BI Publisher reports
- OTBI subject areas
- HDL loads
- OIC integrations
Key Features of Legislative Data Group
1. Country-Based Segregation
Each LDG is mapped to a legislation.
2. Payroll Dependency
All payroll objects are dependent on LDG.
3. Legal Employer Mapping
Multiple legal employers can belong to one LDG.
4. Reusability
Shared configurations across legal entities within same legislation.
Real-World Business Use Cases
Use Case 1: Multi-Country Payroll Implementation
A global organization operates in:
- India
- US
- UK
Each country has:
- Separate LDG
- Independent payroll processing
- Local compliance rules
Impact:
- Separate payroll runs per LDG
- Different statutory deductions
Use Case 2: BI Publisher Payroll Reporting
A client needs a report showing:
- Employee salary details
- Tax deductions per country
Solution:
Join tables:
- PER_ALL_PEOPLE_F
- PAY_PAYROLL_ACTIONS
- PER_LEGISLATIVE_DATA_GROUPS
Filter by:
Use Case 3: HDL Data Load Validation
While loading payroll data using HDL:
- LDG must match employee’s legal employer
- Incorrect LDG causes load failures
Configuration Overview
Before LDG is used, the following setups must exist:
- Enterprise structure
- Legal employers
- Legislative data groups
- Payroll definitions
Navigation Path
Navigator → Setup and Maintenance → Manage Legislative Data Groups
Step-by-Step Configuration in Oracle Fusion
Step 1 – Navigate to LDG Setup
Navigator → Setup and Maintenance
Search Task: Manage Legislative Data Groups
Step 2 – Create Legislative Data Group
Enter details:
- Name: India LDG
- Legislation Code: India
- Enterprise: Vision Enterprise
Step 3 – Assign Legal Employers
Map legal employers to LDG.
Step 4 – Save Configuration
Click Save and Close
How LDG Table is Used in SQL Queries
Sample Query
ldg.LEGISLATIVE_DATA_GROUP_ID,
ldg.NAME,
ldg.LEGISLATION_CODE,
ldg.EFFECTIVE_START_DATE,
ldg.EFFECTIVE_END_DATE
FROM
PER_LEGISLATIVE_DATA_GROUPS ldg
WHERE
ldg.LEGISLATION_CODE = ‘IN’;
Advanced Join Example
papf.person_number,
papf.full_name,
ldg.name AS legislative_data_group
FROM
per_all_people_f papf,
per_legislative_data_groups ldg
WHERE
papf.business_group_id = ldg.business_group_id;
Testing the Setup
Scenario: Validate LDG Assignment
- Create a legal employer
- Assign it to LDG
- Create employee under that legal employer
Validation Steps
- Check employee record
- Verify payroll assignment
- Confirm LDG consistency
Expected Result
- Employee inherits correct LDG
- Payroll processes successfully
Common Implementation Challenges
1. Incorrect LDG Mapping
Issue:
- Payroll fails or data mismatch
Solution:
- Verify legal employer assignment
2. HDL Load Errors
Issue:
- LDG mismatch during load
Solution:
- Use correct LDG reference in HDL files
3. Reporting Issues
Issue:
- Missing records in reports
Solution:
- Ensure LDG joins are correct
4. Multi-LDG Confusion
Issue:
- Mixing LDG across countries
Solution:
- Always filter by LEGISLATION_CODE
Best Practices
1. Always Filter by LDG in Reports
Avoid cross-country data issues.
2. Maintain Naming Standards
Example:
- India LDG
- US LDG
3. Validate LDG During Integrations
In OIC integrations:
- Pass LDG as parameter
- Validate before processing
4. Use LDG in Security Design
Restrict access based on LDG.
5. Avoid Hardcoding IDs
Always use:
- LEGISLATION_CODE
- NAME
instead of IDs.
Expert Consultant Tips
- During payroll implementation, define LDG early
- Align LDG with business expansion plans
- Always validate LDG before go-live
- Use LDG in OTBI filters to avoid performance issues
Summary
The Legislative Data Group Table in Oracle Fusion HCM is a core component that ensures proper segregation of payroll and legislative data. From configuration to reporting and integrations, LDG plays a central role in maintaining compliance and system integrity.
Understanding the LDG table is essential for:
- Payroll consultants
- Technical developers
- Integration specialists
For deeper reference, always check official Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html
FAQs
1. What is the main purpose of Legislative Data Group?
It separates payroll and legislative data based on country-specific rules and ensures compliance.
2. Can multiple legal employers share the same LDG?
Yes, as long as they belong to the same legislation.
3. Which table stores LDG data in Oracle Fusion?
The primary table is PER_LEGISLATIVE_DATA_GROUPS.