You can set up event enabled lookups that trigger the automatic association of the
appropriate Tax Reporting Unit (TRU) for an employee.
Auto TRU Association derives and associates the
appropriate TRU for an employee without manual intervention. The event-enabled lookups
determine when automation runs, and component-specific value sets determine which TRU is
returned.
Before you start
- Enable AUTO_TRU_ON_HIRE_GT when auto association is required for New Hire and GT
events.
- Enable AUTO_TRU_ON_LOC_CHANGE when auto association is required for Location
Change events.
- Create a value set for each TRU component to be automated.
- Add the component lookup code and set its meaning to the corresponding value-set
name.
Navigation:
Here's what to do
-
Configure the following lookup codes in the lookup type
ORA_HRX_IN_PAY_OVERRIDE
| Lookup Code |
Lookup Meaning |
| AUTO_TRU_ON_HIRE_GT |
ENABLED_AUTO_TRU_HIRE: Enables auto TRU association for
new hire and global transfer events. |
| AUTO_TRU_ON_LOC_CHANGE |
ENABLED_AUTO_TRU_LOC: Enables auto TRU association for
location change events. |
-
Create a lookup entry for every TRU component that needs to be automated. The
lookup meaning must be the exact name of the value set you've created. Each
value set query must return the TRU mapped to the relevant component.
| Lookup Code |
Lookup Meaning |
| PROFESSIONAL_TAX_TRU_VS |
Professional Tax TRU value set name |
| INCOME_TAX_TRU_VS |
Income Tax TRU value set name |
| PROVIDENT_FUND_TRU_VS |
Provident Fund TRU value set name |
| ESI_TRU_VS |
ESI TRU value set name |
|
LWF_TRU_VS
|
LWF TRU value set name |
|
NPS_TRU_VS
|
NPS TRU value set name |
-
You need to design the TRU value-set query using any combination of the
available runtime inputs that include:
- LEGISLATIVE_DATA_GROUP_ID
- PERSON_ID
- PSU_ID
- ASSIGNMENT_ID
- LOCATION_ID
- PAYROLL_RELATIONSHIP_ID
The query needs to return the TRU applicable to the employee and
effective-date context.
Here's an example that derives the Income Tax TRU using the organization, PSU,
establishment, legal entity, and the effective-date information.
| Definition Attribute |
Configured Value |
| Value Column Name |
xbp.NAME |
| ID Column Name |
orgStab.ORGANIZATION_ID |
| Order By Clause |
xbp.EFFECTIVE_FROM DESC |
FROM Clause
XLE_ETB_PROFILES xbp,
XLE_ENTITY_PROFILES xnp,
HR_ALL_ORGANIZATION_UNITS_F_VL orgStab,
HR_ALL_ORGANIZATION_UNITS_F_VL orgPsu,
hr_organization_information_f orgInfo,
HR_ORG_DETAILS_BY_CLASS_V orgDtls
WHERE Clause
xbp.ESTABLISHMENT_ID = orgStab.ESTABLISHMENT_ID
AND nvl(fnd_date.canonical_to_date(:{PARAMETER.EFFECTIVE_DATE}),sysdate)
BETWEEN orgStab.EFFECTIVE_START_DATE AND orgStab.EFFECTIVE_END_DATE
AND xnp.LEGAL_ENTITY_ID = xbp.LEGAL_ENTITY_ID
AND orgPsu.LEGAL_ENTITY_ID = NVL(xnp.PARENT_PSU_ID, xnp.LEGAL_ENTITY_ID)
AND nvl(fnd_date.canonical_to_date(:{PARAMETER.EFFECTIVE_DATE}),sysdate)
BETWEEN orgPsu.EFFECTIVE_START_DATE AND orgPsu.EFFECTIVE_END_DATE
AND orgInfo.ORGANIZATION_ID = orgStab.ORGANIZATION_ID
AND orgInfo.ORG_INFORMATION1 = 'HRX_IN_IT'
AND nvl(fnd_date.canonical_to_date(:{PARAMETER.EFFECTIVE_DATE}),sysdate)
BETWEEN orgInfo.EFFECTIVE_START_DATE AND orgInfo.EFFECTIVE_END_DATE
AND orgInfo.ORG_INFORMATION_CONTEXT = 'PER_TRU_TYPE'
AND nvl(fnd_date.canonical_to_date(:{PARAMETER.EFFECTIVE_DATE}),sysdate)
BETWEEN orgDtls.EFFECTIVE_START_DATE AND orgDtls.EFFECTIVE_END_DATE
AND orgDtls.CLASSIFICATION_CODE = 'HCM_PSU'
AND orgDtls.ORG_INFORMATION_CONTEXT = 'PER_PSU_PAYROLL_INFO'
AND orgPsu.ORGANIZATION_ID = orgDtls.ORGANIZATION_ID
AND orgPsu.ORGANIZATION_ID = :{PARAMETER.PSU_ID}
Tip:
- Confirm that the value set returns a valid TRU for the required PSU
and effective-date combinations.
- Validate automated association using representative employee events
in a test environment.
Results:
For an enabled event, the value set returns the most
recently effective TRU matching the employee's PSU and the supplied effective date. The
process then creates the applicable TRU association automatically.