RFC Connection Problem

Former Member · ‎02-24-2006

I'm using 4.7 unicode system and accessing data through the portal. My problem is when I try to display a PO in the portal so that I can go a goods receipt, I'm getting this error "The function module "BAPI_MATERIAL_EXISTENCECHECK" not released for 'remote' calls., error key: RFC_ERROR_SYSTEM_FAILURE". If I check the attributes of this bapi, the processing type is remote-enabled module and start immediately for updates.

This is what's shown in ST22

untime Errors CALL_FUNCTION_NOT_REMOTE

Occurred on 02/24/2006 at 11:32:21

-

The function module "BAPI_MATERIAL_EXISTENCECHECK" not released for 'remote'

-

What happened?

-

The function module "BAPI_MATERIAL_EXISTENCECHECK" was called via RFC, but the 'Remote Function Call supported' flag is not set.

Error in ABAP application program.

The current ABAP program "SAPLBUS1001 " had to be terminated because one of the statements could not be executed.

This is probably due to an error in the ABAP program.

-

Error analysis

-

The function module "BAPI_MATERIAL_EXISTENCECHECK" was called via RFC, but has not been released for 'remote' calls.

With the following call types, a 'remote' calls must be supported:

a) CALL FUNCTION 'BAPI_MATERIAL_EXISTENCECHECK' DESTINATION ...

b) CALL FUNCTION 'BAPI_MATERIAL_EXISTENCECHECK' IN BACKGROUND TASK ...

c) CALL FUNCTION 'BAPI_MATERIAL_EXISTENCECHECK' STARTING NEW TASK ...

-

How to correct the error

-

If the function module is one of your own, go into the

Function Library and release the module "BAPI_MATERIAL_EXISTENCECHECK" for RFC calls

by setting the 'Remote Function Call supported' flag so

that it can be called externally.

RichHeilman · ‎02-24-2006

This BAPI is remote enabled in 46c. Is it in 4.7?

Go to SE37, enter the name of the BAPI, click display, click attributes tab. Is it flagged for "Remote Enabled"?

It definitly should be since it is a BAPI.

Regards,

Rich Heilman

Former Member · ‎02-24-2006

Hello:

Please enable your function as candidate for Remote call. Go to Abap workbench and search for your BAPI. Then in Attributes check:

PROCESSING TYPE -> REMOTE ENABLED MODULE

Re-activate the function afterwards

Hope it helps

Alejandro

Former Member · ‎02-24-2006

That's the first thing I did - I checked the attributes and yes, it is remote-enabled. That's why I'm really at a loss right now.

former_member188685 · ‎02-24-2006

Hi ,

Run the transaction BAPI, now click on the tab Alphabetical , now go to Material in the list left side, open it , now you can see

Existence Check, click on it.

now right side you can see some info about it like below..

                                                            
 Method               ExistenceCheck                                                                                
Business object      Material                                                                                
Short description    Check existence of object             
                                                            
 New in Release       31G                                                                                
Function module      BAPI_MATERIAL_EXISTENCECHECK          
                                                            
 ALE message type     Does not exist                                                                                
Instance-depend                                                                                
<b>Release status        Released</b>

what is there against Release Status check it, is it relased or not..

Regards

vijay

Former Member · ‎02-24-2006

Hi Vijay,

I did as you instructed and yes it is released.

Release Status = released

RichHeilman · ‎02-24-2006

Can we please see how you are calling it? Are you using a valid RFC destination?

REgards,

Rich Heilman

former_member188685 · ‎02-24-2006

Hi,

show the line# where you got the dump..

can you show the lines of code..

The current ABAP program "SAPLBUS1001 " had to be terminated because one of the statements could not be executed.

Regards

vijay

Former Member · ‎02-24-2006

I checked how it's being called and everything looks correct.

Here's the source code where the dump occured.

-

Information on where terminated

-

The termination occurred in the ABAP program "SAPLBUS1001 " in

"BAPI_MATERIAL_GET_DETAIL".

The main program was "SAPMSSY1 ".

The termination occurred in line 68 of the source code of the (Include) program "SAPMSSY1 "

of the source code of program "SAPMSSY1 " (when calling the editor 680).

-

Source code extract

-

000380

000390 module %_rfcdia_call output.

000400 "Do not display screen !

000410 call 'DY_INVISIBLE_SCREEN'.

000420 perform remote_function_diacall.

000430 endmodule.

000440

000450 module %_cpic_start.

000460 if sy-xprog(4) = '%RFC'.

000470 perform remote_function_call using rfctype_external_cpic.

000480 else.

000490 call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.

000500 perform cpic_call using convid.

000510 endif.

000520 endmodule.

000530

000540

000550 form cpic_call using convid type c.

000560 communication send id convid buffer header.

000570 if sy-subrc eq 0.

000580 perform (sy-xform) in program (sy-xprog).

000590 else.

000600 message a800.

000610 endif.

000620 endform.

000630

000640 form remote_function_call using value(type).

000650 do.

000660 * test if sy-xprog and sy-xform are set

000670 * sy-xform = 'quatsch'. sy-xprog = 'quatsch'.

-

> call 'RfcImport' id 'Type' field type.

000690 perform (sy-xform) in program (sy-xprog).

000700 rsyn >scont sysc 00011111 0.

000710 enddo.

000720 endform.

000730

000740 form remote_function_diastart.

000750 do.

000760 call 'RfcImport' id 'Type' field rfctype_rfcdia.

000770 perform (sy-xform) in program (sy-xprog).

000780 "Parking position for next request

000790 rsyn >scont sysc 00011111 10.

000800 "ALternativ : Free mode

000810 "COMMIT WORK.

000820 "SYSTEM-CALL FREE MODE 0.

000830 enddo.

000840 endform.

000850

000860 form remote_function_diacall.

000870 sy-xcode = '%_@no@'.

former_member188685 · ‎02-24-2006

Hi,

i feel you gave wrong rfc destination, that may be the reason for dump.

regards

vijay

Former Member · ‎02-24-2006

What's the value of TYPE? Is it a valid RFC destination?

Rob

RichHeilman · ‎02-24-2006

Please check that the RFC destination is valid in SM59, also you may want to do a connection test.

Regards,

Rich HEilman

Former Member · ‎02-24-2006

My Java guy and I checked how this BAPI is being called and everything looks fine. From all the BAPIs (notifications, orders, etc) we used in the portal, this is the only problem that we've encountered.

Former Member · ‎02-24-2006

I would like to show you the code on how the BAPI is being called, unfortunately, it's not my code to give. I don't know how it's being called in the Java side but I also had another ABAP person look at it who, by the way, is knowledgeable in Java, and she said that everything is correct.

RichHeilman · ‎02-24-2006

I believe you if you say that the call is good. Have you check the RFC destination? Do a connection test in SM59. What is being used to call this from java, jCo? JCA? Webdynpro model(Adaptive RFC)?

Regards,

Rich Heilman