MESSAGE_TYPE_UNKNOWN

[Former Member]

Hi ABAP gurus ,

please provide me the solution sothis dump.

Country  NL
System  SAP P10
Area  EDI
daily we they are  getting 24 dumps (every hr) in P10.
Dump – MESSAGE_TYPE_UNKNOWN
User - hjkuyhi

Program - SAPLPC32
FM - TP_INVOICE_CVTYP_CHECK
As per log it says, “Message type is unknown” and as per error analysis “Only message types A, E, I, W, S, and X are allowed”.
is TRFC is responsible for dump which was executed same time when dump occurred.

Runtime Errors         MESSAGE_TYPE_UNKNOWN
Date and Time          2012-09-17 23:41:46

Short text
     Message type " " is unknown.

What happened?
     Error in the ABAP Application Program

     The current ABAP program "SAPLPC32" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.

What can you do?
     Note down which actions and inputs caused the error.

     To process the problem further, contact you SAP system
     administrator.

     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.

Error analysis
     Only message types A, E, I, W, S, and X are allowed.

How to correct the error
     Probably the only way to eliminate the error is to correct the program.
     -

   If the error occures in a non-modified SAP program, you may be able to
   find an interim solution in an SAP Note.
   If you have access to SAP Notes, carry out a search with the following
   keywords:

   "MESSAGE_TYPE_UNKNOWN" " "
   "SAPLPC32" or "LPC32U12"
   "TP_INVOICE_CVTYP_CHECK"

   If you cannot solve the problem yourself and want to send an error
   notification to SAP, include the following information:

   1. The description of the current problem (short dump)

      To save the description, choose "System->List->Save->Local File
   (Unconverted)".

   2. Corresponding system log

      Display the system log by calling transaction SM21.
      Restrict the time interval to 10 minutes before and five minutes
   after the short dump. Then choose "System->List->Save->Local File
   (Unconverted)".

   3. If the problem occurs in a problem of your own or a modified SAP
   program: The source code of the program
      In the editor, choose "Utilities->More
   Utilities->Upload/Download->Download".

   4. Details about the conditions under which the error occurred or which
   actions and input led to the error.

Information on where terminated
    Termination occurred in the ABAP program "SAPLPC32" - in
     "TP_INVOICE_CVTYP_CHECK".
    The main program was "SAPMSSY1 ".

    In the source code you have the termination point in line 101
    of the (Include) program "LPC32U12".

78             NO_CVPROF_FOR_KOKRS = 2

79             KOKRS_NOT_FOUND     = 3

80             OTHERS              = 4.

81

82 * check if transfer pricing  is active

83   CHECK SY-SUBRC = 0 AND

84         ACTIVE   = 'X'.

85

86 * defaults

87   group = gc-false.

88   prctr = gc-false.

  89

  90   if not i_ebeln is initial and not i_ebelp is initial.

  91     CALL FUNCTION 'ME_EKPO_SINGLE_READ'

  92          EXPORTING

  93               PI_EBELN            = i_ebeln

  94               PI_EBELP            = I_ebelp

  95          IMPORTING

  96               PO_EKPO             = ekpo

  97          EXCEPTIONS

  98               others                   = 8.

  99

100     IF SY-SUBRC <> 0.

>>>>       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

102               WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

103     ENDIF.

104   endif.

105

106 * if group or prctr valuation exist, then the default says there should

107 * be seperate values for these valuations

108   LOOP AT T_TCVPROFD.

109     if T_TCVPROFD-valutyp =  GC-VALUTYP_GROUP.

110       group = gc-true.

please provide the solution,

Regards,

vanamala kashavena

[iftah_peretz]

Hi Arpita,

The problem is caused exactly where the arrow shows, i.e line 101 in program  SAPMSSY1 in include LPC32U12.

To fix this just comment the line 101 and line 102 and the problem will be solved.

Or put a message you want to screen like this (instead of lines 101 and 102):

MESSAGE 'WHAT WILL SHOW ON STATUS BAR' TYPE 'I'.

Instead of type 'i' (which stands for information) you can use types A, E, W, S, and X where type E(error) will halt the process at that case.

From what it seems the first option of making lines 101,102 into a comment is what the code writer intended, otherwise he would have taking care of the messages to begin with.

The reason for this is that the person that made the code at that point, probably, used the pattern button in the ABAP editor when he inserted the function 'ME_EKPO_SINGLE_READ', as a default the code:

IF SY-SUBRC <> 0. 

      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

     WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

  ENDIF.

is added, however these variables are not defined - or in the error lingo - are unknown.

This will solve your problem.

All the best,

Iftah

[Former Member]

this is the standard program and the standard functional module

[Former Member]

Hi

The dump is very easy: the fm is trying to select a purchase document doesn't exist.

Try to check if there's a SAP note, but if there's no note, probably some inconsistency is in the data, because that error is was not expected.

Max

[Former Member]

What I can suggest to the client

i have searched for the sap notes also i did not found any note for this

Regards,

vanamala kashavena

[iftah_peretz]

HI,

The correction I have suggested will solve this issue - even if its a  SAP program.

This will be a first aid kind of solution and you can continue your research in the meanwhile.

Best,

Iftah.

[Former Member]

Hi

Yes your solution will works but it needs to considere it's a standard program:

so if you think it's all correct (I mean the data and how the user runs the report), you should open an OSS message to SAP, it could be a bug not solved yet.

Max

[iftah_peretz]

Hi Max,

First off I agree with you, read what I said - this is a first aid solution.

Arpita, try implementing   notes 548121,676245,321767,392649,411846,129238,215949,117852,155094,144536,305159,

425212,305159,605273,452513,64289,460254,202640,138886,508702,130022,119773,400859,336085,

78412,377910,126826,542666.

These are all notes that are directly associated with this program and helped us with issues in this process.

Best,

Iftah.

[Former Member]

this dump is coming in the idoc process daily they are getting around 100 dumps same.

in sm58 ,in the targetsystem it is showing NONE