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: 

why org vaues is not updating the Changed Objects

sreekanth_sunkara
Active Participant
0 Kudos
578

hi all,

we have a master role with some some objects as maintained and some as changed and some as standard.

when i derived some 10 child roles and added org values. this org value is not pusing for the changed objects, even when i add it in the field, once if i make any other modification in the master role and distribute it to child roles then all the org values for the changed objects are going to blank again

so, org values wont push or work for changed objects? please help

thanks,

SSS

1 ACCEPTED SOLUTION

jurjen_heeck
Active Contributor
0 Kudos
193

Looks as if the org fields where initially filled on the object line itself in the master role, instead of in the separate org-field screen.

Best go to the master role, enter into the authorization screen and hit the little trashcan next to each org field in the objects.

If you blank out all org fields in the separate screen as well you should end up with red traffic lights.

Now regenerate the children and all should be fine.

If you do not see trashcan icons when you unfold all objects go to menu 'utilities'->'settings' and check all boxes there.

11 REPLIES 11

jurjen_heeck
Active Contributor
0 Kudos
194

Looks as if the org fields where initially filled on the object line itself in the master role, instead of in the separate org-field screen.

Best go to the master role, enter into the authorization screen and hit the little trashcan next to each org field in the objects.

If you blank out all org fields in the separate screen as well you should end up with red traffic lights.

Now regenerate the children and all should be fine.

If you do not see trashcan icons when you unfold all objects go to menu 'utilities'->'settings' and check all boxes there.

0 Kudos
193

HI,

it is filled with $werks in object line at first, will this also effect it?

thanks,

SSSS

0 Kudos
193

Hi,

I tried but no use.

can you tell the difference between maintained and changed in PFCg

thanks,

SSS

0 Kudos
193

>

> can you tell the difference between maintained and changed in PFCg

>

Hi Sun,

Is it a coincidence that the objects having ORG level fields are in changed state in the master role or is it becasue of the SAP feature?

When we directly maintain ORG fileds in objects and NOT in the specified ORG window, then

first - > the object status goes to changed

second -> when you create derived roles, that field will not be maintained in the derived role even though you maintain ORG values in derived roles. The value maintained in the master role is passed to the child role.

What you need to do is follow what Jurjen said..... first ... fix the messed up master role, and then maintain the ORG values in the derived roles.

Hope this helps

Abhishek

0 Kudos
193

hi all,

what happend is as you all some changed the value in field and so it turned to changed and even i remove all the values and added them back in org tab, some how the status is still chnaged and not changing to maintained.

so i copied it to another role and then added org values in the org tab. this fixed the issue

but it is very strange, i learned that org tab wont push any values to changed objects.

so i need to make to sure all the objects containing org values should be maintained first

thanks,

Sun

0 Kudos
193

thanks for your help

0 Kudos
193

thanks for your help

Former Member
0 Kudos
193

Hi Sun,

If it is filled with $werks then it means that org value need to be maintained for that field.

it implies no value is maintained for that field.

Hope this helps,

Regards,

Rakesh.T

0 Kudos
193

thanks for your help

Former Member
0 Kudos
193

Hi Sun,

The org. level values should be maintained under the organizational level and not at the field level.Any field containing a value in it with a prefix $ signifies an org. field.

After you derive a role, you should first maintain all the org, level values for the derived roles under the organizational level and then save and generate.After the org.level values have been maintained for the derived roles separately then you should generate the derived roles by going inside the master role.This will not override the org level values maintained for the derived roles.If the org. level value is missing for any of the fields in the child role then on generating the derived role the value stored in the master role is passed down to the derived role as default value.

Thanks,

Saby..

0 Kudos
193

thanks for your help