How To Fix STW_OL604 - Obsolete BAdI implementation detected


STW_OL604 - Overview

  • 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

  • Show details Hide details
  • 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

    Already have an account? Login here!




Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant