SU25 Upgrade Error - u201CAuthorization default values of transaction XXXX for

[shivraj_singh2]

Subject: After running SU25, the default (field) values for several authorization objects are missing

Description:

After running SU25, when we go to PFCG to update role in change mode, it does not allow it and system gives following error

u201CAuthorization default values of transaction XXXX for object X_XXXX_XXX inconsistentu201D

(Display mode gives the same error)

On opening the tcode in SU24 and checking for the field values for the object and comparing it with values in SU21 and TOBJ, - the object in SU24 is missing fields. While checking for the same object in our ECC 5 back up system in SU24, the fields are present.

For example: SM35

In ECC 6 after SU25 -

---

| In ECC 5.0

Object Field -

---

| Object Field

S_BDC_MONI BDCAKTI -

---

| S_BDC_MONI BDCAKTI

S_BDC_MONI BDCGROUPID -

---

| S_BDC_MONI BDCGROUPID

S_BTCH_JOB JOBACTION -

---

| S_BTCH_JOB JOBACTION

Missing |----

---

| S_BTCH_JOB JOBGROUP

[Bernhard_SAP]

Hello Shivraj,

to get rid of that inconsistency, simply change the proposals in SU24 (perform any change)->save.

Then undo your change and save again. (you need to perform a change, so that the correct values are copied again).

Then the inconsistency is repaired.

b.rgds, Bernhard

[Former Member]

Hi Bernhard

I've not encountered this problem but is there any other option to fix enmasse instead of one transaction at a time? If there are many transactions with inconsistent object fields it sounds like something major has happened?

Cheers

David

[Former Member]

I have encountered this a few times before and if the roles are intact then the easiest way is to list them all in SUPC and hit the "change authorizations" button once on one role from each of the series where the menu is the same.

The error message will tell you the object and via the where-used-list of proposals you will find the tcode in display mode. Note that fixing one will in some cases expose the next one, so double-check.

It takes about 10 minutes for a vanilla FI, CO, SD, MM type system and is completely stressfree... ... depending of course on how the roles had been built and maintained!

Cheers,

Julius

[Bernhard_SAP]

>

 it sounds like something major has happened?

Hi,

don't worry, the only thing that happend was the implementation of that consistency-check. some of the inconsistent values you may detect are years old.... As ther was no check in the past, nobody realized them...

b.rgds, Bernhard

[shivraj_singh2]

Thanks,

Switching the flag on/off in SU24 worked.