cancel
Showing results for 
Search instead for 
Did you mean: 

M7043 during 311 movement of value-splitted material with Batch

claudio_carrara
Active Participant
0 Kudos

311.jpgAfter setting split-valuation for a material, for managing 2 different valutation class at the same time, I have this error when try to change Valutation-type for a batch managed material using MIGO and 311 movement type.
The system issue the Error M7-043 Valutation type ZP differs from valuation type of Batch ZV. In my scenario ZP is the destination Valuation type and ZV the Origin. The enclosed image can help to undertand the problem. The same error is issued if I don't change Stogare location. I've tried to search on OSS and SCN website but I don't find a solution. Thanks for help.

Accepted Solutions (0)

Answers (2)

Answers (2)

JL23
Active Contributor
0 Kudos

OSS note 2474477 speaks about debugging to find the real error.

It gave an example for a mandatory field. If you have made the reason for movement mandatory then SAP expects an entry, You can do such entries in MIGO, but nobody can do it in background programs like it is with the 340 movement which is created in background if you change the valuation type in MSC2N.

So check your movement 340 for mandatory fields which cannot be entered in a background .

JL23
Active Contributor
0 Kudos

you cannot change the valuation type with a 311 movement.

Use MSC2N and change it in the batch master, SAP will then automatically create a 340 movement in the background.

claudio_carrara
Active Participant
0 Kudos

Thanks Jurgen, I didn't know this feature.
Anyway when save the changes with MSC2N transaction the system issue the message: M7661-error 5 in posting for status change. I checked OSS notes but 1892299 and 2474477 which speaks about SV and batches are not related to my error (see picture enclosed). Thanks for your precious help.msc2n.jpg