topic Re: Object P_ORGIN inconsistent in Application Development and Automation Discussions

Object P_ORGIN inconsistent

Former Member — Thu, 26 Oct 2006 07:17:36 GMT

Hi all,

I have created a new Role and inserted the Tcode OOOE in the menu tab and when click on change authorization data in Authorization tab it pops up with an error message

“Authorization default values of transaction OOOE for object P_ORGIN inconsistent”.

Message no. 5 @ 015

Diagnosis

The authorization fields included in authorization default values are incomplete or incorrect

System Response

The action is terminated to avoid inconsistent authorization data

Procedure

In transaction SU24, modify the authorization default values in object definition from transaction SU21, and repeat the action.

I have checked the values of P_ORGIN using SU21 & SU24 and they have default values. How to make the P_ORGIN object consistent?

Thanks in Advance

Ravi

Re: Object P_ORGIN inconsistent

Former Member — Thu, 26 Oct 2006 10:10:27 GMT

Hello,

After switch over to the authorization TAB u will get another screen to define organizational level....i think in that one u have to select the value according to u r requirement.....or u can select full authorization over there but i dont know the impace of that giving full authorzation.

Re: Object P_ORGIN inconsistent

Former Member — Fri, 27 Oct 2006 07:14:01 GMT

Kamlesh,

Thanks for you response,

but my problem is:

When i click on Change Authorization Data button in the Authorization Tab screen I am getting the error message as mentioned in my earlier posting and not allowing to go to the next screen.

I am not able to goto the next screen (Change Role Authorizations) to maintain any Organizational/Authorization values.

Please let me know if you are still not clear with my problem

Thanks,

Ravi

Re: Object P_ORGIN inconsistent

Frank_Buchholz — Fri, 27 Oct 2006 08:52:24 GMT

Result of a test in 4.6C and 4.7 system (with up-to-date support package):

The PFCG loads the merged authorization proposals for S_TCODE, PLOG, P_ORGIN and P_TCODE according to the SU24 data for the parameter transaction OOOE and the 'master' transaction PPOM. -> It seems that you have a special problem in your system.

I assume that you have the same problem if you add transactopn PPOM inte a role, because the systems loads these authorization proposals.

The PFCG shows the message if there is an inconsistency between authorization proposals in table USOBT_C and the definition of an authorization object in table TOBJ

My suggestion: Use SU24 to delete the authorization proposals for transaction PPOM, save it and add them again.

P_ORGIN    
AUTHC      *
INFTY      0000 0001 0002 0003
PERSA      <empty>
PERSG      <empty>
PERSK      <empty>
SUBTY      *
VDSK1      <empty>

Please check note <a href="https://service.sap.com/sap/support/notes/745655">745655</a>, too, which might be applicable.

Kind regards

Frank Buchholz