Tim Woods Series #2: Did you Accidentally Delete an LSMW Script?

By Winshuttle Staff Blogger on Mar 22, 2017

In the 2nd post in this TIM WOODS series, find out how Winshuttle helps eliminate inventory challenges in data management when working with SAP’s LSMW.

Managing inventory templates

Angry at LSMW

Think about LSMW in your business, and how it’s developed and grown in adoption. It’s often the default choice of IT for data uploads to SAP because at face value, it seems to be an easy low cost option. When you decide to create a new LSMW script or recycle or reuse an existing one – it’s pretty easy to just create a new one, and this is often the approach users follow.

If  your development process is outsourced, you probably don’t know how your LSMW scripts are managed. How do you know if your service provider is just recycling existing solutions or rebuilding stuff you already paid for? You’re left in the dark.

From LSMW’s initial screen, it’s fairly easy to accidentally delete an LSMW script. No audit trail, no history – poof! You may have a recovery history you can rely on, but this isn’t usually enabled and if it is, it often limits the number of items or purges after a period of time. On SAP SCN, you will find suggestions on how to recover your project, but most seem to think once it’s dead, it’s gone! If you’re a little OCD you could export your project to a text file and then re-import it, but then you’d have to manage your projects in more than one place.

As a business user, you often won’t have access to LSMW. Auditors and IT won’t allow you to have access because LSMW is meant to be used as a developer or IT administration tool. Some of your templates will work with your LSMW script – but you won’t know unless you’re really disciplined in naming and creating inventories of data templates.

A new perspective on uploads

Winshuttle’s approach to data upload tools is quite different than using LSMW.  With Winshuttle Studio, whether your script is based on a transaction recording,  a BAPI or a query, the script is local to your machine and not necessarily specifically tied to any specific SAP system.

If you have the right application and the correct license assignments, you can quickly examine the characteristics of your script and identify its inner workings by looking at the mapper.  If you deploy Studio with User Governance, you can easily manage your scripts and templates centrally.

Winshuttle Studio allows you to create explicit relationships between the data template and the integration script, enabling you to modify the relationships with cells and columns in Excel. If you choose to publish the script to the workbook then wherever the workbook goes, the integration object goes with it.  Only users with valid Winshuttle author or runner licenses can use the integration objects as scripts or embedded scripts, but they have to have the requisite SAP access in the target system in order to use the scripts.

End to end, business and IT users have far more options for managing and keeping track of what they develop and use in Studio than is typically available with LSMW. Learn more about the benefits to using Studio vs LSMW here.

Check out other posts in this series:

About the author

Staff Blogger

The Winshuttle blog is written by professional thought leaders who are dedicated to providing content on a variety of topics, including industry news, best practices, software updates, continued education, tips and techniques, and much more.

Questions or comments about this article?

Tweet @Winshuttle to continue the conversation!