VETS-100A - Employee Not Counted in Recently Separated VETS Column if Does Not Have a Military Status (Doc ID 1263250.1)

Last updated on OCTOBER 09, 2015

Applies to:

PeopleSoft Enterprise HRMS Human Resources - Version 8.8 SP1 to 9.1 [Release 8.8 to 9]
Information in this document applies to any platform.


In PER027, procedure Process-Estab-For-Recently-Separated-New-Hires (for Column T) selects employees based upon PS_PERS_MILIT_USA.MIL_DISCHRG_DT_USA, but does not use any PS_PERS_DATA_MAX.MILITARY_STATUS.

Procedure Process-Estab-For-Recently-Separated-EEs (for Column O), uses both PS_PERS_MILIT_USA.MIL_DISCHRG_DT_USA as well as PS_PERS_DATA_MAX.MILITARY_STATUS.

We believe only PS_PERS_MILIT_USA.MIL_DISCHRG_DT_USA is correct criteria for both procedures. Currently, if employee provides MIL_DISCHRG_DT_USA but does not provide MILITARY_STATUS , then Column O in under-counted.

The issue can be reproduced at will with the following steps:
1. Run Workforce Monitoring > Meet Regulatory Requirements > VETS-100 reports > VETS-100 Process (Report Type = VETS-100A)
2. Run Workforce Monitoring> Meet Regulatory Requirements > VETS-100 reports> VETS-100 Analysis
3. In the .pdf output, the new hire is counted under the Recently Separated Veteran column (Column T) if the employee has a Military Discharge Date but does not have a Military Status. However, the existing employee is NOT counted under the Recently Separated Veteran column (Column O) if he has a Military Discharge Date but does not have a Military Status. The calculation procedures for new hire and existing employee are not consistent.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms