How To Carry Out Data Transfer Through Files Using SAP TDMS

Size: px
Start display at page:

Download "How To Carry Out Data Transfer Through Files Using SAP TDMS"

Transcription

1 SAP NetWeaver Hw-T Guide Hw T Carry Out Data Transfer Thrugh Files Using SAP TDMS Applicable Releases: SAP Test Data Migratin Server 4.0 Versin 1.3 February 2015

2 Cpyright 2015 SAP AG. All rights reserved. N part f this publicatin may be reprduced r transmitted in any frm r fr any purpse withut the express permissin f SAP AG. The infrmatin cntained herein may be changed withut prir ntice. Sme sftware prducts marketed by SAP AG and its distributrs cntain prprietary sftware cmpnents f ther sftware vendrs. Micrsft, Windws, Outlk, and PwerPint are registered trademarks f Micrsft Crpratin. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivli, Infrmix, i5/os, POWER, POWER5, OpenPwer and PwerPC are trademarks r registered trademarks f IBM Crpratin. Adbe, the Adbe lg, Acrbat, PstScript, and Reader are either trademarks r registered trademarks f Adbe Systems Incrprated in the United States and/r ther cuntries. Oracle is a registered trademark f Oracle Crpratin. UNIX, X/Open, OSF/1, and Mtif are registered trademarks f the Open Grup. Citrix, ICA, Prgram Neighbrhd, MetaFrame, WinFrame, VideFrame, and MultiWin are trademarks r registered trademarks f Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks r registered trademarks f W3C, Wrld Wide Web Cnsrtium, Massachusetts Institute f Technlgy. Java is a registered trademark f Sun Micrsystems, Inc. JavaScript is a registered trademark f Sun Micrsystems, Inc., used under license fr technlgy invented and implemented by Netscape. MaxDB is a trademark f MySQL AB, Sweden. SAP, R/3, mysap, mysap.cm, xapps, xapp, SAP NetWeaver, and ther SAP prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f SAP AG in Germany and in several ther cuntries all ver the wrld. All ther prduct and service names mentined are the trademarks f their respective cmpanies. Data cntained in this dcument serves infrmatinal purpses nly. Natinal prduct specificatins may vary. These materials are subject t change withut ntice. These materials are prvided by SAP AG and its affiliated cmpanies ("SAP Grup") fr infrmatinal purpses nly, withut representatin r warranty f any kind, and SAP Grup shall nt be liable fr errrs r missins with respect t the materials. The nly warranties fr SAP Grup prducts and services are thse that are set frth in the express warranty statements accmpanying such prducts and services, if any. Nthing herein shuld be cnstrued as cnstituting an additinal warranty. These materials are prvided as is withut a warranty f any kind, either express r implied, including but nt limited t, the implied warranties f merchantability, fitness fr a particular purpse, r nn-infringement. SAP shall nt be liable fr damages f any kind including withut limitatin direct, special, indirect, r cnsequential damages that may result frm the use f these materials. SAP des nt warrant the accuracy r cmpleteness f the infrmatin, text, graphics, links r ther items cntained within these materials. SAP has n cntrl ver the infrmatin that yu may access thrugh the use f ht links cntained in these materials and des nt endrse yur use f third party web pages nr prvide any warranty whatsever relating t third party web pages. SAP NetWeaver Hw-t Guides are intended t simplify the prduct implementatin. While specific prduct features and prcedures typically are explained in a practical business cntext, it is nt implied that thse features and prcedures are the nly apprach in slving a specific business prblem using SAP NetWeaver. Shuld yu wish t receive additinal infrmatin, clarificatin r supprt, please refer t SAP Cnsulting. Any sftware cding and/r cde lines / strings ( Cde ) included in this dcumentatin are nly examples and are nt intended t be used in a prductive system envirnment. The Cde is nly intended better explain and visualize the syntax and phrasing rules f certain cding. SAP des nt warrant the crrectness and cmpleteness f the Cde given herein, and SAP shall nt be liable fr errrs r damages caused by the usage f the Cde, except if such damages were caused by SAP intentinally r grssly negligent. Disclaimer Sme cmpnents f this prduct are based n Java. Any cde change in these cmpnents may cause unpredictable and severe malfunctins and is therefre expressively prhibited, as is any decmpilatin f these cmpnents. Any Java Surce Cde delivered with this prduct is nly t be used by SAP s Supprt Services and may nt be mdified r altered in any way.

3 Dcument Histry Dcument Versin Descriptin 1.0 First fficial release f this guide 1.1 Updates n relevant migratin slutins 1.2 Flexible chice f target systems t save yur files 1.3 Changing the file path and file attributes

4 Typgraphic Cnventins Type Style Example Text Descriptin Wrds r characters quted frm the screen. These include field names, screen titles, pushbuttns labels, menu names, menu paths, and menu ptins. Crss-references t ther dcumentatin Icns Icn Descriptin Cautin Nte r Imprtant Example Recmmendatin r Tip Example text Example text Example text <Example text> EXAMPLE TEXT Emphasized wrds r phrases in bdy text, graphic titles, and table titles File and directry names and their paths, messages, names f variables and parameters, surce text, and names f installatin, upgrade and database tls. User entry texts. These are wrds r characters that yu enter in the system exactly as they appear in the dcumentatin. Variable user entry. Angle brackets indicate that yu replace these wrds and characters with apprpriate entries t make entries in the system. Keys n the keybard, fr example, F2 r ENTER.

5 Table f Cntents 1. Business Scenari Backgrund Infrmatin Technical Settings fr Exprt and Imprt f Data Extracts Prerequisites Step-by-Step Prcedure Creating an Exprt Package Creating a Standard Migratin Package Specifying the Apprpriate Methd f Transfer Defining a Data Extract ID fr File Transfer Flexible Chice f Target System t Save Yur Files Starting the Data Exprt Restarting the Exprt Data t Files Activity Transferring the Files t the Receiver System Creating an Imprt Package Creating an Imprt Package Specifying the Data Extract ID Starting Data Extractin fr Imprt Starting the Data Transfer Prcess Relevant Migratin Slutins... 11

6 List f Figures Figure 1: Graphical Representatin f the File Transfer Prcess... 1 Figure 2: Creating an Exprt Package... 3 Figure 3: Data Extract ID Definitin... 4 Figure 4: Transactin FILE... 6 Figure 5: Overview f Assignment f Physical Paths t the Lgical Path... 6 Figure 6: Setting Values in the Exec. Target Field in the CNVMBTDEXDEFAULT Table... 7 Figure 7: Creating an Imprt Package... 9 Figure 8: Specify Data Extract ID... 10

7 Hw T Transfer Data Thrugh Files Using SAP TDMS Business Scenari Yu can carry ut data transfer thrugh files in the fllwing cntexts: Yu d nt have a direct cnnectin between the sender system and the receiver system in yur test landscape. Yu want t carry ut multiple imprts f test data using a single exprt file. The figure belw shws the main steps t be fllwed in bth cntexts. Figure 1: Graphical Representatin f the File Transfer Prcess 2. Backgrund Infrmatin SAP TDMS ffers the fllwing mdes f data transfer: Data transfer based n Remte Functin Calls (RFC) Data transfer thrugh files Legend S: Sender System P : Cntrl System C: Central System S : Virtual Sender System P : Cntrl System C : Central System R: Receiver System Yu cannt transfer individual tables using file transfer. Use the trubleshting available with the RFC-based apprach t transfer individual tables. 2.1 Technical Settings fr Exprt and Imprt f Data Extracts Definitin f Data Extract Exprt and Imprt Directry Yu can specify the exprt and imprt directry fr the data extract files by defining the lgical path DMIS_DEX_ROOT in the SAP standard maintenance transactin fr lgical paths and file names (TA: FILE). By default, the lgical path DMIS_DEX_ROOT pints t the transprt directry DIR_TRANS that is defined in the system prfile f the respective Data Transfer Cntrl system. T change the assigned exprt r imprt path, yu can carry ut any ne f the fllwing methds: February

8 Hw T Transfer Data Thrugh Files Using SAP TDMS 4.0 Change the definitin f the lgical path DMIS_DEX_ROOT in the cntrl system by using transactin FILE. Create yur wn lgical path definitins and assign them as the new lgical exprt r imprt path by using transactin CNV_MBT_DEXDEFAULTS in the cntrl system. Definitin f Maximum File Size fr Data Extract Data Files Yu can change the maximum size fr each data extract file by defining a crrespnding maximum file size in bytes using transactin CNV_MBT_DEXDEFAULTS fr the cntrl system. File Lcatin after Exprt Cmpletin If the central system and the sender system are distinct in yur system landscape, place all files generated after the exprt in the central system. 3. Prerequisites Yu have installed SAP TDMS 4.0 n yur central system, the sender system, and the receiver system. Yu have installed the latest service packs fr SAP TDMS. Befre Data Imprt The imprt package requires a dummy sender system, where SAP TDMS can create the cluster DMC_INDXCL and imprt files t the cluster. The dummy sender system can be the receiver system, the cntrl system, r a different system nt used during exprt. February

9 ... Hw T Transfer Data Thrugh Files Using SAP TDMS Step-by-Step Prcedure This sectin cntains detailed instructins fr the fllwing prcedures: Creating an Exprt Package Transferring Files t the Receiver System Creating an Imprt Package 4.1 Creating an Exprt Package Fr yur required slutin, create an exprt package t cpy data frm the data cluster in the sender system t multiple files nt the cntrl system. By default, SAP TDMS stres the files in the transprt directry. Yu can change the default path using the FILE transactin in the cntrl system. The figure belw shws the main steps t be fllwed while creating an exprt package. Create a standard TDMS package Specify the apprpriate methd f transfer Define the data extract ID Exprt the files Figure 2: Creating an Exprt Package Creating a Standard Migratin Package Create a TDMS migratin package fr the required applicatin. Fr a cmplete list f available migratin slutins, see Sectin Specifying the Apprpriate Methd f Transfer By default, SAP TDMS chses RFC-based data transfer. T change the mde f transfer t data transfer thrugh files, execute the Specify the Data Transfer Methd activity in the prcess tree. When yu execute this activity, a dialg bx appears where yu can chse the fllwing mdes f transfer: February

10 Hw T Transfer Data Thrugh Files Using SAP TDMS 4.0 Mde 1: Fr RFC-based data transfer Mde 2: Fr file based transfer When yu chse the file-based transfer, activities relevant t data transfer thrugh files appear in the prcess tree. Specifying the Mde f Transfer at the Prject Level Yu can als make the mde f transfer setting at the prject level. If yu set the Data Transfer Thrugh Files parameter at the prject level and select the Final checkbx, the data is transferred thrugh files. If required, yu can change this setting at the migratin package level. Cntinue with the remaining activities f the tree as yu wuld have dne fr a nrmal TDMS tree Defining a Data Extract ID fr File Transfer After yu have cmpleted data selectin fr all tables, execute the Defining a Data Extract ID fr File Transfer activity. This activity generates a unique data extract ID fr the transfer. Assign the new data extract ID t the package. Make a nte f the data extract ID, which is necessary fr the imprt prcess. Yu can change the fllwing attributes: Exprt Path: The lgical path where SAP TDMS stres the files. Yu can view the actual path crrespnding t the lgical path in the transactin FILE. Maximum File Size: The size f a particular file. Maximum Blck Size: SAP TDMS ppulates the file based n the blck size. If the file size is 100 MB, fr example, and the blck size 1 MB, SAP TDMS iterates 100 times t stre the data in a file. Executin Target: The system where yu want t stre the files. Nte: Chse the Inf pushbuttn t view the estimated space required at the perating system level t stre the files. The figure belw shws the screen where yu can enter a descriptin fr the data extract ID. Figure 3: Data Extract ID Definitin February

11 Hw T Transfer Data Thrugh Files Using SAP TDMS Flexible Chice f Target System t Save Yur Files The cntrl system is the default system t save the files that yu want t exprt r imprt. Prir t DMIS 2011 SP04, the cntrl system was the nly system available t save the files exprted ver the WAN frm the sender system. The cntrl system als initiated the file imprt t the receiver system ver the WAN. Beginning DMIS 2011 SP04, yu can chse a different system frm the cntrl system as the target system fr the files. Yu can save yur exprt package n the sender system r the central system. Additinally, yu can transfer the files t the receiver system thrugh an imprt package withut ging thrugh an intermediate WAN. Prerequisite If yur TDMS versin is SP04 r SP05, yu can make the settings in a table (details prvided belw). If yur TDMS versin is SP06, yu can make the settings in a maintenance view (details prvided belw). This feature is available as a standard feature starting DMIS 2011 SP06. If yu have cnfigured SAP TDMS t run n DMIS 2011 SP04 r DMIS 2011 SP05, ensure that yu have applied the fllwing SAP Ntes: SAP Nte WAN independent File Transfer slutin SAP Nte WAN independent extract slutin SAP Nte Data Transfer is in errr in WAN independent slutin Hw t prvide the target system T change the target system fr file exprt (exprt system) r fr file imprt (imprt system) frm the cntrl system t a different system, prceed as fllws: Hw t change the file path: The Exprt Data t Files activity uses the File Extract feature t create files fr the data f the sender system. The activity stres the files in the fllwing paths: Lgical Path: A lgical path maps a lgical, r virtual, directry name t an actual directry name n the server. Fr example, yu might map the lgical directry name DGN t the physical directry C:/DATA/DGN.. If yu use the lgical name in a URL, fr example, the server returns a representatin f c:/data/dgn/test.dgn. Physical Path: The physical path is actually present in the hard disk. The default name f the lgical path in SAP TDMS is DMIS_DEX_ROOT. The physical path that is mapped t the lgical path DMIS_DEX_ROOT is DIR_TRANS. If yu d nt want t stre the archived files created by SAP TDMS in the DIR_TRANS lcatin, here s hw yu can change the physical path: 1. G t transactin FILE as shwn belw. February

12 Hw T Transfer Data Thrugh Files Using SAP TDMS 4.0 Figure 4: Transactin FILE 2. Click n Psitin pushbuttn t find the lgical path DMIS_DEX_ROOT. 3. Select the lgical path DMIS_DEX_ROOT and duble-click the Assignment f Physical Paths t Lgical Path pushbuttn. Figure 5: Overview f Assignment f Physical Paths t the Lgical Path 4. Duble-click the type f Operating system, fr example, Unix r Windws NT. (T check the type f Operating system, chse G t System Status Operating System.). February

13 Hw T Transfer Data Thrugh Files Using SAP TDMS 4.0 Figure 6: Detailed View f Assignment f Physical Paths t the Lgical Path 5. Change the path by chsing the Display/Change pushbuttn. Example: If yu want t stre the files in the lcatin: C:\Users\<yur name>\desktp\dex, make sure that the physical path value is: C:\Users\<yurname>\Desktp\DEX\<FILENAME> Fr DMIS 2011 SP06: 1. Run the activity Define a Data Extract ID fr File Transfer. 2. Check the lgs f the activity and nte the DEX ID fr the package. 3. In the maintenance view V_CNVMBTDEXHEADA, change the value in the Executin Target field t: S if yu want t create files in the sender system P if yu want t create files in the cntrl system. 4. Execute the activity Exprt Data t Files t create the files in the desired system. Fr DMIS 2011SP04 and DMIS 2011 SP05: 1. Set the value f the executin target in the EXEC_TARGET field in table CNVMBTDEXDEFAULT t: S if yu want t create files in the sender system C if yu want t create files in the central system 2. Alternatively, yu can set the values fr the EXEC_TARGET field in the maintenance view V_CNVMBTDEXDEFAU. Figure 6: Setting Values in the Exec. Target Field in the CNVMBTDEXDEFAULT Table 3. Execute the activity Define a Data Extract ID fr File Transfer. 4. Execute the activity Exprt Data t Files t create the files in the desired system. February

14 Hw T Transfer Data Thrugh Files Using SAP TDMS Starting the Data Exprt This activity starts the exprt f data frm the data cluster in the sender system t multiple files in yur preferred path (in the cntrl system). While executing the activity, a set f data extract files is stred in the assigned exprt directry. By default, SAP TDMS stres the files in the transprt directry. Yu can change the default path using the FILE transactin in the cntrl system After this activity is cmplete, check the lg and ensure that there are n errrs Keep in mind the fllwing imprtant pints during exprt: Data extract files are available in the transprt directry f the TDMS cntrl system. SAP TDMS creates multiple files in the transprt directry during a data extract exprt. SAP TDMS creates data extract files based n the data extract ID generated during the data extractin prcess. The ttal space required fr the data extract files is the same as the size f the data cluster DMC_INDXCL. If the ttal data in DMC_INDXCL fr the current exprt package is 40GB, fr example, an additinal space f 40GB is required in the cntrl system t stre the data extract files. File Types frm Data Extract A data extract cnsists f the fllwing files: Legend Data Extract Header File: <SID><9xxxx><nnnnnnnnnnnn>_000000_H Data Extract Cntrl File: <SID><9xxxx><nnnnnnnnnnnn>_000000_C 1...n Data Extract Data Files: <SID><9xxxx><nnnnnnnnnnnn>_000001_D <SID><9xxxx><nnnnnnnnnnnn>_NNNNNN _C <SID>: System ID f the data extract exprt cntrl system. <9xxxx>: Package number f the transfer package frm which the data extract is created. <nnnnnnnnnnnn>: Unique number fr data extracts exprted frm the sender system Restarting the Exprt Data t Files Activity 1. If the subactivities get terminated due t a temprary system issue, execute the Exprt Data t Files activity again. This activity ensures that the files already exprted are nt exprted again and starts the subactivities that are nt yet started. 2. If the subactivities get terminated due t a temprary system issue, yu can change the parameter fr exprt using the Maintain Data Extract Specific Attributes trubleshting activity. Execute the Exprt Data t Files activity again. The files that are already exprted are nt exprted again. Additinally files are exprted using yur new settings. 3. If yu want t restart the exprt f files even thugh the exprt is successfully cmpleted nce, here s what yu need t d: i. Execute the trubleshting activity Un-assign Assigned Dex ID t Repeat Exprt belnging t the Exprt Data t Files activity. The trubleshting activity resets the data extract ID if the exprt is already cmplete. ii. Next, execute the activity Define a Data Extract ID fr File Transfer. Yu can als change the default values f the attributes such as exprt path, maximum file size and maximum blck size. After this activity is successfully cmpleted, it assigns a new extract ID. February

15 ... Hw T Transfer Data Thrugh Files Using SAP TDMS 4.0 iii. Execute the Exprt Data t Files activity again. The activity exprts the data t files using the new extract ID and the settings yu made in the Define a Data Extract ID fr File Transfer activity. SAP TDMS transfers data thrugh files in the binary mde. Hence, ensure that yu transfer files frm ne lcatin (exprt path) t anther lcatin (imprt path) nly using the binary mde. 4.2 Transferring the Files t the Receiver System Befre Data Imprt Fr mre infrmatin, see the prerequisites under Sectin Creating an Imprt Package Yu create an imprt package t cpy data frm the files in the transprt directry t the data cluster in the receiver system. SAP TDMS cpies the data frm the data cluster t the apprpriate tables. The figure belw shws the main steps t be fllwed while creating an imprt package. Create an imprt package Specify the data extract ID Start the data extractin prcess Start the data transfer prcess Figure 7: Creating an Imprt Package Creating an Imprt Package Create a new imprt package t imprt data thrugh files. February

16 Hw T Transfer Data Thrugh Files Using SAP TDMS 4.0 Fr a cmplete list f migratin slutins relevant t imprting data thrugh files, see Sectin 5. The migratin prcess tree fr data imprt cntains the fllwing new activities: Identificatin f Data fr File Imprt Start f File Imprt T imprt the required data, such as HCM data r Banking data, execute the crrespnding prcess tree fr the migratin slutin Specifying the Data Extract ID T specify a data extract ID, prceed as fllws: 1. Assign a data extract t the imprt package by executing the Select Data Extract fr Imprt activity. The Specify Data Extract ID fr Exprt screen appears. The figure belw shws the Specify Data Extract ID fr Exprt screen. Figure 8: Specify Data Extract ID 2. Enter the data extract ID (fr example LOI ) and press Enter. The data extract details appear n the screen. 3. If yu want t imprt the cntrl data and header data but nt the applicatin data, chse the Start Pre-Imprt pushbuttn. After pressing the pre-imprt buttn, the screen belw appears. February

17 5. Sel ect Imprt/Transfer Data -> Pr epare Data Transfer 6. Refresh until all state lights f the acti vity and sub-acti vities are green (t see the sub-acti viti es, chang e t Extended Vi ew ) 7. Sel ect Transfer Data -> Data Transfer Hw T Transfer Data Thrugh Files Using SAP TDMS If yu want t imprt all types f data, chse the Assign pushbuttn and save yur entries Starting Data Extractin fr Imprt Execute the Start Data Extract Imprt activity t imprt the data t the data cluster DMC_INDXCL in the defined sender system. When yu carry ut data imprt, yu can cnfigure the sender system and the receiver system in a single system Starting the Data Transfer Prcess Execute the Data Transfer Start activity. SAP TDMS transfers the data frm the data cluster in the receiver system t the apprpriate tables. 5. Relevant Migratin Slutins Data transfer thrugh files is available fr the fllwing applicatins and migratin slutins: Applicatin Exprt-Package Relevant Imprt Package-Relevant SAP ERP Time-Based Reductin fr SAP ERP Data Imprt Thrugh Files fr SAP ERP Cmpany Cde and Time-Based Reductin fr SAP ERP SAP ERP HCM Transfer f PD and PA Data fr SAP ERP HCM Transfer f PD and PA Data fr SAP ERP HCM (Expert) Transfer f PA Data fr SAP ERP HCM Data Imprt Thrugh Files fr SAP ERP HCM February

18 Hw T Transfer Data Thrugh Files Using SAP TDMS 4.0 SAP Banking Object-Based Reductin fr SAP Banking Data Imprt Thrugh Files fr SAP Banking SAP Retail Object-Based Reductin fr SAP Retail Data Imprt Thrugh Files fr SAP Retail SAP SRM Time-Based Reductin fr SAP SRM Data Imprt Thrugh Files fr SAP SRM SAP Utilities Object-Based Reductin fr SAP Utilities Data Imprt Thrugh Files fr SAP Utilities SAP CRM Time-Based Reductin fr SAP CRM Object-Based Reductin fr SAP CRM fr Utilities Data Imprt Thrugh Files fr SAP CRM Data Imprt Thrugh Files fr SAP CRM fr Utilities SAP SCM Time-Based Reductin fr SAP SCM Data Imprt Thrugh Files fr SAP SCM SAP NetWeaver BW Time-Based Reductin fr SAP NetWeaver BW Data Imprt Thrugh Files fr SAP NetWeaver BW SAP Oil & Gas SAP BPL Time-Based Reductin fr SAP Oil & Gas (Dwnstream) Business Prcess-Specific Transfer fr SAP ERP Data Imprt Thrugh Files fr SAP Oil & Gas (Dwnstream) Data Imprt Thrugh Files fr BPL-based Transfer Data transfer thrugh files is nt available fr the fllwing migratin requirements and migratin slutins: Migratin Requirements System Shell Creatin Stand-Alne Scrambling Client-Specific Data Deletin Migratin Slutins Transfer f Master Data and Custmizing fr SAP ERP Transfer f Master Data and Custmizing fr SAP CRM February

19 Hw T Transfer Data Thrugh Files Using SAP TDMS 4.0 Transfer f Master Data and Custmizing fr SAP SRM Full Transfer f Client-Specific Data fr SAP ERP Full Transfer f Client-Specific Data fr SAP CRM Full Transfer f Client-Specific Data fr SAP SCM Full Transfer f Client-Specific Data fr SAP SRM Full Transfer f Client-Specific Data fr SAP GTS February

20