topic RFC going dump in Application Development and Automation Discussions

RFC going dump

geetha_k — Sat, 23 Jul 2011 07:05:20 GMT

HI to all,

I have developed a RFC fucntion module for to calculate tax for every employee nubmer. Its showing tax details in portal. But when we execute same RFC in SE37 its showing dump. Why it can happen like that.can u suggest reason for that.

Re: RFC going dump

nirajgadre — Sat, 23 Jul 2011 08:52:10 GMT

Hi,

What is the dump you are getting...?

Re: RFC going dump

deepak_dhamat — Sat, 23 Jul 2011 08:56:55 GMT

hi ,

Please check whether return parameter in export

RETURN type BAPIRET1 is there or not .

call function 'BALW_BAPIRETURN_GET1'

exporting

type = 'I'

cl = '8I'

number = 152

par1 = msgv1

importing

bapireturn = return.

message id sy-msgid type sy-msgty number sy-msgno with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

endif.

regards

Deepak.

Edited by: Deepak Dhamat on Jul 23, 2011 10:58 AM

Re: RFC going dump

geetha_k — Sat, 23 Jul 2011 08:57:14 GMT

hort text

Exception condition "T500P_NOT_FOUND" raised.

hat happened?

The current ABAP/4 program encountered an unexpected

situation.

hat 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.

rror analysis

A RAISE statement in the program "SAPLHRPADINA1" raised the exception

condition "T500P_NOT_FOUND".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

Region not found for personal area

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

ow to correct the error

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:

"RAISE_EXCEPTION" " "

"SAPLHRPADINA1" or "LHRPADINA1U03"

"HR_IN_GET_ALGRP_ELIG"

"SAPLHRPADINA1" "T500P_NOT_FOUND"

"RS_TESTFRAME_CALL " "T500P_NOT_FOUND"

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.

nformation on where terminated

Termination occurred in the ABAP program "SAPLHRPADINA1" - in

"HR_IN_GET_ALGRP_ELIG".

The main program was "RS_TESTFRAME_CALL ".

In the source code you have the termination point in line 78

of the (Include) program "LHRPADINA1U03".

Re: RFC going dump

Clemenss — Sat, 23 Jul 2011 21:01:33 GMT

Hi Geetha,

probably the error is not related to RFC.

Regards,

Clemens

Re: RFC going dump

nirajgadre — Sun, 24 Jul 2011 05:44:20 GMT

Hi,

Check the all the parameters which on you are passing to the RFC function module are correct or not, while you executing the function module using SE37 transaction.

Since it is working fine from portal try to put the external break point and try to see what are parameters are getting passed to the RFC function module from portal.

Re: RFC going dump

Former Member — Sun, 24 Jul 2011 08:36:44 GMT

Hi,

Catch the exception T500P_NOT_FOUND in your RFC and react to it. You can use TRY..CATCH block or if exception is being raised by Function module then you can use EXCEPTION parameter while making call to RFC for T500P_NOT_FOUND.

Regards,

Alok.