Material getting set for Batch Management in O/B delivery

[former_member221091]

Hi Folks,

For a material which is not batch managed, I created an outbound delivery.

For some reason, the material is getting set as 'BatchManagement' even though the Batch Management indicator is not set.

Due to this PGI is not possible.

Any thoughts on why the 'Batch Management' indicator has been set and how to resolve this?

Regards,

[raviraj_sharma · Accepted solution]

what is the Batch level set in your system?

If it is at batch/ mateirlal level, then may be in some other senario user must have slected Batch management in the basic view, this will be applicable throught the system then..

if your batch level is "plant" , then may be in the supplying plant it will be Not batch managed, but in receiving plant it could be batch managed.

[JL23]

Your material is probably split valuated.

check in MM03 at accounting view if there is an entry valuation category field

[former_member221091]

Hi Jürgen ,

I checked the valuation category field is blank. Anything else had to be checked?

Regards,

[JL23]

what is the error message number?

[former_member221091]

Hi Jürgen ,

I am unable to replicate this problem in Q. Its occuring only in P while doing a goods issue.

Message is

"The batches are not defined for delivery item XXXXXX".

As I said earlier, we have not set the batch management check box in MM.

However the outbound delivery has the batch management check box selected .

Anything I missed to check? Q is almost identical to P. But still issue is only in P.

Regards,

[JL23]

This sounds like a inconsistency, the question is just what/who has caused it.

Can it be that the delivery was created as the batch management flag was set active in material master, and it got removed later (somehow - not with standard maintenance),

Or is it set in the delivery with a userexit.

Just assumptions......but I have seen often cases where people changed the batch management indicator directly in the tables because it is so restrictive with MM02. and this is a bad mistake of the users.

[former_member221091]

Hi Jürgen L. et al,

I had checked the history, no changes done to the Batch Managment field.

I raised an OSS note for this. Was provided with a correction report. Not still possible to determine the root of the cause.

Note that the report did work only in Production as there were no inconsistencies in other environs.

The report did table level updates and PGI was possible.

Thanks.