Title
Item with no version. This may cause inconsistencies in the MRP plan.
Severity
Warning message.
Data
ID of the item that does not have any version.
Explanation
During SRP computation or when matching requirements, the computation engine could not create a WO for the item mentioned, because there is no existing version for that item.
The missing WO can create inconsistencies in the MRP plan. It may also affect other items whose definition is otherwise correct.
Example: The data model includes BOM FP1 <-- SF1 <-- SF2. If SF2 has no item version, it is impossible to readjust it, which implies it is also impossible to readjust SF1.
In fact, the SRP engine builds a memory hierarchy of items, starting from those at the highest level — that is, those that do not have any component (SF2 in the example). This hierarchy ignores the items that do not have a version, because their definition is invalid.
Therefore, the SRP engine has no access to SF1, and cannot readjust it.
If that same BOM had SF1 requiring SF2 and SF3, with SF3 having an item version, the SRP engine would readjust SF3. Because the SRP engine would then have a path to SF1 from an item at the highest level of the BOM (SF3), it would also readjust SF1.
Action
Create at least one item version for the item concerned.
¿Le ha sido útil este artículo?
¡Qué bien!
Gracias por sus comentarios
¡Sentimos mucho no haber sido de ayuda!
Gracias por sus comentarios
Sus comentarios se han enviado
Agradecemos su esfuerzo e intentaremos corregir el artículo