Restricting time dependent records on employee master data in BW

Question

Experts,
We have a Future hire report which gets data from 0Employee. Now whenever hire date of an employee is getting assigned in case of new hire  record get's created in BW.
Now, due to some reason this new hire employee is not able to join on the hire date first assigned to him and new hire date is updated in PA30 for this employee in ECC.
This would create a new record in BW with new hire date for this employee which is valid in BW from the date it moved into BW till 9999 and the previous record 'Valid To' date is changed to previous date of the "Valid From" date of newly entered record.
Now all these records has moved into Multiple Cubes also therefore we cannot delete these records from Master data until transaction data is delete.
Client HR team is saying that previous records of all such employees are not valid , so they should not appear in BW reports even if they are running this report on historical dates.
0Employee is time dependent master data. So it makes sense to have one records for any actions done for an employee in HR system.
Cleaning up a master data for all such employee would be a tedious task and need lot of effort.
Is there any way , we can restrict previous records of all such employee , so that they do not appear in BW report in case users are going to run the report previous dates.

Answer 1

We were doing this activity as part of weekly house keeping job. Weekly we get list of invalid PERNR records from ECC team.
While deleting particular PERNR (say 10015824) from 0EMPLOYEE, and the log (SLG1)says, SID exists in DIM table (like /BIC/D0PA_C011).
First delete that PERNR (10015824) from cube (0PA_C01)
Use Tcode RSRV --> Tests in Transaction RSRV  --> All Elementary Tests --> Transaction Data --> Entries Not Used in the dimension of an InfoCube (Dbl Click)
             From the right side window, expand “Entries Not Used in the Dimension of an InfoCube” Node &
             Enter InfoCube (like 0PA_C01), click “Transfer”
             Now, click “Execute” (Toolbar)… and the results displayed in the right side window..
             Now, click “Correct error” (Toolbar)
Now, try to delete same PERNR from 0EMPLOYEE, and if the log says SID used in some other DIM table, follow the above process.
If the log says, the SID used in DSO/Cube, then goto manage (of DSO/Cube) and do the selective deletion.