Batch classification

[maarten_muetgeert2]

We use batch numbers unique at client level. When i record the UD this will be written to the batch classification. We use this in batch selection during production and sales.

Now i have the followng problem. When I release (AA, Accept) a batch in plant A this will be stored in the batch classification. Now I use a STO to transport part of it from plant A to B. During transport something happened and no I have to Reject (RD) the batch. When i now make the UD the batch classification will be overwritten. But the remaining part in plant A can still be correct.

How to handle this? Should we split of the batch?

[Former Member · Accepted solution]

Standard batch characteristics like UD code can have only one value. So when you make another UD original value will be overwritten.

Try this to move partial quantity of batch to another plant.

1. Using 309 movement split original batch in two before transfer.

2. Transfer the split quanity using STO, as batch numbers are different you can have two separate UD codes.

When we split the batch, we normally keep th original batch number but suffix batch number with X, so we can easily find the original batch and new batch.