How To Fix STW_OL604 - Obsolete BAdI implementation detected

SAP Error Message - Details

• Message type: E = Error

• Message class: STW_OL - Messages of the Object Layer (Stream Work Library)

• Message number: 604

• Message text: Obsolete BAdI implementation detected

What causes this issue?

The BAdI STW_ITEM_FACTORY has been made obsolete by an architectural gap
discovered after the BAdI was published. The change was made in the
SAP_BASIS releases:
7.02 SP12
7.30 SP08
7.31 SP05
7.32 SP00

System Response

The execution of the current process has to be stopped to avoid
inconsistent code executions.

How to fix this error?

The new BAdI STW_ITEM_FACTORY2 was introduced instead. Move all of your
implementations to the new BAdI. Here you will find that a new filter
value SCOPE has been added.
This filter value is a freely definable string value. You can set it
using the new interface method IF_STW_API->SET_SCOPE. This can be done
once per roll area, or you can do it each time before you trigger an API
call which triggers the creation of StreamWork items.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message STW_OL604 - Obsolete BAdI implementation detected ?

  The SAP error message STW_OL604 indicates that an obsolete Business Add-In (BAdI) implementation has been detected. This typically occurs when a BAdI implementation is no longer valid or has been replaced by a newer version or alternative implementation.
  Cause:
  
  Obsolete BAdI Implementation: The BAdI implementation you are using has been marked as obsolete. This can happen if SAP has updated the BAdI or if the BAdI is no longer supported in the current version of the software.
  System Upgrade: If your SAP system has been upgraded, some BAdI implementations may become obsolete due to changes in the underlying business logic or enhancements in the system.
  Custom Code: If there are custom implementations of BAdIs that are not aligned with the latest SAP standards, they may be flagged as obsolete.
  
  Solution:
  
  Check for Updates: Review the SAP notes and documentation related to the specific BAdI to understand the changes and find the recommended alternative BAdI or implementation.
  Implement New BAdI: If a new BAdI has been introduced, implement the new BAdI instead of the obsolete one. This may involve adjusting your custom code to align with the new BAdI interface.
  Remove Obsolete Implementation: If the obsolete BAdI is no longer needed, you can remove the implementation from your system.
  Consult SAP Support: If you are unsure about the changes or how to proceed, consider reaching out to SAP support for guidance on how to handle the obsolete BAdI implementation.
  
  Related Information:
  
  BAdI Documentation: Check the SAP Help Portal for documentation on the specific BAdI you are working with. This will provide insights into its usage, alternatives, and any migration paths.
  SAP Notes: Search for relevant SAP Notes that may address the specific BAdI and provide guidance on how to handle the obsolescence.
  Transaction Codes: Use transaction codes like SE18 (for BAdI definitions) and SE19 (for BAdI implementations) to manage and review BAdI implementations in your system.
  
  By following these steps, you should be able to resolve the STW_OL604 error and ensure that your SAP system is using supported and up-to-date BAdI implementations.