VLOG #1: Data validation rules
Inconsistencies in your finance processes and procedures drives inefficiency, and time spent on rework can often be traced to ineffective processes and procedures; especially in the arena of the close, consolidation and reporting.
In this first of 5 part finance VLOG series, I will review how you can enhance your transaction automation process with validation rules, improving your process efficiency for SAP data validation.
Hi my name is Clinton Jones and I am a Director of Product Management at Winshuttle, and today I thought I would quickly go through some of the ways you can enhance transaction processing automation with validation rules, and how those might work within Winshuttle products. So SAP is configured to only accept certain kinds of data, and when we switch on validation in our Studio product that validation can be tested by physically calling transaction and then before we physically save transaction, we get a response back from SAP to say yes the data is all good or it’s only partially good. But we can enhance that further and one of the ways we can do that is by making use of a feature called offline validation. And what offline validation effectively is within Winshuttle mapper you can define field level data validation – so you can define for example whether a field is mandatory or not mandatory, you can define a pick-list for it so you can define a number of items that are part of a restricted list, and what you can also do is you can define types that those fields might have. Once you’ve defined these types what happens is you don’t have to have an SAP connection to actually check that the data conforms to these rules, within Studio 11 there is a button you press that just gives you an offline data validation and actually brings back the coordinates of the results and where the problems might be. That is the offline scenario.
But you also have an online scenario which requires an SAP credential so you have to have a connection to SAP – and again it is a slightly smaller button on the ribbon , but it gives you a number of different options. So you can either do line level validation for all of the lines within a document, or you can just do them for some of the lines, or a range of lines.
And the third part to this is what we refer to as simulate – and what this does is this actually checks the whole document. Again here if you have multiple documents within one workbook, you can simulate just one or all of them or you can simulate all of them or a subset.
The big difference between these three approaches is that first doesn’t require SAP credentials, these two do require SAP credentials. This particular one looks at the line level, this one looks at the header, so the whole document. So in finance, if your journal is unbalanced, this will actually register that there is a problem with that journal because it is unbalanced.
Stay tuned for the next post – Finance VLOG Series Tip #2: Automation!
Questions or comments about this article?
Tweet @uploadsap to continue the conversation!