The business reason that you define to describe exceptions used in unit effectivity. A requirement can be, for example, a specific market, model, or customer.
If this field is empty, the exception is linked to a single effectivity unit.
Exceptions (tcuef0105m000)Use this session to define whether a specific object such as a BOM line or a routing will be used or not to produce a specific item. You must start this session from an object such as a BOM line, a routing operation, or a purchase business partner that is used to produce the item. Select the object, for example the BOM line, and start the Exceptions (tcuef0105m000) session from the appropriate menu. After the session is started, you must define an effectivity unit or a requirement for the exception. After that, you must define when the object is used. This is determined by the settings of the Valid check box and the Standard Configuration check box:
Note It is not logical to both clear or select the Valid check box and the Standard Configuration check box. The following table displays the objects for which exceptions can be defined, and the accompanying session from which the Exceptions (tcuef0105m000) session is started:
Requirement The business reason that you define to describe exceptions used in unit effectivity. A requirement can be, for example, a specific market, model, or customer. If this field is empty, the exception is linked to a single effectivity unit. Effectivity Unit The effectivity unit to which the exception applies. If this field is empty, the exception is linked to a requirement. Object The object to which the exception is attached. The object can refer to:
Valid If this check box is selected, the object (for example, the BOM line) to which the exception is attached, is valid for the effectivity unit.
| |||||||||||||||||||