Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

HR objects in SPAU

Go to solution
TMNielsen
Contributor

‎2011 May 09 11:17 AM

0 Likes
1,286

Hi

We have just upgraded from SAP ECC 6.0 without enhancement packs - to SAP ECC 6.0 Enhp4.

In the SPAU list we now find a lot of HR objects - personnel calculation rules, Symbolic constants and wage types and others.

Examples:

Personnel Calculation Rule Z001

Wage Type 09 2400

Form 09 9MOO

Group for sem. short text for PD plan AUTSW

Semantic short name for PD plan ORGPD

Symbolic constants (with currency) 09 &FKMI

Most of the object has the yellow traffic light, but some of the wage types has the green "Object has been adjusted" mark.

I have implemented and run report RSUMOD_CHECK_NON_TADIR from oss note 634146, but that didn't remove any entries. The report returned this list:

R3TR PFCS XDIST
R3TR PFCS XNET
R3TR PFCS XPA
R3TR PFCS XPAY
R3TR PFCS XRETR
R3TR PFCS XWPBP
R3TR SCVI 2_6310
R3TR SCVI 7_6310

Can anyone tell me what to do with the HR objects?

Best regards

Thomas Madsen Nielsen

1 ACCEPTED SOLUTION
Read only

Go to solution
PedroGuarita
Active Contributor

‎2011 May 09 12:06 PM

0 Likes
689

I have had this issue in every Upgrade as well. These objects don't have versions so it's hard to analyse exactly what they are. I usually check the tranport that was responsible for the object and see what was done, most of them are creation or changes to wagetypes configuraration due to OSS Notes implementation (manually). So, i know it will be a bit of a pain to analyse this, but it's the safest way. Most of them have the yellow light, so check all objects for one order for example, and reset them to standard and see the efect. On the downside, if something is lost, you will have to implement the changes again over the standard, but usually, since these are due to manually implemented notes, the back to standard should be ok.

I have had this issue in every Upgrade as well. These objects don't have versions so it's hard to analyse exactly what they are. I usually check the tranport that was responsible for the object and see what was done, most of them are creation or changes to wagetypes configuraration due to OSS Notes implementation (manually). So, i know it will be a bit of a pain to analyse this, but it's the safest way. Most of them have the yellow light, so check all objects for one order for example, and reset them to standard and see the efect. On the downside, if something is lost, you will have to implement the changes again over the standard, but usually, since these are due to manually implemented notes, the back to standard should be ok.

Reply
1 REPLY 1
Read only

Go to solution
PedroGuarita
Active Contributor

‎2011 May 09 12:06 PM

0 Likes
690

I have had this issue in every Upgrade as well. These objects don't have versions so it's hard to analyse exactly what they are. I usually check the tranport that was responsible for the object and see what was done, most of them are creation or changes to wagetypes configuraration due to OSS Notes implementation (manually). So, i know it will be a bit of a pain to analyse this, but it's the safest way. Most of them have the yellow light, so check all objects for one order for example, and reset them to standard and see the efect. On the downside, if something is lost, you will have to implement the changes again over the standard, but usually, since these are due to manually implemented notes, the back to standard should be ok.