Message type: E = Error
Message class:  SEEF_BADI - Messages on BAdIs 
Message number: 150
Message text: Creation of classic BAdIs no longer supported (see long text)
The new BAdIs, which are integrated in the ABAP language, are far
superior to the classic BAdIs, since the latter are slower and offer
fewer features than their newer counterparts.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Create your BAdI in the new technology.
The new BAdIs are integrated in the enhancement framework. They are
created and transported as part of an enhancement spot. You can store
semantically-related BAdIs in a common enhancement spot. You should
structure enhancement spots in a hierarchy of composite enhancement
spots to ensure a clear overview of enhancement possibilities.
An enhancement spot has one or more enhancement implementations. Since
an enhancement spot can contain several BAdIs, an enhancement
implementation can contain several BAdI implementations.
Procedure
Select a package node in the Repository Browser, open the context menu
and choose "Create" -> "Enhancements" -> "Enhancement Spot".
In the dialog box that appears , select or define an enhancement spot
and a composite enhancement spot
In the enhancement spot editor, choose "Create BAdI" on the "BAdI" tab.
Define the attributes and a BAdI interface (see "Application Help").
Error message extract from SAP system. Copyright SAP SE.
The SAP error message SEEF_BADI150 indicates that the creation of classic Business Add-Ins (BAdIs) is no longer supported in the current version of SAP. This is part of SAP's transition towards using the newer, more flexible enhancement framework, which is based on the concept of "New BAdIs" or "Enhancement Spots."
Cause: The error occurs when a developer attempts to create a classic BAdI in an environment that only supports the new BAdI framework. Classic BAdIs are based on the older implementation method, which is now deprecated in favor of the new BAdI approach that offers better performance, easier management, and more features.
Solution: To resolve this error, you should follow these steps: Use New BAdIs: Instead of creating a classic BAdI, you should create a new BAdI using the new enhancement framework. This can be done using transaction SE18 (for BAdI definition) and SE19 (for BAdI implementation). Check Existing Implementations: If you have existing classic BAdIs,
 Get instant SAP help. Sign up for our Free Essentials Plan.
Get instant SAP help. Sign up for our Free Essentials Plan. 
SEEF_BADI148 Name of BAdI implementation &1 is invalid
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SEEF_BADI147 Function code &2 in program &1 already declared in BAdI &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SEEF_BADI151 Use transaction SPAU to migrate CMOD implementation &1
What causes this issue?  Migrate CMOD implementation &1 using Transaction SPAUSystem Response  The system issues an error message and will not all...
SEEF_BADI152 CMOD &1 for SMOD &2 has yet to be migrated
What causes this issue?  Migrate CMOD implementation &1 using transaction SPAUSystem Response  The system issues an error message and will not all...
Click on this link to search all SAP messages.