This paper describes 7 best practices that many companies have adopted in automating the upload of Excel data into SAP. Adopting these best practices will alleviate many of the pains that business users and IT analysts face in uploading Excel data to SAP.
A WHITE PAPER BY WINSHUTTLE, INC. 1729 208TH STREET SE, SUITE 202 BOTHELL, WA 98012, USA (800) 711-9798 WWW.WINSHUTTLE.COM
Routine uploading of data from Excel files to SAP remains a thorny challenge facing many companies today. Business users are feeling the pain of manually re-keying Excel data into SAP; while programmers in IT departments are having to constantly write new programs to automate the upload of Excel files to SAP. This article describes 7 best-practices that many companies have adopted in automating the upload of Excel data into SAP. Adopting these best practices will alleviate many of the pains that business users and IT analysts face in uploading Excel data to SAP.
1. Avoid Programming. With the several non-programming choices available to connect Excel and SAP, custom programming in ABAP or VB should be the absolute last resort for ad hoc uploading Excel data to SAP. Not only is programming expensive and time consuming; a program that will be used only once or even once a year particularly wasteful. Further, creating robust programs require a fair bit of testing and if a program has not been well-tested, it could be dangerous and cause irreparable data damage. Use a scripting or a non-programming approach as much as possible. SAP provided tools such as BDC, CATT, LSMW, and third party tools such as Winshuttle's TxShuttle will allow you to avoid programming to a large extent. 2. Do Not Upload Directly to SAP tables. While this point is very obvious, it cannot be overemphasized. Writing directly to SAP tables avoids all the data validation and checks and balances that happen when creating data through the normal SAP transactions. So, avoid using any method that writes directly to SAP tables. Always upload data via the pre-configured SAP transactions or BAPIs. Again, using tools such as BDC, CATT, or LSMW, or TxShuttle will allow the upload of data via SAP transactions instead of writing directly to SAP tables. 3. Choose a Record, Map, and Run strategy. A record, map, and run strategy generally involves first recording an SAP transaction where data needs to be uploaded. The recording step is followed by a mapping step where the SAP data fields captured during the recording are mapped to the Excel fields. Finally, the transaction is run over and over again with the different rows of data in the Excel file. A Record, Map, and Run strategy is similar to recording and running macros for automating routine tasks. The advantages of choosing a record, map, and run strategy are that (a) it is very general a... [download for more]