Correct DataSource to load data into 0EMPLOYEE InfoProvider.

Question

Hi Experts,
I am implementing BW (7.0) - HCM (ECC 6.0). We are implementing functional areas such as OM, PA, PY, Leave, Time, Work Pattern Management, EHS, LSO and Comeptencies. We are implementing using standard BCT (Business Content).
The most important InfoProvider I've noticed that would be used across almost all the functional areas is 0EMPLOYEE. Now I have noted that there are a couple of Standard DataSources that load data (mostly Full Updates) into 0EMPLOYEE as below:
      Techinca Name                  -         Description     
1) 0EMPLOYEE_ATTR                 -            Employee
2) 0EMPLOYEE_0077_ATTR       -            Employee - additional person data
3) 0EMPLOYEE_0016_ATTR       -            Employee - contract elements
4) 0EMPLOYEE_0763_ATTR       -            Long-Term Incentives Participant Data
5) 0EMPLOYEE_ID_ATTR            -            Employee - personnel ID
6) 0EMPLOYEE_USER_ATTR      -            Employee - system user name
7) 0HR_PA_0                               -            Employee
8) 0EMPLOYEE_TEXT                  -            Employee (This is not a concern)
Points to be noted are:
1) All the DataSources have PERNR (Personnel Number) in common that maps into 0EMPLOYEE (Employee Number) in BW along with various fields which makes sense.
2) Most of  the InfoPackages have Full Update.
My question is... which DataSources am I supposed to use to load 0EMPLOYEE? If all the DataSources, then in which sequence should I use the DataSources during Go-Live so that it is best suited for the project? Does this also mean that the PERNR field comes from only one table in ECC so that I don't have to bother about the Full Updates in various InfoPackages for different DataSources?
Also, are there any DataSources that I might have missed for 0EMPLOYEE?
Any help is much appreciated. Thanks in advance.
Regards,
Chandu

Answer 1

Hi,
Commonly I use 0employee_attr to get all data from HR infotypes, because when I want to add additionnal fields in 0employee_attr, I prefer focus on one datasource rather than managing several datasource.
But you can use any other datasources mentionned in your post to update data to 0employee infoobject.
In the HR BCT, 0employee is the main datasource that provide data from HR infotypes, but this datasource is only a full type.
You have 2 options :
1°) If your HCM manages alot of employee, you can face performance loading problems. So, most of the time people don't use 0employee_attr datasource, but create one customer datasource per infotype (delta enable via enddate). You will thus manage one DSO perdatasource to load the target infocube.
2°) If your HCM manages a range of employee which performance are OK, you can use 0employee_attr, and then use the standard BCT.
Load your data and check the performance.
The reason why performance of 0employee_attr is poor according to me is that the module function that extract data manage the "PROVIDE" function that align data from the several infotype according to begin and end date.
Form a BCT point of view you can use 0PAPA_C02 for headcount analysis and/or 0PA_C01 for heacount and action analysis. You can use these cubes and add addditionnal fields regarding to addintionnal information from your HR infotypes. In both cases,  they build a historical view per month of employee situtation, that is very insteristing in HR reporting.
Feel free to ask questions.