2Q SAP Message class TMS Service Message class
2Q 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(2Q).
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(2Q) with ld_field1.
Message class details can be viewed directly within your SAP system by entering the object name 2Q into the relevant SAP transaction such as SE91 or SE80.
000 - *** Domain link bootstrap and modification
001 - System &1 on host &2 already known
Additional information exists about message 001 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 001 class 2q.002 - SAP System on &1, service &2 displays a known domain
Additional information exists about message 002 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 002 class 2q.003 - Domain links between domains with same name (&1) not possible
004 - Domain &1 already known in domain &2
005 - System &1 is not a controller
006 - Specify a system name
007 - System name &1 must have 3 characters
008 - Enter a host name
Additional information exists about message 008 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 008 class 2q.009 - Enter a service number
Additional information exists about message 009 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 009 class 2q.010 - &1 &2 &3 &4
Additional information exists about message 010 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 010 class 2q.011 - Service number contains 2 digits
012 - Character string for host name and SAProuter must be &1 long
Additional information exists about message 012 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 012 class 2q.013 - Domain link to domain &1; controller &2 already exists
Additional information exists about message 013 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 013 class 2q.014 - System &1 originates from its own domain &2; cannot be deleted
Additional information exists about message 014 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 014 class 2q.015 - Domain link &1 does not exist in domain &2
Additional information exists about message 015 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 015 class 2q.016 - Request for domain link sent to system &1
017 - Cannot delete systems from other domains
Additional information exists about message 017 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 017 class 2q.018 - Cannot lock systems from other domains
Additional information exists about message 018 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 018 class 2q.019 - Cannot unlock systems from other domains
Additional information exists about message 019 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 019 class 2q.020 - Domain link to domain &1 deleted
Additional information exists about message 020 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 020 class 2q.021 - Domain link to controller &2 of domain &1 does not exist
022 - Domain link to domain &1 deleted
023 - Proposal for domain link for &1 reset
Additional information exists about message 023 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 023 class 2q.024 - Proposal for domain link for &1 accepted
Additional information exists about message 024 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 024 class 2q.025 - Status of domain link &1 is 'Waiting to be accepted'
Additional information exists about message 025 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 025 class 2q.026 - Status of domain link &1 is 'Received domain link request'
Additional information exists about message 026 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 026 class 2q.027 - Domain link to domain &1 unknown
Additional information exists about message 027 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 027 class 2q.028 - Domain &1 unknown in its own domain &2
029 - You cannot link domains that have the same name
030 - Domain link cannot have a controller with the same name
031 - Follow the password rules for TMSADM (SAP Notes 1515926, 1414156)
Additional information exists about message 031 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 031 class 2q.Search for further information about these or an SAP related objects