Tips

If a required view (table in MVIEW:MMS) is not processed by the material master maintenance, the corresponding filter will not be valid.

If operators „=" or „<>" are used, it is possible to mask the value in the filters and activation (but not in the Selection of Control Groups).

• Example: Check value = M* and Operator „=" → all values starting with an M are valid.

In general multiple filter entries are linked as AND, e.g. all conditions must be fulfilled (for special requirements please refer to Dependencies / Dependent values, field Type). But if the same field in a related filter definition is entered several times, the definitions for this field will always be linked OR.

• Example

Filter is valid if

• MARA-LABOR = '001' OR '002' AND MARA-MTART = 'HALB'

• Exception: „Not equal test" (<>) on the same field will always be linked AND, because using OR for multiple entries will always return one valid result.

The date format is JJJJMMDD e.g. 20041201 for December 1st 2004.

If it is required to check initially (e.g. empty or zero), „<INITIAL>" must be entered. For the Selection of Control Groups this entry cannot be used. „<INITIAL>" will only be applied on loaded views, see above tip 1.

For numeric values (packed and numeric string) the following additional rules must be considered:

• Left-aligned, no zero ahead.

• Decimal separator: dot ( . ).

• No apostrophe ( ´ ) or other symbols to separate thousands.

• Minus sign always before the number.

• If numeric fields with decimal places are test „equal" or „not equal", the test values must be either marked with a * (e.g. 1.*) or must have the exact same number or decimal places.

Minus sign always before the number.

Characteristic values must always follow their internal syntax.

For selection fields (  ) use „X" or leave blank.

Creating a material master record (MM01), certain MVIEW:MMS fields may be initially. For example MARA-ERNAM will be implemented by the material master shortly before updating.

If ProMaterialData is used together with object dependencies from ProConfiguration (CFM), ProMaterialData will not show a new material status which has been set (plant specific, cross plant, distribution chain).

• ProMaterialData data updates are carried out BEFORE updating CFM object dependencies.

• In general ProMaterialData and ProConfiguration should not handle the same status fields.

• To avoid ProMaterialData activities triggered by CFM object dependencies, and if no further actions are necessary it may be possible to use option „set directly" in CFM.

For activating a control group using a filter on Plant do the following: