3
SAP Note Header Data Symptom The following transactions for entering and displaying goods movements (material documents) - called "MB transactions" below - have been replaced by the single-screen transaction MIGO since Release 4.6: l MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A, MB1B, MB1C, MB31, MBNL, MBRL, MBSF, MBSL, MBST, MBSU For reasons relating to the protection of standards for existing process configurations, the specified transactions are still available up to the 6.xx releases. However, they are not maintained in full: ¡ Corrections in the MB transactions are carried out only if the equivalent process cannot be posted demonstrably using transaction MIGO or if serious errors occur that cause inconsistencies or other legally-relevant problems. ¡ New functions are developed only for transaction MIGO. In Releases 6.xx, system message M7 499 refers to the situation. You can set the message category in Customizing (default: "I" Info). The system issues the information message once daily in non-production clients only. Message category "E" (from SAP Note 2029600 onwards) results in an error message in live clients as well. When MB03 is called from other transactions, the calls are automatically forwarded to MIGO for document display, if the message category "E" is set. With batch input, the system does not generally issue message M7499. In the next SAP_APPL release up (7.00 at the earliest, not in an enhancement pack), the MB transactions will be decommissioned. This means that they are then no longer available. Other Terms MIGO_GR, MIGO_GI, MIGO_ST, BAPI_GOODSMVT_CANCEL, M7499, M7-499, omcq Reason and Prerequisites The double-maintenance of the transaction families MIGO and MB* delays the processing of problems with MIGO and other transactions, and reduces the development capacity provided for continuous further development. Therefore, the discontinuation of the double-maintenance is also in the interest of all SAP customers. Solution You can still use the MB transactions in the 6.xx Releases. However, it is advisable to replace them with transaction MIGO. The BAPI "BAPI_GOODSMVT_CREATE" is provided as a replacement for background processing via batch input. ------------------------------------------------------------------------ |Manual Activity | ------------------------------------------------------------------------ |VALID FOR | |Software Component SAP_APPL SAP Application | | Release 600 Until SAPKH60023 | | Release 602 Until SAPKH60213 | | Release 603 Until SAPKH60312 | | Release 604 Until SAPKH60413 | | Release 605 Until SAPKH60510 | | Release 606 Until SAPKH60607 | | Release 616 Until SAPKH61601 | ------------------------------------------------------------------------ 1. SE91 Create system message: M7 499 Short text: "Transaction &1 is obsolete (SAP Note 1804812)" 1804812 - MB transactions: Limited maintenance/decommissioning Version 11 Validity: 06/12/2014 - active Language English Released On 06/12/2014 07:30:20 Release Status Released for Customer Component MM-IM-GF Basic Functions Priority Recommendations / Additional Info Category Release planning information

1804812 - MB Transactions - Limited Maintenance or Decommissioning

Embed Size (px)

DESCRIPTION

SAP Note

Citation preview

  • SAP Note

    Header Data

    Symptom

    The following transactions for entering and displaying goods movements (material documents) - called "MB transactions" below - have been replaced by the single-screen transaction MIGO since Release 4.6:

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

    For reasons relating to the protection of standards for existing process configurations, the specified transactions are still available up to the 6.xx releases. However, they are not maintained in full:

    Corrections in the MB transactions are carried out only if the equivalent process cannot be posted demonstrably using transaction MIGO or if serious errors occur that cause inconsistencies or other legally-relevant problems.

    New functions are developed only for transaction MIGO.

    In Releases 6.xx, system message M7 499 refers to the situation. You can set the message category in Customizing (default: "I" Info). The system issues the information message once daily in non-production clients only. Message category "E" (from SAP Note 2029600 onwards) results in an errormessageinliveclientsaswell.WhenMB03iscalledfromothertransactions,thecallsareautomaticallyforwardedtoMIGOfordocumentdisplay, if the message category "E" is set.

    With batch input, the system does not generally issue message M7499. In the next SAP_APPL release up (7.00 at the earliest, not in an enhancement pack), the MB transactions will be decommissioned. This means that they are then no longer available.

    Other Terms

    MIGO_GR, MIGO_GI, MIGO_ST, BAPI_GOODSMVT_CANCEL, M7499, M7-499, omcq

    Reason and Prerequisites

    The double-maintenance of the transaction families MIGO and MB* delays the processing of problems with MIGO and other transactions, and reduces the development capacity provided for continuous further development. Therefore, the discontinuation of the double-maintenance is also in the interest of all SAP customers.

    Solution

    You can still use the MB transactions in the 6.xx Releases. However, it is advisable to replace them with transaction MIGO. The BAPI "BAPI_GOODSMVT_CREATE" is provided as a replacement for background processing via batch input.

    ------------------------------------------------------------------------ |Manual Activity | ------------------------------------------------------------------------ |VALID FOR | |Software Component SAP_APPLSAP Application | | Release 600Until SAPKH60023| | Release 602Until SAPKH60213| | Release 603Until SAPKH60312| | Release 604Until SAPKH60413| | Release 605Until SAPKH60510| | Release 606Until SAPKH60607| | Release 616Until SAPKH61601| ------------------------------------------------------------------------

    1. SE91 Create system message: M7 499 Short text: "Transaction &1 is obsolete (SAP Note 1804812)"

    1804812 - MB transactions: Limited maintenance/decommissioning

    Version 11 Validity: 06/12/2014 - active Language English

    Released On 06/12/2014 07:30:20 Release Status Released for Customer Component MM-IM-GF Basic Functions Priority Recommendations / Additional Info Category Release planning information

  • 2. SE80 Package MB Create SET/GET parameter: "M7499" Short text: "Control message M7499"

    3. SE16 Table T160MVAL Create new entries for M7 499: MSGTP = ' ', 'E', 'I'

    Validity

    Correction Instructions

    Causes - Side Effects

    Support Packages & Patches

    References

    This document refers to:

    SAP Notes

    This document is referenced by:

    Software Component From Rel. To Rel. And Subsequent

    SAP_APPL 600 600

    602 602

    603 603

    604 604

    605 605

    606 606

    616 616

    617 617

    Correction Instructions

    Software Component Valid from Valid to Number

    SAP_APPL 600 603 1558852

    SAP_APPL 604 605 1738813

    SAP_APPL 604 616 1556078

    Notes / Patches corrected with this note

    Note Reason From Version To Version Note Solution Version Support Package The table does not contain any entries

    The following SAP Notes correct this Note / Patch

    Note Reason From Version To Version Note Solution Version Support Package

    1804812 0 0 2029600 0

    Support Packages

    Software Component Release Support Package

    SAP_APPL 600 SAPKH60024

    602 SAPKH60214

    603 SAPKH60313

    604 SAPKH60414

    605 SAPKH60511

    606 SAPKH60608

    616 SAPKH61602

    1888722 MIGO: Change Material Document 1816363 MIGO: Enhanced functions for EHP7 1810419 MM-IM reports: Switch from MB03 to MIGO 1808576 MIGO:ndernMaterialbeleg(~MB02)

    729408 Document flow: Material doc. disp. w/ MIGO instead of MB03

  • SAP Notes (4)

    1993407 Document flow: Branching to material document using MB03 instead of MIGO 1810419 MM-IM reports: Switch from MB03 to MIGO 729408 Document flow: Material doc. disp. w/ MIGO instead of MB03 1816363 MIGO: Enhanced functions for EHP7