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: 

SU24, USOBX_C, USOBT_C don't allign.

former_member318517
Participant
0 Kudos

Hello all,

We have a situation where we have set the SU24 proposal for SMQ1 for S_ALV_LAYO to NO and after saving...USOBX_C shows Check Flag of X for that object (good), but USOBT_C has an entry for S_ALV_LAYO (bad) and when adding SMQ1 to a role it brings in S_ALV_LAYO. (bad)

Any valid reasons for this and is there a way to allign these tables back up with SU24?

Thanks,

Tom

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Remove the object completely and save to remove possible inconsistencies.

If a popup appears stating "data automatically corrected" then it is because of table TSTCA.

If the object still appears then it is a parameter transaction and the core transaction is proposing the object. Changing it to check only does unfortunately not help (at the moment...).

You must set the object to inactive in the role itself.

Cheers,

Julius

3 REPLIES 3

Former Member
0 Kudos

Remove the object completely and save to remove possible inconsistencies.

If a popup appears stating "data automatically corrected" then it is because of table TSTCA.

If the object still appears then it is a parameter transaction and the core transaction is proposing the object. Changing it to check only does unfortunately not help (at the moment...).

You must set the object to inactive in the role itself.

Cheers,

Julius

0 Kudos

Removing object from SU24 worked but that is not feasible for so many tcode we want to turn S_ALV_LAYO off for...so we'll just inactivate it in the role when it comes in.

0 Kudos

If they are parameter transactions, then it is currently your only option.

I have a development request open for this as well and will update this thread when available.

Cheers,

Julius