How To Fix SRT_REG085 - This transaction is obsolete; read the long text

SAP Error Message - Details

• Message type: E = Error

• Message class: SRT_REG - SRT Registry

• Message number: 085

• Message text: This transaction is obsolete; read the long text

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

What causes this issue?

From SAP NetWeaver AS 7.00, SP14, new service definitions in the ABAP
development environment are no longer administered using transactions
<AB>WSADMIN</> and <AB>WSCONFIG</>.

System Response

The transactions <AB>WSADMIN</> and <AB>WSCONFIG</> will remain active
until all old web service configurations have been migrated, which means
you can continue to configure web services from SAP NetWeaver AS 6.40,
7.00, and web service definitions from the XI 3.0 environment. You can
also continue to access the runtime configurations of old service
definitions using these transactions.
However, new service definitions created in the ABAP development
environment will be hidden in these transactions.

How to fix this error?

Use transaction SOAMANAGER (SOA = Service Oriented Architecture) for the
administration of new service definitions.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SRT_REG085 - This transaction is obsolete; read the long text ?

  The SAP error message SRT_REG085 indicates that the transaction you are trying to access is obsolete. This typically means that the transaction has been deprecated in favor of a newer transaction or functionality within the SAP system.
  Cause:
  
  Obsolescence of Transaction: The specific transaction you are trying to use is no longer supported or has been replaced by a different transaction or process.
  System Upgrade: If your SAP system has been upgraded, certain transactions may have been removed or replaced as part of the upgrade process.
  Configuration Changes: Changes in system configuration or the introduction of new modules may lead to certain transactions being marked as obsolete.
  
  Solution:
  
  Check Documentation: Review the SAP documentation or release notes for your version to find out what the recommended alternative transaction is.
  Use Alternative Transactions: Identify and use the new transaction or functionality that has replaced the obsolete one. This information can often be found in the long text of the error message or in the SAP Help Portal.
  Consult with SAP Support: If you are unsure about the alternative or need further assistance, consider reaching out to SAP support or your internal SAP team for guidance.
  Training and Resources: Ensure that users are trained on the new processes or transactions to avoid confusion and improve efficiency.
  
  Related Information:
  
  Long Text: The error message usually has a long text that provides additional context or details about the obsolescence. You can access this by clicking on the message or using the appropriate function in SAP to view the long text.
  SAP Notes: Check for any relevant SAP Notes that may provide additional information or patches related to the obsolete transaction.
  Transaction Codes: Familiarize yourself with the transaction codes that are currently in use and their purposes to ensure smooth operations.
  
  If you need specific details about the transaction that is obsolete, you may need to provide the transaction code or context in which you encountered the error.