Following an upgrade of your SAP S/4HANA on-premise system to a higher release, you perform a Modification Comparison using SU25. What does this comparison do?

Question

Options

• AIt compares your changes to the SAP defaults in USOBX_C and USOBT_C with the new SAP
• BIt compares your changes to the SAP defaults in USOBX and USOBT with the new SAP defaults
• CIt compares the Role Maintenance data from the previous release with the data for the current
• DIt compares the Role Maintenance data from the current release with the data for the previous

• A
  16% (7)
• B
  73% (33)
• C
  7% (3)
• D
  4% (2)

Explanation

After an S/4HANA upgrade, SU25's Modification Comparison examines the customer's deviations from the old SAP standard authorization proposal tables - USOBX (check indicators) and USOBT (authorization field proposals) - and compares them against the new SAP-delivered defaults in those same tables, surfacing conflicts or gaps that require attention post-upgrade.

Why A is wrong: USOBX_C and USOBT_C are the customer-modified copies of those tables (the "C" suffix = Customer). The comparison's reference baseline is the SAP standard (no "_C" suffix), not the customer copies.

Why C and D are wrong: Both describe comparing Role Maintenance data between releases - that involves transaction PFCG and role transport, not SU25. SU25 Modification Comparison operates on authorization proposal values (check indicators and field assignments), not on roles themselves.

Memory tip: Think of the "_C" suffix as "Customer" - USOBX_C/USOBT_C hold your changes, while USOBX/USOBT hold SAP's standard. The Modification Comparison always references the no-suffix (SAP standard) tables, because that's the baseline being updated by the upgrade.

No community discussion yet for this question.