Problem while scheduling info package using HR datasource.

Question

hi experts,
while scheduling the info package i am getting the following error.
Delete init. request
REQU_D340A67OSEQ9A6Q2B20X9SIOM before running
init. again with same selection
I think by deleting the setup it will work...
am i right or is there any other solution for this problem..
please reply soon.
its too urgent.
thanks n regards.
uday shankar.

Answer 1

Hi,
You are correct there is no setup table concept in HR extractors.
But there is a cache. Usually HR extractions will be full load. But it also supports delta. There is no setup table concept in HR.Once you perform your init (with or without Data transfer your delta path is set and delta will follow else can go for Full loads alone. It will extract data from the relevant tables like generic extractors. The data will be filtered based on the selection parameters.
Except for payroll and time management rest all sub-functional areas supports only full load.
In case of full loads, old data needs to be deleted to avoid duplicated records in the target.
Auditing Information Technical name: 0HR_PY_PP_1
http://help.sap.com/saphelp_nw70/helpdata/EN/c7/532d7835db9a41b744aea58ed699ed/frameset.htm
Delta Update
This DataSource supports delta updates. The source system fills table HRMS_BIW_PPDELTA with the date and time of the first data transfer (initialization) and the date and time of all subsequent data transfers. This information enables the system to perform a delta transfer. It only selects posting runs with the above statuses whose last changed on date is after the date in table HRMS_BIW_PPDELTA.
If you use DataSources 0HR_PY_PP_2 (Posting Documents) and 0HR_PY_PP_1 (Auditing Information), you must transfer data to BW from both DataSources using the same selection criteria.
Also
http://help.sap.com/saphelp_nw04/helpdata/en/2a/77eb3cad744026e10000000a11405a/frameset.htm
https://websmp201.sap-ag.de/~sapdownload/011000358700004478862001E
/people/swapna.gollakota/blog/2008/01/14/one-stage-stop-to-know-all-about-bw-extractors-part1
step by step
https://websmp201.sap-ag.de/~sapdownload/011000358700004478862001E
HR extraction:
The HR module enables customers to effectively manage information about the people in their organization, and to integrate that information with other SAP modules and external systems
HR broadly has the following modules:
PA (Personnel Administration) and Organization Management
Personnel Development
Payroll Accounting
Time Management
Compensation
Benefits
Training and Events
The Personnel Administration (PA) sub module helps employers to track employee master data, work schedules, salary and benefits information. Personnel Development (PD) functionality focuses on employees' skills, qualifications and career plans. Finally, the Time Evaluation and Payroll sub modules process attendance and absences, gross salary and tax calculations, and payments to employees and third-party vendors
HR delivers a rich set of business content objects that covers all HR sub-functional areas.
How the data extraction happens:
Before getting into how the data gets populated into HR info cube
Let's understand the term info type
"An info type is a collection of logical and/or business-related characteristics of an object or person"
Here the data will be extracted from an info type (PA, PD, time management etc) and for few other applications it is from the cluster tables (Payroll, compensation etc.)
HR is basically master data centric because it is always related to people related Info Objects, such as Employee, Person. In most of the cases HR master data is defined as Time Dependent to enable historical evaluation. HR R/3 system records a specific period of validity for each Info type.
Procedure to extract the HR data:
Activate Data Sources in the Source system (R/3)
Replicate Data Sources in BW system:
Activate business contents in BW.
Populate HR cubes with data by scheduling info packages.
Note: Master Data should be loaded first
Except for payroll and time management rest all sub-functional areas supports only full load.
In case of full loads, old data needs to be deleted to avoid duplicated records in the target.
Check the below links for more information
Technical Considerations in Global SAP BW/HR Implementations
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/505351fe-ec8c-2910-c5b5-a43bbf53f6fc
BW/HR Implementation
https://websmp201.sap-ag.de/~sapdownload/011000358700004478862001E
Hope this helps.
Thanks,
JituK