cancel
Showing results for 
Search instead for 
Did you mean: 

Business Content HR Extractors.

Former Member
0 Kudos
330

Hi All,

1. Most of the HR BCT extractors are not delta supported.

Which is the best way to implement delta on these

extractors?.

2. If any body experienced in HR data sources, what are

precautions we need to take while activation of

Business content.

Thnaks in advance.

RC

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanks for your suggetions.

Former Member
0 Kudos

Hi Ravi,

it would be nice, if you would assign some points to all guys helping you. It is the way to say thanks in SDN.

Siggi

Former Member
0 Kudos

Some points to be noted.....

i)Master Data Centric:

In Human Resources business, the people related InfoObjects, such as Employee, Person, and Applicant have tremendous amount of the attributes to describe them.

When reviewing SAP delivered HR business contents, it is important to recognize that although the Employee transaction data source consists of merely two data elements (InfoObjects 0employee & 0calmonth), the critical dimensions for drill down analysis can be brought in from Employee Master data as dimensional characteristics via update rules or as navigational attributes.

The former approach is used in the standard delivered business content for the Headcount and Action InfoCube. This approach added more overheads during the population of the InfoCube, but would yield better performance at query time. And without that we wouldn’t be able to report on the master data history correctly, e.g. changes in cost center, when doing time comparisons in BW queries.

ii) Time Dependency:

To preserve the Human Resources data for historical evaluation, HR R/3 system records a specific period of validity for each Infotype. In an HR decision support (DSS) environment, this is of particularly importance, as ‘point in time’ analysis is one of the key requirements for HR DSS.

BW/HR business contents delivered by SAP inherited the R/3 time constraints in HR Master Data to enable such essential requirement. Nearly all HR master data is defined as Time Dependent data. There are three types of time constraint master data in HR R/3.

Time constraint 1 is predominately used in Personnel Administration and Organizational Assignment data, which means the validity periods of the individual records must not overlap and must not have any gaps. This is quite important to be aware of when you loading master data into BW environment.

In time dependent Master data load, any overlapping record will result in error condition. If you have external source of master data to be integrated with R/3 data into BW environment, this will be an important design consideration. This is especially evident for parallel implementation of HR R/3 and BW.

If you converting the current data of active employees in R/3 environment often want to convert history data from legacy systems into BW and using BW as an environment for historical data storage and integration with the active employee data. If such requirement is mandatory, the conversion team must take the time dependency into consideration when integrate Employee, Person and Applicant master data.

Coming to the update part most of them support Full Updates as you dont have a lotta changes pften.

But Payroll, Time Management(Time & Labor Data) and CATS( Cross Application Time Sheets) very much support Delta.

Let me know if you need further information.

Former Member
0 Kudos

Ravi,

1) HR application logic is complicated and hence no delta support. The best way to go about it is to find out how far back are changes made. For e.g. changes made to employee masters are only after 1/1/2003. Once you have such a date, fix a safety period of a few months and extract full udpates for that period onwards. So in this example, re-load data from say 1/6/2002 onwards every month.

Delta is not too much of an issue with HR as you should nto have a requirement to load data daily in most cases and hence slightly loading times once a month are acceptable.

For datasources with very high volumns like payroll, delta support is possible.

2) Activation of business content - have fun. Ensure employee masters are updated and data is active before any other data is extracted.

Aneesh

Former Member
0 Kudos

Hi Ravi,

I think Aneesh already gave you the answers you need. Just on hint. In the project I worked on in the last year data load were scheduled from 3 months back in the past up to 1 year into the future. This covered the changes. Only sometimes (once or twice a year) it was necessary to back some more time.

Hope this helps

regards

Siggi