Rule-based where conditions can be defined based on the mappings IDENT MAPPED_TO IDENT, LP_ID MAPPED_TO LP_ID, or a combination of both. You can use a combination of Rules section and Commodity Code Properties section in the Where Condition Details page for defining the criteria for IDENT MAPPED_TO IDENT. You can use a combination of Rules section and the List Position Properties section in the Where Condition Details page for defining the criteria for LP_ID MAPPED_TO LP_ID.
If you create a where condition based on IDENT MAPPED_TO IDENT, only modules with the Mapped to Column IDENT can be assigned to the where condition in the Where Conditions page.
If you create a where condition based on ‘LP_ID MAPPED_TO LP_ID’, only modules with the Mapped to Column LP_ID can be assigned to the where condition in the Where Conditions page.
If you create a combination of both ‘IDENT MAPPED_TO IDENT’ and ‘LP_ID MAPPED_TO LP_ID’, no validation of the module will be carried out.
The modules that you can select to map with the column are defined in Modules tab of the Query Builder page.
If you insert values into the Table Name, Table Group, and/or Table Detail cells, the MV_WHERE-View will only find table detail based commodity codes and associated idents and you can not make entries in the lower left block of this tab. If the lower left block is already populated with data, you cannot insert values into any one of the Table Name, Table Group, and Table Detail cells.
The columns in the Rules section of the Where Condition Details page refer to the following tables:
Cell |
Table |
---|---|
Commodity Group |
M_COMMODITY_GROUPS |
Commodity Part |
M_PARTS |
Master Table |
M_DICT_TABS |
Table Name |
M_DICT_TABS |
Table Group |
M_TABLE_GROUPS |
Table Detail |
M_TABLE_DETAILS |
Commodity Code |
M_COMMODITY_CODES |
Ident Code |
M_IDENT_CODES |
Input1 |
M_IDENT_CODES |
Input2 |
M_IDENT_CODES |
Input3 |
M_IDENT_CODES |
Input4 |
M_IDENT_CODES |
Input5 |
M_IDENT_CODES |
Criteria for IDENT MAPPED_TO IDENT
If rule based where condition is defined based on mappings IDENT MAPPED_TO IDENT, you can use the Commodity Code Properties section in Where Condition Details page to select properties and values for the ‘Property based’ commodity codes of the selected where condition.
Use the following operators for combining properties and values:
Operator |
Description |
---|---|
= <> < <= > >= |
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 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 |
For values of type VARCHAR2, use quotes and parentheses.
Criteria for LP_ID MAPPED_TO LP_ID
If you define rule based where condition based on mappings LP_ID MAPPED_TO LP_ID, use the List Position Properties section in the Where Condition Details page to select properties and values to limit the selected idents. If the selected property has a Derived_From or valid values assigned on Properties page, you can select a value from a list of values.
Use the following operators for combining properties and values:
Operator |
Description |
---|---|
= <> < <= > >= |
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 the 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 SQ wildcard matching. You can use _ (underscore) as a 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 |
For values of type VARCHAR2, use quotes and parentheses.