Good Bye MB1A MB1B MB1C

Say good bye to those old inventory transaction codes like MB1A MB1B and MB1C, they are officially close in S/4 HANA.

This will be a headache to those companies that are still using batch input program for inventory updates.

The reason why the old transaction codes are used in the first place is because it is very difficult to do batch input using MIGO.

Alternative is to use the BAPI function for such inventory updates.

Obsolete Material inventory management transactions

2210569 - Obsolete Material inventory management transactions

Symptom

The following transactions for entering and displaying goods movements (material documents) - called "MB transactions" - below, have been replaced by the single-screen generalized transaction MIGO or the BAPI's BAPI_GOODSMVT_CREATE and BAPI_GOODSMVT_CANCEL:

MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A, MB1B, MB1C, MB31, MBNL, MBRL, MBSF, MBSL, MBST, MBSU and MBBM

The transaction MMBE_OLD has been replaced by transaction MMBE. Alternatively there is also the Fiori App Stock Overview

These transaction do still exist as transaction codes but calling these transaction codes from the menu has the consequence that an error message is raised.

SAP MM Tips

See also
Material Master Multiple Choice Questions Answers

Get help for your SAP MM problems
SAP MM Forums - Do you have a SAP MM Question?

SAP MM Books
SAP Material Management Certification, Interview and Configuration Reference Books

SAP Material Management Tips
SAP MM Configuration Tips and Materials Management Discussion Forum

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.