Different ABAP message types

There is an ABAP statement called a MESSAGE that can be used to raise an message from an program to drive it. The message a form of text identified by its ID. The message ID is associated with the text that can be maintained in multiple languages. Along the ID, there is also message type with the message.

The message type is classified by one character that defines how the message is displayed in SAP GUI and it drives further flow of the ABAP program.

Following are message types:

A termination (Abort) message, also called as ABEND (Abnormal END, see Similarities of SAP and mainframes)

E Error message

I Information message

S Status message

W Warning message

X eXit message

 

The message type is stored in domain MSGTY used in system structure SYST.

At first sight, one may say that message type A and E are the same. However, there is a difference. In case, A message type the program is ultimately terminated after the message is raised and it cannot be resumed in this case. In case of E message type, the error message raised and program processing is interrupted. Once the message is acknowledged, processing can continue.

Inconsistency in delta administration

Recently I encountered following error related to delta mechanism:

Inconsistency in delta administration RSM1363

 

Message appeared in my case when I attempted to browse an InfoPackage. If you get this error message InfoPackage is not accessible at all. I research on this message. I came across interesting site which pointed me into way how to resolve this error.

Basically root cause seem to be in tables on ECC and on BW sides storing information on delta initialization requests. It might be that in BW table RSSDLINIT contains entry for initialization for specific data source. On other hand table ROOSPRMSC in ECC does not contain entries for the same.

According note 852443 - Dump in include LRSSMU36/RSSM_OLTPSOURCE_SELECTIONS there are five scenarios that could happened. Two of them are mentioning ABAP report RSSM_OLTP_INIT_DELTA_UPDATE. This tool can be used to delete init selections in the 'Scheduler/Init selections in the source system' menu in the InfoPackage.

Notice that before you do any changes into the BW system you need to study above mentioned note and also other listed below:

873401 - Consulting: Data mart delta administration/duplicate data

873694 - Consulting: Delta repeat and status in monitor/data target

 

System manipulation error message

Here another stories about odd SAP BW system messages. This time it is error message that you may face after or during system copies. Especially in case system copy was not properly or entirely finished. When you would run e.g. TA RSA1 during system copy it may appear. The message is following:

"system manipulation!!!" SAP BW R3208

Internal control tables have been changed manually in the system by someone in your company. This leads to errors in all the connections to other systems.
To prevent further manipulation of the tables, you are no longer able to make changes in the system.

 

Issue is cause by mixed entries in RSBASIDOC table. Resolution is manual check of content of this table followed by manual adjustment of entries in this table. It can be for example that you have 2 systems with same names assigned (e.g. two myself BW system).

See some other stories about SAP system error messages:

SAP system crashes

BEx related error messages:

librfc32.dll troubles

Few more BEx messages 2

SAP BW: BEx Connectivity Issue

Error when opening BEx Query Analyzer under SAP GUI 7.10

DSO objects related error messages:

Further checking of broken DSO objects