Installation, Control Center and Configuration Guide

Installation, Control Center and Configuration Guide
Copyright 2009 –2020 EPI-USE Systems Limited and its related entities, hereinafter EPI-USE.
The information in this document is confidential and subject to change without notice. The companies, names, and
data used in this document’s examples are fictitious unless otherwise noted. The data contained in this document is
for information purposes only, unless explicitly mentioned otherwise. National product specifications may vary. No
part of this document may be reproduced or transmitted in any form or by any means, whether electronic or
mechanical or for any purpose, without the express written permission of EPI-USE Systems Limited.
EPI-USE may have patents or pending patent applications, trademarks, copyrights, or other intellectual property
rights covering the subject matter in this document. The furnishing of this document does not give you any license to
these patents, trademarks, copyrights, or other intellectual property rights, except as expressly provided in a written
license agreement from EPI-USE. For a complete list of EPI-USE Labs’ products and trademarks, please consult
Copyright Information at www.epiuselabs.com.
All product names, trademarks, and registered trademarks are the property of their respective owners. All company,
product and service names used in this guide are for identification purposes only.
documentation@labs.epiuse.com
Data Sync Manager™ 5
Document version B
27 February 2020
i
Contents
1. Getting started with Data Sync Manager ........................................................................................................................ 1
1.1 Introduction ................................................................................................................................................................... 1
1.2 What is the Control Center? ..................................................................................................................................... 1
1.3 Download and import the latest code library and Data Sync Manager 5 transport ........................... 2
1.4 Activate your product ................................................................................................................................................ 4
1.5 Name spaces .................................................................................................................................................................. 5
2. Authorization template roles ............................................................................................................................................... 6
3. Control Center settings .......................................................................................................................................................... 8

3.1 Control Center concepts ........................................................................................................................................... 8
3.1.1 RFC Types ..................................................................................................................................................... 9
3.1.2 DSM_CONTROL and the DSM_COMM_<SID> users .................................................................. 11
3.2 Control Center configuration ................................................................................................................................ 12
3.2.1 System registration................................................................................................................................. 13
3.2.2 Applications .............................................................................................................................................. 17
3.2.3 Environments ........................................................................................................................................... 18
3.2.4 System and Client Assignment .......................................................................................................... 19
3.2.5 Shared folders........................................................................................................................................... 21
3.2.6 Routes.......................................................................................................................................................... 22
3.2.7 Data Disclose client registration ........................................................................................................ 24
3.2.8 Distribute Configuration....................................................................................................................... 25
3.2.9 RFC destination (for manual RFC Controllers only)..................................................................... 26
4. Administration features ....................................................................................................................................................... 30

4.1 Backend Utilities ......................................................................................................................................................... 30
4.1.1 OData identities ....................................................................................................................................... 31
4.2 Table exceptions ........................................................................................................................................................ 31
4.2.1 Client Sync grouping exceptions ...................................................................................................... 32
4.2.2 Enterprise slice tables ............................................................................................................................ 33
4.2.3 System Builder table rules.................................................................................................................... 34
4.3 Number range handling .......................................................................................................................................... 35
4.3.1 Data insert behavior ............................................................................................................................... 35
4.3.2 Number range maintenance ............................................................................................................... 38
4.4 Cleanup and Optimization ..................................................................................................................................... 39
4.4.1 Recommended index check ............................................................................................................... 40
4.4.2 Date slice index check ........................................................................................................................... 41
4.4.3 Database consistency check ............................................................................................................... 41
ii
4.4.4 Object Sync cleanup .............................................................................................................................. 42
4.4.5 Client Sync cleanup ................................................................................................................................ 43
4.4.6 File explorer............................................................................................................................................... 44
4.4.7 Clean up mapping table ....................................................................................................................... 45
4.4.8 Optimization program .......................................................................................................................... 46
4.4.9 HR cluster optimizer ............................................................................................................................... 47
4.4.10 Pre-calculate masked values ............................................................................................................... 48
4.4.11 Data Disclose index run ........................................................................................................................ 50
4.4.12 Object flow optimization...................................................................................................................... 51
4.4.13 Pre-system export optimization ........................................................................................................ 51
4.5 Masking ......................................................................................................................................................................... 52
4.5.1 Address database .................................................................................................................................... 52
4.5.2 Company database................................................................................................................................. 54
4.5.3 Person database ...................................................................................................................................... 55
4.6 Business Object maintenance ............................................................................................................................... 56
4.6.1 Mapping Editor ........................................................................................................................................ 56
4.6.2 Generate object classes ........................................................................................................................ 58
4.6.3 Generate Profiles and Groupings ...................................................................................................... 60
4.6.4 Maintain Semantic Tags........................................................................................................................ 61
4.7 Audit and security...................................................................................................................................................... 62
4.7.1 Group Management............................................................................................................................... 62
4.7.2 Object protection list ............................................................................................................................. 64
4.7.3 Object protection editor ....................................................................................................................... 65
4.7.4 SAP Authorizations for Objects .......................................................................................................... 67
4.7.5 User preferences...................................................................................................................................... 68
4.7.6 Sync Audit Report ................................................................................................................................... 70
4.8 Client Sync utilities .................................................................................................................................................... 71
4.8.1 Index enabler ............................................................................................................................................ 72
4.8.2 Index disabler ........................................................................................................................................... 72
4.8.3 Tables for which secondary indices can be dropped ................................................................. 73
4.8.4 Object key processing limits ............................................................................................................... 74
5. Troubleshooting ..................................................................................................................................................................... 76
6. Accessing support through Client Central .................................................................................................................... 77

6.1 Requesting access to Client Central .................................................................................................................... 77
6.2 Logging a ticket .......................................................................................................................................................... 77
6.3 Additional help and resources .............................................................................................................................. 78
6.3.1 Guides.......................................................................................................................................................... 78
6.3.2 Knowledge base articles ....................................................................................................................... 78
iii
6.3.3 Videos .......................................................................................................................................................... 78
6.3.4 Forums ........................................................................................................................................................ 78
6.3.5 Contact us .................................................................................................................................................. 78
Appendix A: Relationships between Administration utilities and DSM products ................................................. 79
iv
DSM5 Installation, Control Center and Configuration Guide Getting started with Data Sync Manager
1. Getting started with Data Sync Manager
1.1 Introduction
Every company using SAP® needs to transfer data between clients and systems for production support and
development or to refresh training clients. However, without an adequate transfer solution, full client or
system copies can be time-consuming and use a lot of storage space. There is also the risk of exposing
sensitive data in less secure systems.
The Data Sync Manager™ 5 (DSM5) suite includes four complementary products: Object Sync™, Client
Sync™, Data Secure™ and System Builder™.
 Object Sync allows you to select and transfer specific data objects, easily and accurately, as you need
them.
 Client Sync provides a table-oriented approach to copying a subset of client data.
 Data Secure provides in-place data masking and provides integrated masking for other DSM suite
products.
 System Builder allows you to make complete repository copies easily, then add the client data as you
need it.
1.2 What is the Control Center?

The Control Center is a new feature that has been released with DSM5. It replaces some of the system
connectivity configuration that users found on the Administration screen in the earlier DSM4 version that
controlled such behavior as the file paths, RFCs, local client settings, etc.
With Object Sync and Data Secure now working across systems automatically (for example, ERP and CRM),
there is much more complexity to these settings and something more powerful is required to control
them, hence the Control Center being introduced. It does, however, remain part of the Administration
screen in DSM5, with other settings and reports also available there. Unlike previous versions of DSM, the
Control Center settings are configured once in a ‘controller’ system client and distributed to all the defined
systems. This central management lessens the amount of manual effort to keep the configuration updated
and ensures the consistency of these settings between systems. It does, of course, require more DSM-
specific connectivity between the systems.
Copyright 2020 by EPI-USE Systems Limited. Confidential and proprietary: duplication prohibited. 1
1.3 Download and import the latest code library and Data Sync
Manager 5 transport
All EPI-USE Labs products make use of a generic code library shared between products and distributed as a
separate Library 2 (Lib2) transport. Data Sync Manager requires the installation of this Lib2 transport as
well as the DSM5 transport, on every system that it should have access to.
The transport import order should always be:
1. Library 2
2. DSM5
The latest versions of the Lib2 and DSM5 transport releases can be found on the EPI-USE Labs Client
Central website. To download these from within Client Central, navigate to Workspaces > Data Sync
Manager > Downloads > Data Sync Manager 5:
DSM5 only supports NetWeaver 7 kernel systems and above. Kernel functionality that is essential to
DSM5 is not available on lower versions.
In the ‘Data Sync Manager 5’ folder, find and open the DSM sub-folder for the required SAP system type
(ERP, ECC, SRM, CRM, NW, etc.). Then, find and open the release sub-folder matching the release of the
system(s) that DSM will be installed on, e.g. for ECC6 with EhP5.
It is important to import the transports for your current SAP release. Please ensure that the Library
transport (see point 1 below) has been imported successfully before importing the DSM5 Build
transport.
To successfully import the necessary transports, import the client-independent transports in the order
specified below:
1. First, import the client-independent Library 2 Build x transport once into each system that you would
like to update.
2. Then, import the client-independent DSM5 Build x transport on any client on the system.
Please ensure that the following ‘Import Options’ are selected for both transports:
 Import Transport Request Again

 Overwrite Originals
 Overwrite Objects in Unconfirmed Repairs
 Ignore Invalid Component Version (if available*)
* This last additional Import Option may appear at the bottom of the list on systems with SAP NetWeaver
7.0 EhP2 or higher.
1.4 Activate your product

Once you have downloaded and imported the latest Library 2 and DSM5 transports, you can activate your
product by following these steps.
When you access DSM for the first time by entering /n/use/dsm, you will first be prompted to select the
version of DSM you will be using from the pop-up below:
Only clients that already have DSM4 licenses will be required to make this selection. New clients
starting on DSM5 will go automatically to the DSM5 Landing page.
Once you have selected ‘5’, your system will automatically try to load your transport and display this pop-
up:
A “Successfully activated” message will be displayed once the activation is complete. However, if you
receive the “We could not activate your product automatically” message, you’ll need to activate Data Sync
Manager manually.
To activate Data Sync Manager manually:
1. Click the ‘Client Central’ link in the pop-up window above.

2. Click ‘Download license’ in the top right to download the license file.
3. In SAP, click the button to upload the license file.

4. To activate the product, click ‘Continue’ .
If you require a new license file or experience any problems during activation, please log a ticket on Client
Central.
1.5 Name spaces

A name space is an ID assigned exclusively by SAP that allows SAP customers, SAP partners and SAP to
develop SAP components and products using SAP applications, without the danger of naming conflicts.
(Naming conflicts can occur during transports to external SAP systems, or when importing external
products into your own systems.)
You assign objects to a namespace in the ABAP Workbench by placing the namespace prefix in front of the
object name. The namespace ID begins and ends with a delimiter (/) and can be up to 10 characters long.
EPI-USE Labs has registered the /use/ and /epiuse/ name spaces with SAP and does product development
and the addition of objects exclusively within these name spaces. The only exception to this is packages
and authorization classes for authorization objects. Since these cannot be shipped in /USE values, they are
provided as Z objects. The rest of the transport contains only /USE objects and contents.
DSM5 Installation, Control Center and Configuration Guide Authorization template roles
2. Authorization template roles

Within DSM there are some products where customers may want to ensure a segregation of duty. In these
cases, there may be a ‘super user’ who can carry out all activities for that product, and then a ‘user’, ‘audit’
or other types of users whose access is more limited. The DSM5 transport includes Authorization Role
Templates for each of these DSM5 product user types. The roles can be seen as Best Practice roles for
organizations that are keen to take guidance from the software vendor on commonly required groupings
of access and they link more specifically to the functional user types that will access the products. For
some organizations the ‘super user’ role is sufficient and they will not require these other roles.
For the Administration of the DSM5 product suite there are two Administrator roles and then two more
limited roles that can be used to distribute responsibilities for different parts of administration to different
users.
There are also template roles that can be used for the service users DSM5 uses to manage the Control
Center configuration distribution and the additional service users that are used to communicate between
systems when data is being copied or masked.
For more information regarding the role templates, options and configuration of the authorization
roles, please refer to the DSM5 Authorizations Guide.
To see the list of templates included in the transport execute transaction PFCG. Then access the ‘Utilities’
menu and select ‘Templates’ from the drop-down list. The DSM5 templates have a prefix of /USE/DM1_.
The DSM5 role templates can be adopted into an existing SAP user profile with the steps below in a Dev
system:
1. Access SAP transaction ‘PFCG’.

2. Create a new <DSM_USER>/<DSM_ADMIN> role, as required.
3. Go to the ‘Authorizations’ tab.
4. Select the ‘Change Authorization Data’ option.
5. Choose the relevant template from the pop-up window.
6. Select ‘Apply Template’.
7. Change the authorization values according to the required security preferences described below.
8. Ensure that this new role is generated successfully.
DSM5 Installation, Control Center and Configuration Guide Authorization template roles
9. Transport the role to all higher systems in the landscape and assign it to the user(s).
Data Sync Manager Administration includes an audit report ‘SAP Authorizations for Objects’ that lists
the SAP authorizations that are checked before search results for an EPI-USE Business Object can be
returned. This is discussed in more detail in Section 4.7.4 in this guide.
DSM5 Installation, Control Center and Configuration Guide Control Center settings
3. Control Center settings

After importing the product transports, you will need Administration authorization. It may be necessary to
create a new user role as described on the previous page or you can refer to the DSM Authorizations Guide
in the Downloads > Data Sync Manager 5 Documentation space.
When you try to execute any DSM transaction on a system where the Control Center has not yet been
configured, it will automatically launch the DSM Administration screen and inform you that you need to
complete the Control Center configuration for this system or distribute the configuration from the
Controller to this system.
To access DSM Administration you can either use the transaction /USE/DSM_ADMIN or use any of the
other DSM transactions e.g. /USE/DSM, navigate to the Administration launchpad and select
‘Administration’.
If you need additional information for any of the screens you are navigating in, you can select the
Documentation button or press Shift+F1. This will display information and guidelines that are
pertinent to the screen you are on at that moment.
3.1 Control Center concepts

The ‘Landscape’ refers to systems of the same type of SAP application. For example, a CRM landscape may
consist of a Development, Quality Assurance and Production systems.
An ‘Environment’ is a collection of clients in one or more applications that work together. For example, a
Production environment can consist of an ERP, BW and CRM systems.
To set up the configuration of all the systems and their clients in their respective application landscapes
we need a Controlling System (known as the Controller). The Control Center configuration will be done
once on this system and then distributed across the landscapes.
Typically, the Controller will be a specific client on the Production ERP system. This Controller serves as a
Control Center for all the connected systems. Therefore, users are required to connect systems to the
Controller.
Each system can only have one Controller. So for any sort of multi-tenant system, the clients on the
system have to be in the same Control Center group.
Right-click on ‘Control Center’ to Enable or Disable a system client as the Controller. This will then ask you
which RFC type you wish to use (see section 3.1.1 below).
For additional information and details relating to the Control Center RFC connections, please
consult the knowledge base article by that name.
The Controller distributes configuration to other systems. These systems are called Controlled Systems.
One client from each of these systems should be registered under the Control Center. These clients are
called Control Clients.
Object Sync and Client Sync source clients need to communicate with target clients. DSM5 includes cross-
application support. This allows sibling clients to communicate, for example, communication between the
QA ERP client 400 and the corresponding QA CRM client. The DSM Controller needs to communicate with
all of these systems to update the configuration. This communication is facilitated by RFC connections.
3.1.1 RFC Types

There are four types of RFCs (Remote Function Calls) used by the Control Center:
 Control Center to Control Client Communication (USE_DSM5-<SID>-CC): These RFC

destinations only exist on the Control Center system and connect to each Controlled System's
Control Client.
 Control (USE_DSM5-<SID>-CTRL): Control RFC destinations exist between each source and
target system as well as each system within an environment. These RFC destinations are used to
perform control actions, such as checking that a client exists on another system.
 Authentication (USE_DSM5-<SID>-<CLIENT>-AUTH): These are dialog RFC connections used
to check the authorization of a user performing a Sync. Authentication RFC destinations
existing between each source and target system as well as each system within an environment.
The RFC destinations allow for remote integration point refine settings to be set in the Object
Sync User Interface as well as performing authorization checks on remote systems for the
current user.
 Communication and data transfer (USE_DSM5-<SID>-<CLIENT>-COMM): These RFCs refer to
communication RFC destinations existing between each source and target system as well as
each system within an environment. These RFC destinations perform data transfer for the Syncs
as well as distributing the data secure mapping database. A local communication RFC is also
used by Client Sync to perform post-processing. In this case, Client Sync will automatically
update the users' authorization profiles in order to successfully perform the post-processing
steps.
There are different naming conventions used for the four types of RFC connections used by the
Control Center. These RFCs will be created when the systems are registered or when the Control
Center (CC) configuration is distributed.
The Control Center (CC) and control (CTRL) destinations use the DSM_CONTROL User unless this is
changed with the profile parameter DSM/CC/CONTROL_USER (see section 3.1.2 for more details).
The communication (COMM) RFC uses the DSM_COMM<SID> user unless this is changed with the
profile parameter DSM/CC/TRANSFER_USER.
When you first enable a system as the Controller a pop-up appears asking whether it should use
Dynamic, Fixed or Manual RFCs. This will determine when and how the control and
communication connections are configured.
The Fixed, Dynamic and Manual RFC options are described below:
 Dynamic RFCs. The Control Center and Control RFC connections are created when the
configuration in the Control Center is distributed. These RFC connections are retained.
COMM connections are only created as needed. When a COMM connection is needed, the
control connection auto-generates and sets the password for the DSM_COMM_<SID> user. The
COMM RFC is then created and used for the intended activity or function (for example, reading
data from linked systems for Object Sync).
After the activity is completed, the COMM RFC is deleted. A new COMM RFC with a new
password is created every time a communication connection is needed and user information is
encrypted before it is shared between systems.
From a technical security perspective, this is arguably the most secure option, but it does mean
there are automatically created and deleted RFC connections.
 Fixed RFCs. Control Center, Control and Communication RFCs are generated and retained the
first time they are needed. Secure encrypted passwords are used for the communication user.
 Manual RFCs. This provides a list of connection RFCs that should be created via SAP transaction
SM59 and the names populated inside the Control Center. This requires more configuration
effort but ensures no connections or users are created automatically by the Control Center
during configuration distribution. It is not recommended to use existing RFC connections but
rather ones specifically created for DSM5.
In Manual RFC mode, RFCs will not be generated on the controlled systems but instead a
lookup table (/USE/DC1_RFC_CFG) will be used to read the RFC mappings.
3.1.2 DSM_CONTROL and the DSM_COMM_<SID> users

Before setting up the Control Center and distributing the configuration to all the controlled
systems, it is essential to decide which options to use for user creation. There are five (5)
parameters in transaction /USE/USY2_PROFILE (EPI-USE Labs Product profile parameter editor)
that must be maintained in ALL systems unless you wish to use the default configuration.
The default configuration creates these users as ‘service users’ with the profile SAP_ALL. Some
organizations may allow this and there will be existing service users with SAP_ALL, while for
other organizations this will not be permitted and a different profile should be used from one
of the template roles listed below. Please check with your Authorizations team before
continuing.
These settings are not distributed, so you must update them directly in each system before
distributing the Control Center configuration from the Controller and keep in mind that the
parameters in the /USE/USY2_PROFILE transaction do not influence the manual RFC mode.
 DSM/CC/CONTROL_USER: The default value for this parameter is DSM_CONTROL. This user is
used by Control Center RFCs from the Control Center to the control client of each controlled
system. It is also used by Control RFCs between systems. The user is automatically created when
a system is connected in Dynamic or Fixed RFC modes. Automatic user creation can be
overwritten by setting the DSM/CC/CONTROL_USER_MANUAL_CREATION profile parameter.
Presently, this user will be assigned the SAP_ALL profile, which can be changed in
DSM/CC/CONTROL_USER_PROFILE parameter.
 DSM/CC/CONTROL_USER_MANUAL_CREATION: This option determines if the control user

should be generated automatically. The flag is off by default which will allow DSM to generate
the control user automatically. While this might be advantageous on test systems, it could be
an issue for Production systems and systems that use CUA. It is recommended to change this to
an ‘X’ on Production systems and to create the user directly.
 DSM/CC/CONTROL_USER_PROFILE: If this parameter is blank, which is the default value, it will

assign the SAP_ALL profile to the user. Again, it might be acceptable on test systems for some
organizations but in Production this could be an issue. On each system, you will need to assign
the Profile name that is generated with the Role created from the role template.
 DSM/CC/TRANSFER_USER: The transfer user is automatically created and updated when the
Control Center configuration is distributed in Fixed RFC mode or when a Sync is performed in
Dynamic RFC mode. The default for this parameter is DSM_COMM_<SID>. The <SID> allows
visibility of which system is making a call. The username prefix can be overwritten by setting the
profile parameter DSM/CC/TRANSER_USER, but the <SID> will still be added at the end. It is
therefore recommended to only use a maximum of eight (8) characters for these users. The
DSM_COMM_<SID> user is generated to facilitate communication between the source and
target systems as used by the Communication RFCs. For example, when ED1 reads data from
CD1, the DSM_COMM_ED1 user will be visible in CD1. A dedicated user should be used in this
case, because DSM5-encrypted passwords will be used, except in the case of Manual RFC mode.
 DSM/CC/TRANSFER_USER_PROFILE: Similarly to the parameter for the DSM_CONTROL user,

this parameter allows you to specify what profile should be used for the DSM_COMM* users. If it
is blank, SAP_ALL will be assigned. For Object Sync and Data Secure, also note that standard
SAP functional access to display the data or process the creation of it on a target system will be
required. Use the Administration report ‘SAP authorizations for Objects’ if you need to see
exactly which authorizations are required. However, it is recommended to assign a wide-
reaching functional display role on the source systems and perhaps allow SAP_ALL on the
target systems for Object Sync.
The user used for communication (DSM_COMM_<SID>) is by default generated with SAP_ALL
unless the parameter noted above is changed. If you don't use SAP_ALL, the user must have
functional authorizations to display data on source systems (typically Production) and create
data on target systems. Without that, Object Sync will not find remote data in the preview step
and will not copy it.
3.2 Control Center configuration

All the components of the Control Center that need to be configured are listed in the navigation tree on
the left side of the screen as highlighted below:
The diagram below provides a high-level overview of a typical SAP landscape and its components.
3.2.1 System registration

All the systems that will be using Data Sync Manager must be registered in the Control Center on
the Controller before any product configuration will be possible for the system. To register a
system on the Controller, open the ‘System registration’ node in the tree on the left of the screen
and select the ‘Add’ button as shown below:
There are different kinds of systems:
 SAP systems: These are SAP ABAP based systems with

DSM5 loaded. Syncs and masking may be performed on
these systems.
 Virtual systems: These are placeholders for future SAP
ABAP systems. You can add virtual systems to facilitate the
mapping of RFCs and Logical Systems in the copied data.
Adding virtual systems avoids the need for BDLS runs.
 External systems: These are non-SAP systems that connect to your SAP environments. These
systems are typically connected using RFCs or HTTPS. SAP SuccessFactors is an example of an
external system that connects using HTTPS.
The SAP System will be the system type chosen most often. Click on the ‘Continue’ button to
display the ‘Register SAP System’ dialog.
This screen will be shown instead of the one above when creating a SAP system in manual RFC
mode:
A ‘Control User’ (as configured in the DSM/CC/CONTROL_USER profile parameter) will be created
automatically on this system by the Control Center. This user’s password will also be generated by
default (Use generated password option), although you do have the option to specify a password
. You need to use the ‘Specify password’ option if the manual user creation option is enabled
(parameter DSM/CC/CONTROL_USER_MANUAL_CREATION) on the system being registered.
When adding a system to the Control Center, you can either enter the system details or choose an
existing locally-defined RFC destination (visible from transaction SM59) connecting to the
Control Client on the system being registered The RFC provided here is only used to find the
system’s information will not be used by DSM5. DSM5 will create the Control Center and Control
RFC connections using this system information (see section 3.1.1).
The ‘Allow profile generation’ parameter behaves as follows:
 When selected: DSM5 will create the ‘Control User’ on the remote system and assign the
SAP_ALL profile to the user and you have to explicitly select the option if you want DSM5 to
assign SAP_ALL.
 When deselected: DSM5 will create the ‘Control User’ on the remote system and assign the
authorization profile as specified by the DSM/CC/CONTROL_USER_PROFILE profile parameter
requires configuration.
The profile specified in the parameter needs to be in line with the applicable authorizations and
policies in your organization.
The default option is deselected to avoid automatically assigning the SAP_ALL profile.
The buttons in the System registration toolbar are defined in the table below:
Button Name Description

Refresh Updates the ‘System registration’ window.
Expand / Collapse Allows you to collapse or expand the System type

subtree folders.
Find / Allows you to search for a specific system in the list.

Find next
Add Allows you to add a specific system to the list.
Change Allows you to edit a specific system.
Delete Allows you to delete a specific system.
Reconnect system Reconnect systems when their connection details

change or when a system becomes available again
that was disconnected for maintenance reasons.
Disconnect system Disconnect systems that are no longer available for

use or that may not be accessible for a period of time
due to system maintenance.
Test connection Tests the Control Center connection to the system.

It is recommended to test the system
connections after registration.
Please note that the ‘Warning’ icon ( ) is a notification that a System is disconnected.
3.2.2 Applications
It is necessary to define and maintain all your applications with their corresponding SAP
application types. A typical landscape may include the following applications: ERP, HCM (ERP),
SRM, CRM, SCM, and BW. Default entries are provided for convenience. This comes pre-configured
so you can remove any or add new ones.
When creating a new application, specify a name and description that is appropriate for your
landscape and avoids confusion. Typical application names include ERP, HCM, FI, SRM, CRM and so
forth. For each application, set the application type to the appropriate SAP application or other
applications such as SAP ERP, SAP SRM, SAP CRM, External Systems (SAP SuccessFactors), etc.
Keep in mind that more than one Application can belong to the same Application type. For
example, Application ERP and HCM are both of Application type ‘SAP Enterprise Resource
Planning’.
Also remember that S/4 HANA has its own application type and should be used instead of ERP if
the system is S/4.
The buttons in this toolbar are defined in the table below:

Sort in Ascending / Allows you to sort the Applications grouping list in
Descending Order an Ascending or Descending order according to your
personal preference using standard ALV
functionality.
Find / Find next Allows you to search for a specific application in the
list.
Add Allows you to add an Application.
Change Allows you to edit an Application.
Delete Allows you to delete an Application.
3.2.3 Environments
An environment is a collection of clients in one or more applications that work together. Typically,
a landscape would include at least the following environments: Development, Quality Assurance,
Production.
For example, EDV-100 (ERP Development Client 100) and SDV-100 (SRM Development
Client 100) form part of the same environment.
Default entries are provided for convenience. Delete any entries that you do not need or create any
new environment.
The toolbar used here has the same functions as those described in the previous section for
‘Applications’. For more information, please refer to the table in section 3.2.2.
3.2.4 System and Client Assignment

Every client on the SAP system belongs to an environment and application. It is necessary to assign
the clients on each system to the correct environment and application in the Control Center in the
System and Client assignment folder.
In this step, you essentially map out the landscape where DSM5 will be used, client by client. To
assign a client to an Environment, click on the ‘Create ‘ button and select the System and Client
you want to assign from the drop-down lists. If the client that you want to assign does not appear
in the list, select ‘New’ and specify the client ID.
Take note that it is also necessary to assign Production system clients.
Although the Data Disclose client registration is discussed in detail in section 3.2.7 below, you
need to ensure that the system and client assignment is properly configured to avoid any
problems that may arise when executing a Data Disclose Installation. For more details and
information in this regard, please refer to the Data Disclose Installation Guide.
Update the Description, Environment and Application as required. The Control Center will
automatically populate the Application based on the selected System, but this may need to be
updated for non-SAP systems.
DSM product settings
 Allow scenario: When selected, this permits the use of the Object Sync Scenario copy
functionality into this target client. Typically, this is set on clients that are regularly refreshed
with Client Sync. This option and implications should be discussed with functional super users
of Object Sync before enabled. Most customers will not need to set this option for clients.
 Allow inplace masking: This determines whether in-place Data Secure Object or Client
masking should be allowed on this client.
 Assignments:
 You need to specify Logical Systems, URLs and RFC destinations for each client if these
need to be converted in Client Sync runs.
 The logical system for an existing system client will be automatically assigned with
‘MANDT’ in the ‘Alias’ field. The ‘MANDT’ logical system should match the logical system
associated with the client in Transaction SCC4. For example, if you are setting up C3R 800,
it should match SCC4 in C3R.
The toolbar used here has the same functions as those described in the ‘System registration’
section. For more information, please refer to the table in section 3.2.1.
3.2.5 Shared folders

Some DSM products allow you to export and import data using files. The files can only be created
in or accessed from the Shared folders configured in the Control Center.
To streamline your process, give each shared folder a logical name. This logical Path name e.g.
SHARE FOLDER in the screenshot will be used for the Control Center configuration. For each shared
folder, assign the physical paths that correspond to the logical shared folder name on each server.
A logical path is a logical name that identifies a permissible directory within DSM and has one
or more physical paths assigned to it. For optimal use, it is recommended to use the same
logical Path name for all systems in a specific Environment.
3.2.6 Routes
Routes specify the path that DSM data transfers between system clients can follow. In the Routes
screen, we have much more granular detail on where and how the different DSM products can
send or receive data. For Object Sync there is the choice between ‘Standalone’ and ‘Distributed’
routes, determining whether partner systems will be included. The Access button allows you to
assign users or user groups access to the routes.
When creating a new route, specify the Route ID and Description, select the relevant DSM product
for which the route is intended and choose the ‘Sync type’ and ‘Transfer type’. Depending on the
‘Transfer type’ selected, the Route source and target parameters will differ.
Sync types:
Standalone routes are used to move data from one client to another client. For example, from
EQA-100 (ERP Quality Assurance client 100) to EDV-100 (ERP Development client 100). For a
standalone route:
 an RFC Sync can be performed from the specified source client to the specified target client.
 a file export Sync can be performed from the specified source client to the specified shared
folder.
 a file import Sync can be performed into the specified target client from the specified shared
folder.
Take note that the file export and import would each need a defined route.
Distributed routes are used to move data from one environment to another environment using
DSM Object Sync. For example, it allows you to move all related data from the clients included in
the Quality Assurance environment to the clients included in the Development environment. For a
distributed route:
 an RFC Sync can be performed from the specified source environment to the specified target
environment. An RFC Sync can be started from any of the source environment systems.
 a file export Sync can be performed from the specified source environment to the specified
shared folder. A file export can be started from any of the source environment systems where
the shared folder is also available.
 a file import Sync can be performed into the specified target environment from the specified
shared folder. A file import can be started from any of the target environment systems where
the shared folder is also available.
Data exported with a Standalone Route cannot be imported with a Distributed Route and vice-
versa.
There is however an additional icon in the toolbar, namely the button. The purpose of
this button is to maintain access for a specific user or specific group of users to a route.
When you define a new route, the route is not accessible to all users automatically. You need to
define the Users and/or Groups that should have access to the Route.
The relevant Groups are defined in the ‘Administration’ space in the User Groups utility and you
need to ensure that the Users and Groups exist on the relevant system clients.
3.2.7 Data Disclose client registration

This configuration is only required if you use Data Disclose or Data Redact. For more details, refer
to the Data Disclose Installation Guide on Client Central.
All system clients that should be searched by Data Disclose or used for reporting or redaction by
Data Disclose or Data Redact need to be registered here. The Reporting option (Allow reporting)
should only be enabled for one of the clients. It allows the Data Disclose/Data Redact SAP GUI or
Fiori app to be executed on this system client. If the Fiori apps are used, this should only be
allowed on a system that has the OData transport applied. Discovery (Allow Discovery) means
that the client provides responses to information requests from the reporting system/client.
3.2.8 Distribute Configuration

This function will distribute the configuration set up in the Control Center to the other registered
systems in the landscape. The distribution status and logs are also accessible here for each of the
systems
To execute the distribution, click on the button.
section except for the ‘Display’ feature. For more information, please refer to the table in
section 3.2.1.
If errors occur in the manual RFC mode (“Manual RFC destination not specified, please specify
manual RFC”), the user should first go to the RFC Destinations tab to see which RFCs should be
set up, as shown below:
The statuses for this function are as follows:
Status Description
Config up to date.
Config out of date, distribution required.
Distributed with errors.
3.2.9 RFC destination (for manual RFC Controllers only)

This option will only appear when the Control Center is configured to use Manual RFCs and
provides an area to maintain all RFCs required for the different types of connections needed.
The earlier entries in the Control Center are all distributed between systems but after distribution,
this entry must be maintained on every system including but not limited to the Controller itself.
The Control Center depicts six (6) different types of RFC destinations when in Manual mode:
 Authentication: Connection used to check authorization of user performing a Sync as well as

setting remote ‘Refine’ options for Object Sync.
 Transfer: Connection used for data transfer between source and target clients.
 Partner: Connection between related clients within an environment (e.g. between ERP and
CRM/SRM environments).
 Data Disclose discovery: Connection used by the Data Privacy Suite to perform cross-system
data discovery and redaction.
 Control: Connection between the source system and control client of each controlled system.
 Control Center: Connection between the controlling system and the control clients of other
systems.
After the configuration has been distributed, any RFCs that are now required to be created will be
marked as <Please specify a destination>.
Double-click on an entry or highlight it and click on the Change button in order to enter the RFC
and then Save.
The ID and client indicate for which system and client the connection is for.
Please note that in this example we must now do the same on the remote system CD2 as well.
Once all the required destinations are entered in a system you can then ‘Distribute’ it again to see
that the configuration is complete.
DSM5 Installation, Control Center and Configuration Guide Administration features
4. Administration features
In addition to the Control Center, there are a number of Administration features and settings that you can
use to configure and manage DSM5 according to your requirements. These programs and settings are
specific to the system and/or client where it is executed and the configuration is not distributed by the
Control Center.
To assist users in the configuration of their Administration screen features relating to whether the
configuration is required, optional or suggested, an appendix has been provided at the end of this
document. The appendix expands on the relationship between the individual utilities and to which
products they are applicable. It also looks at whether these utilities are client- or system-specific.
4.1 Backend Utilities

As part of the configuration process, you can access certain backend operations, which are grouped in the
‘Backend Utilities’.
Partner systems manage the application data related to the system you’re currently working on, allowing
you to query and update this application data via a protocol called OData.
4.1.1 OData identities

This is where you can create the OData identities for your partner systems. You can specify
technical details such as the URL, authentication method, and private/public key pairs. Syncs use
this information during runtime to communicate with the partner system via the OData protocol
and extract/insert data as needed.
For example, if you have HR data on both your SuccessFactors system and ERP systems that you
want to move to a target environment, you need to identify the SuccessFactors system as a partner
system by creating an OData identity.

Display OData identity Allows you to display an OData identity.
Change OData identity Allows you to edit an OData identity.
Create OData identity Allows you to create or add an OData identity.
Delete OData identity Allows you to delete an OData identity.
4.2 Table exceptions

This section enables you to exclude or include some tables from every Client Sync or System Builder run.
Default exceptions are shipped with the product, but for each installation, a decision to keep or change
these exceptions must be taken to ensure that customers get a solution that meets their needs.
Changes should only be made after careful consideration and preferably only once you have consulted
with EPI-USE Labs. Please see the Client Sync or System Builder User guides for more information on these
settings.
4.2.1 Client Sync grouping exceptions

This utility allows a user to maintain specific exceptions per table for the system. Such an exception
will alter the standard behavior of Client Sync when evaluating the particular table in the context
of the specified grouping.

Sort in Ascending / Allows you to sort the Table list in an Ascending or
Descending Order Descending order according to your personal
preference using standard ALV functionality.
Find / Find next Allows you to search for a specific Exception in the
list by entering a search string. DSM will match this
search string with text in the Table, Grouping
columns, etc.
Set Filter… Allows you to select a dimension value from the

available list.
Add Table Click on the ‘Add Table’ button to add a new entry
into the list.
Remove Table Click on the ‘Remove table’ button to remove an

entry from the list.
Export Click on the ‘Export’ button to open a dialog box

that will allow you to export the custom exception
configuration to a file (.xcg extension). This is
typically used to either back up the exception
configuration or import the same configuration on

another system or client.
Import Allows you to import previously exported a custom

exception configuration on a system from file. This
is often used when you need the same exceptions
configured on multiple systems.
To change the inclusion behavior for a specific table, click on the icon in the ‘Table inclusion’
column to cycle through the available options. The icons in the ‘Table Inclusion’ column have the
following meanings:

Include in The table will be copied in full from the source client to
Syncs the target client.
Exclude from The table will not be selected on the source client, and no
Syncs changes will be made to the table on the target client.
Delete table The table will not be selected on the source client, but its
data contents will be deleted on the target client.
Table The table exception will be disabled, meaning it will be

exception copied according to its original behavior. Master and
disabled transactional tables may be time-sliced and/or enterprise-
sliced in correlation with their current inclusion in
standard master and transactional objects. Customization
tables will be copied completely.
4.2.2 Enterprise slice tables

This utility allows a user to maintain specific tables and fields to use for ‘Client Sync’- enterprise
slicing. This configuration is done in addition to the configuration that exists as part of Business
Object Definitions and should only be done if the configuration cannot be done within the context
of a Business Object.
The toolbar used here has the same functions as those described in the previous section for ‘Client
Sync grouping exceptions’. For more information, please refer to the table in section 4.2.1.
For more information regarding the meaning and purpose of enterprise slicing, you can refer to
the DSM5 Client Sync User Guide found in the DSM > Downloads > Data Sync Manager 5
Documentation > English space on Client Central.
The information can be found in section 3.2.3.a. (Application data) in the ‘Create Sync’ section
of the guide.
4.2.3 System Builder table rules

This utility allows a user to maintain specific exceptions per table for System Builder. This exception
will alter the standard behavior of System Builder when evaluating the particular table for export.
The toolbar used here has the same functions as those described in the previous section for ‘Client
Sync grouping exceptions’, with one additional button. For more information on the toolbar
functions, please refer to the table in section 4.2.1.
The additional button mentioned above is the ‘Change’ button . By clicking on the
‘Change’ button, you will be able to edit the exception for the selected table.
For more information on the functions and benefits of the System Builder product, please refer
to the DSM5 System Builder User Guide that can be found in the DSM > Downloads > Data Sync
Manager 5 Documentation > English space on Client Central.
4.3 Number range handling

This section can be used to influence the ‘insert behavior’ on the target client of master data for Object
Sync and for the troubleshooting of number range inconsistencies between source and target clients.
4.3.1 Data insert behavior

This utility allows you to influence the Object Sync Insert behavior when copying master and
transactional data to the target client. The following should be considered:
 The Business Object may not allow some options in exceptional cases.
 These options are client-independent and therefore apply to all clients on the system.
Please note that the settings adopted for the Master Data tab in the screen above remain the
same for the ‘Transactional Data’ and that only the exceptions will vary according to your
requirements.
Also, note that the button will save any changes you make to the Exceptions in the
behavior options on this screen. The button will revert any changes you
made to the available options and exceptions to the delivered defaults.
a. Default Copy Behavior

 Keep Original Number
By default, DSM will ‘Keep Original Number’ for Business Objects. However, keeping the same
number is not possible if the target number range interval is ‘internal’ and the source object
number is greater than the current target internal ‘number range’ pointer. This problem can
be overcome by ensuring that the Target client's internal ‘number range’ pointer for the
interval is large enough.
This can be achieved by manually adjusting the internal number range pointer for the
applicable number range intervals. The ‘Number Range Maintenance’ utility under the
Administration functions can be used to assist with this.
Alternatively, DSM can automatically adjust the number range pointer during Syncs so that all
Business Object numbers in the Sync are smaller than the internal number range pointer. To
enable this functionality, select the ‘Adjust Number Range Pointer’ option. This is the default
configuration option.
The second option is to have the Sync of the Object Sync ‘Fail with Error Message’. If this
option is set, DSM will by default not insert the Business Object on the target client and give
an error message indicating a problem with the number range.
 SAP assigns number and DSM maintains a cross-reference
DSM provides an alternative to ‘Keep the original number’, which adheres to the standard SAP
behavior. If the relevant number range interval on the Target system is set to ‘internal’, a new
number will be assigned based on the number range configuration. If the Target system's
number range interval is set to ‘external’, the source number will be used on the target client.
This option is less frequently chosen by customers because the test data is not obviously the
same as the original on the source system and can, therefore, be harder to test with.
b. Default Insert Behavior

If the ‘Allowed Insert Behavior’ in the Business Object Workbench (BOW) is specified as ‘Object
Definition Logic (ODL) and Business Logic’, then the specified ‘Default Insert Mode’ will be
applied when the Business Object is inserted on the Target client. The Insert Behavior may be
restricted for some Business Objects in BOW in which case this configuration option will be
ignored.
c. Default Clone Behavior

The Administrator can choose to disable the ‘Cloning’ functionality for all Business Objects
other than those listed as Exceptions when they uncheck the ‘Cloning of Objects allowed’
option.
By default DSM allows the user to decide how new numbers will be assigned to the cloned
Business Objects in an OS Sync. There are two options to choose from: ‘Start at user-specified
number’ and ‘Automatically generate new number’. The Administrator can limit the number
assignment method choice to one of these options only or leave it up to the user to specify for
each Sync.
d. Exceptions

Add Exceptions Allows you to add and configure specific
Insert Behavior Exceptions for the specific
Business Object.
Remove Allows you to remove the Business Object

Exceptions from the Exceptions list.
Toggle display Allows you to switch information displayed in

the Business Object Description column
between the Business Object name, a
combination of the Business Object name
and the technical name and only the
technical name.
This list allows exceptions to be made for specific Business Objects. For example, you may
wish to use the default behavior for everything except EMPLOYEE. You can then add the
EMPLOYEE object as an exception and specify different options that should be used for this
object specifically instead of the global Default behaviors. Remember to add the exceptions
on both source and target systems.
4.3.2 Number range maintenance

This utility allows you to compare the number range configuration between clients per Business
Object. The utility also allows you to move number range pointers or change number range
intervals to external. RFC Object Sync routes must be configured before this utility can be used.
The following functions are available when configuring and maintaining a number range:
 In the ‘Selection options’ block, you have the option to indicate for which Business Objects this
utility should be run. By using the ‘Additional Settings’ button, you can further include
and manage values and ranges.
 By clicking on the ‘Remote System’ button, you can select the remote client with which the
number range comparison should be done. Once you have clicked on this button you will be
presented with the ‘Destination value help’ pop-up window where you can select the remote
system and client from the list of RFC destinations (you can only use DSM-registered RFC
destinations with this utility).
Once all the configuration and/or maintenance is done, click on the ‘Execute’ button to
execute the report.
From this screen, you can see exactly which number range intervals have errors (i.e. those that
have different customizing) and those that do not. You can click on the ‘Alter Pointer’ button to
move the pointer or change the interval from internal to external (this function can only be used
for intervals that are internal and do not contain any errors). Number range intervals on production
clients may not be altered.
4.4 Cleanup and Optimization

This section contains utilities to perform specific actions that fall into two main categories:
 Cleanup - utilities to clear Sync logs and files.

 Optimization - utilities that will enhance the performance of your Syncs if performed periodically.
4.4.1 Recommended index check

This report lists secondary indexes that could be created on the specified tables to improve the
performance of Syncs. The check is performed per Business Object.
Regarding the Business Object selection, you have the option to indicate for which Business
Objects this report should run. If you select the checkbox 'Consider empty tables', the report will
also include tables that are currently empty in the recommendation.
In the ‘Selection options’ block, you have the option to indicate for which Business Objects this
utility should be run. By using the ‘Additional Settings’ button, you can further include and
manage values and ranges.
To start the ‘Recommended Index Check’ report, click on the ‘Execute’ button.
4.4.2 Date slice index check

This report lists the index required by Client Sync per Business Object as well as the available index
which will be used during a Sync process.
Regarding the Business Object selection, you have the option to indicate for which Business
Objects this report should run. If you select the checkbox 'Only show missing indexes', the report
will only show those indexes that do not match the indicated Business Object values or ranges.
To start the ‘Recommended Index Check’ report, click on the ‘Execute’ button.
4.4.3 Database consistency check

This report will perform the checks listed below on all transparent tables that are not part of the
$tmp package:
 Database and Runtime object checks available in transaction SE11 under the ‘Utilities’ menu.
 Attempt to select a single record as a sanity check.
The ‘Job Log’ will list any tables that have inconsistent Database objects, Runtime objects or where
the single select failed.

Sort in Ascending / Allows you to sort the Job Log list in an
Descending Order Ascending or Descending order according to
your personal preference using standard ALV
functionality.
Refresh Updates the ‘System registration’ window.
Job Overview To display the ‘Job Overview’.
In the Toolbar, you have the following additional functionalities:
 : This option allows you to execute this utility immediately in the foreground.
 : This option allows you to execute this utility in the background,

especially if it is likely to take some time.
 : If you need to schedule the consistency check to execute at a

later stage, then you have the option to choose from any of the scheduling options
displayed on the ‘Start Time’ screen. Once you have entered your selection, click on the
‘Check Input’ button to exit this screen and save your execution options. You can exit this
screen without saving your execution options by clicking on the ‘Cancel’ button.
4.4.4 Object Sync cleanup

This utility allows you to clean up old Object Sync runs and/or Object Sync runs that are marked for
deletion from your System. This utility should be run periodically to keep the number of database
table entries to a minimum.
When a user marks a Sync for deletion it is removed from their Monitor Desk but can still be
seen by the Administrator.
In the ‘Selection options, you can also specify whether the related Object Sync files (generated
during a File Export Sync) should be deleted according to the filter options and settings available
in the checkboxes. By using the ‘Additional Settings’ button, you can further include and
The ‘Job Log’ or foreground pop-up will list all the activities relating to the cleaning up of Object
Syncs that have been carried out. When run in the foreground the logs will not be visible in the
future, only at the time of execution.
For more information on the utility functions and buttons available on this screen, you can refer to
the table and the ‘Infobox’ in the previous section, section 4.4.3.
4.4.5 Client Sync cleanup

This utility allows you to clean up old Client Syncs and Client Syncs that are marked for deletion
from your System. This utility should be run periodically to keep the number of database table
entries to a minimum.
In the ‘Selection options, you can also specify whether the related Client Sync files (generated
during a File Export Sync) should be deleted according to the filter options and settings available
in the checkboxes. By using the ‘Additional Settings’ button, you can further include and
The ‘Job Log’ or foreground pop-up will list all the activities relating to the cleaning up of Client
Syncs that have been carried out. When run in the foreground the logs will not be visible in the
future, only at the time of execution.
the table and the ‘Infobox’ in section 4.4.3.
4.4.6 File explorer

This utility allows you to clean up the exported Sync Data Files related to a Sync. It will list all the
Syncs for which related Sync Data Files exist. If you expand the Sync, you will be shown a list of all
the files (header, control and data) for the Sync, with their sizes. All the files for a Sync will be
deleted at the same time as deleting them individually will render the remaining files inconsistent
and therefore not useable.
In your ‘Selection options’, you have the option to indicate which DSM directory the cleanup utility
should run for.
Currently, the Path name has only one option, namely the ‘SHARE’ option.

Refresh Updates the ‘File Explorer’ window.
Expand / Allows you to sort the Exceptions grouping list in

Collapse Descending order according to your personal
subtree preference using standard ALV functionality.
Find / Find Allows you to search for a specific system in the list.
next
Kilobytes This drop-down menu allows you to set the

measurement level for the
amount of data is linked to a
specific system as per the
following options:
4.4.7 Clean up mapping table

This utility allows you to conduct a consistency check on DSMs mapping tables in order to remove
entries where a specific Business Object no longer exists, i.e. inconsistent key mappings.
In your ‘Selection options’, you have the option to select specific Business Objects in order to
remove their inconsistent key mappings. By using the ‘Additional Settings’ button, you can
further include and manage values and ranges.
The ‘Job Log’ will list all the activities relating to the cleaning up of the Mapping table that have
been carried out. The starting date and time can be defined by the user and other filters can be set
in place to generate more specific information, as is required.
This will only find inconsistent mapping values where data has been removed from a client, for
example, mappings for Employee keys that have since been deleted in the client.
4.4.8 Optimization program

This utility runs on a regular basis to improve the performance of Syncs. The optimization is
performed per Business Object.
In the ‘Selection options’, you can select specific Business Objects to optimize or leave blank to
optimize all Business Objects. The checkbox 'Evaluate delta changes only' is set by default and this
option will only re-evaluate tables that were empty with the previous run, meaning that
subsequent optimization runs will require less runtime.
The ‘Job Log’ will list all the activities relating to the performance improvement of Syncs by means
of the Optimization programs that have been carried out. The starting date and time can be
defined by the user and other filters can be set in place to generate more specific information, as is
required.
Object Sync will automatically run the optimization if the objects in scope have not been
optimized in the previous week but scheduling it ahead of time makes the run quicker. For Client
Sync it is essential for it to have run recently so having it run weekly is highly recommended.
This utility automatically runs per Source and Target client configured for the product, every
seven days if it is scheduled.
4.4.9 HR cluster optimizer

The ‘HR Cluster Optimizer’ is an optional report that optimizes selects from the PCL4 table for the
'U1', 'F2', ‘K1, ‘F1’, 'SA' and 'SB' cluster ids. The report is only valid for Users of the Payroll,
Garnishing, and Short Term Audit Trail Data Groups. It will improve runtimes on employee or
applicant Syncs that use one or more of these Data Groups.
In the ‘Selection options’, you can set the maximum number of days per run to be evaluated. In the
example above, all records changes in the last 60 days will be evaluated.
The ‘Job Log’ will list all the activities relating to the specific HR-cluster activities necessary for
optimization that have been carried out.
Please note that this report should be scheduled to run once per day.
4.4.10 Pre-calculate masked values

This utility allows a calculation run to be executed for a particular masking policy. When Object
Sync, Client Sync or inplace Object or Client masking are used there will be an option to ‘Reuse
previous masking values’ that will leverage this masking database.
To execute a calculation run, click on the Policy and then ‘Create run’.
In the pop-up, you can assign processes for the calculation run in each system/client in the
environment, with a tab to make the selections on each one.
You can then choose to add Notifications if you wish to know when the run has Started, Finished, is
Cancelled or if you want status updates on it.
And finally, add the execution options for when it should run:
The buttons in this toolbar and the icons in the table are defined:

Refresh Updates the list of pre-calculated masked values.
Create run Stars a masking database calculation run.
Detail Shows the details of the calculation run, including the

number of keys processed for each Object in the Policy.
Delete Deletes the mapping run or the calculation database

depending on what is selected at the time.
Resume Continues a run that has been stopped.
Stop Stops a running Calculation run.
Diagnostic Downloads a Diagnostic log that can be uploaded with a

log support issue on Client Central.
Has data Indicates the policy has a precalculated mapping database.
No result Indicates the policy does not have a mapping database.

exists
4.4.11 Data Disclose index run

This utility allows an index run to be executed for a particular masking policy so that data for legal
person types can be searched more easily. When Object Sync, Client Sync or inplace Object or
Client masking are used there will be an option to ‘Reuse previous masking values’ that will
leverage this masking database.
Sensitive values won't be duplicated. Indexing occurs according to the configuration set up in
'Data Disclose client registration' (under 'Control Center') and indexing runs can only be
executed from systems and clients that have 'Allow reporting' enabled.
For more information on the utility functions and icons available on this screen, you can refer to
the ‘Infobox’ in the previous section, section 4.4.10.
4.4.12 Object flow optimization

This program will scan your transactional data flows to determine your typical document flow in
the various modules, e.g. Sales, Purchasing, etc. This is then stored for optimal use during the
selection phase of data for the Sync process.
Select the checkbox 'Persists results' if you want to save the results of this analysis. Deselecting the
checkbox will result in a report only.
The list box 'Trace level' can be used to define the level of detail to be provided in the analysis
report.
4.4.13 Pre-system export optimization

This utility can be used to re-evaluate the table-splitting conditions used by System Builder when
performing a system export. This utility should be run at least once after installation and may be
run again from time to time in order to improve performance.
The runtime for this utility will vary according to system performance. A typical runtime of at least
30 minutes should be expected if the system contains version control information, on Production
systems the runtime can be as low as one or two minutes.
The ‘Job Log’ will list all the activities relating to the pre-system optimization that have taken place
before it is exported.
4.5 Masking
This section enables you to configure the settings that will be applied when making use of the Masking’
options in Data Secure and now working across systems automatically and embedded into Object Sync
and Client Sync. This is necessary because of the greater complexity of these settings and the additional
power it provides to users.
4.5.1 Address database

This utility allows you to configure the address scrambling behavior of Object Sync and Data
Secure.
Data Sync Manager delivers a database of default address values that are used by the address-
scrambling logic to randomly create gender and country-specific addresses. These values are
recombined to form an address that passes input checks but does not truly exist and does not
match the original address. The Rules in Data Secure determine how these name and address
values are utilized.
Individual configurations for the Address database can be adapted for each of the following:
 Street names
 City names
 Regions
 Postal codes
Each option comes with pre-delivered values that can be added to or replaced completely. The
export/import capability makes this much quicker.
A customer-specified address may be added, removed, exported to and imported from a comma-
delimited file, reloaded from the database and sorted.

Insert row Allows you to add an address to the list.
Delete row Allows you to remove an address from the list.
Activate Activates a delivered entry that has been deactivated.
Deactivate Deactivates a delivered entry so it is not used.
Export data Exports the value list to a file for modification.
Import Imports a file that has been modified.

data
Select All Allows you to select the entire list with one action.
Postal codes may be altered fully, partially, or not at all, depending on the effect the alteration
will have on tax and other calculations. You can specify country-specific postal-code settings in
the 'Postal codes' tab.
4.5.2 Company database

In the case of the companies, there are three separate configuration possibilities for you to
consider and use, according to the country specified. These are:
 Company names
 Company industries
 Company suffixes
Masking rules that use random values for companies will randomly select from the name, industry
and suffix list for the country the data is assigned to.
As with the Address database the delivered content can be deactivated, downloaded, modified
and uploaded back in.
the table in section 4.5.1.
4.5.3 Person database

For the name-scrambling logic, default male first and nicknames, female first and nicknames and
surnames exist with a country-specific setting and can be used to generate new random name
values. This list can be updated with customer-specific values also.
Adapting these delivered values could be used to increase or decrease variety (e.g. a single
name per type per country that all records get) or to ensure non-realistic names such as days of
the week or months of the year.
4.6 Business Object maintenance

This section contains utilities to perform specific actions on the Business Objects, which are used by the
DSM products.
4.6.1 Mapping Editor

This utility allows you to manipulate the number to be used by Object Sync when inserting Master
Data on a target client.
You need to select the Master Data Business Object in the object tree, and then you can specify the
values of the source system, client and object key that you wish to manipulate. If none is specified,
all the existing mapping records for the selected Business Object will be listed.
When using standard ALV-grid functionality, you will be able to:
 Edit existing records

 Create new records
 Delete existing records
 Download the list to a local file

Refresh Updates the ‘Object Map Editor’ window.
Expand / Collapse Allows you to sort the Exceptions grouping list in

selection Descending order according to your personal
preference using standard ALV functionality.
Search Allows you to search for a specific Object in the Main

Object Selection by entering a search string.
Toggle Display Allows you to switch between the Business Object

name, a combination of the Business Object name and
the technical name and only the technical name.
4.6.2 Generate object classes

This utility allows you to regenerate the classes for a Business Object.
This utility will only be used by EPI-USE Labs Support in an effort to resolve a problem.
The Business Object Selection options are twofold when generating object classes:
 Select which Business Objects this utility should be run for.

 You are able to generate the classes for Business Objects on a Remote client as defined in the
RFC Destinations utility but only on DSM-registered RFC destinations.
 : This option allows you to execute this utility immediately in the foreground. An
Object Class Generation Trace is displayed when run in the foreground.


By selecting the ‘Execute on remote system’ checkbox, you can select the remote client with which
the connection should be made for generating the object classes remotely. Once you have clicked
on this button, you will be presented with the ‘Destination value help’ pop-up window where you
can select the remote system and client from the list of RFC destinations (you can only use DSM5-
registered RFC destinations with this utility).
The buttons in this screen’s toolbar are defined in the table below:

Sort in Ascending Allows you to sort the Applications grouping list in
/ Descending an Ascending or Descending order according to
Order your personal preference using standard ALV
functionality.
Refresh Updates the Job log list.
Job Overview To display the ‘Job Overview’.
The ‘Job Log’ will list all the activities relating to the generation of Object classes that have
occurred. You can set various filters to define more specific information, as is required.
For more information on the Execution options available on this screen, you can refer to the
‘Infobox’ in section 4.6.1.
4.6.3 Generate Profiles and Groupings

This utility allows you to regenerate the classes used by Client Sync, based on updates received for
Business Objects.
You should always run this generation without specifying any selection for a consistent result.
The Selection options deal with two categories, namely:
 Profile: Select which Client Sync Profiles this utility should be run for.
 Grouping: Select which Client Sync Grouping this utility should be run for.
In your ‘Selection options’, you have the option to select specific Profiles or Groupings and by
using the ‘Additional Settings’ button, you can further include and manage values and
ranges.

Sort in Ascending Allows you to sort the Job list in an Ascending or
/ Descending Descending order according to your personal
Order preference using standard ALV functionality.
Refresh Updates the Job log window.
Job Overview To display the ‘Job Overview’ and the ‘Job Log’.
The ‘Job Log’ will list all the activities relating to the generation of Profiles and Groupings that have
occurred. You can set various filters to define more specific information, as is required.
For more information on the Execution options available on this screen, you can refer to the
‘Infobox’ in section 4.6.2.
4.6.4 Maintain Semantic Tags

A Semantic tag is metadata associated with a Content Item (Integrity Map, Transformation function
or parameter) as a hint to the product to what other content items it could be associated with. This
utility allows the visibility, deletion and creation of additional semantic tags.
Tags can also be created with the content they are linked to in Data Secure.

Sort in Ascending Allows you to sort the Semantic Tags in an
/ Descending Ascending or Descending order according to your
Order personal preference using standard ALV
functionality.
Find… Allows you to search for a specific term and to filter

the ‘Search Direction’ within the table as well as
excluding partial words or values. You will also
have the option to activate a function by which the
number of hits will be displayed.
Create Allows you to create and define a new semantic

tag.
Delete Allows you to delete an existing semantic tag that

is no longer required.
Select All Allows you to select the entire list with one action.
Display Displays the Description assigned in all the

description languages that it has been created with.
4.7 Audit and security

This section can be used to set up security-related settings for objects, groups, users as well as running
audit reports.
4.7.1 Group Management

This utility allows you to define logical groups within which users can be placed. This step is
required to give user groups access ( ) to specific policies (Data Secure Policies), Sync templates,
System routes and other artifacts. Wherever the Access button is available it can be assigned to
specific users or groups. By collecting users together in groups, the assignment is easier to
manage.
The EVERYONE group is all users with DSM access and the $ADMIN group is all users with the
following authorization pattern:
 Object - /USE/DM1MT
 ID – /USE/DM1MT = ‘M13’
 ID – ACTVT = ‘02’
Other groups can be created and then users assigned to those Groups or sub-groups assigned to
the group.
The buttons in the ‘User groups’ toolbar are defined in the table below:

Refresh Updates the ‘Group Management’ User groups.
Change Allows you to select User group and change or edit the
Group detail in the pop-up window shown below:
Create Group Creates a new user group.
Delete Group Deletes a user group.
Display Shows the Policies, Templates and Routes the group has
effective access access to.
The buttons in the ‘User’ window are defined in the table below:

Find Allows you to search for a specific term and to filter the
‘Search Direction’ within the table as well as excluding
partial words or values. You will also have the option to
activate a function by which the number of hits will be
displayed.
Manage the Add or remove sub-user groups for this Group.

groups included
Manage users Add or remove users to the Group.
Add single user Allows you to add a single user to the list or obtain
selection options for lists or ranges of users.
Delete row Allows you to remove a single user from the list.
Display effective Shows the Policies, Templates and Routes the group
access has access to.
The ‘Access’ buttons are a very useful way to see from here which Policies, Templates and
Routes a Group or an individual User has access to.
4.7.2 Object protection list

The 'Object Protection List' report provides a list of objects on a target system that cannot be
overwritten by DSM. Object Protection provides a means to protect objects from being
overwritten by future Syncs. This process is performed on the Target system that contains the
object instances you wish to protect.
By selecting the ‘Execute on remote system’ checkbox, you can specify specific business objects to
retrieve the protection list for. Once you have clicked on this button you will be presented with the
‘Destination value help’ pop-up window where you can select the remote system and client from
the list of RFC destinations (you can only use DSM registered RFC destinations with this utility).
4.7.3 Object protection editor

Object Protection provides a means to protect objects from being overwritten by future Syncs. This
process is performed on the Target system that contains the object instances you wish to protect.
On this screen, the following is relevant:
 Main Object Selection Tree: Double-click on the Business Object that you wish to protect or
select the Business Object and click on the ‘Edit’ button.
This will generate an ‘Object Protection’ pop-up screen:
 Select Options pop-up screen: Select the instances that you wish to protect.
 Object Protection ALV Grid screen: You are then presented with a list of object instances in an
ALV grid, from which you can select specific instances that you wish to protect. Either click the
lock/unlock icon in the Status column or select a row and click on the ‘Protect’ or ‘Unprotect’
buttons in the grid toolbar. The protection of these instances can be enabled and disabled from
this screen. All the selected objects will appear in the list and can be individually protected or
unprotected.
Administrators have the additional option to remove protection from all the listed object instances
for a specified type using the Clear Protection menu option in the ‘Action’ menu.
Once an object instance is protected, only the user that protected it or an Administrator/Super-
User can unprotect it. Administrators can also use the 'Clear Protection' menu option under
'Administration' to remove protection for all object instances of a specified type.

Refresh Updates the ‘Object Map Editor’ window.
Expand / Allows you to expand or collapse a node of the Object

Collapse Selection tree.
selection
Search Allows you to search for a specific Object in the Main

Object Selection by entering a search string.
Toggle Display Allows you to switch between the Business Object

name, a combination of the Business Object name and
the technical name and only the technical name.
4.7.4 SAP Authorizations for Objects

This report allows you to retrieve the SAP standard authorizations which are checked as part of the
data retrieval process of a Business Object on the Source client.
To get the Authorization Details, select the ‘Execute’ button to start the report. The
result will be displayed in an HTML output that can be printed or alternatively downloaded to file
using the relevant toolbar (Print) or (Download to file) buttons.
4.7.5 User preferences

This utility allows you to edit another user's User Settings.
To select a ‘User Name’, click on the ‘Select User’ button to display the ‘Username value help’ pop-
up screen.
Click on the F4 pop-up button to select a ‘User Name’ from the list of SAP users. Make a selection
and click on the ‘OK’ button to display the name of the user in the ‘Username value help’ pop-up
screen. When you click on ‘Continue’ again, you will generate the Transaction Display.
In the ‘Main Object Selection’ block, you will see the Business Objects and Integration Objects that
are displayed on the DSM Business Object Hierarchy Tree. These can be viewed according to
various filters:
 Supported Objects: All delivered Business Objects.

 Objects with Data: Objects that have data (instances) on systems.
 Licensed Objects: Objects for which you have purchased a license (not available as part of the
Integration View).
 My Authorized Objects: Objects for which a user has authorizations.
 My Usable Objects: Objects that have assigned authorizations, data available, and that are
licensed.
In the ‘File Import View’, you can view the imported Syncs may be listed according to four types of
filters:
 List by Date: Import Syncs are listed according to the creation date.
 List by Source: Import Syncs are listed according to the Source system where the Sync was
created.
 List by User: Import Syncs are listed according to the User who created the Sync.
 List by Main Object: Import Syncs are listed according to the main object.
The Client Sync File Import View can be viewed by:
 List by Date: Import Syncs are listed according to the creation date.
 List by Source: Import Syncs are listed according to the Source system where the Sync was
created.
 List by User: Import Syncs are listed according to the User who created the Sync.
The DSM Product block allows you to set the default version of DSM or choose between version 4
and version 5 each time DSM is opened. This will only appear on systems that also have DSM4
loaded.
On the ‘List Display’ tab, you can list output limits.
The ‘List Output Limit’ function sets the upper limit for the number of items that may be displayed
per User. In the example displayed, the limit is set to 200 items. This will, for example, affect the
number of Business Object instances on the Preview screen or in the Monitor Desk statistics.
Select or deselect this checkbox to show or hide the ‘List Output Limit’ pop-up screen that is
displayed prior to the Preview Screen. If this checkbox is not selected, a warning is displayed when
the output is limited.
The last tab on this screen is the ‘Limits’ tab, which allows you to set your Sync limits.
The checkboxes available here allow you the following options:
 Limit Objects: Limit the maximum number of Business Objects allowed within a single Sync.
The default is unlimited.
 Limit Parallel Processing: Limit the maximum number of usable parallel processes while
executing a Sync. The default is unlimited.
4.7.6 Sync Audit Report

This utility allows you to generate an audit report per SAP user for Sync Number, Business Object,
Business Object Instance, SAP ‘User Name’ and Sync Period.
The Selection Options allow you to specify the Sync Number, Business Object definition, Business
Object Instance, SAP ‘User Name’, and Sync Period. Once you have identified a Business Object,
you will also have the option to add, remove or clear Instance Keys for that object by clicking on
the button.
In your ‘Selection options’, you also have the option to use the ‘Additional Settings’ button,
to further include and manage values and ranges.
The Output Options allows you to choose meaningful fields to be displayed in the report.
 : This option allows you to execute this utility immediately in the foreground.


4.8 Client Sync utilities

This section is used to configure utilities that can be used to streamline and improve the performance of
Client Sync.
4.8.1 Index enabler

This utility recreates indexes deleted by the Index Disabler program. Any indexes that were
previously inactive on the database will not be activated by this program.
The buttons available for use in the ‘Job Log’ window are as follows:

Sort in Ascending Allows you to sort the Job list in an Ascending or
/ Descending Descending order according to your personal
Refresh Updates the Job log window.
Job Overview To display the ‘Job Overview’ and the ‘Job Log’.
The status displayed in the screenshot above indicates that the job is finished.
4.8.2 Index disabler

This utility allows you to delete secondary indexes. Secondary index deletion can greatly improve
the Client Sync 'Delete' performance. Results can be dramatic and reduce table deletion times from
hours to minutes for larger tables with multiple indexes.
Please be aware that deleting an index will affect all clients in that system and can also seriously
affect performance in other clients.
For the uses of the buttons available in the ‘Job Log’ window, refer to the relevant table in section
4.8.1. above.
The status displayed in the screenshot above indicates that the job is finished.
4.8.3 Tables for which secondary indices can be dropped

This allows users to maintain tables that have secondary indexes to be deleted or recreated by the
'Index enabler' and 'Index disabler' programs. This is only done for tables that have performance
problems (when deleting records from the table) and is done by typing in the table name.

Sort in Ascending Allows you to sort the Table names in an Ascending
/ Descending or Descending order according to your personal
Find…/ Allows you to search for a specific term and to filter

Find Next… the ‘Search Direction’ within the table as well as
excluding partial words or values.
Create Allows you to create a new Table name for the

Secondary index.
Delete Allows you to delete an existing table for which a

secondary index is no longer required.
Toggle headers Toggles between the Functional and Technical

names of the Table fields.
Remember to save the tables that you have created so as to not lose them, even if you’re just
navigating between screens.
4.8.4 Object key processing limits
The Object key processing limit settings are used to control the number of keys that are processed
by Client Sync at a time in relation to transactional objects. The data is stored in the table
/USE/CS1_OBJKYL. The fields available are the following:
 Business Object Definition Name: Name of the object you wish to control. This object needs
to be transactional either by default or by using the /USE/CS1_TOBJ table.
 SELECT_LIMIT: The maximum number of keys that Client Sync can select from the 'Check' table
of the object at a time for processing.
 PROCESS_LIMIT: The maximum number of keys that Client Sync can process at once when
selecting data on tables related to the 'Check' table of the object.

Sort in Ascending Allows you to sort the Table names in an Ascending
/ Descending or Descending order according to your personal
Find…/ Allows you to search for a specific term and to filter

Find Next… the ‘Search Direction’ within the table as well as
excluding partial words or values.
Create Allows you to create a new Table name for the

Secondary index.
Delete Allows you to delete an existing table for which a

secondary index is no longer required.
Toggle headers Toggles between the Functional and Technical

names of the Table fields.
a. Example of usage
Scenario:
Some customers run into inconsistencies for material ledger data due to data being created
while the sync export is being run. The data for material ledgers is stored in the object
ES_MATPLANT, which is a master data object. The inconsistencies are caused when data is
read from one ledger table and by the time the table is extracted and moves onto the next
ledger table, there have been updates. This means that data relating to a transaction is in one
table but not in another. To try to minimize the inconsistencies we set the object
ES_MATPLANT to transactional using the /USE/CS1_TOBJ table. Now that the object is
transactional, we can use the /USE/CS1_OBJKYL table. The following entry is made:
 OBJECT: ES_MATPLANT
 SELECT_LIMIT: 5
 PROCESS_LIMIT: 1
Impact:
 SELECT_LIMIT: As the object is now transactional, the relating keys are selected from the
table MARC which is the 'Check' table of the object ES_MATPLANT, 5 at a time as that is the
limit that has been set.
 PROCESS_LIMIT: Now that Client Sync has the keys from the 'Check' table of the object, it
can now go through all the other tables in the object and select the related data. This is
done using 1 key at a time as the setting change indicates.
Effect:
As Client sync is processing so few keys at a time, the time between the select on one table
and another related table is minimal, meaning the data in the tables at the time of selection is
more likely to be consistent.
Possible negative effect:
As a possible side effect of the above changes, it may be that the performance of the Sync is
negatively impacted. To ensure the best balance between performance and consistency
testing may be needed with different settings.
Remember to save the tables that you have created so as to not lose them, even if you’re just
navigating between screens.
DSM5 Installation, Control Center and Configuration Guide Troubleshooting
5. Troubleshooting
In the course of your installation and specifically the setting up of your Control Center, you might
encounter some problems. Here are some tips on how to deal with possible issues:
 If you have issues with the Control Center and connections you may want to strip the configuration
down and delete RFCs before building it up again while checking settings such as the ‘Logon’ groups in
your connections.
 If you keep being prompted to log on, check the RFCs in Transaction SM59 and use the Utilities ->
Authorization test.
 Check the output logs where an icon shows as yellow or red. There may be additional information in
the log that helps explain what the issue is.
 Registering systems after a System Copy. The Control Center encrypts the information that it uses to
communicate between systems. If a system is copied from another system using traditional system
copy, the private key it stores will still match the old system ID, not the new one. This will cause system
registration to fail in the Control Center. Go to the copied system and execute the program
/USE/DC1_REGENERATE_PRIVATEKEY in the background. Once this job has completed (it may take 5
minutes), the system can then be registered.
 Look in the Knowledge Base articles in the DSM Workspace of Client Central for any error message or
description of the situation you are encountering. If that doesn’t resolve the issue, log a ticket via Client
Central. See section 6.2 below on how to do that.
DSM5 Installation, Control Center and Configuration Guide Accessing support through Client Central
6. Accessing support through Client Central

EPI-USE Labs provides customers with solution and services support through Client Central for virtually 24
hours on working days. Among other services, you can log tickets, access knowledge base articles and
tutorial videos, download the latest transports and user guides, post messages in the forums, and
contribute to the improvement of our solutions with suggestions.
6.1 Requesting access to Client Central

If you do not have access to Client Central, click ‘Register’ and follow the prompts.
6.2 Logging a ticket

If you encounter an error or need more specific help, log a ticket with our Support team:
1. Click Tickets > Log a ticket.

2. Complete the required fields.
DSM5 Installation, Control Center and Configuration Guide Accessing support through Client Central
 To find out which version of DSM you are running, click About > About on the menu bar.
 Under ‘Description’, provide a short but detailed description of the problem, including screenshots and
the error message or unusual output that you received.
 Exporting and attaching a diagnostic log (DL) to your ticket will save time and help the Support team
assist you. Please create a zipped folder if you would like to attach multiple files.
3. Click ‘Submit’.
The system will issue you a ticket number and send you an email acknowledging the ticket, and an EPI-USE
Labs support representative will begin to assist you. You can view the status of your tickets on Client
Central’s homepage under ‘Tickets’.
6.3 Additional help and resources
6.3.1 Guides
View and download various DSM5 installation, configuration and user guides in the DSM5
Documentation folder.
6.3.2 Knowledge base articles

Visit the DSM knowledge base space for articles about solution features, troubleshooting and best
practices, FAQs, change logs, and more.
6.3.3 Videos
Browse the DSM video library for product overviews, demonstrations and tutorials.
6.3.4 Forums
Visit the forums to ask questions to or share your expertise with other members of Client Central’s
online community.
6.3.5 Contact us
You are welcome to send us comments and suggestions regarding our products, documents,
services and support via:
 the Client Central support portal (for existing customers only) or support@labs.epiuse.com (if
you do not have access to Client Central)
 the EPI-USE Labs website.
We are happy to incorporate suggestions that make our products more powerful and easier to use. In this
way, we can contribute to making your work simpler and more efficient.
DSM5 Installation, Control Center and Configuration Guide Utilities and Products relationship
Appendix A: Relationships between Administration

utilities and DSM products
This appendix is meant to assist users of the DSM range of products to identify which utilities listed in the
Administration features screen are applicable to the separate products that make up the Data Sync
Manager (DSM) suite. The table on the following pages will be useful to users in terms of identifying the
specific utilities that may need setting up and configuring the Administration features.
The following legend/key will help you navigate the

table on the following page:
Product abbreviations:
 OS: Object Sync

 CS: Client Sync
 DS: Data Secure
 SB: System Builder
 DD: Data Disclose
 DRd: Data Redact
 DRt: Data Retain
The last two columns (Config. and C/S) represent the

following concepts:
 Config: Is this utility a required configuration during

installation? The options here are R for Required,
O for Optional and S for Suggested.
 C/S: Is this configuration client-specific (C) or system-
specific (S)? For example, ‘Client sync grouping
exceptions’ and ‘Generate object classes’ are system-
wide but the ‘Optimization program’ needs to be
executed on each client
Please note that the ‘Backend utilities’ feature

does not form part of this appendix and is covered
separately as part of the SAP Fiori and Odata
Services Configuration Guide on Client Central.
Admin Con C/S

Utility OS CS DS SB DD DRd DRt
Folder -fig
Table Client Sync X S S
exceptions grouping
exceptions
Enterprise slice X S S
tables
System Builder X S S
table rules
Num. range Data Insert X O S
handling behavior
Number range X X O C
maintenance
Cleanup & Recommended X X X X S S
Optim. index check
Date slice index X S S
check
Database X X S S
consistency
check
Object Sync X R C
cleanup
Client Sync X R C
cleanup
File explorer X X O S
Clean up X O C
mapping table
Optimization X X X X X X R C
program
HR cluster X X R C
optimizer
Pre-calculate X O C
masked values
Data Disclose X X R C
index run
Object flow X S C
optimization
Pre-system X R S
export
optimization
Admin Utility OS CS DS SB DD DRd DRt Con C/S

Folder -fig
Masking Address X X X X O S
database
Company X X X X O S
database
Person X X X X O S
database
Bus Obj Mapping Editor X O C
maint.
Generate object X X X X X X S S
classes
Generate X S S
Profiles & Grps
Maintain X X X X X O S
Semantic Tags
Audit and Group O C
security Management
Object X X X O C
protection list
Obj protection X X X O C
editor
SAP Auths for X X X X O S
Objects
User X X X X X X X O C
preferences
Sync Audit X O C
Report
Client Sync Index enabler X O S
utilities
Index disabler X O S
Tables for which X O S

secondary
indices can be
removed
Object key X O S
processing
limits

Installation, Control Center and Configuration Guide

Uploaded by

Copyright:

Available Formats

Installation, Control Center and Configuration Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation, Control Center and Configuration Guide

Uploaded by

Copyright:

Available Formats

Installation, Control Center and Configuration Guide

Data Sync Manager™ 5

2. Authorization template roles ............................................................................................................................................... 6

3. Control Center settings .......................................................................................................................................................... 8

4. Administration features ....................................................................................................................................................... 30

6. Accessing support through Client Central .................................................................................................................... 77

Appendix A: Relationships between Administration utilities and DSM products ................................................. 79

1. Getting started with Data Sync Manager

1.2 What is the Control Center?

The transport import order should always be:

 Import Transport Request Again

1.4 Activate your product

To activate Data Sync Manager manually:

1. Click the ‘Client Central’ link in the pop-up window above.

3. In SAP, click the button to upload the license file.

1.5 Name spaces

2. Authorization template roles

1. Access SAP transaction ‘PFCG’.

3. Control Center settings

3.1 Control Center concepts

3.1.1 RFC Types

 Control Center to Control Client Communication (USE_DSM5-<SID>-CC): These RFC

3.1.2 DSM_CONTROL and the DSM_COMM_<SID> users

 DSM/CC/CONTROL_USER_MANUAL_CREATION: This option determines if the control user

 DSM/CC/CONTROL_USER_PROFILE: If this parameter is blank, which is the default value, it will

 DSM/CC/TRANSFER_USER_PROFILE: Similarly to the parameter for the DSM_CONTROL user,

3.2 Control Center configuration

3.2.1 System registration

There are different kinds of systems:

 SAP systems: These are SAP ABAP based systems with

The ‘Allow profile generation’ parameter behaves as follows:

Button Name Description

Expand / Collapse Allows you to collapse or expand the System type

Find / Allows you to search for a specific system in the list.

Add Allows you to add a specific system to the list.

Change Allows you to edit a specific system.

Delete Allows you to delete a specific system.

Reconnect system Reconnect systems when their connection details

Disconnect system Disconnect systems that are no longer available for

Test connection Tests the Control Center connection to the system.

The buttons in this toolbar are defined in the table below:

Button Name Description

Add Allows you to add an Application.

Change Allows you to edit an Application.

Delete Allows you to delete an Application.

3.2.4 System and Client Assignment

Take note that it is also necessary to assign Production system clients.

DSM product settings

3.2.5 Shared folders

3.2.7 Data Disclose client registration

3.2.8 Distribute Configuration

To execute the distribution, click on the button.

The statuses for this function are as follows:

Config out of date, distribution required.

Distributed with errors.

3.2.9 RFC destination (for manual RFC Controllers only)

 Authentication: Connection used to check authorization of user performing a Sync as well as

4.1 Backend Utilities

4.1.1 OData identities

The buttons in this toolbar are defined in the table below: