BAPI_SAG_GETDETAIL Error

[Former Member]

Dear Guru's,

We're doing upgrade to EHP5 and having error in BAPI_SAG_GETDETAIL, Message type " " is unknown.

Bellow are the complete shortdump message, feedback would be appreciated.

Regards,

AT

[Former Member]

Short text
    Message type " " is unknown.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLMEOUT" 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" " "
    "SAPLMEOUT" or "LMEOUTP14"
    "IF_PURCHASE_OUT_FACTORY~CREATE_HEADER"
    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.
System environment
    SAP Release..... 702
    SAP Basis Level. 0009
    Application server... "dev01ec"
    Network address...... "10.1.7.17"
    Operating system..... "SunOS"
    Release.............. "5.10"
    Hardware type........ "sun4u"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 13
    Shortdump setting.... "full"
    Database server... "dev01ec"
    Database type..... "ORACLE"
    Database name..... "PED"
    Database user ID.. "SAPPED"
    Terminal.......... "AllanTheGreat"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Oct 16 2011 21:41:26"
    create on........ "SunOS 5.9 Generic_122300-28 sun4u"
    Database version. "OCI_102, 10.2.0.4.0, V3 "
    Patch level. 109
    Patch text.. " "
    Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
    SAP database version. 720
    Operating system..... "SunOS 5.9, SunOS 5.10, SunOS 5.11"
    Memory consumption
    Roll.... 0
    EM...... 29328656
    Heap.... 0
    Page.... 90112
    MM Used. 4121872
    MM Free. 4254904
User and Transaction
    Client.............. 350
    User................ "T_ALLANT"
    Language key........ "E"
    Transaction......... "SE37 "
    Transaction ID...... "4EDE873781FC1439E10000000A010711"
    EPP Whole Context ID.... "80144FAAED041EE188C1CB7C02F14B89"
    EPP Connection ID....... 00000000000000000000000000000000
    EPP Caller Counter...... 0
    Program............. "SAPLMEOUT"
    Screen.............. "SAPMSSY0 1000"
    Screen Line......... 6
    Debugger Active..... "(TPDA)"
Information on where terminated
    Termination occurred in the ABAP program "SAPLMEOUT" - in
     "IF_PURCHASE_OUT_FACTORY~CREATE_HEADER".
    The main program was "RS_TESTFRAME_CALL ".
    In the source code you have the termination point in line 2476
    of the (Include) program "LMEOUTP14".
Source Code Extract
Line  SourceCde
 2446 * contract, scheduling agreement or fail: get from reference if
 2447 * necessary
 2448     IF NOT im_doc_to_copy IS INITIAL AND
 2449            l_doc-doc_type IS INITIAL.
 2450       l_ebeln = im_doc_to_copy.
 2451     ELSEIF l_doc-trtyp EQ cl_mmpur_constants=>ver AND
 2452            NOT l_doc-doc_key(10) IS INITIAL.
 2453       l_ebeln = l_doc-doc_key(10).
 2454     ELSEIF l_doc-trtyp EQ cl_mmpur_constants=>hin AND
 2455            l_doc-doc_type = cl_mmpur_constants=>mmpur_contract.
 2456       l_is_contract = cl_mmpur_constants=>yes.
 2457     ELSEIF l_doc-trtyp EQ cl_mmpur_constants=>anz AND
 2458           l_doc-doc_key(10) IS NOT INITIAL.
 2459       l_ebeln = l_doc-doc_key(10).
 2460     ENDIF.
 2461     IF NOT l_ebeln IS INITIAL.
 2462       CALL FUNCTION 'ME_EKKO_SINGLE_READ'
 2463         EXPORTING
 2464           pi_ebeln         = l_ebeln
 2465         IMPORTING
 2466           po_ekko          = l_ekko
 2467         EXCEPTIONS
 2468           no_records_found = 1
 2469           OTHERS           = 2.
 2470       l_doc-doc_type = l_ekko-bstyp.
 2471       IF l_doc-doc_type = cl_mmpur_constants=>mmpur_contract.
 2472         l_is_contract = cl_mmpur_constants=>yes.
 2473       ELSEIF  l_doc-doc_type = cl_mmpur_constants=>mmpur_sag.
 2474         l_is_contract = cl_mmpur_constants=>no.
 2475       ELSE.
>>>>>         mmpur_message_forced sy-msgty sy-msgid sy-msgno sy-msgv1    "1476525
 2477                                       sy-msgv2 sy-msgv3 sy-msgv4.
 2478         RAISE EXCEPTION TYPE cx_mmpur_root.
 2479       ENDIF.
 2480     ENDIF.
 2481
 2482 - object creation -
 2483
 2484     CREATE OBJECT l_header
 2485       EXPORTING
 2486         im_document    = l_doc
 2487         im_tcode       = im_tcode
 2488 *       im_protect     = im_protect
 2489         im_doc_to_copy = im_doc_to_copy
 2490         im_is_contract = l_is_contract
 2491         im_options     = im_options.
 2492
 2493 - registration -
 2494     l_protect = im_protect.
 2495     IF l_protect EQ cl_mmpur_constants=>yes.
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 1
SY-DBCNT 1
SY-FDPOS 255
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM STRT
SY-TITLE Call test environment
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20111209
SY-UZEIT 094412
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT

[madhu_vadlamani]

Hi At,

Check these notes 1069602.

Regards,

Madhu.

[Former Member]

Hi Madhu,

I've tried to implement that note, but it's grey in snote.

I assumed that because it's obsolete in our version of EHP5

Regards,

AT

[madhu_vadlamani]

Hi Allan,

Can you raise a note to sap .

Regards,

Madhu.

[Former Member]

Hi Madhu,

Yes I can raise note to SAP, but I'm trying to find other workaround before using last resort.

Regards,

AT