t Dms Release Note

Published on December 2016 | Categories: Documents | Downloads: 32 | Comments: 0 | Views: 273
of 42
Download PDF   Embed   Report

t Dms Release Note

Comments

Content

SAP Test Data Migration Server
Release Note September 2011

Agenda

1. Value Proposition: Why Should a Customer Choose 4.0
2. SAP TDMS 4.0: A Summary of New Features 3. Upgrade from SAP TDMS 3.0 to SAP TDMS 4.0 4. SAP TDMS for the Business Suite 5. SAP TDMS for Industry Solutions 6. Data Scrambling 7. Business Process Library 8. Data Transfer Through Files 9. Full Transfer of Client-Specific Data

10. Enhancements for SAP ERP HCM
11. Web Interfaces 12. Integration with SAP Solution Manager 13. Technical Prerequisites
© 2011 SAP AG. All rights reserved. 2

Value Proposition

Value Proposition of SAP TDMS 4.0
Expansion of existing migration requirements across SAP Business Suite components Consistency of business processes across SAP Business Suite components

Easy-to-use interfaces for business users
Special migration solutions for certain industry solutions Focus on the overall test system landscape creation Closer integration with SAP Solution Manager Easy upgrade from Release 3.0 to Release 4.0 Compliance with data privacy laws by providing a one-stop scrambling workbench.
© 2011 SAP AG. All rights reserved. 4

A Summary of New Features

SAP TDMS 4.0: A Summary of New Features

New Features with TDMS 4.0: SAP Solutions Available with SAP TDMS Classic: ERP, BW, CRM, HCM Industry-Specific Solutions Available with SAP TDMS: Apparel & Footwear (AFS) Discrete Industries & Mill Products (DIMP) Healthcare Retail (Time-Based Selection) Business Process Library (BPL) 2007 2008 SAP Solutions Available with SAP TDMS Classic:
SCM, SRM

Industry-Specific Solutions Available with SAP TDMS:
Banking, Oil & Gas, Retail (Store-Based Selection), Utilities

Feature-Rich Data Scrambling Integration with SAP Solution Manager

User-Friendly Work Centers
BPL Modeler Data Transfer Through Files for SAP ERP Full Transfer of Client-Specific Data

Data Scrambling Workbench This document contains intended strategies, developments and/or functionality and is not
intended to be binding upon SAP to any particular course of business, product strategy and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

Upgrade to SAP TDMS 4.0

Upgrade 3.0 -> 4.0

Upgrade of the standard software without any custom
changes
Any standard customizing such as new migration objects, new selection groups and so on are retained after the upgrade. Existing projects and migration packages cannot be used after the upgrade. With SAP TDMS 4.0, the TDMS control system is required to be on SAP NetWeaver Release 7.0 or above. If the existing control system is on a lower release, carry out one of the following actions: Upgrade the SAP NetWeaver Release of the control system to 7.0 or above Migrate all TDMS data from the control system to any system having SAP NetWeaver Release 7.0 or above and use the new system as the control system.

Control System Release Requirement
-

Upgrade impact on Data Scrambling
Your can manually recreate your custom scrambling rules from Release 3.0 to Release 4.0 by using the new scrambling workbench.

© 2011 SAP AG. All rights reserved.

8

Upgrade 3.0 -> 4.0

Upgrade impact on Business Process Library (BPL) in SAP
TDMS
A new and easy-to-use BPL Modeler is now available for business processspecific transfer. Any customizing that you did in SAP TDMS 3.0 must be

Upgrade impact on early shipment

manually redone for SAP TDMS 4.0.

of SAP TDMS 4.0 for SAP

Utilities, SAP Retail, and SAP Banking
Any standard customizing such as new migration objects, new selection groups and so on are retained after the upgrade. Existing projects and migration packages cannot be used after the upgrade.

© 2011 SAP AG. All rights reserved.

9

SAP TDMS for the Business Suite

SAP TDMS for the Business Suite (1/2)
Delta 3.0 -> 4.0
ERP
Time-Based Reduction Company Code and Time-Based Reduction Transfer of Master Data and Customizing System Shell Creation

HCM
Transfer of Personnel Administration (PA) Data Transfer of PA and Organization Management Data File-Based Transfer Scrambling - 33 countries content HCM Authorization

BI

CRM

Time-Based Reduction
Transfer of Master Data and customizing System Shell Creation PSA Data Eliminated

Time-Based Reduction Transfer of Master Data and Customizing System Shell Creation Mobile Clients Deploy SAP TDMS

Business Process Library
Full Client Transfer

Scrambling Only
Data Transfer Through Files Extension for EHPs BPL Modeler

Full Client Transfer E-Recruitment Process and Forms Extension for EHPs

Specific Data Slice Date for Individual InfoAreas
Extension for EHPs

Full Client Transfer Extension for EHPs Consistency with ECC system

New UI, Scrambling, Solution Manager Integration
© 2011 SAP AG. All rights reserved. 11

TDMS for Business Suite (2/2)
Delta 3.0 -> 4.0
SCM SRM

Time-Based Reduction System Shell Creation Full client transfer SAP liveCache reduced by date and planning version Demand Planning for BW

Time-Based Reduction Transfer of Master Data and Customizing System Shell Creation Full client transfer Consistentency in Document Flow

New UI, Scrambling, Solution Manager Integration
© 2011 SAP AG. All rights reserved. 12

SAP TDMS for Industry Solutions

Data Extraction Modes for Industry Solutions
 Horizontal Approach: Represents the TDMS time slice throughout the system
Time Slice

Data Volume

Examples •ERP Time-based reduction •BI Time based reduction

 Vertical Approach: Represents an objectoriented extraction with complete history
Object-Oriented

time

Business objects such as: •Business Partners •Plant/Retail stores

time
Data Volume
© 2011 SAP AG. All rights reserved.

14

SAP TDMS – Industry Solutions with Horizontal Extraction
Industry Solutions with time slice extraction: IS data for the following solutions is extracted based on the specified data slice date.

© 2011 SAP AG. All rights reserved.

15

SAP TDMS for Industry Solutions: Combined Horizontal and Vertical Extraction
Extraction of industry specific data based on specified business objects and extraction of other data based on a time slice.

Object-Oriented

Time
Data Volume

Goal: Best of both – a combination of horizontal and vertical extraction approaches
© 2011 SAP AG. All rights reserved. 16

SAP TDMS for IS: Business Objects Available for Selection

© 2011 SAP AG. All rights reserved.

17

Data Scrambling

Data Scrambling: New Look
Reasons for Enhancements
Compliance with data privacy laws to protect sensitive data before data leaves the production system. Additional ready-to-use content for scrambling. Scrambling platform with a user-friendly interface that can be used to scramble standard and custom data across different SAP applications.  Scrambling of data in a specific client without data transfer across systems.

New Look TDMS
Stand-alone scrambling Scrambling workbench: One UI for all scrambling needs Integration in TDMS migration projects and packages  Ready-to-use scrambling content for customer number, vendor number, material number, address and HCM data.

© 2011 SAP AG. All rights reserved.

19

Stand-Alone Scrambling
Description
A new feature that enables you to scramble data in a client without data transfer.

Advantages
You

can define scrambling rules, create content, and reuse standard content for all scrambling needs.
You

can integrate the scrambling rules with any TDMS migration solution. process tree. and modification of scrambling rules for specific projects and packages.

Compact Definition

© 2011 SAP AG. All rights reserved.

20

Scrambling Workbench: One UI for All Scrambling Customizing
Description
Easy-to-use interface to create, copy or change scrambling rules. The customizing can be used by both Stand-Alone scrambling and all migration solutions with data transfer

Advantages
You

can define new rules for standard and custom tables and re-use existing can define scrambling rules for table fields or domains. mapping types are available. Examples:
Selection Table with 1 Column Selection Table with 2 Columns

rules
You

Several

Random Random Value Fixed

Range Table Value Conversion
21

Number

© 2011 SAP AG. All rights reserved.

Scrambling Workbench: Integration with Project and Package
You

can easily access the scrambling rules created in the scrambling workbench from your TDMS project. You can copy the rules to the project and make changes according to your specific project requirements.
TDMS

automatically copies the scrambling rules defined at the project-level to the migration packages in the project. You can carry out package- specific changes using the scrambling workbench. This will not impact other packages in the same project.
Customizing

at different levels helps in reuse across projects and packages. At the same time, it helps to maintain application-specific customizing.

© 2011 SAP AG. All rights reserved.

22

Business Process Library

Business Process Library
Business Process Library Modeler
Business Process Library Modeler to maintain and depict the relationship and attributes of a Business object and its entities About 80 standard business objects and sub objects in ERP delivered with TDMS 4.0. The objects are classified as master data, transactional data and process data You can copy the standard business objects and add custom tables to them.  You can create custom business objects You can specify your data selection (delimitation) parameters by copying standard business objects and modifying the active fields. You can deactivate certain subobjects within business objects.

© 2011 SAP AG. All rights reserved.

24

Business Process Library
Integration
User-friendly Packages New

interface for assigning the data selection criteria in the project

can be executed several times for different selection criteria

scrambling features fully integrated steps in the process tree

Fewer

© 2011 SAP AG. All rights reserved.

25

Full Transfer of ClientSpecific Data

Full Transfer of Client-Specific Data
Client-specific 

data is transferred without any reduction

The following data is excluded from transfer:
 Change Documents  SAP Business Workflow items  User Data  ArchiveLinks  Authorization  Roles  Business Workplace  Variants

High

performance system name assignment in receiver system is included

Logical

© 2011 SAP AG. All rights reserved.

27

Data Transfer Through Files for SAP ERP

Overview of File-Based Transfer
File

transfer is different from standard TDMS packages as it does not require the RFC destinations to all the involved system


File transfer enhance the flexibility of multiple import of test data without additional load on source system
TDMS Data Extract Export Package
(no connection to Receiver)
RFC

S

P C
Data extract

File system

R

TDMS Data Extract Import Package TDMS Data Extract Import Package RFC RFC TDMS DataP’ Extract Import Package

Data Extract

S’

RFC

S’

S’

P’ RFC C’ P’ C’ C’

RFC

R

RFC

R

R



File-Based Transfer, separate Data Selection and Data Transfer process by introducing  An Export Package - Standard TDMS Package without receiver related actions  An Import Package – Allows a data transfer to selected receiver system
S :Sender System P: Control System C: Central System S’ : Virtual Sender System P’: Control System C’: Central System R: Receiver System
© 2011 SAP AG. All rights reserved. 29

Enhancements for SAP ERP HCM

Enhancements in SAP TDMS 4.0


E-Recruiting Data

Transfer of internal and external candidates information along with erecruiting objects like requisition, job posing, application, candidacy, talent group and, support group. Selection can be done based on personnel number, e-recruiting objects or, PD objects like position, organizational unit and, so on. Internal and external candidate multiplication can be done for the load testing


Processes and Forms

Transfer of HCM processes along with the PDF form content Scrambling of the form content can be done Personnel administration and organization related processes can be transferred

© 2011 SAP AG. All rights reserved.

31

Object Selection Method
 

Selection can be done based on complex business criteria.

Selection can be defined in a separate transaction by HR administrators instead of TDMS experts.


The list of objects and relations obtained from such a selection can be used in multiple transfers.


Standard SAP HCM authorizations are active for selection of objects plus additional authorization checks to control access to transaction.
Reports

Comparison of time evaluation results (Cluster B2) between personnel numbers can be done within the same system or with the remote system .

It’s also possible to store the time evaluation results in the TDMS cluster for the comparison e.g. Results before applying SP and after applying SP for the same personnel number.
Comparison can also be done using the TDMS package
© 2011 SAP AG. All rights reserved. 32

Work Centers

SAP TDMS Work Centers at a Glance Central Access to All SAP TDMS Functions
Portfolio
SAP TDMS Control Center
 Includes all available migration solution(s) structured by typical migration requirements



Project Template

 Includes all selected migration solution(s) to be used in one or multiple projects such as TimeBased Reduction for different applications 

Projects
 Provide guidance during the entire execution phase  Manage and control the technical execution of a migration project

In addition, the Help Center and Related Links areas are also accessible from the entry screen of the SAP TDMS control center.
© 2011 SAP AG. All rights reserved. 34

SAP TDMS Software: Project Execution
TDMS Landscape

Portfolio Project Template Project

Sender System

Central System

Receiver System
© 2011 SAP AG. All rights reserved. 35

Integration with SAP Solution Manager

Integration with Solution Manager

SAP

Solution Manager can be used as the central system or the control system for SAP TDMS.
RFC

destinations defined using SMSY transaction can be referred in the system landscape workcenter.

© 2011 SAP AG. All rights reserved.

37

Technical Prerequisites

SAP TDMS software: Software Components and Supported Releases
SAP TDMS – Control/Central System (Netweaver – 7.0x - 731) Execution Systems ( Release 4.7 – 731)

DMIS_CONT 2011 DMIS 2011 SAP_ABA SAP_BASIS
AddOn 620 640 700(incl. 01,02,03)

DMIS_CONT 2011

DMIS 2011 SAP_ABA
SAP_BASIS
710 730 731

DMIS_2011

2011_1_620

2011_1_640

2011_1_700

2011_1_710

2011_1_730

2011_1_731

DMIS_CONT _2011

2011_1_620

2011_1_640

2011_1_700

2011_1_710

2011_1_730

2011_1_731
39

© 2011 SAP AG. All rights reserved.

Application Releases Supported
Applications
SAP ERP

Required Release
SAP R/3 Enterprise 4.7 or above; SAP Basis Releases 6.20, 6.40, or 7.00

SAP ERP HCM SAP CRM SAP SCM

SAP HCM 4.7 or above SAP Basis Release 7.00 or above and SAP CRM 7.0 or above SAP SCM 7.0 or above; SAP Basis Release: 6.20, 6.40, or 7.00

SAP SRM Banking (Loans and Deposits) Oil & Gas (Downstream) Utilities CRM for Utilities Retail SAP NetWeaver BW SAP GTS

SAP SRM 7.0 or above SAP Banking 6.0, or 7.0, or above SAP Oil & Gas 4.72 or above SAP Utilities 4.72 or above SAP CRM 6.0 or above SAP Retail 6.0 or above SAP NetWeaver BW 7.0 or above (including 7.3) SAP GTS 8.0 or above

© 2011 SAP AG. All rights reserved.

40

Thank You!
Contact information: SS Malthi TDMS Product Management [email protected]

Legal Disclaimer

This presentation outlines our general product direction and should not be relied upon in
making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this

presentation. This presentation and SAP's strategy and possible future developments are
subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a

particular purpose, or non-infringement. SAP assumes no responsibility for errors or
omissions in this document, except if such damages were caused by SAP intentionally or gross negligence.

© 2011 SAP AG. All rights reserved.

42

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close