How To Fix /BOBF/CUST_UI081 - Transaction BOB is deprecated.

SAP Error Message - Details

• Message type: E = Error

• Message class: /BOBF/CUST_UI -

• Message number: 081

• Message text: Transaction BOB is deprecated.

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 /BOBF/CUST_UI081 - Transaction BOB is deprecated. ?

  The error message /BOBF/CUST_UI081 Transaction BOB is deprecated in SAP indicates that the transaction code BOB (Business Object Builder) is no longer supported or has been deprecated in the version of SAP you are using. This typically happens when SAP transitions to newer technologies or methodologies, such as the SAP Business Object Framework (BOBF) or when they encourage the use of newer tools and transactions.
  Cause:
  
  Deprecation of Transaction: SAP periodically deprecates older transactions as they move towards more modern frameworks and tools. The BOB transaction may have been replaced by newer functionalities or tools.
  Version Upgrade: If you have recently upgraded your SAP system, certain transactions may no longer be available or may have been replaced with new ones.
  Configuration Changes: Changes in system configuration or updates to the SAP system can lead to the deprecation of certain transactions.
  
  Solution:
  
  Use Alternative Transactions: Check for alternative transactions or tools that have replaced BOB. For example, you might want to look into using the SAP Fiori apps or the SAP Web IDE for development and customization tasks.
  Consult SAP Documentation: Review the latest SAP documentation or release notes for your version to find out what has replaced the BOB transaction and how to use the new tools effectively.
  SAP Support: If you are unsure about the alternatives or need further assistance, consider reaching out to SAP Support or your SAP administrator for guidance on how to proceed.
  Training and Resources: Look for training materials or resources that cover the new tools and methodologies that SAP is promoting. This can help you transition smoothly from the deprecated transaction.
  
  Related Information:
  
  SAP Business Object Framework (BOBF): Familiarize yourself with the BOBF, which is the framework that supports the development of business objects in SAP. Understanding this framework can help you adapt to the new methodologies.
  SAP Fiori: If your organization is moving towards a Fiori-based user experience, consider learning about Fiori apps and how they can replace traditional transactions.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered the same issue and what solutions they have found.
  
  By following these steps, you should be able to address the deprecation of the BOB transaction and find suitable alternatives for your SAP development and customization needs.