cancel
Showing results for 
Search instead for 
Did you mean: 

Transaction MB1A is obsolete (SAP Note 1804812)

former_member219179
Contributor
0 Kudos

Hello SAP Enthusiast,

We have upgraded our Sxx (sandbox) from EHP 6 to EHP 7.After up gradation I observe that when ever I am entering at first time to transaction MB1A I got the below warning message,

Transaction MB1A is obsolete (SAP Note 1804812)

Message no. M7499

Based on the message I understand it is a warning and not an error and still I can able to proceed further on goods issue. My concern is since I have a several users in Pxx environment they will raise a ticket and ask for a permanent fix in case this warning message appears after EHP 7 up gradation.

Please let me know why in case of transaction MB1A / MB1B and MB1C I am getting this warning message and guide me how to fix this issue that is warning message should not appear in Pxx environment after up gradation.

I also gone through the SAP Note 1804812 but it says The message is issued once daily in non-production clients only that mean in Pxx system i will not get this warning message?Please confirm.

Please help me to over come this issue by providing our valuable input.

Regards,

Kumar S

Accepted Solutions (1)

Accepted Solutions (1)

Prasoon
Active Contributor

Hi,

   As explained in the note:  1804812 - MB transactions: Restricted maintenance/discontinuation

, the MB* transactions will be discontinued from next SAP release. For release 6.XX, the system may issue the message M7499 in non productive environment only, not in PRD system.

   It is recommended to use MIGO instead of MB* transactions.

Regards,

AKPT

former_member219179
Contributor
0 Kudos

Experts,
Let me know how this change in process can be handled to my business.

Provide your valuable input from your end.

Cheers,

Kumar S

Former Member
0 Kudos

Hi,

This is not only for you its for all.

Yes definitely there will be change in process as users already habituated with MB* Transactions.

But yes you need to explain them that further going you need to Use MIGO transactions which is same as MB* transactions.

Rgds,

JL23
Active Contributor
0 Kudos

.

you do a survey who needs to be trained on MIGO

you analyze if you have some batch programs running still with the MB* transaction

you schedule and conduct  trainings

you replace the batch programs  with BAPIs

you tell your users to use MIGO instead of the MB transactions

and schedule a data to  remove transaction authorization for the MB* transaction.

MIGO is already old, it came with 46c release.

Former Member
0 Kudos

This message was moderated.

Answers (2)

Answers (2)

Former Member
0 Kudos

In continuation to AKPT reply, refer notes 1816363, 1743574.

Former Member
0 Kudos

Hi,

If you see correctly what the OSS Note explains you should understand.

The Note says that after release 7.0 the MB* transaction will be replaced by MIGO transaction which will be having all facility as MB*