Friday Features Series: Allowed Values

By Jennifer Hwang on November 18, 2016

I’m excited to kick off a new blog series where we’ll dive into interesting Winshuttle product features! Our first Friday Features post hones in on a much improved feature found in Studio v11: Allowed Values. The Allowed Values features enables you to control what value, values, or range of values are valid or invalid for a certain field in a Winshuttle script.  In addition to values that are allowed in SAP, this gives you even more granular control, if needed.  You can easily use Winshuttle to apply business validation rules to SAP fields, without having to make changes within SAP.

In Studio 10, Allowed Values was called ‘Validate by List’ and only let you set a list of fixed allowable values from one item on upward. In Studio v11, there are so many more options available! Along with the list of allowable values that were already available, you now have the opposite option too.  You can define a field to have any allowable value, except what’s on your not allowed list. Here’s an example where a Loading Group can have any value except 0005.not-allowed1

Operators

In Studio v11 you can also use standard operators for your allowed values. For example, in the image below, ‘Standard Price’ needs to be between 100.00 and 250.00. You can also use operators like greater than, less than, not between, contains, starts with, ends with, etc. Now you have more control than ever to ensure Winshuttle users are entering in the right values.between-1

Dynamic Values

Why stop there – there’s more! Your defined allowed values do not have to be static in Studio v11. Now, you can define dynamic lookup lists by pointing them to  an Excel or text file that contains the allowable values. You can update these files whenever they need to be, to contain the allowable values for that moment. They can be external files or the current data file, so if your allowed values list needs to change, you don’t need to change the property in the script itself. Simply update the dataset that the dynamic lookup list is pointing to. In this example, you can see the values allowed for the Purchasing Group are being pulled from column A from another tab in the current data file.dynamiclist1

Conditional Values

To take things up a notch, you can also use IF conditions to have conditionally allowed values. Let’s say you have a material creation template that allows creation of finished goods (FERT) as well as raw materials (ROH). The first set of allowed values would go in the material type field, and the only values allowed within that template would be FERT and ROH; even though there are many other values that SAP allows. For a FERT, you would only want base units of measure to be EA or PC, whereas ROH could have a base unit of measure from a much wider range. You can set different allowed values for two sets of the same field, based on the conditional usage scenario.conditionalallowed1

Offline Data Check

Wondering what the runtime experience is like? There is a new Check Data button that will run through all your Allowed Values settings, as well as Required Data settings to test outside of SAP. This allows you to test all of those “rules” you’ve built in before you do any validations against your SAP system. All these improvements were implemented based on feedback from our customers. We hope you will take advantage of these new features to help you better manage your SAP data. Stay tuned for the next Friday Features on script & template version control!checkdata1


Questions or comments about this article?

Tweet @Winshuttle to continue the conversation!