org value and auth field

[Former Member]

Hi experts,

what is organization value, how do we define it.

and what is the diff between authorization value and org

value.

thanks and regards,

kavitha

[jurjen_heeck]

> what is organization value, how do we define it.

It's just a kind of authorization value, filled in PFCG.

> and what is the diff between authorization value and org value.

The only difference is the table in which the value is stored (AGR_1252 instead of AGR_1251). The organizational value is also an authorization value.

If you read about the concept of " derived roles" you'll understand.

Jurjen

[Bernhard_SAP]

> kavitha l wrote:

>

> what is organization value, how do we define it.

Hi,

you can define org.values by using the report pfcg_orgfield_create. Please refer to [SAP Note 323817|https://service.sap.com/sap/support/notes/323817] . Please read carefully the documentiation in that note about the necessary steps for each client/system!

The big advantage of using org.-fields is, that if such a field is contained in many authorizations of your roles profile, you will have to maintain the value for the orgfield only once in the org.-level popup. The values maintained there are refelected then to all authroizations containing that field.

b.rgds,

Bernhard

[former_member1061482]

Adding to that, they are helpful if the same field in different objects need to have the same value.

Otherwise you need to break the org level by making changes directly into the object for which the value needs to be maintained differently.

An object level field can be converted to an org level by using pfcg_orgfield_create and the reverse, i.e. an org level can be converted back to an object level field using program pfcg_orgfield_delete. But before using these programs you need to be pretty sure coz these require too much of workaround as these may affect many roles(as these fields may be present in many roles).

[Former Member]

Hi.

Be aware that when you bypassed the organizational value by putting direct information in the field of the object, it will not take over any value you put in the organizational value screen. It is very confusing to by pass the organizational value screen and it invites you to make mistakes. If you did this you can repair this by deleting the value in the authorization object, you she a little dustbin in front of the field. Also be very careful with derived roles and a generate from all derived roles with the button in the template role. You must check if the by passed value is still there.

Please use organizational fields/ values/ screen as it is meant to be using the same functionality(role) and different organizational values.

Have fun

Bye Jan van Roest

[former_member1061482]

Hi,

Sometimes requirement is such that you have to break org level fields and manually assign values to some objects.

As far as repairs are concerned, if you go and delete the value in authorization object, that won't be of much help; especially if you have directly gone and made changes to standard instance, unless you go to the role in expert mode.

[Former Member]

Hi Kavitha,

Organisational value is the one where u can define all the organsational value e.g (company code), it can be defined as * too. It is defined by using pfcg tcode. If org value is defined as * it will execute for all org value if value is been maintained then it will execute for those values only.

organisational values are also maintained in auth values through some object.

The organizational value is also an authorization value.

Hope this makes clear

[Former Member]

Hi,

Authorization field is nothing but the activities it contain to authorization object like(p_orgin) under this auth object there will be more fields like infotype;subtype..all these are authorization fields.

Org value is Company code.This org value occurs in some authorization objects only.

Regards,

Parimala

[Former Member]

hi,

Thank you for the response. useful information

regards,

kavitha