«How to Scramble Data Using SAP Test Data Migration Server Release 4.0 Typographic Conventions Type Style Description Example Words or characters ...»
How-To Guide CUSTOMER
Document Version: 1.5 – 2015-12-28
How to Scramble Data Using SAP Test Data
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions.
Technical names of system objects. These include report names, program names,
EXAMPLEtransaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.
Output on the screen. This includes file and directory names and their paths, messages, Example names of variables and parameters, source text, and names of installation, upgrade and database tools.
Exact user entry. These are words or characters that you enter in the system exactly as Example they appear in the documentation.
Variable user entry. Angle brackets indicate that you replace these words and characters Example with appropriate entries to make entries in the system.
Keys on the keyboard, for example, F 2 or E N T E R.
1.5 December 2015 Updates to Custom Mapping (Section 9.1.9) How to Scramble Data Using SAP Test Data Migration Server Error! Reference source not found.
Document History © 2012 SAP AG. All rights reserved. 3 Table of Contents 1 Business Scenario
2 Getting Started
2.1 Navigating to the TDMS Work Center
2.2 Roles and Authorizations
2.3 System Landscape for Data Scrambling
2.3.1 Scrambling System Requirements
2.3.2 Landscape for the Stand-Alone Scrambling Scenario
2.3.3 Landscape for Scrambling During Data Transfer
2.3.4 Landscape for Stand-Alone Conversion Package
2.4 Taking the First Steps
3 Scrambling Objects
3.1 Solution Category
3.2 Scrambling Supergroups and Scrambling Groups
3.3 Scrambling Rules
3.4 Global Mapping
4 Stand-Alone Scrambling
5 Scrambling During Data Transfer
6 Stand-Alone Conversion
7 Working with Standard Scrambling Content
7.1 Preparing the Ready-to-Use Content
7.1.1 Ready-to-Use Standard Content from SAP TDMS
8 Working with Custom Requirements
8.1 Understanding the Process Flow Graphically
8.2 Working with Multiple Product Levels
8.3 Working with the User Interface to Create Scrambling Objects
8.4 Working with the Solution Category
8.4.1 Creating a Solution Category
8.4.2 Assigning the TDMS Migration Solution to a Solution Category (Required)................. 30
8.5 Working with the Scrambling Supergroup
8.6 Working with the Scrambling Group
8.7 Copying a Scrambling Rule
9 Working with Scrambling Rules
9.1 Creating Rules in the Standard Mode
9.1.1 Step One: Adding a Scrambling Type (Required)
9.1.2 Delete Value
9.1.3 Fixed Value
Error! Reference source not found. How to Scramble Data Using SAP Test Data Migration Server
4 © 2012 SAP AG. All rights reserved. Table of Contents9.1.4 Manual 1 to 1 Mapping
9.1.5 Number Conversion
9.1.6 Random Table with One Column
9.1.7 Value Range Table
9.1.8 Random Table for Time Periods
9.1.9 Custom Mapping
9.1.10 Step Two: Adding Table-Field Combinations (Required)
9.1.11 Step Three: Setting the Primary Table-Field (Required)
9.1.12 Step Four: Using a Key-Set
9.1.13 Step Five: Using a Domain
9.2 Additional Features in the Expert Mode
9.2.1 Step Six: Assigning Routine Names
9.2.2 Step Seven: Assigning Includes
9.2.3 Step Eight: Using the Identifier and Scrambling Function Modules
9.2.4 Step Nine: Using Condition-Sets
10 Consistent Scrambling of Data
11 Additional Features in the Scrambling Workbench
11.1 Validation Feature for Scrambling Rules
11.2 Simulation for Scrambling Rules
11.3 Search Feature for Scrambling Rules
11.4 Import-Export of Data from Files for Manual 1:1 Mapping
11.4.2 Exporting Data to the.CSV File
11.4.3 Importing the Mapping Values to a Scrambling Rule
12 Using Scrambling Objects at the Project and Package Levels
12.1 Copy Option at Project Level
12.2 Activating Scrambling Customizing at Project Level
12.3 Copy Option at the Migration Package Level
12.4 Activating Scrambling Customizing at the Migration Package Level
13 Example Rule Creation
15.1 Types of Data that Can Be Scrambled
15.2 Solution Category
15.3 Scrambling Rules: Basic Technical Information
15.4 Scrambling Rules: Condition Sets
15.5 Scrambling Rules: Expert Technical Information
16 The Scrambling Configuration After Upgrade Tool
Your organization has a lot of sensitive data in the systems and you want to scramble the data before making it available to testers, developers, and others.
You can use SAP TDMS 4.0 to make this possible by scrambling data before making it available in the nonproduction system.
Note Data scrambling does not scramble the actual data residing in the production system.
You can scramble data in the following contexts:
Stand-Alone Scrambling: You can scramble data residing in a particular system using this scenario.
Typically, you have set up your non-production system with data copied from the production system or a quality system. You want to scramble the data to prevent the developers and testers from viewing the original data of the production system.
Scrambling During Data Transfer: You can scramble data selected for transfer across systems by SAP TDMS.
SAP TDMS selects the data for transfer and stores it in a temporary cluster in the sender system. SAP TDMS next scrambles the data in the cluster before transferring it to the receiver system.
Stand-Alone Conversion: You have built a test system by copying the data from the production system or a quality system. During the copy, the production system name is also copied to the test system. To uniquely identify the test system, you want to rename the logical system name of the test system.
You can rename the logical system names residing in the test system to your preferred list of names.
You can use the stand-alone conversion as an advanced parallel processing technique that serves as an alternative to BDLS - the standard system copy process for logical system rename.
Method 1 Install the SAP NetWeaver Business Client 3.5 or 4.0. 1.
To add your system to the NWBC, enter the following information:
System name URL for the system System type Client Language You can get this information from the transaction TDMS_CFGCHK in your SAP Solution Manager system. After you enter the transaction, select your NWBC version and execute to view the system information.
Add your SAP logon system to your SAP logon pad by entering the following information:
System ID Message server URL group 1.server System number Use transaction TDMS to enter the TDMS work center.
Assign appropriate roles to your users from among these roles:
SAP_TDMS_SCRAMBLING_DISPL A user with this role only has Display authorizations for scrambling objects.
SAP_TDMS_SCRAMBLING_ADMIN A user with this role has Create and Edit authorizations.
This role is a part of the composite role SAP_TDMS_MASTER_CR.
SAP_TDMS_SCRAMBLING_USER How to Scramble Data Using SAP Test Data Migration Server Getting Started © 2012 SAP AG. All rights reserved. 7 A user with this role has Copy and Activate authorizations for the scrambling objects created at the package level.
This role is a part of the composite role SAP_TDMS_TECH_EXECUTION_USER.
SAP_TDMS_SCRAMBLING_EXPERT A user with this role has Copy and Activate authorizations for scrambling objects created at both the project and package levels.
This role is a part of the composite role SAP_TDMS_TECH_EXECUTION_EXPERT.
SAP_TDMS_SCRAMBLING_BUS_EXPERT A user with this role has Create, Change, Display, Copy, and Activate authorizations for all scrambling objects created at both the project and package levels.
This role is a part of the composite role SAP_TDMS_BUSINESS_EXPERT.
SAP_SLOP_MASTER This rule should be assigned to the RFC user that is used in the RFC connection.
2.3 System Landscape for Data Scrambling This section describes the system landscape requirements for the scrambling scenarios.
For information about the system landscape for SAP TDMS, see the Master Guide for SAP TDMS 4.0 on SAP Service.Marketplace at http://service.sap.com/tdms.
2.3.1 Scrambling System Requirements For information about the scrambling system requirements, see the landscape requirements outlined in the Master Guide for SAP TDMS and the detailed information in the Operations Guide for SAP TDMS on SAP Service Marketplace at http://service.sap.com/tdms.
For the Execution System:
You have installed SAP Basis Release 620 or above.
2.3.2 Landscape for the Stand-Alone Scrambling Scenario This figure shows a typical landscape and communication flow among the systems in a stand-alone scrambling scenario.
Figure 1: System landscape for the stand-alone scrambling scenario Control System All TDMS scrambling-specific settings and customizing are stored in this system. This system triggers and monitors the activities in the process tree.
Execution System The execution system is a non-production system that has already been set up using a client copy, system copy, or SAP TDMS (without scrambling). This is the system where you would like to scramble the sensitive content before users can handle the data.
Sender System This supplies data to the non-production system that you want to set up using SAP TDMS. The sender system is usually a production system. SAP TDMS selects data from the sender system based on your selection criteria and stores the data in a cluster table in the sender system. Before transfer, SAP TDMS reads the data from this cluster table, scrambles the data, and stores the data in the same cluster table. During transfer, SAP TDMS transfers the scrambled content to the receiver system.
Receiver System This is the target system in the SAP TDMS data migration process.
SAP TDMS transfers the scrambled data from the sender system to the receiver system.
The TDMS Server Control System: All TDMS-specific settings and Customizing are stored in the control system. The control system triggers the TDMS activities in the process tree.
Central System: The back-end processing for data migration takes place in the central system.
2.3.4 Landscape for Stand-Alone Conversion Package For information about the landscape for Logical System Rename package, take a look at Section 2.2.2 Landscape for the Stand-Alone Scrambling scenario.
We provide you with a scrambling workbench to design and develop the objects to scramble data. This workbench is used across all applications running SAP TDMS and can be accessed through the TDMS work center under the transaction TDMS. Navigate to the Data Scrambling Workbench from the TDMS Work center.
To start using TDMS Scrambling, copy the scrambling content we deliver to your work center by choosing the Copy from Template pushbutton. During the first run, this option copies the objects provided by SAP to the work center.
After you copy the initial content from the template to the work center, you can copy any additional content
available with support packages using these copy options:
Copy Enhanced Scrambling Objects: Copies an enhancement provided by SAP but not yet available with the customers.
Append Scrambling Objects: Appends the scrambling objects delivered by SAP to the work center.
SAP TDMS provides standard scrambling content so that you can carry out data scrambling. If you find that you
need additional content, you can define the following TDMS scrambling objects:
Solution Category Supergroup Group Scrambling Rule Global Mapping Keep reading for a detailed description of each scrambling object.
3.1 Solution Category
You can use the solution categories to group scrambling objects (groups, rules and mappings) according to specific TDMS migration solutions (TDMS packages). The Master Guide for SAP TDMS 4.0 contains more information about TDMS migration solutions. You can find it in the SAP Service Marketplace at http://service.sap.com.tdms.
Example If, for example, you want to scramble vendor names (Table LFA1 Field NAME1) in the SAP ERP application, SAP TDMS provides the solution category SAP_ERP that groups all the TDMS ERP migration solutions.