SAP TDMS HCM Configuration Guide

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.
com
2010 SAP AG 1
SAP TDMS HCM Configuration
Guide
Applies to:
SAP TDMS HCM.
Summary
This article provides a step by step guide to configuring and using SAP TDMS for HCM.

Author: Poonam Assudani
Company: SAP Labs India
Created on: 27 September 2010
Author Bio
Poonam Assudani is working with the SAP Labs India for the past 4.5 years .She is
working as Senior Consultant - Development with SAP Landscape Optimization Team.
SAP TDMS HCM Configuration Guide
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 2
Table of Contents
Introduction ......................................................................................................................................................... 3
Overview ............................................................................................................................................................. 3
Customizing steps: ............................................................................................................................................. 5
Related Content ................................................................................................................................................ 10
Copyright........................................................................................................................................................... 11

2010 SAP AG 3
Introduction
This article assumes that the reader has some knowledge of SAP TDMS solution.
The article focuses on configuration settings of SAP TDMS HCM. Here I will explain the maintenance and
usage of the customizing activities for the TDMS HCM.
Overview
TDMS HCM solution helps customer builds a complete HCM test system quickly and efficiently.
The solution also provides scrambling functionality for sensitive HCM data.
Overview of the TDMS HCM components

TDMS for HCM works with three clients:
Sender (system where the data are extracted from)
Receiver (system where the data are transferred to)
Central (control system where the settings are made)
In different steps settings can be made in the control system to identify the data which should be transferred
from the sender to the receiver.
The TDMS Process Tree / Monitor in the central system is the place where all settings are made. It can be
reached via transaction CNV_MBT_TDMS.
Before the data is sent out of the central system it is scrambled using the scrambling engine.
SAP provides scrambling templates for different countries which can be copied and used as per the
requirements. To do so, use transaction CNV_TDMS_HCM_SCRAM - Scramble maintenance.
There are three scenarios (Process types) for HCM TDMS
1. ERP initial package for HCM Personnel Administration (PA)
2. ERP initial package for HCM Personnel Dev PD & PA
3. ERP initial package for HCM Personnel Dev PD & PA-EXPERT
For SAP TDMS HCM there are some of customizing activities that can be maintained one time from an
existing package. These activities are actually independent of the package you use.
2010 SAP AG 4

2010 SAP AG 5
Customizing steps:
1. Exclude Objects from the Transfer

This Customizing option allows you to exclude specific infotypes and subtypes from the transfer. Even if
those infotypes or subtypes are selected in the selection screen of the transfer, they will be not moved to the
receiver client.
In most Customizing settings, you can choose to assign your decisions to a project, a subproject, a package
ID, or sometimes even to a specific user. Wildcards can be used from left to right. More specific settings
have priority over less specific settings.
2. Exclude Organizational Groups from the Transfer

In this customizing activity, you exclude organizational groups, as defined in infotype 0001. You may want to
exclude a specific organizational group from the transfer, and you can do it here by setting a return value of
X.
The values from infotype 0001 may not always be sufficient. In this case, you can include self-written
routines to check whether a particular PERNR should be included or excluded.
Customizing data must be either defined or transported to the sender system. If it cannot be directly
maintained in the sender system with this activity, then you must maintain it using transaction PE03. The
associated feature is TDHC1. Note that a number of fields from infotype 0001 are available in the structure
supplied with this feature.
3. Define Target Areas
2010 SAP AG 6

With this Customizing option, you define key areas in the target system. Typically, you would define
key areas for specific users to prevent users overwriting each other's data.
As mentioned before, settings can also be made on project, subproject, and package level, if this
better fits your requirements.
In addition, you can define a maximum number for each object type to prevent users from
transferring to much data by accident.
Note that for PD objects, you are always required to enter a plan version.
4. Predefine Country-Specific Tables

In this Customizing activity, you define the countries that are valid for a given project, subproject,
and pack ID combination. You need to maintain entries if you plan to transfer PA data that is country-
specific. This data is stored in tables that are neither infotypes nor clusters. The program transfers
the infotypes and clusters, so there is no need to define countries for them.
5. Set Technical Switches
a. PD_NO_EMPTIES
When this switch is defined with the value X, those objects that have no related child objects
will not be copied. For example, if the selection criteria is such that a job is found but there is
no PERNR related to the job, then this job will not be transferred. Without this switch, the job
would be transferred.
b. SND_LOGON
An explicit logon to the sender system will be forced if this switch is set to X. This will occur
only if the sender and control system have differing RFC destinations (different system or
client). When the switch is set, the user must log on first to the control system and then, on
calling the dialog, also log on to the sender system. The sender system user must have
applicable HCM authorizations.
c. SAPGUI_PROGRESS_OFF
2010 SAP AG 7
If this is set to X, the information that is provided during the confirm activity of the selection
criteria definition function will be suppressed. Suppression could result in a slight
performance improvement.
d. NEXT_KEYS_OFF
When this value is set to X, the automatic search for the next free target key area is switched
off. If it is switched off, the user must manually set the target area range for each affected
object type. If the switch is not set and the target area should not be deleted, the program
will search for the next key area within the permitted range into which the selected source
records should be copied. If the target area should be deleted, no search for an available
area is necessary.
e. MULTIPLICATION_ON
When this switch is defined with the value X, an additional parameter appears on the
selection screen of the transfer programs. This parameter enables the user to enter a
multiplication factor.
f. PA_IT0001_OM_FIELDS_CLEAR
When this switch is defined with the value X, the OM-related infotype 0001 fields STELL,
ORGEH, and PLAN are cleared. This applies when the two following conditions are fulfilled:
You are working with the PA process type
You are working with the Expert process type
This does not apply to the PD and PA process type. Here, the fields are never cleared.
g. USE_BEGDA_<Tabname>
There are certain PA tables or clusters that are automatically selected with a date value
using. Apart from these tables and clusters, the data is generally selected and transferred
without any consideration of time.
Certain tables contain data that is not referenced to other tables and can therefore be read
with a date without consideration of any inconsistencies. When such tables are potentially
extremely voluminous they can be defined as exceptions to the general rule and also read
using the Partial _Cuttoff_date.
h. LOGGING_SCRAM_FIELD_DETAIL_OFF
When this switch is defined with the value 'X', then information about the individual fields
that are scrambled is suppressed. You will still be able to see which scrambling groups and
sets were active but the potentially voluminous field information doesn't appear.
1. Define Customer Table Transfer Groups

With this step, you define table groups or categories. You can assign tables to these groups or categories.
This allows you to transfer your own tables without any extra programming.
The tables in these groups are not infotypes or cluster tables. The program can automatically transfer
infotypes and cluster tables.
2. Define Customer Tables for Transfer Groups
2010 SAP AG 8

In this task, you define tables, which you then assign to groups or categories. This allows you to transfer your
own client-dependent tables without any extra programming.
Note that assignment to these groups is not required for infotypes or cluster tables. The program
automatically transfers infotypes and cluster tables.
If you want to include a development class that contains infotypes, use the exclude option at table level to
exclude them.
3. Table Transfer Status

All data that is transferred needs to be registered in the table called by this activity. SAP provides the initial
entries.
When you define new entries like own-defined infotypes or clusters, you must add them to the table. Once
they have been added, they need to be checked in the Inc/Exc box; otherwise, they could not be part of any
transfer.
If there is no entry for a table, then the transfer program does not copy it. In this case, a warning message is
written to the log. If an entry in the table does not have a set Include / Exclude value, the transfer does not
occur and there is no warning message.
4. Define Non-Payroll Clusters

Clusters can be divided into payroll clusters and others. This distinction is made because SAP treats payroll
clusters differently. Payroll clusters have special ABAP Dictionary definitions, and special function modules
to import and export them.
2010 SAP AG 9
The other SAP and customer clusters have macros and are composed of structures that are related to
dictionary objects, but you need to define these for the transfer program if scrambling is to occur. The SAP
standard clusters are included in the software, and you can add your own if required.
2010 SAP AG 10
Related Content
1. http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/20463
2. http://service.sap.com/tdms
2010 SAP AG 11
Copyright
Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP TDMS HCM Configuration Guide

Uploaded by

Document Information

Original Title

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

SAP TDMS HCM Configuration Guide

Uploaded by

Copyright:

Available Formats

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.

You might also like