How To Fix SIG620 - This transaction is obsolete; do not use it any more

SAP Error Message - Details

• Message type: E = Error

• Message class: SIG - Digital Signature

• Message number: 620

• Message text: This transaction is obsolete; do not use it any more

What causes this issue?

For release 4.6C, the process for logging digital signatures has been
completely reworked and assigned to a new transaction code. The
previous transaction is no longer being enhanced, but is being retained
so that you can still access data for digital signatures that were
created before release 4.6C.

System Response

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

How to fix this error?

Use the new transaction DSAL for logging digital signatures (digital
signature logs).

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SIG620 - This transaction is obsolete; do not use it any more ?

  The SAP error message SIG620 indicates that the transaction you are trying to access is obsolete and should not be used anymore. This typically occurs when SAP has deprecated a transaction code in favor of a newer, more efficient, or more secure alternative.
  Cause:
  
  Obsolescence of Transaction: The transaction code you are trying to use has been marked as obsolete by SAP. This can happen due to various reasons, such as the introduction of new functionalities, changes in business processes, or the need for improved security measures.
  System Upgrade: If your SAP system has been upgraded to a newer version, certain transactions may no longer be supported.
  Custom Development: If the transaction was custom-developed, it may have been intentionally marked as obsolete by your organization.
  
  Solution:
  
  Identify the Replacement Transaction: Check the SAP documentation or consult with your SAP administrator to find out what the recommended replacement transaction is. SAP often provides alternative transaction codes that serve the same purpose.
  Use the New Transaction: Once you have identified the new transaction code, use it instead of the obsolete one.
  Update User Training: If the obsolete transaction was widely used, ensure that users are trained on the new transaction to avoid confusion.
  Check for Customizations: If the transaction was a custom development, you may need to consult with your development team to understand the implications and find a suitable alternative.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific guidance related to the obsolete transaction. SAP Notes often provide detailed information about deprecated transactions and their replacements.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered the same issue and what solutions they have found.
  Documentation: Review the release notes or documentation for your specific SAP version to understand the changes made and the rationale behind the obsolescence of certain transactions.
  
  By following these steps, you should be able to resolve the SIG620 error and transition to using the appropriate transaction code.