RFC Call Missing

I am a novice at this and would like to get some suggestions from the gurus in this forum. I am trying to integrate an RFC call CTS_API_CREATE_CHANGE_REQUEST. But I do not see this RFC call using SE37. So I have two basic questions.
1) Is there a transaction that I can use to see a list of all RFC calls that are available in my R/3 system ?
2) Do I have to do anything to enable RFC calls, to be invokable from outside the SAP system ?
TIA
Yogi.

Ok, I am posting this for the benefit of everyone.
I figured out a mechanism by which all RFC and BAPI calls within an R/3 system can be listed.
1) Invoke Transaction SE37
2) With the cursor on the 'Function Module' field press F4.
3) In the popup that shows , press the 'Information System' button on the task bar at the bottom. Its the one with the 'Binocular' graphic.
4) Another popup called "R/3 Repository Information System: Function Modules" opens up.
5) The third icon from the right of the task bar at the bottom reads "All Selections". It is a white icon, with a green mark and a black down arrow. Click on that.
6) You now get an advanced search screen with lots more options than the ones previously displayed.
7) One of the radio's says "RFC modules", another checkbox says "Only modules for BAPI".
8) Set whatever you are interested in and hit the "Check"
Enjoy.
Thanks,
Yogi

Similar Messages

RFC Call: Missing namespace declaration

Dear experts,
I have a file to RFC scenario. I imported the RFC and create files exactly according to the RFC structure, so I don't use a mapping. When I create a file, it provides the following error in the adapter log:
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get functionname from XML requst: com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declaration(2)
What do I need to do to fix this.
Thanks in advance!

This is the whole message:
I created my own interface and mapped it to the RFC:
This is the message. Now it successfully pass XI and the adapter sais it is delivered.
BUT nothing is seen in the target system... how is that possible???
<?xml version="1.0" ?>
<ns:MT_TO_CREATE xmlns:ns="urn://cchbc/w2/xi/mes/warehousetransfer">
<LGNUM></LGNUM>
<TIMEST>20071207094550.0000000</TIMEST>
<WERKS>4510</WERKS>
<ZLAST>0</ZLAST>
<ZSCID>SCANPRD4</ZSCID>
<I_LTAP>
<item>
<EAN11>5449000003096</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48.000</VSOLM>
<LENUM>00345101239500010930</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:43:32</ZTIME>
<BRGEW/>
</item><item>
<EAN11>2229000058744</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48</VSOLM>
<LENUM>00000000003000002961</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:44:01</ZTIME>
<BRGEW/></item><item>
<EAN11>2229000058744</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48.000</VSOLM>
<LENUM>00000000003000002978</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:44:32</ZTIME>
<BRGEW/></item></I_LTAP></ns:MT_TO_CREATE>
And the output is:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:ZWM_TO_CREATE xmlns:ns1="urn:sap-com:document:sap:rfc:functions">
<LGNUM />
<TIMEST>20071207094550.0000000</TIMEST>
<WERKS>4510</WERKS>
<ZLAST>0</ZLAST>
<ZSCID>SCANPRD4</ZSCID>
- <I_LTAP>
- <item>
<EAN11>5449000003096</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48.000</VSOLM>
<LENUM>00345101239500010930</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:43:32</ZTIME>
<BRGEW />
</item>
- <item>
<EAN11>2229000058744</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48</VSOLM>
<LENUM>00000000003000002961</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:44:01</ZTIME>
<BRGEW />
</item>
- <item>
<EAN11>2229000058744</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48.000</VSOLM>
<LENUM>00000000003000002978</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:44:32</ZTIME>
<BRGEW />
</item>
</I_LTAP>
</ns1:ZWM_TO_CREATE>

XI RFC call failing

Hello,
 I am setting up a very simple scenario where I am making a sychronous RFC call to a BAPI in R/3 (Version 4.6c) from an XI Sandbox (Version 7.0).
 I have the RFC Communication channel properly configured, or so I think, and have verified everything else as well. I initiate the message from the Runtime Workbench and it shows with status "Successful" in the Message Monitoring section. However, when I look in SXMB_MONI transaction I am unable to find a response message from the BAPI coming back in the payload. I notice that even though the scenario is synchronous, the "Type" column in the SXMB_MONI transaction results shows it as "Asynchronous". Also, in the message details there is a Payload (which I am sending when I create and send the message from the RWB), in every step, until the Call Adapter step. After that there is no payload in the Call Adapter or the Response steps, just the SOAP Body with the Manifest.
 In the message details I see that the <SAP:Processing Mode> entry is set to "Asynchronous" rather than "Synchronous".
 Does anyone have any idea why this is so?
Thanks,
Murtaza.
Message was edited by:
 Murtaza Madraswala

Hi Amitabha,
 I looked in the location you suggested and got a list of "Success" messages. These are listed below for you to look at:
Time Stamp Status Description
2007-06-18 15:17:54 Success Message successfully received by messaging system. Profile: XI URL: http://camapox1:50100/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-06-18 15:17:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-06-18 15:17:54 Success Message successfully put into the queue.
2007-06-18 15:17:54 Success The message was successfully retrieved from the receive queue.
2007-06-18 15:17:54 Success The message status set to DLNG.
2007-06-18 15:17:54 Success Delivering to channel: GeneratedReceiverChannel_RFC
2007-06-18 15:17:54 Success MP: entering
2007-06-18 15:17:54 Success MP: processing local module localejbs/RfcAFBean
2007-06-18 15:17:54 Success RFC adapter received an asynchronous message. Attempting to send tRFC for Z_SD_RFC_ATP_WRAPPER with TID XIlc32S1tf4Togkm0mRWaHRG
2007-06-18 15:17:55 Success MP: leaving
2007-06-18 15:17:55 Success The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
2007-06-18 15:17:55 Success The message status set to DLVD.
 The problem that I am seeing is that this is posted under the list of Asychronous Received Messages. Thats something I am just unable to understand. I have a Synchronous Outbound Interface defined and an RFC Communication Channel, which is Synchronous as far as I know. So why is the processing mode for the message being chosen as Asynch? Which config setting have I missed that is causing this problem? I am just unable to find the answer so far.
 I appreciate your help. Please let me know if you have any clues.
Thanks,
Murtaza.

SLD setup for UDF to RFC Call in XI

Hello,
I am trying to create a UDF that has an RFC Call to the XI backend and I have it working in my development system. But for some reason I cannot create the Business Service > Communication Channel > GeneratedReceiverChannel_RFC in my Assurance system.
I'm guessing it has something to do with a missing connection in my SLD but right now I can't see what could be missing. What do I need to create in the SLD to allow XI to appear as a business service?
Thanks,
Matt

Hi
you dont need to do anything in SLD
follow this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70d90a91-3cf4-2a10-d189-bfd37d9c3231
infact there is another way (from what is explained in this doc), even without importing the RFC in IR/ ESR
more info
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b64ca6-b1e3-2b10-4c9b-c48234ccea35
Regards
Vishnu

Question on service userid - for RFC call

Hi
In XI 3.0 SP18 , we are making a RFC call from XI mapping runtime - to XI's ABAP stack - RFC function module . In the RFC receiver communication channel , I tried using service user XIISUSER , XIAPPLUSER for this RFC call - I got short dumps on XI ABAP stack mentioning that these two service users do not have authorization to make RFC calls -
Does anybody out there know what service user on XI has RFC call authorization that can used to make RFC calls onto XI ABAP stack from its mapping runtime ?
Correct answers will be rewarded rightaway. Thanks for your time in advance.

Hi,
u have to make entry in sld...
Hi,,
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
The Client must be the client number of the backend SAP system.
Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
Double-click on the business system in the Integration Directory.
Switch to Edit mode.
Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
The RFC Destination is from step 3.1.
The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Reward points if find useful.

FILE to multiple BAPI/RFC calls

Hi,
I have one input source (CSV with about 100 rows) and I wish to call a custom rfc for each row in my spreadsheet. (The custom RFC has a single flat import structure as opposed to a table or anything complex).
I am struggling to do this in XI.
I assumed I needed to assign one source to multiple targets in the Message interfaces, but this errors on activation due to the RFC occurrence being set to 1.
Do I need to do the same trick as with IDOCS or am I missing the point somewhere?
I have read several threads and one in particular seems to indicate it is possible, but so far this has evaded me.
Re: BOM CREATION
Please could you point me in the right direction.
Thanks
Andrew

Andrew,
You could read the CSV file into an Integration Process
Save the message in a multiline container (in your case 100 rows)
Create a block
Create another container to hold the single row defined within this block
Set the following for the block
Step Name eg SplitForRFC
Mode ParForEach
Multiline Element Multiline container defined above
Current Line Single line container defined above
The Mode 'ParForEach' acts like a loop
Then within the block create a synchronous Send step which calls your RFC
Design
I would question having to make 100 RFC calls
If possible change the design so that the RFC interface can accept multiple messages and the RFC logic to loop through them and process the messages one at a time
Regards,
Mike

"No Receiver Determined" in BPM Sync RFC Call

My scenario is xml file -> XI BPM -> RFC1 -> RFC2 (will call RFC2 if RFC1 is successful).
I am still just trying to get the RFC1 call working properly. I have been using blogs 1822, 1403 and 1926. I have also used some related BPM threads. It seems to be making the RFC call properly, but failing on the response.
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
These docs show my IB Repository and Directory setups. Can anyone look at them and tell me what is missing? Thanks in advance!
http://webpages.charter.net/kpwendel2/bsmDir.jpg
http://webpages.charter.net/kpwendel2/bsmRep.jpg

Keith,
the problem is quite clear.
In your BPM, you have a synchronous interface in your sync send step.
However, in configuration, you have configured two asynchronous interfaces.
To be able to use sync send step in BPM, your RFC needs to be able to send a response back. Then you need to have two message mappings (one for bpm->rfc messages, and other for rfc_response -> bpm_response messages) and a interface mapping between the 2 sync interfaces (bpm_sync_int -> rfc_sync_int) using these 2 message mappings.
Also, some hints:
1. Don't do these mappings in BPM transformation step. You can execute them outside of BPM. Doing this, you will get better performance and also won't need to create abstract interfaces for RFC messages.
2. Use configuration wizard in Integration Directory (first, remove and reimport your BPM in Integration Directory). This way, you avoid different interfaces errors.
Regards,
Henrique.

Finding caller program in a RFC call

Hi experts,
We are having lots of CALL_FUNCTION_NOT_FOUND short dumps in one of our systems. The errors are caused because other systems call a function that does not exist, so the dumps are created.
What we would like to know is what program is doing these calls, since all we can see in the short dump is the caller system and the function it is trying to access, but not the exact program where the call is performed so we can fix the code.
Thanks in advance for your support.

Sorry if this is too much of a wall of text, I can't find an "attach file" type feature.
ABAP runtime errors CALL_FUNCTION_NOT_FOUND
 Occurred on 11.12.2006 at 10:04:34
Function module "Y_EF_DETERMINE_PICTURE" not found.
What happened?
The function module "Y_EF_DETERMINE_PICTURE" was called, but cannot be
found in the Function Library.
The current ABAP/4 program "SAPMSSY1 " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
The program "SAPMSSY1 " contains a CALL FUNCTION statement. The name
of the function module to be called is "Y_EF_DETERMINE_PICTURE".
No function module exists with the name "Y_EF_DETERMINE_PICTURE".
All function modules are stored in the Function Builder (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
 to upper/lower case and underscores ("_").
or
b) Transport error
c) In the case of an enqueue/dequeue module, the lock object
 may not have been activated (ABAP Dictionary).
How to correct the error
Check the last transports to the R/3 System.
Is the program "SAPMSSY1 " currently being changed?
If an enqueue/dequeue module is involved, is the activation
of the lock object missing in the ABAP/4 Dictionary?
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"CALL_FUNCTION_NOT_FOUND"
"SAPMSSY1 " or "SAPMSSY1 "
"REMOTE_FUNCTION_CALL"
Function modules with names similar to "Y_EF_DETERMINE_PICTURE":
Y_EF_USEX_DETERMINE_TAX
Y_GF1_DETERMINE_RECTYPE
Y_GK_DETERMINE_PRCTR
Y_EF_USEX_PICTURE_SUBMIT
Y_EF_USEX_SHOW_PICTURE
Y_EF_RFC_PICTURE_POST
Y_GF1_DETERMINE_SBU
Y_GF_DETERMINE_VERSION
Y_GF_DETERMINE_DATE_PREVMON
Y_GF1_DETERMINE_CURRENT_PERIOD
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
 To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
 To obtain this, call the system log with Transaction SM21
 and select the "Print" function to print out the relevant
 part.
3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, you can either use the "PRINT" command in the editor or
 print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
 or which actions and input led to the error.
System environment
SAP Release.............. "46C"
Application server....... "sapgp1s"
Network address.......... "52.99.71.21"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C4449E4C00"
Database server.......... "sapgp1s"
Database type............ "DB6"
Database name............ "GP1"
Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "46D"
Created on............... "Aug 26 2005 22:40:31"
Created in............... "AIX 1 5 0056AA8A4C00"
Database version......... "DB6_71 "
Patch level.............. "2113"
Patch text............... " "
Supported environment....
Database................. "DB6 06., DB6 07., DB6 08.*"
SAP database version..... "46D"
Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3
5, , System build information:, -
, LCHN :
User, transaction...
Client.............. 000
User................ "SAPSYS"
Language............ "E"
Transaction......... " "
Program. ........... "SAPMSSY1 "
Screen. ............ "SAPMSSY1 3004"
Line of screen...... 2
Information about Remote Function Call (RFC) Caller:
System.............. "WP1 "
Database release.... "46C "
Kernel release. .... "46D "
Connection type. ... "3 " (2 = R/2, 3 = R/3, E = Extern, R = Reg.
Call type........... "S-" (S = synch., a/A = asynch., T = transactional
Client.............. 510
User................ "PC1706 "
Transaction......... "/COCKPIT/1 "
Function module..... "Y_EF_DETERMINE_PICTURE"
Call destination.... "GP1590"
Source server....... "wsdux44_WP1_10"
Source IP address... "52.99.71.124"
Additional information about RFC logon:
Trusted relationship " "
Logon return code... " "
Trusted return code. " "
Note: In Releases earlier than 4.0, some of the above information about
RFC calls may not be available.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPMSSY1 " in
"REMOTE_FUNCTION_CALL".
The main program was "SAPMSSY1 ".
The termination occurred in line 67
of the source code of program "SAPMSSY1 " (when calling the editor 670).
Source code extract
000370 ENDMODULE.
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.
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
000650 FORM REMOTE_FUNCTION_CALL USING VALUE(TYPE).
000660 DO.
 CALL 'RfcImport' ID 'Type' FIELD TYPE.
000680 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000690 RSYN >SCONT SYSC 00011111 0.
000700 ENDDO.
000710 ENDFORM.
000720
000730 FORM REMOTE_FUNCTION_DIASTART.
000740 DO.
000750 CALL 'RfcImport' ID 'Type' FIELD RFCTYPE_RFCDIA.
000760 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000770 "Parking position for next request
000780 RSYN >SCONT SYSC 00011111 10.
000790 "ALternativ : Free mode
000800 "COMMIT WORK.
000810 "SYSTEM-CALL FREE MODE 0.
000820 ENDDO.
000830 ENDFORM.
000840
000850 FORM REMOTE_FUNCTION_DIACALL.
000860 SY-XCODE = '%_@no@'.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 1
SY-TABIX 0 SY-DBCNT 0
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+....4
SY-XPROG
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
SY-XFORM Y_EF_DETERMINE_PICTURE
 554454454544445544555422222222
 9F56F45452D9E5F093452500000000
%_SPACE
 0
 0
SY-MSGID
 22222222222222222222
 00000000000000000000
EBC_TO_ASC-X05 P&QéRêSëTèUíVîWïXìY~ZÜ[$*])^;_^
 525E5E5E5E5E5E5E5E575D5252525355
 06192A3B485D6E7F8C9EACB4CAD9EBFE
RFCTYPE_QUEUE 6
 0000
 0006
%_PRINT 000
 2222333222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 80 0 ########
 2222222222320000000022222222222222222222
 0000000000000000000000000000000000000000
... + 120
 22222222
 0000000
SY-MSGNO 000
 333
 000
EBC_TO_ASC-X04 @ A BâC{DàEáFãGåHçIñJÄK.L<M(N+O!
 424A4E474E4E4E4E4E4F4C4243424242
 0010223B405163758791A4BECCD8EBF1
SY-MSGV1
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40
 2222222222
 0000000000
SY-MSGV2
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40
 2222222222
 0000000000
SY-MSGV3
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40
 2222222222
 0000000000
SY-MSGV4
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40
 2222222222
 0000000000
%_?NOT_ASSIGNED?
 2222
 0000
SPACE
 2
 0
SY-REPID SAPMSSY1
 5454555322222222222222222222222222222222
 310D339100000000000000000000000000000000
TYPE 3
 0000
 0003
SYST ########################################
 0000000000000000000000000000000000000000
 0001000000000000000000000000000000000000
... + 40 ########################################
 0000000000000000000000000000000000000000
 0000000000010000000100000000000000000000
... + 80 ########################################
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
... + 120 #######################################T
 00000000
 0000000
Active calls / events
No.... Type........ Name..........................
 Programm
 Include Line
 1 FORM REMOTE_FUNCTION_CALL
 SAPMSSY1
 SAPMSSY1 67
 2 MODULE (PBO) %_RFC_START
 SAPMSSY1
 SAPMSSY1 31
Internal notes
The termination occurred in the function "link_rfdir" of the SAP
Basis System, specifically in line 165 of the module
"//bas/46D/src/krn/runt/ablink.c#3".
The internal operation just processed is "CALY".
The internal session was started at 20061211100434.
Active calls in SAP kernel
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = unlimited
=> Core limit = 51200000
=> File size limit = unlimited
=> Heap address = 0x118dba360
=> Stack address = 0xfffffffffff5d50
=> Stack low = 0xfffffffffff5d50
=> Stack high = 0xffffffffffff600
=> Stack Trace:
 AixStack() at 0x100059364
 CTrcStack2() at 0x10005945c
 rabax_CStackSave() at 0x10003959c
 ab_rabax() at 0x1000425b4
 link_rfdir() at 0x100540418
 ab_link() at 0x100540a18
 ab_rfcimport() at 0x1005f49f0
 ab_jcaly() at 0x100024560
 ab_extri() at 0x100487474
 ab_xevent() at 0x10059c804
 ab_dstep() at 0x10043bd98
 dynpmcal() at 0x100942f94
 dynppbo0() at 0x100941320
 dynprctl() at 0x100948f40
 dynpen00() at 0x1008f7818
 Thdynpen00() at 0x1001429f4
 TskhLoop() at 0x100146368
 tskhstart() at 0x1001576ac
 DpMain() at 0x100e06e38
 main() at 0x100de72f4
List of ABAP programs affected
Type
Program
Gen. date time
LoadSize
Prg
SAPMSSY1
04.01.2000 19:06:59
20480
List of internal tables
No dump information available
Directory of application tables (contents)
Program
Name.......... Contents.1........2........3....+....
Directory of data areas (administration information)
Program
No.. Name.......... Lgth Ofsg Type Next Gen date Gen time
SYST
 L not assigned -15 0 IN
 M /%_LISTTABLE -14 1 CO 0
 T global stack -13 1 2 GL 0
SAPMSSY1
 A global data 0 3 DA
 L constant dat 1 4 LI .0 .0216
 L constant dat 2 5 LI SSY .0 .018B
 L not assigned 3 6 IN
 L SYST 4 7 TA 0
 L SY 5 8 TA
 L RSJOBINFO 6 9 TA
 M /%_SYS%% 7 0 CO
 M field symbol 8 1 FS
 L TCPIC 9 2 TA
 M field symbol 10 3 FS
 L text pool 11 4 TP
Directory of data areas (contents)
Program
No.. Name.......... Contents..1........2........3....+....
SYST
 L not assigned 0
 L text pool 102 |SAPMSSY1
ABAP control blocks CONT
Include Line source code
Index Name F1 Co Par01 Par2. Par3. Par4. Tabl
SAPMSSY1 60 MESSAGE A800.
215 CLEA 00 84
216 CLEA 00 85
217 MESS 00 27
SAPMSSY1 62 ENDFORM.
218 ENDF 00
219 -
223 -
SAPMSSY1 65 FORM REMOTE_FUNCTION_CALL USIN
227 PERP 00 1
228 PERP 02
SAPMSSY1 66 DO.
229 WHIL 00 2
233 WHIL 00 3
237 BRAN 05 Branch to 251
SAPMSSY1 67 CALL 'RfcImport' ID 'Type' FIE
238 CALY 00 3 86 70 71 71
>>>>> CALY 02 87 P0
SAPMSSY1 68 PERFORM (SY-XFORM) IN PROGRAM
246 xper 02 12 13
248 PERP 80
SAPMSSY1 69 RSYN >SCONT SYSC 00011111 0.
249 SYSC 1F
SAPMSSY1 70 ENDDO.
250 BRAX 00 Branch to 233
251 WHIL 00 4
SAPMSSY1 71 ENDFORM.
255 ENDF 00
256 -
End of runtime analysis

Locking objects across RFC calls

Hi All,
I am developing a business application using SAP UI5 and the NetWeaver Service Gateway in an embedded scenario. I have RFCs build for the backend interaction. As per my knowledge, each RFC is considered as a separate transaction and the user is logged on and off as the RFC is processed. This removes the lock on the object that I need to be sustained till the next RFC call. Unlocking the object exposes it to possible editing by other users which is not desirable.
From what I have studied from this community, there are, by and large, two solutions
1. Custom Lock Table
2. Checking if the status of the object is the same during the second RFC call, and going ahead only if it was unchanged.
However, I am looking for more credible solution to this problem and would like to know how someone who experienced this issue have handled it.
Thanks in advance,
Neelesh

Hi Jacob
S_RFC and S_SERVICE This two authorization is nedded while calling RFC module from R3.
first of all test the module in R3. create a role using PFCG assign the tcode. su53 (authorization check) and also assign the S_RFC and S_SERVICE to role.
now test the RFC function module with this role in R3.
if u give any warning/error due to authorization. imediate run tcode su53 in same session or new session
i.e /nsu53 or /osu53.
look which authorization is missing for a object.
assign the relevant object and authorization to role.
any query revert back.
regards,
kaushal

RFC call in Servlet problem

Hello,
I have servlet in my web application module, and I try to make RFC call, within it. I use com.sap.mw.jco.*.
I compile it but when run the server respond with
Application error occurs during processing the request.
Details: java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO The ID of this error is
Exception id: [000C763FB7EE00390000001F000007E800043A148A45F9B4
I think that I should packaged the jco lib in my war and make it available to servlet, but how can I do this ?
Thank for any help.

Hello,
Thanks a lot Maksim, Bhavik, you helped me.
I try to make a reference and now the library ClassNotFound error is gone.
But now I have a next problem with RFC call, I also wrote it to post (Webdynpro VS. Java Servlet). I have a code in which I make RFC call. When I embed this code into regular Java aplication and run, it will return results as I expect. (of course I must run it with jco lib .jar in classpath). But when I run it on my servlet, I got an exception with message: "'mshost' missing"
I don't know what this supposed to mean, because I run the mentioned application, also from PC where I have j2ee engine installed and it work.
If you can please help.
(and thank for your help again (Maksim, Bhavik))

Program making a RFC call to Function Module not working in background

Hi All,
I have an ABAP Program which is used to do a reconciliation check between the R/3 and BI system for Invoice Data. Please find below the details of the program flow:
1.     Program counts the number of records in the DSO table and aggregates the Net_Value based on the date range (passed as parameters)
2.     Program calls a Function Module (RFC Call) which counts the number of records in the R/3 table and aggregates the Net_Value for the same date range
3.     Function Module Passes back the count values and aggregated Net_Value to the program
4.     Program compares the count and aggregated Net_Value from EDWH and MSP systems and sends an email mentioning whether the counts match or not
However we are facing an issue.
Whenever, we execute the program in dialog mode, it works fine and fetches results within 5-6 minutes. However if we schedule the program to run in background (parameters through a variant), it gives no results even after running for over 3-4 hours. We tried figuring it out yesterday but could not come to any conclusion. Since there is a RFC call being to the function module, we were wondering if we need to specify some other parameter as well.
Thanks & Regards
Dharmendra

RFC Call is a procedure for executing remote enables function modules. It is done via the 'Remote Enabled' radio button on the function module's attribute screen.

Assigning value returned from RFC call to a global variable

If I have an RFC call to SAP how can I assign the value returned to a global variable on my data services job?

Hi,
For now, it seems u haven't specified the destination properly. the call function statement must be suffixed with the 'destination' addition to make sure that the function call is an RFC and the particular function be executed at the desired destination.

Is there any way to limit the number of RFC calls from xMII to SAP R/3

Hi All!
I wanted to know whether the number of simultaneous RFC connections made from xMII to SAP R/3 system can be controlled in any way. Suppose we have a scenario wherein some million Sales Orders or Production Orders are to be updated in SAP R/3 from xMII in a short span of time. For all these updations to take place, multiple RFC calls will be established from xMII to SAP at the same time. This will increase the load on the SAP R/3 system and affect performance of the SAP R/3 system. Is there any check on xMII side to limit the number of RFC calls that can be made to SAP R/3 system?
Regards
Anupam

Anupam,
If you are using 11.5 just keep in mind that the JCO connection points to a single application server (based upon the SAP Server alias connection settings), but the traffic itself to make a BAPI request is effectively the same as any client user traffic. There will obviously be limitations on performance and throughput, with network and server constraints added to the number and size of the R/3 requests, but there is no magic formula to plug-in because of all of these variables.
If you are using 12.0 (or plan to migrate when it goes GA) then taking advantage of the JRA (java resource adapter) and the associated application server pooling that it offers on the NetWeaver side of things will greatly help you in the throughput capacity.
If you have put some of your xMII application into either test or productive use and are running into issues then I would highly recommend entering the specifics into the customer / partner support portal so that they can help you through any associated problems.
Regards,
Jeremy Good

SAP R/3 RFC Call to XI

Hallo,
My scenario is as follows: when sending a RFC to XI via the RFC adapter, I get a short dump with the following error: "the error occurred in an RFC call to another system (XI).The termination occurred in the function "RfcExtendedReceive" of the SAP
Basis System, specifically in line 392 of the module
"//bas/640_REL/src/krn/rfc/abrfcrcv.c#2".
The internal operation just processed is "FUNC".
The internal session was started at 20060125163632".
The RFC adapter has been configured as the Sender and all the parameters populated with the system details.
Has someone seen this eror before?
Please assist.
Thanks,
Catherine

Maybe you're invoking RFC synchrounously from ABAP code and your receiving scenario is on Asynchrounous interfaces? What are you doing then in XI with data sent by the RFC?
Message was edited by: Alessandro Guarneri

Flat File-to-RFC question, multiple RFC calls for one file.

Hi guys,
I'm quite new to XI / PI and I have a question regarding a File-to-RFC scenario we're trying in NW PI 7.1.
We have a flat file which has two lines with two fields each, let's take this as an example :
001,001
002,002
The files needs to be converted to XML and then transferred to the RFC program which will update a table with the values above.
In the ESR I've created 3 data types (z_row1,z_record1 and z_fileinput1), 1 message type (z_file2rfc_ob_mt), 1 message mapping (z_file2rfc_mm), 2 Service Interface (z_file2rfc_ob_si and z_file2rfc_ib_ztestpi) and 1 operation mapping (z_file2rfc_om).
In the Integration Builder (ID) I've created everything required (The sender and receiver communication channels, sender and receiver agreement, receiver determination and interface mapping).
We're also using content conversion to convert the flat file to XML, this does seem to work because I see all the lines/field in the message when it gets into PI. The problem is that the RFC can only accept two fields at a time and only the first line gets updated. I see that only the first line gets sent to the RFC.
How can I make the RFC call for each and every line ?
Thanks !!

Create the RFC with table, which takes multiple lineitem as input and update the table in single call.
If you want response back then call RFC as synchrounous else in Asynchrounous mode.
By doing this in single call it will update the complete table.
Gaurav Jain
Reward Points if answer is helpful

RFC Call Missing

Similar Messages

Maybe you are looking for