PFCG_ORGFIELD_DELETE

Hello Experts,
We have a system where personnel area was created as org field but the derived roles also have the values maintained at field level. This is causing issues whenever we generate the derived roles; hence thinking of deleting this org level. Will all valules be lost? SAP notes suggest default values will reflect in the roles. What would that mean considering that PERSA usually is blank in the default.
Thanks in advance for your inputs
Vijaya

Hello,
don't you think repairing the roles once will be the better way then deleting the org-level field itself?
If values have been entered on field level directly, simply remove them by using the dustbin icon. then the field gets back its org.-field status. Of course if the direct maintenance has been performed in the master role, all derived will get that field value from the master. So check the master role as well. As soon the dustbin icon appears left to the field, the value has bene entered directly.... (that is a save indication).
b.rgds, Bernhard

Similar Messages

Error message while transporting the HR role

All
I was trying to move my HR role from Dev to QA.
I got the error message from transport and not sure about it.
Please let me know if you have any suggestions.
Invalid organizational level $ORGEH deleted from role Z_ALL_MODULES_EXCEPT_BASIS_HR
Invalid organizational level $ORGUNIT deleted from role Z_ALL_MODULES_EXCEPT_BASIS_HR
Errors occurred during post-handling
PRGN_AFTER_IMP_ACTGROUP_ACGR for ACGR L
PRGN_AFTER_IMP_ACTGROUP_ACGR belongs to package S_PROFGEN
The errors affect the following components:
BC-SEC-USR-PFC (Authorization and Role Management)
Post-import method PRGN_AFTER_IMP_ACTGROUP_ACGR completed for ACGR L, date and time: 20071011162942

Pranav,
You can see a list of all org levels in table USORG
There are standard SAP programs for adding or deleting org levels
PFCG_ORGFIELD_CREATE
PFCG_ORGFIELD_DELETE
If you want these fields to be maintained as org levels then you need to make sure that you have created them in all system.
If you don't want these fields as org levels then you can delete them using the program I listed above.

Maintaining the authorizations for parent role and derived role

Hi Experts,
Kindly advice me the Pro and cons of the parent role and derived role.. below is the scenario
Currently we have created the 700 role in our regionally organization and we want to dervie the roles for each country
1 ) we want to do the Auth field (activity level) settings in parent role and Org levels in the derived role .
2) But one my collegue says do the default Auth filed ( activity values) common to every country in the parent role and diff activity one in the derived role .
please advice me wat will be the best scenario for mantaining the authorizations filed values like (activity level one)

I will try to answer both your queries here:
"my collegue says they are some NON ORG values different from each country ..suggest us to maintain all the default values in Parent role and auth with diff values needs to be maintained in derived role (child role).. "
The only set of values which should/can be different in a child role (when compared with its parent) will be the org level values. So if this filed is NON_ORG you will not be able to maintain it directly inside the child roles.....this is the basic principle of derived role conceptu2026 that the only item you will directly maintain in a child role are the org levels(which will come as u2018organisational levelsu2019 in the upper tab in the auth data of a role).
All NON_ORG fields inside a child role is acquired from the parent role. You should never change the values of any such fields (non-org fields) in the child role. these changes will get lost the next time you run the parent child inheritance from u201Cgenerate derived roleu201D function in your parent role.
Coming to the second question on how to run the program, you just need to enter the technical name of the field you want to convert (tech names like BUKRS, WERKS etc u2026 figure out the name of the concerned field you have in hand)u2026.executeu2026 you will that the field will now onwards appear as an org level value in all roles in the system and not just as a field inside the auth objectsu2026.I would suggest you take one field and try running it in ur dev or sandbox..see how the field changes in your roles.... the change can always be reverted by using PFCG_ORGFIELD_delete. ... you will understand it better....
Soumya

PFCG_ORGFIELD_DELETE

Similar Messages

Maybe you are looking for