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: 

Transfer users to CUA after upgrade to child systems

Former Member
0 Kudos

Good afternoon - Perhaps one of you experts can help me.

Here is the situation:

 

We have recently migrated all systems to new landscape. The systems in the new landscape were disconnected from the CUA during the migration/upgrade and now we want to connect them back to CUA. While the systems were disconnected, changes were made to the user master records such as demographic, data (parameters, SNC name, etc) as well as, role and profile assignments in the child systems.

  

The systems have been re-connected to the CUA and users can be transferred from the child systems to the CUA, but data for identical user transfers overwrites demographic data that was updated in the child systems with the data from the CUA.  We do not want to push down the existing data from the CUA to the child systems and overwrite the data in the child systems.

  

Is there a way that we can push up the demographic data from the child systems for identical users? 

        

Can we modify our settings in SCUM to control what comes over in the transfer process (SCUG).

Note: The field attributes (SCUM) for Parameters is set to "Proposal".  The field attribute for SNC is set to "Global". 

Any help you could provide would be greatly appreciated!

2 REPLIES 2

Colleen
Advisor
Advisor

Hi Kathleen

You need to revisit your SCUM settings in the CUA to determine where source of truth is.

For example, parameters would make sense to be local as there are different parameters in each system (e.g. CRM vs ECC). Roles and Profiles, on the other hand, should be global as the source should be managed via CUA.

Demographic data, etc- look at the fields and decide if there is a need to have different values in the system. Depending on that your option is either Proposal or Local. But this will mean all subsequent changes need to be managed locally.

Depending on how long you had the system disconnected and changes you might need to analyse you data for impacts

Bernhard_SAP
Advisor
Advisor
0 Kudos

SCUG-->fist come first wins.

If the user is present already in central system with adminitrative data, this will not be overwritten by taking over a 'new ' child system. In opposite, the central systems data will overwrite the child systems data, if scum is set to 'global'.

Therefore its advisable to take over users first from the most actual/important system, i.e. normally the PRD system.

b.rgds, Bernhard