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, the object will not be part of the item’s standard configuration. However, to meet a specific requirement, the object is added to the configuration for a specific effectivity unit or requirement if for example, a customer requests the option.
  • If you select the Standard Configuration check box, the object will be part of the item’s standard configuration. However, the object can be omitted for a specific effectivity unit or requirement, for example, on customer request.
  • Selecting both check boxes is not recommended.

The following table displays the objects for which exceptions can be defined, and the accompanying session from which the Exceptions (tcuef0105m000) session is started:

ObjectSession from which the definition of exceptions is started
Engineering BOM lineEngineering BOM (tiedm1110m000)
Job Shop BOM lineJob Shop Bill of Material (tibom3600m000)
RoutingJob Shop Routings (tirou4100m000)
Routing OperationReference Operations (tirou4150m000)
Source of supplySourcing Strategy (cprpd7110m000)
Item – supplier dataItems - Purchase Business Partner (tdipu0110m000)
Assembly BOMAssembly BOM and Operations (tiapl2520m000)
Assembly OperationsOperation Assignments (tiapl1510m000)
Generic BOMGeneric BOMs (tipcf3110m000)
Production BOM lineProduction Bill of Material (timfc3600m000)

 

Related topics

 

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
  • Job Shop Routings
  • Reference 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.