0PAOS_C01 - wrong Occupied Positions count

[Former Member]

Hi all.

I work with HR cube "Staffing Assignments" (0PAOS_C01). I get wrong number of occupied positions (0POS_OCC).

Before load data to InfoCube, I had loaded all necessary master data.

We use SAP Netweaver 2004s BI with all latest patches.

Any ideas whats wrong with "Occupied positions"?

regards,

Gediminas

[Colin4 · Accepted solution]

Check your own user id as well, for using RSA3.

Colin

[Former Member · Accepted solution]

Neccesary HR authorizations have been added to BIWREMOTE on BI server, but haven't to ALEREMOTE on ECC side.

We added them to ALEREMOTE but still I got wrong OCCUPIED POSITIONS number 😕

Maybe it is because of bad HR configuration on ECC side... don't have any idea anymore...

[Former Member · Accepted solution]

Hello Gediminas,

Below is a a piece of information you mentioned in your previous replies.

5 50000006 0 0 200907

6 50000006 0 0 200907

7 50000006 0 0 200907

How is it possible that the data source gets multiple records for a single position in the same month? The property of this data source is that it gets the status of every active position at the end of the month. From the sample data you have given here, it seems to be defying that logic. I always assume that the chances that the data source brings the wrong data are less so, it might be the problem with the data in R/3 itself. Which system are you testing this in? I mean if it is development system, the data might be bad. Please check the data itself. Else, move your testing to the testing system. Hope this helps.

Thanks and Regards

Subray Hegde

[Former Member · Accepted solution]

Subray, I'm getting 3 records because of different Pers. No (last column) :

5 50000006 0 0 200907 2538

6 50000006 0 0 200907 2539

7 50000006 0 0 200907

My question is this something wrong with configuration or is it normal to get several records per position per month if there were several persons assigned?

[Former Member · Accepted solution]

Hi,

This makes sense now. This totally depends on the configuration that you have in your system. These positions look like have more than one employee assigned on this month. Try this run the extractor checker for the same position but for a different Calmonth and see if the pattern continues. If it does, ask your R/3 functional consultant as to how is this set up. Also, check the vacancy factor for this position. This is a portion of what derives the key figure in the extractor. I still doubt the data.

Thanks and Regards

Subray Hegde

[Colin4]

The problem is your authorizations. Check the notes I mentioned.

Thats why you are getting zero ( chech this first )

Colin

[Former Member]

thanx Colin, I talked to my team, they said they already mentioned this note to our basis guy. I can't check profiles assigned to ALEREMOTE, because I don't have appropriate authoriztions. Will wait for basis to check if they really added all authorizations mentioned in note to a profiles.

Thanx for helpfull answer again

[Colin4]

Hi Gediminas,

Can you tell me what value you get in transaction RSA3 for 0HR_PA_OS_1 and what value

you should be getting or expect.

There are some document on help.sap.com, how to calculate these key

figures in the datasource:

http://help.sap.com/saphelp_nw70/helpdata/en/2b/c4df371aac9f4ae10000009b

38f8cf/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/7d/7ade37864c7529e10000009b

38f8cf/frameset.htm

http://wdfd00166031a:8080/BW_Support_Wiki/index.php/Image:BW-BCT-PA.doc

make sure you have the correct authorizations for BW & HR. OSS note 397208

Colin

[Former Member]

Hi, Colin.

Thax for the links, I've been read them all already.

I'm getting 0 on occupied positions in RSA3, though I except 100 % (or 1). I filtered one position for couple of months and got 8 records:

*******************************************************************

rec_no position occ_number unocc_num month

*******************************************************************

1 50000006 0 1 200906

2 50000006 0 1 200906

3 50000006 0 1 200906

4 50000006 0 1 200906

5 50000006 0 0 200907

6 50000006 0 0 200907

7 50000006 0 0 200907

8 50000006 0 1 200907

it is strange that extractor returns both zeroes for occup. and unoccup. positions in 5-7 records.

[Former Member]

Hi Gediminas,

I have implemented this cube in several projects before. This is a standard field and I haven't found any issue regarding the value that it projected. Please check the data itself because these key figures are pretty accurate.

Thanks and Regards

Subray Hegde

[Former Member]

Thanx, Subray

Which transaction do you use in ECC to check occupied and unoccupied positions?

[Former Member]

Hi Gediminas,

You can use either PO13 or PPOME/PPOSE t-codes to look at the positions. Hope this helps.

Thanks and Regards

Subray Hegde