Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Short dump during RFC Call

john_wayne
Participant
0 Likes
2,420

Im experiencing short dumps when calling the custom RFC function module.

Whats happening is that during the first call to the RFC i can extract up to 50k records but when i try to take another 50k records from the function module it gives me a short dump of

"Program not found."

An error occurred when executing a REMOTE FUNCTION CALL.

It was logged under the name "LOAD_PROGRAM_NOT_FOUND"

on the called page.

Anyone know why this happens when i try to RFC again?

17 REPLIES 17
Read only

madhu_vadlamani
Active Contributor
0 Likes
2,103

Hi,

But error looks like different. Is it a custom one or standard one.

Regards,

Madhu.

Read only

0 Likes
2,103

@madhurao123 what do you mean i dont think the error is customized.

@Deepak Dhamat what i have is that im looping to retrieve 50k data everytime i call the RFC. the thing is that on the first loop it can retrieve the RFC but for the second loop its not returning the record by ending in a dump

Read only

0 Likes
2,103

Hi,

I am not asking you about the error. I am talking about the RFC.

Regards,

Madhu.

Read only

0 Likes
2,103

its a custom RFC function module which grabs data and then send out the data.

Read only

0 Likes
2,103

Hi,

before you call your rfc fm additionally call fm RFC_CONNECTION_CLOSE.

Please check, if this can solve your issue.

Regards,

Klaus

Read only

0 Likes
2,103

Hi,

Please paste your code.

Whats happening is that during the first call to the RFC i can extract up to 50k records but when i try to take another 50k records from the function module it gives me a short dump of

so you are getting data of some number every time. If this is a situation you can check as Klaus told.

Regards,

Madhu.

Edited by: madhurao123 on Aug 11, 2011 11:38 AM

Read only

0 Likes
2,103

CALL FUNCTION 'Z_RFC_GETINFOTYPE' DESTINATION 'TEST

EXPORTING

iv_infotype = p_infty

iv_payroll = lv_payroll

IMPORTING

ev_maxrec = gv_max

TABLES

it_zc002 = gt_zc002sort

et_data = gt_data

et_return = gt_return

it_pernr = so_pernr

it_subty = so_subty

it_endda = so_endda

it_begda = so_begda

it_aedtm = so_aedtm

it_uname = so_uname

  • iv_lgart =

.

CALL FUNCTION 'RFC_CONNECTION_CLOSE'

EXPORTING

DESTINATION = 'TEST'

  • TASKNAME =

EXCEPTIONS

DESTINATION_NOT_OPEN = 1

OTHERS = 2

.

IF SY-SUBRC <> 0.

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

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

ENDIF.

Above is the RFC part of the program its within a loop outside.

Read only

0 Likes
2,103

Try calling ABAP4_COMMIT_WORK after calling your FM 'Z_RFC_GETINFOTYPE'


CALL FUNCTION 'CALL FUNCTION 'Z_RFC_GETINFOTYPE' DESTINATION 'TEST
EXPORTING
iv_infotype = p_infty
iv_payroll = lv_payroll
IMPORTING
ev_maxrec = gv_max
TABLES
it_zc002 = gt_zc002sort
et_data = gt_data
et_return = gt_return
it_pernr = so_pernr
it_subty = so_subty
it_endda = so_endda
it_begda = so_begda
it_aedtm = so_aedtm
it_uname = so_uname
* iv_lgart =
.

CALL FUNCTION 'ABAP4_COMMIT_WORK' DESTINATION 'TEST'.

CALL FUNCTION 'RFC_CONNECTION_CLOSE'
EXPORTING
DESTINATION = 'TEST'
* TASKNAME =
EXCEPTIONS
DESTINATION_NOT_OPEN = 1
OTHERS = 2
.
IF SY-SUBRC 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Edited by: Suresh Radhakrishnan on Aug 11, 2011 5:03 PM

Read only

0 Likes
2,103

sorry it does not resolve the problem

Read only

0 Likes
2,103

I see you are not handling exceptions SYSTEM_FAILURE and COMMUNICATION_FAILURE in the RFC call.

Also check whether you have "released" the RFM in the destination system.

Another thing is if you are calling this FM from a different system, just create a dummy FM 'Z_RFC_GETINFOTYPE' DESTINATION' in the system from where you make this RFC call without any source code. The import, export, tables parameters should be same.

Regards

Suresh

Read only

0 Likes
2,103

can you show me how to handle the exceptions you mention? anyway i fixed the error it was the data being passed that caused the error.

Read only

Read only

0 Likes
2,103

Hi,

To handle those internal exceptions, refer to the ABAP key word documentation link here : [CALL FUNCTION - DESTINATION parameter_list|http://help.sap.com/abapdocu_702/en/abapcall_function_destination_para.htm]

Regards

Suresh

Read only

deepak_dhamat
Active Contributor
0 Likes
2,103

hi ,

Exactly while what doing you get this error .

regards

Deepak.

Read only

0 Likes
2,103

Hi ,

IF you are debugging the RFC and you are extracting records from internal table then it have limitation of 50k .

when you debug it will not save more than 50k records in excel or any any .

regards

Deepak.

Read only

Former Member
0 Likes
2,103

Hi,

Check about internal table declaration in both source system and Target system, May be you are maintaining size for the internal table.

Ram.

Read only

0 Likes
2,103

internal table declaration? can you explain further? and also i reduced the number of extracted data to 500 records and it still have the error.