Question:
Does anybody know the difference between SU22 & SU24 ? Thanks
Answer:
No.
Answer:
Hi,
Perhaps the tcodes su22 and su24 are related in the same way as su01 and su10. When u try to execute mass changes through su01 u r brought to the same screen as that of su10.
In addition to that the objects which are existent for both the tcodes su22&su24 are the same.
So what i feel is that one of the tcode is a subset of the other means the tcode at higher level in addition to several other capabilities also has that other tcode.
With respect to eg of su01 and su10, su01 exists at higher level and comprises of may func. of which mass changes is an option.
So we cannot diffrentiate them clearly bcoz one is a subset of other.
Might be this answers ur query. Other more specific answers are welcome so that we can have a better insight
Regards,
guest__1
Answer:
As I remember it.... SU22 was SAP's view, SU24 was the customer view.
Answer:
I believe SU22 reads the SAP delivered table USOBT and SU24 reads the customer version of this table USOBT_C, it is therefore possible for SU22 and SU24 for display seperate results since they are reading different tables.
Answer:
SU22 displays and updates the values in tables USOBT and USOBX, while SU24 does the same in tables USOBT_C and USOBX_C. The C stands for Customer. The profile generator gets its data from the _C tables. In the USOBT and USOBX tables the values are the SAP standard values as shown in SU24. With SU25 one can (initially) transfer the USOBT values to the USOBT_C table. Using SU24 you can set check indicators to exclude or include certain authorization objects from authority checks. You can also use the check indicators to control which objects appear in the PG and which fields are displayed for editing before the authorization profiles are automatically generated.
Using SU25 (Copy inital defaults), copy the supplied SAP defaults, tables USOBX and USOBT. This steps imports the SAP check indicator defaults for the authorization objects within a transaction and the authorization field values for the PG into customer tables USOBX_C and USOBT_C. You can edit these values later in transaction SU24.
--> Different check flags stands for in SU24
Check/Maintain - A check is carried out against this object. Profile Generator creates an authorization for this object. . Default values for this authorization can be maintained
Check - A check is carried out against this object. Profile Generator does not create an authorization for this object.
No check - Check is disabled.
Unmaintained - Check is carried out.