cancel
Showing results for 
Search instead for 
Did you mean: 

One Batch To another new Batch stock Transfer

former_member240058
Participant
3,635

Dear Friends

I want to do existing Batch To another new Batch stock Transfer using 301 movement

New batch is not created in system and migo gives error Message no. M7042 Batch xxxxxxxxx does not exist

How to allow system to create new batch in Migo using 301 movement

Accepted Solutions (0)

Answers (7)

Answers (7)

Raj_Sinha
Participant

Dear Mayuresh,

You need to check the stock first with that batch no.

Use Tcode MB52 or MMBE;

Enter Material, Plant, Storage Loc & Batch. Then check if you have the stock for that material or not.

If the issue does not resolve. Revert me back I'll help you with some screenshots or post your screenshot for more clarity.

Best Regards

Raj Sinha

former_member240058
Participant
0 Kudos

Hello Raj

Still iam getting same message. please refer attachmentmigo.jpgsap-mmbe.jpg

0 Kudos

hello mayuresh,

Try by maintaining same batch in both (from & dest.)

Raj_Sinha
Participant

Dear Mayuresh,

Make sure while doing MIGO; Transfer Posting - Other; under from Tab; Material, Batch, Storage loc, Qty & Plant is correct.

P.S. the entered Batch should have Stocked in it.

Also, in Destination Tab the New Batched should not be existing batch. Which means it should be unique.

Then try posting.

Hope this helps.

Best Regards

Raj Sinha.

former_member240058
Participant

Dear Raj

It gives same error message gives error Message no. M7042 Batch xxxxxxxxx does not exist

0 Kudos

hello mayuresh,

If you are using Movement type 301- transfering material from one plant to another plant.

In MIGO (Transfer posting- others)

check for the stock of material as your screen shot says that stock is available.

check whether the material is extended in both plants or not.

now provide the details like material,

plant (should be different in both from & dest),

storage location ( wrt to plant),

batch(should be same in both plants),

qty

if you click on post then stock will be transferred to destination plant ->storage location with same batch number.

hope this will help u for further clarification revert back and rewards will be appreciated.

0 Kudos

Hello Mayuresh,

There are 2 ways that you can make your scenario work.

1. Create a batch number using T-code 'MSC1N', assign required classification details. Then while doing Transfer posting (Mov type - 301), you need to enter newly created batch number as a destination batch. I think system will not throw the error as you got now.

2. If you don't want to create a batch number manually everytime and just want to add it while doing Goods movement, then you have to activate automatic batch number generation through config. The path for config is - SPRO->Logistics - General -> Batch Management -> Creation of New Batches -> Define Batch Creation for Goods Movements. Here, you can set the validation criteria against the movement type. As you are doing Transfer posting using 301, you can set validation as 'Automatic / Manual without check' against '301'. Then you can do transfer posting.
I hope it works. Please let me know if you face any other error.

eduardo_hinojosa
Active Contributor
0 Kudos

Hi

Although the note is old, it refers to older releases, check note 555354 - MIGO: Not allowed batch creation (and related notes), maybe it helps you. Check also the integrity of batch in the batch cockpit or create it before with MSC1N.

Regards

Eduardo

former_member240058
Participant
0 Kudos

no error in su53

former_member42743
Active Contributor
0 Kudos

Is it a warning or error? Usually you would get something like "warning - batch does not exist, do you wish to create it"?

I am guessing that the plant and storage location are the same for both batches? Can't tell from the screen shots.

This material is not HU managed is it?

Craig

former_member240058
Participant
0 Kudos

plant and storage location are the same for both batches are same.

Its error message , cant proceed with posting.

Material is not HU managed.

former_member42743
Active Contributor
0 Kudos

By any chance have you tried running SU53 after getting this error? Just curious.

Craig