How To Fix MI558 - Combination of transaction ref. & and screen seq. & not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: MI - Customizing for the Material Master

• Message number: 558

• Message text: Combination of transaction ref. & and screen seq. & not allowed

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message MI558 - Combination of transaction ref. & and screen seq. & not allowed ?

  The SAP error message MI558, which states "Combination of transaction ref. & and screen seq. & not allowed," typically occurs in the context of inventory management or physical inventory processes. This error indicates that there is an issue with the combination of the transaction reference and the screen sequence being used in the system.
  Cause:
  
  Invalid Transaction Reference: The transaction reference you are trying to use may not be valid for the specific screen sequence you are accessing.
  Screen Sequence Configuration: The screen sequence may not be configured to allow the transaction reference you are using. This can happen if the configuration settings in the system do not match the expected values for the transaction.
  Custom Development: If there are custom developments or modifications in the system, they may not align with standard SAP behavior, leading to this error.
  User Authorizations: Sometimes, the user may not have the necessary authorizations to perform the transaction, which can lead to unexpected errors.
  
  Solution:
  
  Check Transaction Reference: Verify that the transaction reference you are using is correct and valid for the operation you are trying to perform.
  Review Screen Sequence Configuration: Check the configuration settings for the screen sequence in the SAP system. Ensure that the combination of the transaction reference and screen sequence is allowed.
  
  You can do this by navigating to the relevant configuration settings in SPRO (SAP Project Reference Object) and checking the settings under Inventory Management.
  
  
  Consult Documentation: Refer to SAP documentation or help resources to understand the valid combinations of transaction references and screen sequences.
  User Authorizations: Ensure that the user has the necessary authorizations to perform the transaction. You may need to consult with your SAP security team to verify this.
  Debugging: If you have access to debugging tools, you can analyze the program flow to identify where the error is being triggered and why the combination is not allowed.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Transaction Codes: Familiarize yourself with relevant transaction codes related to inventory management, such as MI01 (Create Physical Inventory Document), MI02 (Change Physical Inventory Document), and MI03 (Display Physical Inventory Document).
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP support team or consult with SAP directly for further assistance.