Item demands are records, that are automatically generated based on an item disposition according to the Gozinto Method. Starting point is a Product Item E1, which consist of the items B2 and B3, etc..
The resolved BOM for item E1 is based on CX_ALLOCATION_TXN objects. Successors of each single BOM entry are CX_TRANSACTION object, which are all kept as a sub-transaction in a CX_ITEM_DEMAND object . Exceptions are only BOM entries that are marked as "engineering components" (see below).
In each item demand, the quantity field consists of BOM item quantity objects (baseAmount, amount), if this item is actually required. Item demand without quantity elements are first marked as: dispositionEnum = (-1).
One special case occurs, whenever single components are marked in a BOM as "engineering
component". These are components which - from the engineering point of view
- increase BOM readability /
modularization. From production
perspective, this component is not generated separately and in advance, but
instead directly with the parent component. In our example now component B1 is an
engineering component. The item demand is created as follows:
As the image shows, component B1 basically "disappears" from the item demand. T1 and T2 "move up" by one production step.
To "move up" by only one single piece in a component (B1 as an engineering component modified the production stage of both pieces T1 and T2), if this equates to a "loose piece" scenario (Disposition Component):
In the case above, T3 got defined as a "loose piece" inside the component E1. With this, it is "taken" from component B3 and is now - dispositive - part of component E1. With this, T3 also modifies its production step.
As another form of engineering component disposition modification, it is possible to insert a completely new "disposition component". In the following for example, it is required that component B2 and B3 have to be handled as a component D1 in an preliminary stage, before it is the completed product E1(also see Disposition Component):
