cancel
Showing results for 
Search instead for 
Did you mean: 

Batch Status seggregation

Former Member
0 Kudos

Hi Experts,

I am planning to transfer the stock from one Plant to another using Transfer posting with 301 Mov Type.

in 301, its defined that only Batches which are in Released status alone can be transferred.

The Movement type 301 is allowing Batches with Release status only.

Now the issue is, to segregate the Batches which are released from the Batches which are not in release status for the preparation of the Input file for data conversion.

Say Material X has a quantity 10 in 5 different batches. Out of 5 batches, 4 are in Release status and one is not released.

How do we segregate this one batch alone, from the rest of the 4 batches, so that the materials in these 4 batches alone can be transferred to the new plant.

Thanks in advance,

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Batch status can be changed only using MSC2N or QA11 transaction. Batch status can not be changed using MB transactions.

I would suggest

Initially load all batches as un-restricted batch status.

using another batch program (based on MSC2N) change the batch status to restricted.

Hope this helps

Marwadi

former_member42743
Active Contributor
0 Kudos

You can also check using SE16. Look at table MCH1. If your batch management is at plant level, than look at MCHA.

FF

Former Member
0 Kudos

Well if you want to check the status of the batch then you can use

Bapi's

BAPI_BATCH_GET_DETAIL

or

BAPI_MATERIAL_GETBATCHES

bapi will show you the status & RESTRICTED field will tell you whether batch is restricted or not