| # 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: If you select the Valid check box, and clear the Standard Configuration check box, the object is not part of the item’s standard configuration. However, to meet a specific requirement, for example, a customer requirement, the object is added to the configuration for a specific effectivity unit or requirement. If you clear the Valid check box, and select the Standard Configuration check box, the object is part of the item’s standard configuration. However, the object can be omitted for a specific effectivity unit or requirement, for example, when a customer demands so. 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:
Object | Session from which the definition of exceptions is started
--- | ---
Engineering BOM line | Engineering BOM (tiedm1110m000)
Production BOM line | Bill of Material (tibom1110m000)
Routing | Item - Routings (tirou1101m000)
Routing Operation | Routing Operations (tirou1102m000)
Source of supply | Sourcing Strategy (cprpd7110m000)
Item – supplier data | Items - Purchase Business Partner (tdipu0110m000)
Engineering Module | Assembly BOM and Operations (tiapl2520m000)
Related topics Overview of unit effectivity Exceptions in unit effectivity 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: Engineering bill of material (EBOM) lines. Production bill of material (PBOM) lines. Routings. Routing operations. Sourcing strategies. Item – supplier data. 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. |