Field filters
Last updated
Was this helpful?
Last updated
Was this helpful?
It is possible to create specific filters that can be added into fields in the app master data. These filter options should then be referenced against the relevant field in the ‘Source List Option’ of the Detail Screen Configuration. See below for example:
Adding a FILTER configuration option to a specific field allows the selection criteria available for that field to be reduced. Typical filters could be for plant (PLANT_FILTER), storage location (SLOC_FILTER), movement type (GI_MTYPE_FILTER), etc.
A FILTER configuration option should be created in configuration with the data type ‘G Selection Range Filter’.
The naming convention is that the configuration option should always end with ‘_FILTER’.
Examples are:
PLANT_FILTER
SLOC_FILTER
When maintaining the entries for a FILTER, it is possible to INCLUDE a certain set of entries; EXCLUDE a set of entries; or possibly use a combination of both options.
INCLUDE is entered into the app master data with the ‘Sign’ as ‘I’ and EXCLUDE is entered with ‘E’.
The ‘Option’ column is usually filled with either ‘EQ’ (Equal) for a single value entered in the ‘Low Value’ column, or ‘BT’ (Between) for entering a range from the ‘Low Value’ column to the ‘High Value’ column.
The example above uses a movement type filter: it was required to include movement types 311 through to 350 with the exception (exclude) of movement type 317 to 320 and 340.
It is possible to use other Boolean operators as listed below in the ‘Option’ column, but generally most filter selection should be possible using the EQ and BT options with either INCLUDE or EXCLUDE as appropriate:
LT – Less than
LE – Less than or equal to
NE – Not equal to
GT – Greater than
GE – Greater than or equal to
NP – Not in pattern
CP – Contained in pattern
