How To Fix /SMB/BB_INSTALLER090 - Transaction code & not exist in the system assigned to & RFC destination

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/BB_INSTALLER -

• Message number: 090

• Message text: Transaction code & not exist in the system assigned to & RFC destination

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 /SMB/BB_INSTALLER090 - Transaction code & not exist in the system assigned to & RFC destination ?

  The SAP error message /SMB/BB_INSTALLER090 typically indicates that a specific transaction code is not available in the system that is assigned to the specified RFC (Remote Function Call) destination. This can occur in various scenarios, particularly when dealing with SAP Business ByDesign or other SAP solutions that involve remote connections.
  Cause:
  
  Missing Transaction Code: The transaction code you are trying to access does not exist in the target system. This could be due to a misconfiguration or the transaction not being installed or activated in that system.
  Incorrect RFC Destination: The RFC destination may be incorrectly configured, pointing to a system that does not have the required transaction code.
  Authorization Issues: The user may not have the necessary authorizations to access the transaction code in the target system.
  System Version Mismatch: The transaction code may exist in a different version of the SAP system, and the current system does not support it.
  
  Solution:
  
  Verify Transaction Code: Check if the transaction code exists in the target system. You can do this by logging into the target system and trying to execute the transaction code directly.
  Check RFC Destination Configuration: Ensure that the RFC destination is correctly configured. You can do this by going to transaction SM59 in the SAP GUI and verifying the settings for the RFC destination.
  User Authorizations: Ensure that the user has the necessary authorizations to execute the transaction code in the target system. You may need to consult with your SAP security team to verify and adjust user roles and authorizations.
  System Compatibility: If the transaction code is not available in the target system, check if it is available in a different version or if there are alternative transaction codes that can be used.
  Consult Documentation: Refer to SAP documentation or support notes related to the specific transaction code or the error message for additional guidance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with the transaction codes relevant to your SAP environment and their availability across different systems.
  SAP Notes: Search for SAP Notes related to the error message or the specific transaction code for any known issues or patches.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  System Logs: Check system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance.