Skip to Content
0
Nov 27, 2011 at 10:58 AM

MIGO subcontracting batch determination

229 Views

hi guys,

one of our customers just upgraded to ECC605 and now batch determination changed its behavior:

in the same MIGO session two items have the same component 'A' to be issued from vendor stock O (mov type 543); for the first component A the batch determination is OK; for the second one the batch determination still proposes the same batches given for the first component.

Before the upgrade (it was another ECC6.0 but with older packages) the second batch determination was proposing only batches not reserved by the first one.

we had a look in batch determination settings, looks ok and my few tests did not give any result.

we had also a look in availability check settings but with no results and also ATP is not at batch level I guess.

Any suggestion?

thank you in advance, regars, Lucilla and Stefano