Skip to Content

SM51 - wrong messages 14 027 "Transaktions-Abbruch"

Hi collegues, I hope my question is not fully "out of scope" in this group. One of my daily tasks is to check for the help of our SAP EPR system, by using among others transaction sm51. Our system is on SAPKB74010 -- however, in the selection screen it got a check mark "Nur Mel.m.hohem Schweregrad" (Only Messages with high importance). Now, even with this check mark set I get a flood of entries in syslog displayed with text "Transaktions-Abbruch 14 027 ()" (transaction canceled 14 027 (). The reason is, that users tried to open more GUI sessions then allowed in system settings. I would regard this as an error, as this only leads to missing realy important syslog entries -- it only filles up the syslog. But bevore opening a support message -- is there a simple solution for this, which I (more used to SAP ERP module PM) do miss? May be some customizing, which messages are to be treated as "m.hohem Schweregrad" (high importance), which one should be in syslog, which one should not be stored in syslog at all? Thanks, kind regards, Holger

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Nov 03, 2015 at 09:41 AM

    Hello Holger,

    could you already clarify your question? Do you mean the transaction SM21? Which severity has the syslog message "transaction canceled 14 027"? In the syslog you cannot decide, which syslog message should be stored in the syslog, you can only filter the syslog messages. There is no possibility to suppress the syslog messages.

    As far as I see in our test system in SE92 the syslog message "transaction canceled" has the syslog number D01 and has the severity "red with alert". This is why you see it with the selection "Only Messages with high importance". You could change the severity of the syslog message in SE92.

    Regards, Alwina

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Alwina, As the documentation of D01 states -- it comes always with a t100 message (Messages displayed/maintained in se91). As the notes mention too: The application decides. So I think the application needs to be changed. If the application ends by sending a MESSAGE Axxx I get the disturbing D01 messages in the syslog... In my eyes some of the error situations in the SD application do not qualify for a syslog message, but the developers at SAP obviously decided otherwise. In the end, it looks like nothing I can do about this. Thanks and regards, Holger