Summary
This Article describes the features of ADM, Steps to transfer data, and customization of various objects in ADM. 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 SAP experience of over 18 months spans various technologies like ABAP, IS-Utilities.
Table of Contents
Applies to:................................................................................................................................... 1 Summary .................................................................................................................................... 1 Author Bio................................................................................................................................... 1 Table of Contents........................................................................................................................ 2 What is ADM?............................................................................................................................. 4 Timeline of ADM Project.............................................................................................................. 5 ADM Roles ................................................................................................................................. 5 ADM Project Administration: ................................................................................ 5 ADM Data Manager: ......................................................................................... 6 ADM Data User:............................................................................................... 6 ADM Administrator: ........................................................................................... 6 ADM Display User: ........................................................................................... 6 ADM Cockpits ............................................................................................................................. 6 ADM PROCESS COCKPIT: ........................................................................................................ 6 FEATURES OF THE PROCESS COCKPIT: ............................................................. 6 ADM PROCESS COCKPIT -> Project Administration .................................................. 6 ADM PROCESS COCKPIT -> Worksteps ................................................................ 6 General Settings: ................................................................................................................. 7 Define Scope: ...................................................................................................................... 7 Migration Customizing:......................................................................................................... 8 ADM PROCESS COCKPIT -> Monitoring: ............................................................... 8 Preprocessing: ..................................................................................................................... 8 Migration Customizing:......................................................................................................... 9 Generate Runtime Objects: .................................................................................................. 9 Data Import: ....................................................................................................................... 10 Postprocessing: ................................................................................................................. 10 Verification: ........................................................................................................................ 11 ADM PROCESS COCKPIT -> Administration ......................................................... 11 ADM DEVELOPMENT COCKPIT:............................................................................................. 11 FEATURES OF THE DEVELOPMENT COCKPIT .................................................... 11 ADM DEVELOPMENT COCKPIT -> Monitor:.......................................................... 11 Rule Maintenance: ............................................................................................................. 11 Fixed Value Maintenance ................................................................................................... 13 Control Parameters ............................................................................................................ 13 Translation Objects: ........................................................................................................... 14 Variable Maintenance: ....................................................................................................... 14 ADM DEVELOPMENT COCKPIT -> WORK STEPS CONVERSION OBJECTS ................ 15 General Settings: ............................................................................................................... 15
SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 2
Recipient Range: ............................................................................................................... 15 Sender Range:................................................................................................................... 16 Define Structure Relations: ................................................................................................ 16 Define field Relations: ........................................................................................................ 17 Generate Runtime Object:.................................................................................................. 17 MAIN STEPS OF AN ADM PROJECT:...................................................................................... 18 ADVANTAGES OF USING ADM: .............................................................................................. 18 Related Content ........................................................................................................................ 18 Disclaimer and Liability Notice................................................................................................... 19
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.
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.
ADM Data Manager: The ADM data manager has in the process cockpit authorizations for all the treatment steps to be carried 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 data import. The Development Cockpit is concerned with the customization of the Conversion object.
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:
General Settings: A Short Description of the project. Copy suffix provides a project-uniform key. It allows a conversion object to exist in parallel in several projects Maintain the change history of the project Root Datapath is maintained when the data to be imported is present on the application server. The datapath is maintained as <Datapath>/<Name of project>/<Name of subproject>/<Name of Conversion object>/<Run ID>. The Run ID is used to distinguish amongst the different data belonging to the same conversion 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 multiple conversion objects.
Migration Customizing: Rules customizing: Contains the rules that need to be checked at the project level. Fixed Values supply values to compulsory fields in case they are blank. Control Parameters are flags with different pre-defined cases for processing. Translation Objects belong to a rule and are present only when the rule variant selected is Translate 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 includes steps/preparation that need to be done before data import can be carried out.
Migration Customizing: Its similar to migration customizing at the project level, except that the settings are valid only at the conversion object level.
Generate Runtime Objects: The import program is generated in this step. Also XML synchronization and DDIC synchronization take place 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 of migration workbench. DDIC Synchronization: The DDIC structures are compared with the receiver structures of the migration workbench. (This step is important in case of customized conversion Object)
Data Import: The data can now be imported using the import program, using various options. One can also view the data before and after conversion.
Preset Simulate import or Database Update Restart Ability of the object Validation against Cust.Tables Write information for rollback Option to display data before conversion Option to display data after conversion
Directory of Object
Postprocessing: All the steps that need to be carried out for a conversion object after the data import are listed.
SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 10
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 -> 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. The control-type identifies whether the rule is Process Based or Event Based. The type internal is used only when the rule has more than one export parameter.
Administration: It gives the following information Development status: States whether the rule is released, tested. Only a released rule can be used. Visibility: 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 import/export parameter: Each rule has atleast one import/export parameter. Flow Direction: 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. Description: 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 Type: 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. Description: 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 to be in released state before it can be used.
Rule Maintenance
Fixed Value Maintenance Fixed values are used to supply values to compulsory fields in case they are not supplied. Administration: Visibility: 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 or cross 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 the short 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 two states: Yes/No. Administration: Visibility: Stated whether the control parameter is valid at the project level or the Conversion Object level. Sort Criterion: Sorting done for Migration Customizing i.e. whether migration customizing relevant or cross application relevant. Change History Definition
SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 13
Variant Number and description: 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. A translation object belongs to a rule and has the same name as the rule. Administration Options: 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 Handling: 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 the table 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. Also assign 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 throughout the project. Administration Visibility: The visibility of a variable is usually for the entire project. Change History Definition The variable is defined.
ADM DEVELOPMENT COCKPIT -> WORK STEPS CONVERSION OBJECTS With the development cockpit, one has the option to create a customized conversion object to suit the business 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. Administration ! Attributes of the conversion object 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 be carried out after the removal of the error. ! Dependencies: All the objects that must be migrated before the current object can be imported are listed. Also the dependency mode for each dependent object must be specified. ! Change History ! Processing status: After all the tasks have been completed without error, the statuss set to OK. Global Data Definition: 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 DDIC tables. The structures must be placed in the right logical hierarchy so that the import program can be correctly generated. 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.
Sender Range: As with the recipient structures, there can only be one structure at the topmost level in the transmitter range 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 be related to multiple sender structures. Also assign, change, or delete a rule at ! Start of processing (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 Relation: It usually is the primary relation with the sender structure. The data is transferred to the recipient structure only if its a primary relation. ! Cardinality: the cardinality is usually set to 1. ! Data Path Type: Default Path is the first time read of the data of the transmitter structure. Suppress Read: This is helpful when the transmitter structure is related to multiple recipient structures. The data is read only once and further reading of the data is suppressed.
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.
Related Content
ADM Weblog SAP ADM Regarding ADM