ESH_CM_TBO SAP Message class Tagging-by-Object Models and Runtime

ESH_CM_TBO is a standard message class available within your SAP system (depending on your version and release level). Below is a list of all the messages available for within this class and a link to any long text associated with each message. These messages are very simple to use and can be implemented into your ABAP code using the MESSAGE statement and the following syntax.

MESSAGE I001(ESH_CM_TBO).

Note the value "I" represents an information messsage but can be replaced with E for error, W for warning, S for Status/Success, A for Abend/Termination and X for exit which does not display a message and causes a runtime error. Click here for more information about SAP Messages.

Messages can also contain the & symbol, this means custom values can be added to the message when it is displayed, this is done using the WITH statement

MESSAGE I001(ESH_CM_TBO) with ld_field1.

Message class details can be viewed directly within your SAP system by entering the object name ESH_CM_TBO into the relevant SAP transaction such as SE91 or SE80.

000 - &1 &2 &3 &4

001 - &1&2&3&4

002 - Tagging-by-object model cannot be created: Name not provided

003 - TbO name is not unique, there is already a TbO model with name &1

004 - Object handler instance for TbO model &1 cannot be determined

005 - The TbO model and its node structure have not yet been created

006 - TbO models can only be created a central cross-system software component

007 - TbO software component is not provided

008 - Object handler for software component &1 could not be instantiated

009 - Data provider for software component &1 could not be instantiated

010 - Data-type handler for software component &1 could not be instantiated

011 - TBO cross-relations cannot be changed

012 - The cross-relations are already used in TBO usages

013 - Usages for source-to-target navigation have already been set up

014 - Usages for autotagging have already been set up

015 - Usages for cross-system search have already been set up

016 - First, delete the TBO usages

017 - To delete autotagging usages remove target-side autotagging attributes

018 - To delete cross-system search usages remove usage attributes

019 - Usages cannot yet be created

020 - Define cross-relations to the two models to be linked via TBO first

021 - Define cross-relation to the second model to be linked first

022 - A TBO can only link two models

023 - Exceeding cross relations have to be deleted

024 - TBO not yet set up