Today, we take a look at SAP Display Transactions (e.g. FBL1N, FBL3N, and FBL5N) and ask the question that tends to come up which is “How does Winshuttle help streamline and improve SAP “Display Transaction’s - how does this improve productivity of my SAP users?
Today, we take a look at SAP Display Transactions (e.g. FBL1N, FBL3N, and FBL5N) and ask the question that tends to come up which is “How does Winshuttle help streamline and improve SAP “Display Transaction’s – how does this improve productivity of my SAP users…?” First question you have to ask is “Why do Winshuttle’s customers report that automating “display” transactions result in significant time savings over using the SAP GUI?” To answer this question, let’s take a closer look at one of these transactions…
FBL1N/3N/5N – Vendor/GL Account/Customer Line Item Display
A common use case with FBL3N might deal with a document dispute or inquiry of some sort which includes researching a document for a given customer or vendor, identifying it and then editing/saving it. Many Winshuttle customers incorporate the view – edit approach to this transaction and therefore it makes for a great candidate to automate with Winshuttle. Plus it is super awesome to be able to do 100’s if not 1,000’s of FLB1/3/5N transactions with one simple spreadsheet update. Please note the following FBL3N screens for an example of how one has to process through a number of fields, screens to do this task - then check out the simplicity of the Excel spreadsheet example.
In the following table notice the sample time savings of 636 Full Time Employee days (8 hour work days) for the FBL1/3/5N transactions – this is from a recent value assessment report done for a customer in Europe:
MINIMUM SECS SAVED
AVERAGE SECS SAVED
CONVERT SECS TO FTES
FTE DAYS SAVED PER YEAR
G/L Account Line Items
Vendor Line Items
Customer Line Items
To get an idea of how this works let’s take a closer look at the FBL3N – G/L Account Line Items transaction:
# of FBL3N trans during- ST03N reporting period (assume 4:1 screen to transactions)
31,505 steps / 7,876 transactions
Minimum seconds saved per transaction (WS database - see example table of ME21N WS savings from WS customers)
ST03N work days covered in ST03N reports
Minimum seconds saved * number of transactions = total seconds saved during ST03N reporting period
732,491 total seconds saved
Total Seconds Saved / 60 seconds / 60 Minutes / 8 hours / ST03N work days covered equals -single day’s net FTE saving’
# of work days per annum
225 days per year (this is a European customer)
Single day’s net FTE saving times # of work days per annum = FTE DAYS saved per annum to process ME21N
636 FTE Days
The key figure is the minimum time savings associated with this transaction of 93 seconds… this is the LEAST amount of time saved – we do this so we can be as conservative as possible in making these projections based on actual customer usage.
So the bottom line here is that we can begin to understand the impact of Winshuttle on ERP usability by using actual customer usage metrics. Notice how it helps our clients to better evaluate why transactions run more efficiently with Winshuttle, what transactions are best to tackle with Winshuttle and overall, how these transactions are being used. Given the quantity and complexities associated with over 91,000 SAP Transaction Codes – you can see that this approach can help you find that “Tcode in the Haystack”…
Questions or comments about this article?
Tweet @Winshuttle to continue the conversation!