1CO SAP Message class Correspondence Messages

Search SAP Messages

1CO 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(1CO).

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(1CO) with ld_field1.

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

050 - ********** Correspondence Recipient Messages *******************

051 - Map bank statement dispatch types and formats to dispatch control

Additional information exists about message 051 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 051 class 1co.

052 - Activate Correpondence Receiver Administration for product &1 version &2

053 - Entry already exists for Bank Area &1 Account Number &2 BP &3 in Role &4

054 - Unable to find bank statement address for BP &1, Bank Area &2, Account &3

Additional information exists about message 054 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 054 class 1co.

055 - Unable to find correspondence address for BP &1, Bank Area &2, Account &3

Additional information exists about message 055 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 055 class 1co.

Search for further information about these or an SAP related objects