Do you have any question about this error?
Message type: E = Error
Message class: OO - Class Builder/API
Message number: 021
Message text: Interface &1 still contained in interface &2
You wanted to delete the implementation relationship for interface
&V1&. However, interface &V1& is still implemented in interface &V2&.
Since all interfaces contained in &V2& must be implemented, you cannot
delete the implementation relationship for &V1& unless the
implementation relationship for &V2& is also deleted.
Error message extract from SAP system. Copyright SAP SE.
OO021
- Interface &1 still contained in interface &2 ?The SAP error message OO021 indicates that there is an issue with the interface implementation in ABAP (Advanced Business Application Programming). Specifically, it means that an interface (let's call it
&1
) is still referenced or contained within another interface (&2
), which is causing a conflict or violation of the interface implementation rules.Cause:
Interface Inheritance: The error typically arises when an interface that is supposed to be removed or modified is still being referenced by another interface. This can happen if:
- The interface is still being used in the implementation of another interface.
- There are dependencies that have not been resolved.
- The interface has not been properly detached from the implementing classes or other interfaces.
Implementation Issues: If you are trying to delete or modify an interface that is still in use, the system will prevent this action to maintain data integrity and consistency.
Solution:
Check Dependencies:
- Use transaction SE80 (Object Navigator) or SE11 (Data Dictionary) to check where the interface
&1
is being used. Look for any classes or other interfaces that implement or reference it.- You can also use the "Where-Used List" feature to find all occurrences of the interface.
Remove References:
- If you find that the interface is still being implemented or referenced, you will need to remove those references first. This may involve modifying or deleting the implementing classes or interfaces.
Recompile:
- After removing the references, recompile the affected objects to ensure that the changes take effect.
Delete or Modify the Interface:
- Once all references are cleared, you should be able to delete or modify the interface
&1
without encountering the OO021 error.Transport Requests:
- If you are working in a transport environment, ensure that all changes are included in the appropriate transport requests.
Related Information:
By following these steps, you should be able to resolve the OO021 error and manage your interfaces effectively in SAP.
Get instant SAP help. Start your 7-day free trial now.
OO020
Error activating &1 from &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
OO019
Component &1 &2 does not belong to a class or interface
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
OO022
Class/interface was saved
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
OO023
Method implementation does not exist. Save the class first.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.