On the A.60.06 Where Conditions screen, you can define and maintain customized where conditions. These where conditions can be used in certain Smart Materials modules that need a limited view on the database content. For example, you define where conditions to select specific material for a requisition when running an MTO job.
Technically, a where condition corresponds with a database object called VIEW, which can be thought of as a 'stored query'. From the data you enter on this screen, the software will generate this view and assign a unique name to it. The module assigned to the where condition can then access the contents of this view by using this (internal) view name. You do not need to be concerned with these technical details, however. Instead, if you work with this screen, you will be presented with the logical aspects of selecting a certain well-defined subset of your data.
There are two methods of creating a where condition:
-
Attribute based
-
Rule based
The Attribute Based where conditions require the creation of an alias (attribute) that references the base table structure of Smart Materials, whereas the Rule Based where conditions can be built from predefined tables and attributes.
The rule based where conditions can be used similarly to the attribute based where conditions, with one restriction. The conditions defined in the upper section of the Rules tab are joined using the OR operator. This means you cannot define additional conditions that also have to be fulfilled to get a result. You can only define alternative conditions, which means any of the conditions must be fulfilled.
When creating a new where condition in the first (Where Conditions) block on the A.60.06 screen, select the appropriate type from the Kind of drop-down list. In the second (Attributes for Where Conditions) block, the corresponding tab (Attributes or Rules) will automatically be displayed.
It is NOT possible to use both kinds of definitions for one view.