Central User Administration (CUA) in SAP landscapes serves as a uniform interface for managing and maintaining user data and authorizations across different SAP systems. With CUA, organizations can increase efficiency by eliminating the need to configure and update user accounts and access rights separately in each individual SAP system. This results in a consistent security policy, simplifies compliance monitoring and significantly reduces administrative overhead. CUA also facilitates the rapid connection of new systems to the existing infrastructure and thus supports the scalability and flexibility of the IT environment in dynamic business environments.
It may be necessary to temporarily deactivate the Central User Administration (CUA) in an SAP system in order to carry out special maintenance work or adjustments that must be carried out directly in the child system and cannot be managed via the CUA’s central interface. Such situations include, for example, updating user master data, adjusting authorizations or making specific configuration changes that would not be permitted due to the central administration settings. Temporary deactivation allows administrators to make the necessary changes locally and without conflicting with the CUA’s global settings. Once the work is complete, the CUA connection is restored to ensure the consistency of user data and security policies across the entire SAP landscape.
Configuration in the local system
Call up transaction SM30 and enter the table PRGN_CUST and call up the change mode using the “Edit” button:
Change the value for CUA_TEMP_OFF_ENABLED to YES here.
After saving the table, the function for temporarily deactivating the CUA connection is activated.
Deactivation of the CUA
Then call up transaction SCUA in the child system and use the corresponding switch (or CRTL+F2) to temporarily deactivate it:
In the following window, execute the status change using the “Execute” button:
Once the connection to the CUA has been disconnected, maintenance work on the child system has no direct impact on the central user master data. The CUA connection can be reactivated using the “Reactivate CUA” button.
Source: https://etomer.com/temporaere-abschaltung-der-zbv-anbindung/