RSA3 has 52,000 records, BW extracted 41,000 records?????????

[Former Member]

hi BW Experts,

am extracting payroll data. in R/3 RSA3 extract checker shows 51,000 records irrespective of the time period given which means all the records that is there in R/3 side is that much.

in BW while i am extracting, it has just extracted 41,000 records with the status green and reporting icon is available in the data target, when i have seen the contents, it has the data only till 2002/10 when it is suppose to have data till 2006/02.

please try to respond as soon as possible, points will be assigned.

would really appreciate any inputs in this issue.

Thanks in advance

[Former Member · Accepted solution]

Please check the start routines and update routines in transfer rules. There might be some restriction here.

Hope this helps.

Bhargava

[former_member234167]

Hello,

I think this has something to do with the problem i am facing with: In HR a wagetype can be changed during a payrollperiod. This creates a splitrecord: the wagetype appears twice in the PCL2 cluster. One before the split and one after. When loading in BW, BW takes them together as one record. Especially with the number field this can have undesirable consequences.

Kind regards,

Bernd

[Former Member]

Hi Lieu,

You might look over the RSA3 tips of Note 529789.

Which Payroll extractor are you using?

Dave

[Former Member]

Do you have an ODS or anything in the dataflow ?

[Former Member]

Hi all,

I appreciate your quick responce.

Coming to the data flow there was an ODS object included but now we are not selecting the ODS object, only the datatarget infocube 0PY_C02 for the data source 0HR_PY_1.

Message was edited by:

lieu c

[Former Member]

Lieu,

Since you have already identified the missing data being after 10.2002, I suggest you look for an OSS fix.

I had a similar issue with a Business Content extractor where RSA3 shows over 100K records, but the BW load brought only 21K records every time, and this data got cut off at 10.2005. It turns out that the older extractor has ABAP codes not compatible with new BASIS upgrade.

I would go to SAPNET and look for the fix.

[Former Member]

do u mean that i need to go for OSS raising a call for this. if so i will do.

i am extracting in the Development client, recently R/3 development side had some patch work done and after that we have tested few extracted based on the patch in SAP Release notes in BW Dev if those extractors are working fine or not and they are all working fine. And then R/3 production had this patch work done successfully. in the mean time forget about R/3 production client but when i am extracting in BW Dev from R/3 Dev i am facing this problem.

any other SAP Release notes or any other inputs please.

[Former Member]

i am sorry all, i should confess that there is a start routine in update rules which has these include program in that start routine RS_BCT_HR_PAPA_UPDATE_RULES

rs_bct_hr_update_rules_general

apart from this i have seen in update rules that there is a routine for language, age, gender but i cannot understand what exactly they are doing, i mean the code.

secondly when i set the break point in the above include program and press F5, it is not acting in any way then i entered /h - tcode and then pressed F5 then also no change and after that i tried clicking again the red color break point and it has taken to debugging mode but dont know what those programs are, i kept on debugging but nothing showed up related to the program where i set the break point.

[Former Member]

OK, you don't know how to work the OSS thing so let me give a brief explanation here:

OSS notes are SAP software bug fixes. When SAP found a bug in the released software, they create a document that describes the issue together with instruction on how to fix it. Most of the time, the fix is the ABAP codes that you have to apply to your SAP system.

The most common way to search for these notes is at the SAP Service Market place website. You can find it with Google. You will need an account to access the content.

It's probably best that you ask an experienced SAP person to show you how to do this.

[Former Member]

The BC codes in HR start routines usually don't filter data records.

Since you don't understand these codes, you can alway check the messages in the Details tab in your infopackage monitor. If the extraction message said 49000 records extracted then you know for sure the start routine has nothing to do with the fact that your cube has only 41K records compares to 52K in RSA3. Or if the extraction message said 52K records extracted, then the 49K records in the cube was the result of some sort of filtering.

[Former Member]

thank you joe. but do u know how to raise a call in sap service marketplace, because i heard that we can ask or post questions to them.

[Former Member]

joe, i understand that it gets filtered before it enters to PSA only. why is it so when i ran Full load, extracted 51,000 records

when i ran init of Delta load, extracted 41,000 records

any idea on this? BW experts your inputs are appreciated.

[Former Member]

Yes you can report your system issues to SAP on the same website where you look for OSS note. You must have an OSS ID for the system you are working on (OSS ID normally created by Basis people). You basically write a report to SAP describing the problem. They normally reply by writing, but some time you may get a call as well.

[Former Member]

With this new info regarding diff between full and init loads, I found OSS note 834195 that may describe your issue (?).

Summary

Symptom

During initialization of the delta procedure for the Payroll Extractor 0HR_PY_1, you want to only transfer data from a particular key date, and not all accounting data. You may want to do this for example to reduce the dataset during initialization.

Other terms

Payroll Extractor, 0HR_PY_1

Reason and Prerequisites

In the standard version, no period selections are taken into account during the delta initialization, to ensure the consistency of the delta method.

Solution

Using a minor modification, you can have the system only extract data during initialization that is generated after a key date. Specifically, this means that a comparison with the RUNDATE and RUNTIME fields of the settlement directory is executed. In test systems, this may result in unexpected results because the run date often does not correlate with the period (for example, test data is created for previous years with a current creation date). The key date must also be adjusted accordingly if settlement runs occur in the previous period.

<b>However, individual retroactive accounting results in the period before this date may be transferred, which may produce a marginally larger dataset.</b>

Note that this note is valid for the version of the Payroll Extractor as of Plugin 2004.01 and at least Release 4.6C. Earlier versions are dealt with in note 360043.

Implement the source code corrections in line with the correction instructions in function module HRMS_BIW_EXTRACT_PY1.

Header Data

Release Status: Released for Customer

Released on: 09.02.2007 13:27:13

Priority: Recommendations/additional info

Category: Consulting

Primary Component: BW-BCT-PY Payroll Accounting

<b></b>

There is also this note, but it is much older 336216:

Summary

Symptom

During the extraction of DataSource 0HR_PY_1 without time selection, the number of records in the full update differs from the number of records in the delta init mode.

Additional key words

InfoSource, OLTP, load data

Cause and prerequisites

Without explicit time selection in the InfoPackage, the data was only extracted until the day when the loading took place in the case of the full update (SY-DATUM).

Solution

When you implement the attached correction, the system loads the data without time period restriction in the case of the full upload (as with delta init).

Source code corrections

Header Data

Release Status: Released for Customer

Released on: 26.09.2000 22:00:00

Priority: Correction with medium priority

Category: Program error

Primary Component: BW-BCT Business Content and Extractors

Secondary Components: BW-BCT-PA Personnel Management

[Former Member]

However, individual retroactive accounting results in the period before this date may be transferred, which may produce a marginally larger dataset.------can u explain me clearly on this because if it result in larger data set then in the extraction what i have done has lesser dataset. like instead of extracting 51,000 it has extracted 41,000.

[Former Member]

Activate the madter data and apply change run on the in info object.

Then, load the data to the cube.

Ravi Thothadri

[Former Member]

Hi,

Make sure that all the data for 0PERSON and 0EMPLOYEE master data is uploaded into BIW.That means you should have 01.01.1000 as the value for start date and 31.12.9999 as the value for End date in the update tabpage of those Master data info pckages. And donot forget to activae the Master data after completion of master data upload.

And then reupload the data to cube from PSA. .

With rgds,

Anil Kumar Sharma .P

[Former Member]

Hi Lieu,

also check if any selections are made in the info packages ...

Regards,

Sally

[Former Member]

HI,

there is no selection in info package and secondly there are no update and start routine. any other inputs please?

[Former Member]

Check if you mapped all the fields in the datasource to the infoobjects in communication structure and update rules to the data target.

Hope this helps.

Bhargava

[Former Member]

ya, everything is perfectly mapped..