SAP Accelerated Data Migration

7/27/2019 SAP Accelerated Data Migration

1/19

SAP ADM (SAP Accelerated Data Migration)

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2007 SAP AG 1


Applies to:SAP ADM Package (OSS # 943790)

Summary

This Article describes the features of ADM, Steps to transfer data, and customization of various objects inADM.

Author(s): Anjul Gupta

Company: L & T Infotech Ltd.

Created on: 13 March 2008

Author Bio

Anjul Gupta is a Technical Consultant working with L & T Infotech Ltd, Mumbai, India. Her SAPexperience of over 18 months spans various technologies like ABAP, IS-Utilities.


2/19



2007 SAP AG 2

Table of Contents

Applies to:.............. .......................... ......................... ......................... ................................ ......... 1Summary ........................ ......................... ......................... .......................... ................................ 1

Author Bio.............. .......................... ......................... ......................... .......................... ............... 1Table of Contents............................. .......................... ......................... ......................... ............... 2What is ADM?......... ......................... ......................... .......................... ......................... ............... 4Timeline of ADM Project................................. ......................... ......................... ........................... 5

ADM Roles ......................... .......................... ......................... ......................... ............................ 5ADM Project Administration: ................................................................................ 5ADM Data Manager: ......................................................................................... 6ADM Data User:............................................................................................... 6ADM Administrator:........................................................................................... 6ADM Display User: ........................................................................................... 6

ADM Cockpits.......................... ......................... ......................... .......................... ....................... 6ADM PROCESS COCKPIT:...................... .......................... ......................... ......................... ...... 6

FEATURES OF THE PROCESS COCKPIT:.............................................................6ADM PROCESS COCKPIT -> Project Administration.................................................. 6ADM PROCESS COCKPIT -> Worksteps................................................................ 6

General Settings: ....................... ......................... ......................... ......................... ............... 7Define Scope: ....................... ......................... .......................... ......................... ................... 7Migration Customizing:.........................................................................................................8

ADM PROCESS COCKPIT -> Monitoring: ............................................................... 8Preprocessing:...................... ......................... .......................... ......................... ................... 8Migration Customizing:........................ ......................... ......................... ......................... ...... 9Generate Runtime Objects: ......................... .......................... ......................... ...................... 9Data Import:...................... ......................... ......................... .......................... ..................... 10Postprocessing: ......................... ......................... ......................... ......................... ............. 10Verification:....................... ......................... ......................... .......................... ..................... 11

ADM PROCESS COCKPIT -> Administration ......................................................... 11ADM DEVELOPMENT COCKPIT:........................... ......................... ......................... ................ 11

FEATURES OF THE DEVELOPMENT COCKPIT .................................................... 11ADM DEVELOPMENT COCKPIT -> Monitor:.......................................................... 11

Rule Maintenance: ......................... ......................... .......................... ......................... ........ 11Fixed Value Maintenance........................ ......................... .......................... ........................ 13Control Parameters............................. ......................... ......................... ......................... .... 13Translation Objects: ....................... ......................... .......................... ......................... ........ 14Variable Maintenance: ........................ ......................... ......................... ......................... .... 14

ADM DEVELOPMENT COCKPIT -> WORK STEPS CONVERSION OBJECTS................ 15General Settings: ....................... ......................... ......................... ......................... ............. 15


3/19



2007 SAP AG 3

Recipient Range: ....................... ......................... ......................... .......................... ............ 15Sender Range:...................... ......................... .......................... ......................... ................. 16Define Structure Relations: ......................... .......................... ......................... .................... 16Define field Relations: ........................ .......................... ......................... ......................... .... 17Generate Runtime Object:....................... ......................... .......................... ........................ 17

MAIN STEPS OF AN ADM PROJECT:............................................. ......................... ................ 18ADVANTAGES OF USING ADM:............... ......................... ......................... .......................... ... 18Related Content........................... ......................... .......................... ......................... ................. 18Disclaimer and Liability Notice........................ ......................... .......................... ........................ 19


4/19



2007 SAP AG 4

What is ADM?

SAP offers a new and faster method to migrate data from a legacy system to a SAP system.

1. Need to identify what data needs to be migrated.2. Neutral interstructures called the SII (SAP Intermediate Interface) structures are available for the

migration of the data.

3. Data extracted is checked against the structures to ensure correct data is provided.4. After construction of the data files, it is checked against the predefined business content.5. After completion of all the project steps the data can be imported in mySAP via direct insert per business

object.

ADM Solution Approach


5/19



2007 SAP AG 5

Timeline of ADM Project

The timeline of the ADM project consist of 3 phases:

Phase1: Customization of mySAP system and adaptation of the ADM package.

Phase2:A complete data load is carried out in an iterative manner until all the issues are resolved.

Phase3: Productive Migration occurs in this phase.

ADM Roles

With ADM Package following Roles are delivered:

ADM Project Administration:

The ADM project manager has global authorizations for the project and is responsible for the following:

Create a project

Change a project Delete a project

Monitor a project.


6/19



2007 SAP AG 6

ADM Data Manager:

The ADM data manager has in the process cockpit authorizations for all the treatment steps to becarried out with the conversion objects. The Data Manager has no project authorizations.

Can work within the Process Cockpit

Can work within the Development Cockpit

Needs to have Functional Knowledge of all areas

ADM Data User:

The Data user has no project authorizations and can work within the Process Cockpit.

ADM Administrator:

Job Administrator

Input File coordinator

Delete Function of Imported Data.

Import Protocol Administrator

ADM Display User:

The Display User has only reading access in all the areas of the ADM package.

ADM Cockpits

The work in ADM is carried out in the cockpits viz.

Process Cockpit

Development Cockpit

The Process cockpit is mainly concerned with the execution of the project, and is responsible for the dataimport. The Development Cockpit is concerned with the customization of the Conversion object.

ADM PROCESS COCKPIT:

FEATURES OF THE PROCESS COCKPIT:

Central Component of ADM package to handle the standard business content.

Administrates ADM Projects.

Provides the steps to migrate the business object.

Contains comprehensive log file and error handling.

Has a transparent status overview for each step.

Global Administration Functionality for job handling, log files, data file management.

ADM PROCESS COCKPIT -> Project Administration

The Project Administration activities include

Creating a project.

Assign or change the ADM project.

Delete ADM projects.

ADM PROCESS COCKPIT -> Worksteps

The project worksteps in PROCESS COCKPIT include:


7/19



2007 SAP AG 7

General Settings:

A Short Descript io nof the project.

Copy suf f ixprovides a project-uniform key. It allows a conversion object to exist in parallelin several projects

Maintain the change historyof the project

Root Datapathis maintained when the data to be imported is present on the application

server. The datapath is maintained as ////.

The Run IDis used to distinguish amongst the different data belonging to the sameconversion Object.

Define Scope:

This step allows you to select the conversion object. Also by changing the project template,conversion objects from that template can also be selected. A single project can have multipleconversion objects.


8/19



2007 SAP AG 8

Migration Customizing:

Rules customizing:Contains the rules that need to be checked at the project level.

Fixed Valuessupply values to compulsory fields in case they are blank.

Contro l Parametersare flags with different pre-defined cases for processing.

Translat ion Objectsbelong to a rule and are present only when the rule variant selected isTranslate values. They are used to translate the incoming inputs.

ADM PROCESS COCKPIT -> Monitoring:

These steps are carried out at the conversion object level.

Preprocessing:

It includessteps/preparation that need to be done before data import can be carried out.


9/19



2007 SAP AG 9

Migration Customizing:

Its similar to migration customizing at the project level, except that the settings are valid only at theconversion object level.

Generate Runtime Objects:

The import program is generated in this step. Also XML synchronization and DDIC synchronization takeplace in this step. Before the import program can be generated following steps need to be carried out.

Schema Synchronization: Comparison of the customer XML schema with the sender structures ofmigration workbench.

DDIC Synchronization: The DDIC structures are compared with the receiver structures of the migrationworkbench. (This step is important in case of customized conversion Object)


10/19



2007 SAP AG 10

Data Import:The data can now be imported using the import program, using various options. One can also view the databefore and after conversion.

Postprocessing:

All the steps that need to be carried out for a conversion object after the data import are listed.

Current Status of Runtime Ob ect

Directory of ObjectPreset

Simulate import or Database Update

Restart Ability of the objectValidation against Cust.TablesWrite information for rollback

Option to display data before conversion

Option to display data after conversion


11/19



2007 SAP AG 11

Verification:

The possibilities with which one can carry out an examination of the migrated data are described.

ADM PROCESS COCKPIT -> Administration

The following activities are carried out in the administration of the project.

Administer the data files of the source system. The import protocols are carried out and the import run logs are kept.

Recording the delete functions

ADM DEVELOPMENT COCKPIT:

The development cockpit allows the development of ADM Project. The Conversion Logic at the project levelallows developing the rules at the project level. The development cockpit allows the customization of theConversion object to facilitate the data import as per the business requirements.

FEATURES OF THE DEVELOPMENT COCKPIT

Delete, extend, or change existing rules. Create new migration rules.

Provide all worksteps to change an existing conversion object.

Has status overview for each step.

Where used list of each rule.

ADM DEVELOPMENT COCKPIT -> Monitor:

The monitor for the conversion objects gives information about the status of the single working steps.

Rule Maintenance:

A rule contains pre defined coding around the transmitter fields to adapt it according to the receiver field. Thecontrol-type identifies whether the rule is Process Based or Event Based. The type internal is used onlywhen the rule has more than one export parameter.


12/19



2007 SAP AG 12

Administration:

It gives the following information

Developmen t status:States whether the rule is released, tested. Only a released rule can be used.

Visibi l i ty:Whether the rule is a project rule or whether its only a conversion object level rule.

Rule Category :The rule category identifies the control Type i.e. whether the rule is Event based,

Process based, or Internal. Sort Criterion:States how the rule is sorted in the migration customizing i.e. whether customizing is at

the project level or at the conversion object level.

Change History

Parameters:

It gives the following information:

Name of the impo rt/export p arameter:Each rule has atleast one import/export parameter.

Flow Direct ion: Whether the parameter is an import or export parameter.

Data Type:States the data type of the parameter.

Typing Method:States the typing method of the parameter.

Descr ipt ion:A short description of the parameter.

Variants:

Every rule has atleast one variation. It gives the following information:

Variant:The number of the variant.

Variant Typ e:The variant type has one of the following values!Free Coding :It allows the rule to be coded as per the customer requirements.!Conversion Object :A conversion method is specified for the incoming value.!Fixed Value:At the time of processing, a constant value is transferred.

Descr ipt ion:A short description of the variant.

Object:Used Name of a fixed value or translation object.

Domains/Data elements:If a rule is applicable to various fields having the same DDIC definition, it can be assigned to a data element/domain.

Steps to create a new rule:

From the rule maintenance, click the create rule.

Assign the name for the rule from the customer name space. Also assign a short description for the rule.

Set the control type for the rule.

Define the import and the export parameters.

Set up the variants needed. Also maintain the coding for the same.

Set the development status. At the time of creation of the rule its development is New. The rule needs tobe in released state before it can be used.


13/19



2007 SAP AG 13

Fixed Value Maintenance

Fixed values are used to supply values to compulsory fields in case they are not supplied.

Administration:

Visibi l i ty:Stated whether the fixed value is valid at the project level or the Conversion Object level.

Sort Criterion:Sorting done for Migration Customizing i.e. whether migration customizing relevant orcross application relevant.

Change History

Steps to Create a Fixed Value:

From the Fixed Value Maintenance, click on Create Fixed Value.

Assign the name for the fixed value from the customer name space i.e. beginning with Z. Also enter theshort description of the value.

Assign the format and check the properties.

Check the sort Criterion.

Control Parameters

Control Parameters are flags with different pre defined cases for processing. Often it is a switch with twostates: Yes/No.

Administration:

Visibi l i ty:Stated whether the control parameter is valid at the project level or the Conversion Objectlevel.

Sort Criterion:Sorting done for Migration Customizing i.e. whether migration customizing relevant orcross application relevant.

Change HistoryDefinition

RuleMaintenance

Code area Ofthe Rule


14/19



2007 SAP AG 14

Variant Number and descript ion :The variant and its description are maintained.

Steps to create a control Parameter:

Click Create Control Parameter in the Control Parameter Maintenance.

Assignment of control name has to be respected to the customer name space. Also assign a short

description of the control parameter. Type in the format and check the properties.

Add a new line for each new variant.

Check the sort criterion.

Translation Objects:

The translation objects are used to change the source field values as per the customers specifications. Atranslation object belongs to a rule and has the same name as the rule.

Administration

Opt ions:Using Options it tells the import program how to react if the source field has no values.

E.g. Do not translate initial values or Add the missing values. Error Handl ing:With error handling it is determined how the program should react to such mistakes.

E.g. Set Initial or Use standard Value.

Parameters

Here the input/output parameters for the translation object are defined.

1:1 Conversion

The conversion can be done manually by entering the values or automatically from the excel file or filling thetable by test run.

Steps to create the translation Object

Click Create Translation Object from Translation Object Maintenance.

Assignment of name has to be respected to the customer name space. Select the Conversion Type. Alsoassign a short description of the translation object.

Define the parameters.

Specify the sort criterion i.e. whether customizing is at the project level or at the conversion object level.

Choose the options.

Choose the kind of error handling.

Variable Maintenance:

If a variable is needed many times it can be declared as a global variable in the project and used throughoutthe project.

Administration

Visibi l i ty:The visibility of a variable is usually for the entire project.

Change History

Definition

The variable is defined.


15/19



2007 SAP AG 15

ADM DEVELOPMENT COCKPIT -> WORK STEPS CONVERSION OBJECTS

With the development cockpit, one has the option to create a customized conversion object to suit thebusiness needs. It is created under the project titled SAP_ADM.

Work steps of a conversion object:

General Settings:They define the control settings and the data definitions. It also states the current status of the step.

Administ rat ion!Att r ibutes of the conversion ob ject

It states how the data is updated in the database.

The restart ability decides how after the termination of an import the new restart of the import is to becarried out after the removal of the error.

!Dependencies:All the objects that must be migrated before the current object can be imported arelisted. Also the dependency mode for each dependent object must be specified.

!Chang e History!Processing status:After all the tasks have been completed without error, the statuss set to OK.

Global Data Definit ion :All global data definitions required for the conversion object is done here.

Recipient Range:

The suitable recipient structures are assigned to the conversion object. Usually these are the DDICtables.

The structures must be placed in the right logical hierarchy so that the import program can be correctlygenerated.

There is only a single structure at the top most level.

The hierarchical objects need the foreign key dependency.

It is possible to create user defined structures too.

After the structure has been defined, set the status as done.


16/19



2007 SAP AG 16

Sender Range:

As with the recipient structures, there can only be one structure at the topmost level in the transmitterrange hierarchy.

The Transmitter structure hierarchy must be synchronized with the XSD of the import data files.

After the structure has been defined, set the status as done.

Define Structure Relations:

The relation between the sender and the receiver structures is established.

A sender structure can be related with multiple recipient structures. Similarly a recipient structure can berelated to multiple sender structures.

Also assign, change, or delete a rule at!Start of processin g(What rule should be executed at the beginning of all the data files of a

conversion object)!Start of block(What rule should be executed at the beginning of a data file)!End of block(What rule should be executed at the end of a data file)!End of Processing(What rule should be executed at the end of all the data files of a conversion

object).!To change the rule, click the suitable tabstrip. The coding for a rule can be changed from the variants

tab.

Each recipient structure needs to be adapted for the following:

!Type of Relat ion:It usually is the primary relation with the sender structure. The data is transferred tothe recipient structure only if its a primary relation.

!Cardinal i ty:the cardinality is usually set to 1.

!Data Path Type:Default Path is the first time read of the data of the transmitter structure. SuppressRead: This is helpful when the transmitter structure is related to multiple recipient structures. The datais read only once and further reading of the data is suppressed.


17/19



2007 SAP AG 17

Define field Relations:

It is determined how the fields of the related sending and receiving structures are related.

A set of mapping rules exist which help in the transfer of the values. These rules can be created,changed or deleted.

Control calls are also used.

After all the sender fields have been mapped, set the status.

Field Relations

Generate Runtime Object:

This step is similar to the Generate Runtime Object of the process cockpit.

Assign the XSD schema.

Check for the consistency of the XSD with the sender structure.

Check for the consistency of the DDIC structures with the recipient structures.


18/19



2007 SAP AG 18

MAIN STEPS OF AN ADM PROJECT:

Follow the ADM AuthorizationConcept

Create the ADM Project

Define the project scope. Choose the CO (Conversion Object) from the ADM template or choose the

COs from the other ADM projects.

Carry out the project level migration customizing first.

Adapt the migration customizing for each CO.

Migrate the master data first (especially if you use translation variants for the key fields which are

used in the transaction data objects.

Use less data records during the test phase.

First test the data import in the test mode.

Solve all the errors in the log files of the COs. Execute a full integration migration with all the source data.

ADVANTAGES OF USING ADM:

Fast data migration (can migrate up to 200 terabytes of data in one hour).

XML upload to support large data volume.

Better administration.

Easy and fast mapping of data

Related Content

ADM Weblog

SAP ADM

Regarding ADM


19/19



2007 SAP AG 19

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfacesand therefore is not supported by SAP. Changes made based on this information are not supported and canbe overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methodssuggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content ofthis technical article or code sample, including any liability resulting from incompatibility between the contentwithin this document and the materials and services offered by SAP. You agree that you will not hold, orseek to hold, SAP responsible or liable with respect to the content of this document.

Date post:	14-Apr-2018
Category:	Documents
Upload:	ysrphy
View:	243 times
Download:	6 times

SAP Accelerated Data Migration

Documents