How to Debug RAISE_EXCEPTION SAPLARFC Dumps

[maryjane_steele2]

I am getting dumps daily on my ERP system during BW runs with RAISE_EXCEPTION SAPLARFC START_DEST. When I go into SM58 the LUWs have already be reprocessed so how can I find the original cause of the dump?

[maryjane_steele2]

I am getting dumps daily on my ERP system during BW runs with RAISE_EXCEPTION SAPLARFC START_DEST. When I go into SM58 the LUWs have already be reprocessed so how can I find the original cause of the dump?

[Isaias_SAP]

Hello Mary,

Can you attach the dump to this question?

Please save it as a text file (select "unconverted").

Regards,

Isaías

[maryjane_steele2]

I cannot attach the dump because it tells me that the file type is invalid.

[Isaias_SAP]

Try renaming the file to ".txt".

It should work then.

If not, try compressing it ("zip").

[maryjane_steele2]

It is a .txt file and I still get the error message. zip files are not permitted.

[Isaias_SAP]

test.txt

That is strange... I could do it...

[Sandra_Rossi]

RAISE_EXCEPTION means it's a programming error (trigger of a classic exception which is not handled by the calling program). If it's from a standard program, then search a correction in SAP notes (if no correction, raise a ticket at SAP support), or if it's a custom program then ask the developer to have a look at the short dump.

[Jelena_Perfiljeva]

ST22 does not show where the dump came from? I'm confused...