The next step is to build the selection criteria for the selected where condition. You do this in the second (Attributes for the Where Condition) block on A.60.06 by selecting predefined attributes from A.60.07 in the Attribute field, assigning an appropriate operator in the Operator field, and entering a criterion value in the Value field. In this way, you define which attributes need a mapping to one of the predefined result columns in the database view.
The available operators with their meanings are listed below.
|
Operator |
Description |
|---|---|
|
MAPPED TO |
This is a system internal operator used to define the column mapping. Mapping can be created to the database columns IDENT, LP_ID, LN_ID, RLI_ID. Example: IDENT MAPPED TO IDENT This creates the relation of the alias (attribute) IDENT to the database column IDENT. |
|
= <> < <= > >= |
These operators perform comparisons. Examples: ATTR = 'XA' -> matches only values equal to XA ATTR <= 5 -> matches any value less than or equal 5 |
|
BETWEEN NOT BETWEEN |
For these operators, you must define a range as a comparison value. Example: ATTR BETWEEN 2 AND 4 -> matches any values greater than 2 and less than 4 ATTR NOT BETWEEN 10 AND 50 -> matches any values less than 10 and greater 50 |
|
LIKE NOT LIKE |
These operators perform SQL wildcard matching. You can use _ (underscore) as the placeholder for exactly one character, or % (percent) to match any combination of characters. Examples: ATTR LIKE 'X%' matches any value beginning with X. ATTR LIKE 'B_M' matches any three character value beginning with B and having M as the third character. ATTR NOT LIKE ‘A%’ matches any value not beginning with A. |
|
IN |
When using this operator, you must define a list of values to be included in the selection as the corresponding value. Example: ATTR IN ('XX', 'YY', 'ZZ') -> will only fetch records with the assigned values ‘XX’, ‘YY’, or ‘ZZ’. |
|
NOT IN |
When using this operator, you must define a list of values to be excluded from the selection as the corresponding value. Example: ATTR NOT IN ('AB', 'AC', 'AD') -> will only fetch records not having the values ‘AB’, ‘AC’, or ‘AD’ assigned. |
|
IS |
This operator checks for empty fields. You must define either NULL or NOT NULL as the corresponding value. Example: ATTR IS NOT NULL |
|
INPUT |
Can be used to create parameters for formulas. This attribute will become a field in the view definition. Refer to the online help of the A.60.08 Define Formulas screen for a detailed explanation. |
|
OUTPUT |
Can be used to create an updateable attribute for use in a formula. Internally, this will include the ROWID of the base table record in the result set of the view. Refer to the online help of the A.60.08 Define Formulas screen for a detailed explanation. |
|
DISPLAY |
Can be used to include an attribute for display only as a column in the view definition. |
For values of type VARCHAR2, do not forget the quotes and parentheses.
The predefined columns are IDENT, LN_ID, LP_ID and RLI_ID. These refer to the primary key columns of tables M_IDENTS (Ident Data), M_LIST_NODES (BOM structure data), M_LIST_POS (BOM positions data) and M_REQ_LINE_ITEMS (Requisition line items data), respectively. See also the table display of these relations below.
|
Predefined column |
Linked table |
Primary key |
Comment |
|---|---|---|---|
|
IDENT |
M_IDENTS |
IDENT |
Ident data |
|
LN_ID |
M_LIST_NODES |
LN_ID |
BOM structure data |
|
LP_ID |
M_LIST_POS |
LP_ID |
BOM positions data |
|
RLI_ID |
M_REQ_LINE_ITEMS |
RLI_ID |
Requisition line items data |
You must create at least one mapping to one of these columns, which from a logical point of view means that you are selecting specific data from one of the mentioned tables. The other attributes that are not involved in mapping serve to restrict this data according to the selection criteria.
You are not free to choose any mapping, however. Instead, specific modules need a specific column mapped, because their functionality depends on the presence of a primary key column of a specific table in the result set of the view. You must pay attention to the following requirements:
Requisition templates [R.10.41]
Requisition templates must have the column IDENT mapped, because template views perform a selection based on the kind of material for a particular requisition.
Requisition split criteria [R.10.42]
Requisition split conditions must have the column LP_ID mapped, because split sets define how BOM position data is split up so that they make up different requisitions.
BOM Rules [B.10.05]
These rules define how assembly structures are exploded in different stages of a project. You need to map the column IDENT for conditions that you wish to assign to these rules, because the parts that make up an assembly are identified by their idents.
Conditions for other BOM tools [B.20.01.*]
The BOM tools operate on the table M_LIST_POS, so in order to define the data they should operate upon, you must have the column LP_ID mapped.
The MAPPED_TO record in the second block will automatically be generated when saving the new where condition, based on the assigned module and in relation to the definition of the A.60.05 Where Condition Modules screen, as described above in the Where Condition Header Definition section.
There must be at least one column mapping defined for the where condition. Duplicate
mappings are not allowed.
Using the Boolean field, you can connect two conditions with a Boolean operator. Only the operators ‘AND’ and ‘OR’ are allowed; the negation NOT is handled using the comparison operator.
Select the Case check box to define this condition as a case-sensitive condition.
Grouping of Attributes
To group attributes, select the Grp check box of two attributes to be grouped. Then click the 
button to group the attributes. Grouping will be displayed by the brackets as shown
in the picture above. In the sample above, the grouping was made for the attribute
PURC_DEST with values ‘NG’, ‘98’, and IS NULL.
To cancel the grouping, you must select again the Grp check box of two attributes and then click the 
button. To cancel all groupings of the where condition, click the 
button.
Mapping attributes cannot be grouped.