Application Development 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
Showing results for 
Search instead for 
Did you mean: 

Authorization default values of transaction /MRSS/PLBOMGR for object /MRSS/

Former Member
0 Kudos

Hello,

When I add the tcode "/MRSS/PLBOORGM " throuh the menu tab and when I go the authrization tab and click on either

Change Authorization Data or Expert Mode for Profile Generation the is an error message stating the following :

======================================================================================

Authorization default values of transaction /MRSS/PLBOORGM for object /MRSS/PB1 inconsistent

Message no. 5@015

Diagnosis

The authorization fields contained in the authorization defaults are incomplete or incorrect.

System Response

The process had to be terminated to avoid generating inconsistent authorization data.

Procedure

Use transaction SU24 to adjust the authorization defaults to the object definitions in transaction SU21 and then repeat the process.

============================================================================================

SU24, the custom values maintained are same as SAP Default . Any suggestion?

Thanks

Osama Khalifa

1 ACCEPTED SOLUTION

Former Member
0 Kudos

This indicates one of two things resulting from changes to the authorization object AFTER SU22 had been maintained for it:

1) One or more of the fields were converted to org. levels using the "old" technique of maintaining the table instead of running the report for this.

2) One of more of the fields were changed in SU20 or SU21 but the original data in SU22 was not corrected.

Solution in both cases is to correct the proposals in SU24 (customer data) and report it to SAP to correct in SU22 (original SAP data).

Cheers,

Julius

1 REPLY 1

Former Member
0 Kudos

This indicates one of two things resulting from changes to the authorization object AFTER SU22 had been maintained for it:

1) One or more of the fields were converted to org. levels using the "old" technique of maintaining the table instead of running the report for this.

2) One of more of the fields were changed in SU20 or SU21 but the original data in SU22 was not corrected.

Solution in both cases is to correct the proposals in SU24 (customer data) and report it to SAP to correct in SU22 (original SAP data).

Cheers,

Julius