SAP TDMS System Shell creation

Hello,
I am new to SAP TDMS. I want to know about System shell creation.
Is System shell used to create a totally "new system" or can it be done on an existing system? Can it be done on an existing system by using a separate client??
If we use existing system what happens to its already present data. As per the Operations guide it says we need to do a Homogeneous system copy by using TDMS tools.This will delete the data in existing system.So does it mean all database content will be deleted or only the client specific data?
Many Thanks.
Ravindra

You can get more details  from the following documents:
Operations Guide
http://service.sap.com/instguides -> SAP Components -> SAP Test Data Migration Server -> TDMS 3.0
Security Guide
http://service.sap.com/security -> Security in Detail -> SAP Security Guides -> SAP Test Data Migration Server

Similar Messages

  • Shell Creation does also copie : Job's; Work flow ...

    Hi all
    We will do a shell creation to manage our Development system ( like kill all old rubbish ).
    my question we will do a shell creation from our Productive system
    Shell Creation does also copies follows:
    JOB's -> if no we have 400 Jobs how could i copies these to our "new" System
    Work flow / Plan version ->if no what could i do?
    Code Inspector ->if no what could i do?
    Variants -> if no i could transport wit the report for export Variant ( OSS )
    ABAP    Version i know its not transported we have to export but know SAP if we import the Version file that some ABAPs miss ( because we don't want )
    Thanks in Advance
    Lou

    > Shell Creation does also copies follows:
    > JOB's -> if no we have 400 Jobs how could i copies these to our "new" System
    > Work flow / Plan version ->if no what could i do?
    > Code Inspector ->if no what could i do?
    > Variants -> if no i could transport wit the report for export Variant ( OSS )
    All this will be part of the shell system. It's basically your production system without any transactional data.
    > ABAP    Version i know its not transported we have to export but know SAP if we import the Version file that some ABAPs miss ( because we don't want )
    How should "SAP know" that?
    Markus

  • What is the "BW shell creation package for BW system" in TDMS?

    I see for lower version of SAP systems such as 4.6 and BW(e.g.3.0, etc), there is a "shell creation package " for those
    types of systems.
    Could you explain what is that for?
    Thanks!

    1) where to find the info about the copy sequence such as: first shell creation, then initial package or whatever, then ...?
    > TDMS solution operation guide will be helpful, the same is available at SAP service market place. In short the sequence is  -
    first shell (only if the repository is not in sync) then initial package (ex. TDTIM) and then refresh packages (as an when needed)
    2) for HR we do not have shell creation, what we have is "initial package for master data and customizing" , the next step is "ERP initial package for HCM personel dev. PA & PD". Why we do not have shell creation here?
    > For HR as only few objects are transfered the need of a full shell system does not arise. only the object to be transfered are synced.
    3) Will TDMS replace system copy for ERP, BW, CRM completely?
    > Shell will not replace them but we may say that it will supplement it. When you need a complete copy means repository along with application data then you need to go for system copy but if you only need repository to be copied from source to destination then shell is helpful. Also it should be noted that Shell is an TDMS package whereas System copy is a SAP standard tool.
    I hope the above response is helpful.
    Regards,
    Pankaj

  • TDMS 3.0 for ERP 6.0:  step by step procedure for  TDSH6 Shell creation

    Dear All,
    I need to perform shell creation. I have never done this and need help with step by step instructions.
    I need to refresh my my development system with a TDMS shell creation from production client in production system.
    I am familiar with TDTIM and performed many TDTIM copies. I have gone throught the master and operational guides for TDMS also.
    I would try to list down my understanding so far after reading the guides.
    Please correct me if I am wrong ang also suggest correct steps.
    1. All my three systems (central, sender and receiver) are ready from installation point of with with authorizations and latest SPs.
    2. I log into Central/Control system and start a new package  "ERP Shell creation package for AP Release higher 4.6 "
    3. AS I have never executed this option I do not know what are the stps inside it.
       But I assume I should be asked for the source client details from which shell needs to be creates. (000 or pruduction client)
       What type of shell  : slave or master?
    4. During the shell creation from sender system client, is there a downtime for sender system.
    5. Once the shell creation is done an export dump will created.
    6. I perform all the preprocessing steps of a homogenous system copy on the receiver systems.
    7. Stop receiver system, start sapinst  database instance installation with homogenous system copy with R3load option.
    8. Provide the export dump location to sapinst.
    9. After database instance is installed, perform system copy specific post processing steps.
    10. Afte the system is ready it has only one client 000 now available in development system and  i need to create a new cleint from 000 which will act as my new development cleint.
    I request all you experts to please provide your comments at the earliest as activity would be starting from 5th of this month.
    Regards,
    Prateek.

    Hi,
    Let me answer your questions.
    Some queries
    1. Is there a downtime for Production system (sender system).
       SAP recommends that nothing much should be going on during the export of the Sender(PRoduction) system, but so far i have never encountered an issue doing the export in online mode.
    2. Shell creation works on both Production and 000 client or only Production client,
       Be carefull!!! - A Shellcreation is a normal Homogenous Systemcopy using R3load. You will create a 'new' system with the DDIC and clientindependent customization of the Sender system. ALL former data of the target system will be deleted.
    You mention that you will refresh a development system that way. Please be aware of the implications that a development refresh contains. That said. After the refresh you will have the 000 client and parts (users ... authorizations of sonder) of the other clients on the new system.
    3. when I import the the dump using sapinst, how many clients are available in receiver systems.
    See above. All client configuration will be available, but nearly no data will be in these clients except 000. A manual part of the Shellcreation is to clean up the target system (delete the clients that are not needed) This is a fast process.
    4. Soem where in the guide it is mentioned that downtime depends on the type of shell I create.
    Kindly suggest should I create a master shell or slave.
    Hm. The master shell is just a concept that you create a complete new system and put that system into your transport landscape without filling it with data. You can then use that system as the source for a normal (database dependent) systemcopy without impacting your prod system. The result is a very small copy that can be repeated very often without an impact to prod/QA...
    Downtime is as described in point1 not required
    5. Once I execute this activity of shell creation for lets say receiver system A, then can I use the same export dump for second receiver system B.
    Yes
    6. Lastly please suggest the activity execution time as customer has provided us 2 days to execute this activity.
    This depends on your knowledge of homogenuous systemcopies and the preparation + some items like size of stxl  and other tables that will be exported/imported.  If you are very familiar with the systemcopy process using R3Load 2 days are feasable.
    I have seen shellcreations done within 1-2 days but also much longer ones!
    As a prerequisite i would always recommedn to have the latest R3* + migmon exe available on sender + target.
    I hope i have clarified some of your items.
    Best Regards
    Joerg

  • Migration monitor in TDMS shell creation

    Hi,
    I am working on a TDMS shell creation for ECC system, I have few question..
    1) Is it mandatory to run migration monitor manually while in both exporting and importing database with R3load option in tdms shell creation or only while running R3load export?
    2) How to run export monitor activity in background?
    3) How to parallel R3load processes to export a single package instead running one r3load for each package?
    OS: AIX
    DB: DB2
    SAp ECC 6
    Thanks
    Praveen

    Answers to your questions are below -
    1) It is mandatory during the exports of data from the source system.
    2) It should not be run in background
    3) Use table splitting using R3TA, but that should be done before exports.

  • TDMS for BI - shell creation and SMIGR_CREATE_DDL

    If a homogeneous system copy of a BI system is done, it's necessary to run the job SMIGR_CREATE_DDL because depending on what database is used, special SQL scripts for tables must be used (concerning primary keys).
    How does that integrate into a shell creation? Is the shell creation process aware of those scripts? I mean, it's theoretically possible that the SQL scripts has a table that is excluded from being transferred?
    Markus

    Markus and Pankaj:
    I have created a SHELL (BW) using Markus' way as listed below.
    Because Markus did not mention that SMIGR_CREATE_DDL should be run at the beginning, so I did not run it.
    So how to determine in the created shell what is missing?
    We do have partitioned tables and bitmap indexes.
    Thanks!
    Here is the way provided by Markus:
    I basically do shell creation as follows:
    - install the latest system copy tools (R3load, R3ldctl, R3szchk, libdb<database>slib.dll)
    - create an installation directory and give full permissions to <sid>adm and SAPService<SID>
    - create a directory for export location and give full permissions to <sid>adm and SAPService<SID>
    - open a cmd.exe as <SID>adm, step to the installation directory and execute "R3ldctl -l R3ldctl.log -p ." (note the "dot" which means actual directory)
    - in parallel start the client export of client 000 in source system using SCC8 (profile SAP_ALL) and note the file names you get in the last dialog window
    - when R3ldctl is finished give permissions to SAPService<SID> for all files in the installation directory
    - proceed with TDMS
    - when you are at the point to start the system copy start sapinst, choose system copy and select start migration monitor manually (VERY important!)
    - sapinst will run R3ldctl, R3szchk and then prompts you to start migration monitor
    - step to your normal installation directory (c:\program files\sapinst_instdir....), open export_monitor_cmd.properties and adapt the file. The import thing is, that you need to point to YOUR DDL<DB>.TPL file you create in step 4 (in my list here)
    - start export_monitor.cmd and export the system
    - proceed with TDMS to adapt the database sizes (DBSIZE.XML)
    Import:
    - if you have an already installed system uninstall it
    - start sapinst normally, choose system copy and point to the export you created
    - install the system normally (as a new installation)
    - if you want to make sure the import works as the export choose "start migration monitor manually"
    - if sapinst stops and requests you to start migration monitor copy the kernel from source system to target system
    - configure import_monitor_cmd.properties and start migmon
    - logon in client 000, start transaction STMS and create a domain (basically only a transport profile will be created)
    - start program BTCTRNS1 (this will suspend all jobs from the source system but not delete them)
    - copy the files from the client copy to TRANSDIR/cofiles and TRANSDIR/data and import them to client 000 (either use STMS or use command line tp)
    - adapt profile parameters (RZ10)
    - run SGEN
    - invalidate connections in SM59 that point to other production systems
    - finished
    - to re-enable all the jobs run BTCTRNS2, however, I'd do this only if you're sure you have invalidated RFCs and or sending jobs (e. g. from SCOT)

  • TDMS shell creation

    Is TDMS shell creation for the ABAP stack only?
    What happens in the ABAP+Java systems?
    Thanks,
    Sri

    Hi Pankaj,
    I don't think TDMS is meant for JAVA. At preset It is only meant for ABAP stack to transfer data using different senarios.
    You can transfer the data from source and at the same time the Java settings in the target remain the same.
    Thanks,
    Sridhar

  • TDMS shell creation  - R3szchk running longtime

    Hi,
    I am running a shell creation package, in Export ABAP phase R3szchk running long time and there is nothing written to log file
    -rw-r-----    1 root     sapinst           0 Oct  4 19:56 /tmp/sapinst_instdir/ERPEhP4/LM/COPY/DB6/EXP/CENTRAL/AS-ABAP/EXP/R3szchk.exe.log
    where else I can check to find out the issue?
    Thanks
    Din

    Thanks Pankaj for the valuable information.
    ---The size of exports may depend on the data in your client independent tables. There are certain client indepedent table which hold a lot of data for example STXL, STXH and DYNP* tables. It also depends on the volume of custom development that you have done in your systems. Most of the client independent tables are exported in full duing shell.
    I could understand that. I ran an optional activity u201CCheck size of large tables (optional)u201D  in TDMS Shell package, it returns witj some large tables, such as
    STXH- 190,854,900 KB
    STXL- 26,819,840 KB
    DYNPSOURCE- 20,452,251 KB, some of these are independent and some are dependent tables. For ex. STXH is dependent table with size 190GB, does it means that this table will be exported in full during shell export?
    However, you need to be sure that because of certain mistakes you are not exporting the complete system (including application data). As stated by Marcus, you need to make sure that you are using Migration monitor in manual mode and that you configure the Migration monitor control file with correct parameter values.
    I think I configured import monitor control file correctly and started it manually.
    Here is the import monitor startup log:
    Export Monitor is started.
    CONFIG: 2011-10-05 00:49:22
    Application options:
    dataCodepage=4102
    dbType=DB6
    ddlFile=/shell_install/DDLDB6.TPL
    ddlMap=
    exportDirs=/shell_export/ABAP
    ftpExchangeDir=
    ftpExportDirs=
    ftpHost=
    ftpJobNum=3
    ftpPassword=*****
    ftpUser=
    host=
    installDir=/shell_install
    jobNum=6
    loadArgs=
    mailFrom=
    mailServer=
    mailTo=
    monitorTimeout=30
    netExchangeDir=
    orderBy=name
    port=
    r3loadExe=
    server=
    taskArgs=
    trace=all
    tskFiles=yes
    Thanks
    Din

  • Message "Creation of DataSources for SAP source system is not permitted"

    Hi,
    I am in DW Workbench: Modeling and I need to copy a DataSource.
    It's impossible, beacause I have this Message "Creation of DataSources for SAP source system is not permitted"!
    What can I do?
    Thks

    Hii.
    You can not copy the standard datasource to any other source system it will not allow you to do that.
    But if you want to copy you can copy it to PC FILE source system.
    It will allow you to copy there.
    Right click in Datasource->Copy-> Give Target datasource name -
    > intarget Source system tab -
    >Give Source system for File.
    Thanks
    Mayank
    Edited by: Mayank Chauhan on Sep 4, 2009 5:41 PM

  • SAP TDMS add on setup on central/control , sender and reciever systems

    I found that SAP TDMS is shipped in the following add-ons:
    DMIS: Contains general functions, for example for the process monitor and for the technical data transfer
    DMIS_CNT: Contains TDMS-specific functions and some of the process types
    DMIS_EXT: For various additional process types (reduction scenarios) for SAP TDMS; currently, it contains only the process   type for business process library
    DMIS_BSC: For the process types to be used with SAP BI or CRM systems
    DMIS_HR: For the process types to be used in the context of SAP Human Capital Management (HCM)
    I have read TDMS master guide under section 3.4.1 Setting up the TDMS Server. There is a reference to SAP Note 970531 which is for DIMS setup and there is also reference to SAP note 970532 which is for DMIS_CNT setup.
    I would like to know if DMIS_EXT,DMIS_BSC and DMIS_HR need to be setup on TDMS central/control server , sender and reciever or only need to be setup on central/control server for respective scenario realization.
    Best Regards
    Mohammed Ashraf

    All the add-on components need to be installed in all the system (sender, receiver, central, control) in the landscape.

  • What is the "shell creation" in TDMS?

    I cannot find the exact definition of above term "shell creation". Would you please help? Thanks!

    In TDMS, there are different ways of selecting data from the production server. So there are different Process Types.
    Shell Creation is one of those types.
    SHELL CREATION- Migrated data contains only cross-client data and the required client-specific user and address data, but no other client-dependent data.
    Hope this answers your question

  • SAP Source system creation in BI

    Hi Gurus,
    I am trying to create SAP source system in BI,  The trying to create ALE REMOTE user in both systems.
    What roles and profiles i need to assign to this user id. After creating user ids what steps i need to follow. Thanks.
    Best Regards,
    Suresh.

    Hi,
    To Create SAP Source System In BI:
    -Click on Source System tab in RSA1.
    -Then right click on the heading Source system and select Create.
    -Select the first option Automatic. Create SAP System and continue filling the other details.
    -This will create Source system automatically.
    When you enter background user's password, sap system user name is modifiable, but the the BI user.
    The background user of BI system, is defined in
    RSA1 => Settings => Global Settings
    <b>BW User ALE</b> field will have the name of the background user in BI.
    If you are using ALEREMOTE as background user, make sure the same is maintained as BW User ALE.
    regards,
    Pruthvi R
    Message was edited by:
            Pruthvi R

  • SAP-TDMS Installtion

    Dears,
    I am new to SAP TDMS,Recently our company has planned to implement SAP TDMS in our landscape.
    Now I want to know its installation procedure,Prequisties and hardware configuration that we should take for this.
    I searched on marketplace and net but did not find.
    Please suggest.
    Shivam

    Hi Shivam
    I hope this will help you . Here are My Findings on TDMS
    My Findings:
    Step1u2022     Broadly speaking, to setup your TDMS landscape, you need to install the TDMS (DMIS, DMIS_CNT, DMIS_EXT with latest patch levels) software on the sender, receiver and central system. Latest available pack is SP11 (May 2009)
    Step2u2022     Check Latest SPAM/SAINT
    Step3u2022     Arrange - CD material # 51032076 and Material # 51032077. Search in SWDC  with material # put in download basket and download with SAP DM. Read Notes 970531 &  970532 for installation of DMS/TDMS and DMIS/TDMS content.
    Step4u2022     Basically you have to install DMIS and DMIS_CNT only (in all systems involved). But if you want to make full use of all functionality you have to install DMIS_EXT 2007_1 also (in all systems involved). TDMS DMIS_EXT is not a must component but it is good to have.  CD # 51033076 (DMIS EXT ADD-ON Installation ) Search Download words for DMIS_EXT are u201CDMIS_EXT 2007u201D. Read SAP Note Number: 1094395 for installation of DMIS_EXT. Before starting Installation of DMIS_EXT, please make sure your kernel or at least you use an R3trans version dated MAY/14/2008 or later, otherwise you face errors in importing.
    Step5u2022     Patches for both of the packages is also available and required. Patches can be searched as u201CDMIS_CNT 2006_1_700u201D (here 700 is the version from your BASIS release.) & DMIS 2006_1_700. File names of a typical SP look like K-61701INDMIS and K-61701INDMISCNT.
    Step6u2022     Components (packages)  excluded for the installation(check some packages, List from the note, should exist or not in the system se80) Should not exist in the system otherwise open a OSS message as per note-970531.
    Step7u2022     Login to 000 with sap_all but not DDIC or sap*
    Step8u2022     Upload Add-on and support packs to the system inbox. And then install. It is better to install  add-on and sp in one queue.
    Step9u2022     There is one password required for installation of add-on, see the respective notes for this.
    Step10u2022     After Successful  Installation of DMIS and DMIS_ addon with SPs. Generate profiles for TDMS projects . PFCG Utilities Menu  Mass Generation. Generate profiles which starts with these names : SAP_TDMS* , SAP_DMIS* ,  SAP_CMIS* , SAP_SLOP*. Read see SAP Note 897100.
    Step11u2022     Apply Settings mentioned in Note # 890797.
    Step12u2022      Execute  TXN CNV_MBT_TDMS , Create New Project. Now create a  New Subproject under project just created.
    Step13u2022     Create New Package based on your scenario like Shell creation. After successful creation of New Package you will got PROCESS TREE / MONITOR u2013 PACKAGE 90XXXX Screen.You will got following kind of screen once you created TDMS Package, based on the UI you work with. Use TXN CNVMBTUISWITCH to switch to UI.
    Edited by: jaswant purba on May 28, 2009 7:47 PM

  • SAP TDMS - Ensure Repository between Sender & Receiver

    Dear All,
    I've some questions about TDMS prerequisites.
    I know that repository consistency between Sender and Receiver need to be checked before performing SAP TDMS scenario.
    But my question is, how to ensure consistency between Production System and Quality System?
    Repository means workbench and cross client customizing.
    So there are usually inconsistencies between production and quality systems.
    TDMS does not work if  the two systems are not aligned?
    Do we have some recommandations, or best practices to make it happened?
    Regards,
    Benjamin

    Hi Benjamin,
    Your requirement is indeed practical.
    Here the most consistent approach is to use shell creation to build the receiver system since, we know that there is quite a lot of deviation in the cross-client customizing / repository in the quality systems.
    However at the same time, you can continue to use TDMS to copy data from your production environment to the quality environment with the repository as it is ( with some delta difference in the repository)... In this case, you would be able to copy data for at least all the existing transactional / Master Data from production to quality system, which will allow to test your new developments / business scenarios etc...
    Following could be the situations that you need to understand with this approach -
    1. In case there are some new dictionary / DB object newly created in receiver system would remain   blank as there would be no corresponding data for the same in the sender system,
    2. For any dictionary / DB objects if there has been any modification in non-key fields for data type etc.. / or cases where new include structure may have been added, such table fields will not be populated. Rest other table fields data would still be consistent. All such inconsistencies would be displayed in the TDMS activities. Here you would have the option to either synch the corresponding , structures or alternately you may still continue without any changes ,
    3.There may be some dynamically generated program references in the system which may vary compared to your sender environment. Such reports may need to be re-generated using some standard reports etc.. in case you face issues post copy.
    4. In some situations, you may want to re-import some specific customizing's that would vary compared to the sender environment after the TDMS copy. So you need to be pro-active in ensuring such customizing requirements of your team...
    Overall I would suggest that you should try with at least one test TDMS copy , with the existing repository differences . This should be mostly helpful for your case .
    Please do share your experience / challenges in case you decide to go ahead with this suggestion.
    Thanks,
    Rajesh

  • Shell creation issue

    Dear experts, I've got a question regarding shell creation of TDMS.
    I've finished the export from ECC IDES system (SR3). The size of export files are over 30GB... is it normal? Can I reduce the data? Since it'll take me more than 200GB disk in target system.
    Is it been setup in the step of "Determine Tables to be Excluded from the Export"?
    Which data can be reduced in the table regarding IDES shell creation?
    Thanks!

    Hi Jett
    Your first question is not very clear to me -
    Seems that, the data folder of export is still the same as before. Is it normal?
    >I think you mean to say that the size of the data folder of export is of same size as before. Yes that is normal. However i feel the doubt that remains in your mind is that you want to be sure that its doing a reduced transfer and not a full transfer. Well you cant make a decision based on the size of the export folder. To decide that you can do the following -
    Pick one excluded table and in the exports folder try to search for its existence in the .TOC files. If you find it in any of the .TOC files then it indicates that a full transfer is happening instead of a reduced one. If you dont find it in .TOC but you find that excluded table in .STR files that indicates that a reduced transfer is happening and everything is fine. The existence of the excluded table in .STR file indicates that the structure information of the excluded table will be transferred although the data is not getting transferred.
    Regarding your second set of queries -
    Please understand that there are two parts to shell creation one is excluding the data to be transferred for a set of tables, so no data at all get transferred to the target system for all the excluded tables. Second part is that how much filespace (on target system) should be allocated to tables which are there in the excluded tables list, by default the import process will assign same space to a table in target system as the space allocated to it in the source system. So if a table for which no data is getting transferred was of size say 10 MB in sender so the import process will allocate a filesize of 10 MB to the table in target system also although it will be blank. To avoid this and to reduce the overall size of target system, we reduce the sizes that should be allocated to the excluded tables in the target system in the activity "Determin and Modify Size of Tables".
    Now for the question what do the ratios mean and on what basis do we assign the ratios-
    >Say for example Ratio20 means that the import process will assign 20% of the original size (in sender system) to the table in the target system. Regarding on what basis are the ratios determined - The ratios are determined on the basis that how much data do you expect each table to hold later on. So this depends on which process of TDMS (vis TDTIM, TDMDC, TDTCC) do you want to execute after shell creation. In case of TDTIM process type it may also depend on the period for which you want to transfer the data. For this reason we have provided various templates (vis TDTIM, TDMDC etc) in the activity "Determin and Modify Size of Tables". So we have tried to build this intelligence into the system. So if you want to excute a TDMDC scenario after shell creation then you should choose the template TDMDC in the activity "Determin and Modify Size of Tables" and the system will automatically assign defferent ratios to different tables.
    In my last post i had suggested that if you want to further reduce the size of your target system (although the assigned template will automatically reduce the size of the target system) you can do the same by further reducing the ratios for the tables for which you dont expect much data to be transfered. This functionality of altering ratios for certain table or set of tables is available in the activity "Determin and Modify Size of Tables". SAP already delivers ratios which will be optimum for different tables, if you want to override those setting and provide your own ratios then it should be done at your own risk.
    I hope this post explain you the entire concept. In case you have some doubt feel free to write again.
    Regards
    Pankaj.

Maybe you are looking for