Within the management of non-relevant batch management functionality, there are three methods of determining when the batch is not relevant:1 -Batches rejected not relevant according to the error code of their intermediates. This option will mark the relationship between the intermediate and the batch as not relevant if the intermediate error code is in the table / EDGE / SII_ERELEV, this table is accessible from the scope menu:
2 - Intermediates in rejected lots that were subsequently accepted in another lot. This option will mark the relationship between the intermediate and the lot as not relevant if the intermediate was rejected and subsequently accepted in another. For example, if we have a rejected lot with 5 intermediates and subsequently we have sent those intermediates in other lots and they were accepted, the first rejected lot will be marked as not relevant since all the intermediates contained in it were subsequently accepted.
3 - According to the process status of the batch. If the batch has one of the process states parameterized in the table / EDGE / SII_SLNR, the batch will not be relevant. (This form of non-relevant determination does not mark anything in BD since it does so directly by the state of the lot). The table / EDGE / SII_SLNR is accessible from the scope menu:
An entry example for this table would be as follows:
It indicates that the discarded process status is not relevant and the flag is marked to take it into account.