Production: Improved serial number validation in the Life cycle management (LCM) application
K
Knut Sætre Waka
started a topic
24 days ago
Classification: IMPORTANT
The goal of assigning serial numbers to individual Product units (LCM) is to make sure that its history is identifiable as it travels through the supply chain.
We are now making changes to how the validation logic functions when serial numbers are added through manual input via the Life cycle management (LCM) application.
Validation logic to be replaced
From the Life cycle management (LCM) application, users could previously enter any serial number into the SerialNo field in the Part list tab and in the Change LCM Part popup:
The entry was accepted if the entered serial number was available and existed in the Serial numbers (SNO) archive for Goods reception (SSA).
But if the serial number was already in use, then the manual input was rejected.
However, if the serial number was not found in the Serial numbers (SNO) archive, it was also accepted, regardless of whether the Goods reception (SSA) contained serial numbers, or not.
This logic could sometimes lead to traceability issues.
To simplify the rules and to improve upon the integrity of serial numbers we are therefore making the following changes:
New validation logic
Manual entries in the Life cycle management (LCM) application will now check the Goods reception (SSA) quantity against the Serial numbers (SNO) quantity.
If there is a quantity mismatch, no validation will be done except for serial numbers defined in the Goods reception (SSA) that are also used by any other Product unit (LCM).
An error message will inform the user, if the serial number is in use.
Any available serial number can be added via the previously mentioned fields in the Life cycle management (LCM) application.
If there is a quantity match, a validation will be run and all serial numbers must be available in the Serial numbers (SNO) archive.
If those criteria are met, the entry will be accepted.
Please note that an earlier version was previously released, but required to be rolled back due to unforeseen consequences.
Knut Sætre Waka
Classification: IMPORTANT
The goal of assigning serial numbers to individual Product units (LCM) is to make sure that its history is identifiable as it travels through the supply chain.
We are now making changes to how the validation logic functions when serial numbers are added through manual input via the Life cycle management (LCM) application.
Validation logic to be replaced
From the Life cycle management (LCM) application, users could previously enter any serial number into the SerialNo field in the Part list tab and in the Change LCM Part popup:
The entry was accepted if the entered serial number was available and existed in the Serial numbers (SNO) archive for Goods reception (SSA).
But if the serial number was already in use, then the manual input was rejected.
However, if the serial number was not found in the Serial numbers (SNO) archive, it was also accepted, regardless of whether the Goods reception (SSA) contained serial numbers, or not.
This logic could sometimes lead to traceability issues.
To simplify the rules and to improve upon the integrity of serial numbers we are therefore making the following changes:
New validation logic
Manual entries in the Life cycle management (LCM) application will now check the Goods reception (SSA) quantity against the Serial numbers (SNO) quantity.
If there is a quantity mismatch, no validation will be done except for serial numbers defined in the Goods reception (SSA) that are also used by any other Product unit (LCM).
An error message will inform the user, if the serial number is in use.
Any available serial number can be added via the previously mentioned fields in the Life cycle management (LCM) application.
If there is a quantity match, a validation will be run and all serial numbers must be available in the Serial numbers (SNO) archive.
If those criteria are met, the entry will be accepted.
Please note that an earlier version was previously released, but required to be rolled back due to unforeseen consequences.
Release date: 14 April 2025