Tracing an external RFC call

Hi
I am calling a Remote Function Module from a web dynpro application in BW system but somehow it is not functioning properly. I want to find out if the control has actually reached the Function Module in BW system and then some error is happening or the control is not reaching the BW system at the first place .Is there a mechanism/transaction in the BW system by which i can trace whether some RFC call is being made from outside to a FM and if at all some error is happening in that Func Module then what the exception is ?..
please help
regards
Nilesh Taunk.

Hi !
Go to the ST11 and have a look to the devrfc files.
RFC-Activities arfe traced into this files when RFC-Trace is swiched on.
Regards
Rainer
Some points would be fine if that helped a bit.

Similar Messages

Reset or Clear SAP user context by external RFC caller program

Hello,
I have a SAP system with performance problems due to a SAP user context starts using a lot of memory.
This user context comes from an External RFC caller program written in Delphi and which uses the SAP RFC SDK provided by SAPGUI 6.40: SAP Automation library, SAPFuntionsOCX, I mean, using methods in the object "SAPFunctions" in SAPFunctionsOCX in file "wdtfuncU.ocx", in SAPGUI directory.
Everytime we have performance problems, this RFC SAP user context is using near 1400 Mb of extended memory, although there is a lot of free physical RAM memory available, there are free dialog processes and CPU load is low (no more than 30%).
This performance problem is solved by closing the external program (written in Delphi) which connects to SAP via RFC.
This external program works for the warehouse management and connects to SAP several times per minute. Due to connection performance and the high frequency with which this external program must connect to SAP, the connection to SAP is not closed after each call to RFC SAP function modules.
The extended memory used by this SAP RFC user is growing along time. I detected, using ST03 transaction, that these user sessions have always the same transaction code hash, I mean, although the external programs call the same SAP RFC funcion modules several times (¡¡¡ always clearing the variables at the beginning and at the end of de ABAP code, with ABAP commands like REFRESH and FREE ¡¡¡¡) the technical transaction code is the same and I suppose the user context (in extended memory) is not deleted.
I think it is better than the external program close the context memory (similar to "/n" okcode in SAPGUI).
But we don't want to close the connection, because the external program connects to SAP with a high frequency, and the logon process is expensive.
Is there any way to send something similar to "/n" (end of transaction) from the external program? Is there any command in the SAP RFC SDK library (SAPFuntionsOCX or something similar?
I cannot find any method to do that in the object "SAPFunctions" in SAPFunctionsOCX in file "wdtfuncU.ocx", in SAPGUI directory.
Old information for Object Classes "SAPFunctions" in SAPFunctionsOCX in file "wdtfuncU.ocx", in SAPGUI directory, is described in the following URL:
http://help.sap.com/saphelp_45b/helpdata/en/39/7e00d1ac6011d189c60000e829fbbd/frameset.htm
But I cannot find anything related to something similar to a "/n" in SAPGUI.
As I have the SAPGUI installed on my desktop, I can see all SAP RFC classes and methods from Excel, by opening the Visual Basic editor.
I am only asking a way to send to SAP a command to free the user context used for an open RFC session in order to avoid the memory used to be continuously growing, without having to close the RFC session.
The external program only calls a certain SAP function module periodically and we want to free the user context between calls without logging off. This is the same, very similar, as if we called that function from SAPGUI and we used "/n" in SAPGUI between calls.
Anyone can help me?
Thanks and best regards.

Hello,
I don't know if this will solve your problem, but you may be using MF 'RFC_CONNECTION_CLOSE' between each call of you RFC function.
Regards
Brice
Edited by: blsapsdn on Apr 15, 2011 5:27 PM

How to prevent simultaneous external RFC calls

Hi all
We are facing some problems when external systems are caliing one of our RFC's simultaneously.
Is there a way to prevent and RFC to be called simultaneouslly?
Thanks a lot for your support.
Rui Simões

Hi,
We cannot stop external systems to call the RFC. They will call at their own leisure.
However, so as to keep a check so that processing time does not get wasted,
and if we want that only one can call the RFC at a time, we can write some
code inside the RFC.
For this we can create a z lock object and lock it inside the RFC. Just before the last line of the code, we can unlock it also.
In the middle we can write the code that if the lock object is already locked, then it can exit and can return some error message.
But by doing this, it may impact the understanding of the existing RFC by the external system.
Regards,
Amit Mittal.

Error in Mapping of external RFC reponse

Hi experts,
I have big problems with my current scenario. I tried to call a C-program by using RFC connection.
synchronous RFC scenario:
request:
Sender SAP-System RFC-Adapter> XI RFC-Adapter> receiver C-program
on both sides I use RFC-Adapter and the flags of unicode is also set,
on sender side I have created a simple RFC adapter, this side works without problems.
On receiver side I have create an external RFC call. Here a RFC destination which is created on my SAP XI sap Gateway is invoked by the RFC Adapter. My C-program registers the program id of this RFC at receiver side. So by testing the RFC connection (transaction SM59) the RFC works fine.
The request mapping includes on both side the same RFC-structure.
response
Sender SAP-System <RFC XI <RFC receiver C-program
The response mapping includes on both side the same RFC response structure.
When I execute my scenario by calling the ABAP-Program in my SAP system, it seems that request works fine, but during the response in the integration engine following error occurs:
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:1, col:377) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor264.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy189.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor931.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:275) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:217) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7803) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8164) at com.sap.mw.jco.JCO$Server.work(JCO.java:8284) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8231) at com.sap.mw.jco.JCO$Server.run(JCO.java:8147) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:124) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:1, col:377) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:1, col:377)(:main:, row=1, col=377) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:1, col:377) at com.sap.engine.lib.xml.parser.XMLParser.handleContentReference(XMLParser.java:2327) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2458) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:1, col:377) at com.sap.engine.lib.xml.parser.XMLParser.handleContentReference(XMLParser.java:2327) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2458) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_KQ3_TOMATOS_RESPONSE_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:1, col:377)
So could anybody help me.
Thanks a lot.
Best regards
Mario

Hi Jai,
thanks for your fast reply.
I have checked my payload but there is no col. 377. When I copy the following response payload into the mapping test tool it works fine.
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:_-MSG_-4_PM_TOMATOS.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<ET_DIMMARKS_FLOAT />
<ET_DIMMARKS_INTEGER />
<ET_DIMMARKS_STRING />
- <ET_ERRORS>
- <item>
<SEQ_NO>-1</SEQ_NO>
<ERROR_NR>16777216</ERROR_NR>
<RC>-1518068224</RC>
<ERROR_TYPE>E</ERROR_TYPE>
<DESCRIPTION>The data context cannot be found </DESCRIPTION>
<ERROR_CLASS>PM.TOMATOSX error </ERROR_CLASS>
<MODULE_NAME>PM.TOMATOSX </MODULE_NAME>
<MESSAGE>No standard data context is defined. </MESSAGE>
<INSTANCE_NAME> </INSTANCE_NAME>
<PM_MARKNAME> </PM_MARKNAME>
<CALLPOS> </CALLPOS>
</item>
</ET_ERRORS>
<ET_INFOS />
<ET_MARKS_DIMSIZE />
<ET_MARKS_FLOAT />
<ET_MARKS_INTEGER />
<ET_MARKS_STRING />
<ET_OBJECTS />
<ET_PLAUSIS />
<ET_PROFILES />
<ET_PROFILE_MODS />
<ET_RELATIONS />
<ET_STATISTICS />
<IT_DIMMARKS_FLOAT />
<IT_DIMMARKS_INTEGER />
<IT_DIMMARKS_STRING />
<IT_MARKS_DIMSIZE />
<IT_MARKS_FLOAT />
<IT_MARKS_INTEGER />
<IT_MARKS_STRING />
<IT_METHODS />
<IT_METHOD_PARAMS />
<IT_OBJECTS />
<IT_OPTIONS />
<IT_RELATIONS />
<IT_SEQUENCES />
</rfc:_-MSG_-4_PM_TOMATOS.Response>
So have you any idea, what the problem could be.
Best regards
Mario

Strange response time for an RFC call viewed from STAD on R/3 4.7

Hello,
On our R/3 4.7 production system, we have a lot of external RFC calls to execute an abap module function. There are 70 000 of these calls per day.
The mean response time for this RFC call is 35 ms.
Some times a few of them (maybe 10 to 20 per day) are way much longer.
I am currently analysing with STAD one of these long calls which lasted 10 seconds !
Here is the info from STAD
Response time : 10 683 ms
Total time in workprocess : 10 683 ms
CPU time : 0 ms
RFC+CPIC time : 0 ms
Wait for work process 0 ms
Processing time 10.679 ms
Load time 1 ms
Generating time 0 ms
Roll (in) time 0 ms
Database request time 3 ms
Enqueue time 0 ms
Number Roll ins 0
 Roll outs 0
 Enqueues 0
Load time Program 1 ms
 Screen 0 ms
 CUA interf. 0 ms
Roll time Out 0 ms
 In 0 ms
 Wait 0 ms
Frontend No.roundtrips 0
 GUI time 0 ms
 Net time 0 ms
There is nearly no abap processing in the function module.
I really don't uderstand what is this 10 679 ms processing time especially with 0 ms cpu time and 0 ms wait time.
A usual fast RFC call gives this data
23 ms response time
16 ms cpu time
14 ms processing time
1 ms load time
8 ms Database request time
Does anybody have an idea of what is the system doing during the 10 seconds processing time ?
Regards,
Olivier

Hi Graham,
Thank you for your input and thoughts.
I will have to investigate on RZ23N and RZ21 because I'm not used to use them.
I'm used to investigate performance problems with ST03 and STAD.
My system is R/3 4.7 WAS 6.20. ABAP and BASIS 43
Kernel 6.40 patch level 109
We know these are old patch levels but we are not allowed to stop this system for upgrade "if it's not broken" as it is used 7/7 24/24.
I'm nearlly sure that the problem is not an RFC issue because I've found other slow dialog steps for web service calls and even for a SAPSYS technical dialog step of type <no buffer>. (what is this ?)
This SAPSYS dialog step has the following data :
User : SAPSYS
Task type : B
Program : <no buffer>
CPU time 0 ms
RFC+CPIC time 0 ms
Total time in workprocs 5.490 ms
Response time 5.490 ms
Wait for work process 0 ms
Processing time 5.489 ms
Load time 0 ms
Generating time 0 ms
Roll (in+wait) time 0 ms
Database request time 1 ms ( 3 Database requests)
Enqueue time 0 ms
All hundreds of other SAPSYS <no buffer> steps have a less than 5 ms response time.
It looks like the system was frozen during 5 seconds...
Here are some extracts from STAD of another case from last saturday.
11:00:03 bt1fsaplpr02_PLG RFC R 3 USER_LECKIT 13 13 0 0
11:00:03 bt1sqkvf_PLG_18 RFC R 4 USER_LECDIS 13 13 0 0
11:00:04 bt1sqkvh_PLG_18 RFC R 0 USER_LECKIT 19 19 0 16
11:00:04 bt1sqkvf_PLG_18 RFC R 4 USER_LECKIT 77 77 0 16
11:00:04 bt1sqkve_PLG_18 RFC R 4 USER_LECDIS 13 13 0 0
11:00:04 bt1sqkvf_PLG_18 RFC R 4 USER_LECDIS 14 14 0 16
11:00:05 bt1sqkvg_PLG_18 RFC R 0 USER_LECKIT 12 12 0 16
11:00:05 bt1sqkve_PLG_18 RFC R 4 USER_LECKIT 53 53 0 0
11:00:06 bt1sqkvh_PLG_18 RFC R 0 USER_LECKIT 76 76 0 0
11:00:06 bt1sqk2t_PLG_18 RFC R 0 USER_LECDIS 20 20 0 31
11:00:06 bt1sqk2t_PLG_18 RFC R 0 USER_LECKIT 12 12 0 0
11:00:06 bt1sqkve_PLG_18 RFC R 4 USER_LECKIT 13 13 0 0
11:00:06 bt1sqkvf_PLG_18 RFC R 4 USER_LECKIT 34 34 0 16
11:00:07 bt1sqkvh_PLG_18 RFC R 0 USER_LECDIS 15 15 0 0
11:00:07 bt1sqkvg_PLG_18 RFC R 0 USER_LECKIT 13 13 0 16
11:00:07 bt1sqk2t_PLG_18 RFC R 0 USER_LECKIT 19 19 0 0
11:00:07 bt1fsaplpr02_PLG RFC R 3 USER_LECKIT 23 13 10 0
11:00:07 bt1sqkve_PLG_18 RFC R 4 USER_LECDIS 38 38 0 0
11:00:08 bt1sqkvf_PLG_18 RFC R 4 USER_LECKIT 20 20 0 16
11:00:09 bt1sqkvg_PLG_18 RFC R 0 USER_LECDIS 9 495 9 495 0 16
11:00:09 bt1sqk2t_PLG_18 RFC R 0 USER_LECDIS 9 404 9 404 0 0
11:00:09 bt1sqkvh_PLG_18 RFC R 1 USER_LECKIT 9 181 9 181 0 0
11:00:10 bt1fsaplpr02_PLG RFC R 3 USER_LECDIS 23 23 0 0
11:00:10 bt1sqkve_PLG_18 RFC R 4 USER_LECKIT 8 465 8 465 0 16
11:00:18 bt1sqkvh_PLG_18 RFC R 0 USER_LECKIT 18 18 0 16
11:00:18 bt1sqkvg_PLG_18 RFC R 0 USER_LECKIT 89 89 0 0
11:00:18 bt1sqk2t_PLG_18 RFC R 0 USER_LECKIT 75 75 0 0
11:00:18 bt1sqkvh_PLG_18 RFC R 1 USER_LECDIS 43 43 0 0
11:00:18 bt1sqk2t_PLG_18 RFC R 1 USER_LECDIS 32 32 0 16
11:00:18 bt1sqkvg_PLG_18 RFC R 1 USER_LECDIS 15 15 0 16
11:00:18 bt1sqkve_PLG_18 RFC R 4 USER_LECDIS 13 13 0 0
11:00:18 bt1sqkve_PLG_18 RFC R 4 USER_LECDIS 14 14 0 0
11:00:18 bt1sqkvf_PLG_18 RFC R 4 USER_LECKIT 69 69 0 16
11:00:18 bt1sqkvf_PLG_18 RFC R 5 USER_LECDIS 49 49 0 16
11:00:18 bt1sqkve_PLG_18 RFC R 5 USER_LECKIT 19 19 0 16
11:00:18 bt1sqkvf_PLG_18 RFC R 5 USER_LECDIS 15 15 0 16
The load at that time was very light with only a few jobs starting :
11:00:08 bt1fsaplpr02_PLG RSCONN01 B 31 USER_BATCH 39
11:00:08 bt1fsaplpr02_PLG RSBTCRTE B 31 USER_BATCH 34
11:00:08 bt1fsaplpr02_PLG /SDF/RSORAVSH B 33 USER_BATCH 64
11:00:08 bt1fsaplpr02_PLG RSBTCRTE B 33 USER_BATCH 43
11:00:08 bt1fsaplpr02_PLG RSBTCRTE B 34 USER_BATCH 34
11:00:08 bt1fsaplpr02_PLG RSBTCRTE B 35 USER_BATCH 37
11:00:09 bt1fsaplpr02_PLG RVV50R10C B 34 USER_BATCH 60
11:00:09 bt1fsaplpr02_PLG ZLM_HDS_IS_PURGE_RESERVATION B 35 USER_BATCH 206
I'm thinking also now about the message server as there is load balancing for each RFC call ?
Regards,
Olivier

Error in starting SAP GUI as part of an Java RFC call from a PC

Hi,
We are on the 4.6C version of SAP and have the latest basis kernel patches that allow an RFC connection to start the SAP GUI. The program that I am running externally is java using the 3.0.1 JCo. The OS of the PC I am using is Windows XP. The SAPGUI version is 7.10 patch level 11.
The program seems to be working properly as the command prompt window goes grey as if there is another window being opened but then I get back this error message and I do not see the GUI.
The message I am getting back is:
Exception in thread "main" com.sap.conn.jco.JCoException:(136) JCO_ERROR_ILLEGAL_STATE:Launching SAP GUI failed, though it was requested(error message:Communication with SAPGUI timed out)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.startSAPGui(MiddlewareJavaRfc.java:1853)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1285)
at com.sap.conn.jco.rt.ClientConnection.connect(ClientConnection.java:661)
at com.sap.conn.jco.rt.PoolingFactory.init(PoolingFactory.java:103)
at com.sap.conn.jco.rt.ConnectionManager.createFactory(ConnectionManager.java:171)
at com.sap.conn.jco.rt.DefaultConnectionManager.createFactory(DefaultConnectionManager.java:44)
at com.sap.conn.jco.rt.ConnectionManager.getFactory(ConnectionManager.java:160)
at com.sap.conn.jco.rt.RfcDestination.initializ(RfcDestination.java:766)
at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:794)
at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:32)
at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:865)
at GISToSAPWO_Test.get_wo_call(GISToSAPWo.java:91)
at GISToSAPWO_Test.main(GISToSAPWO_Test.java:206)
I have been all over trying to find the solution to this and have come up empty. Any help will be greatly appreciated. If this is the wrong forum for this please let me know and I will re-post.
Thank you in advance for any information you can pass on about the issue,
Mark

Hi Greetson,
Thank you in advance for your response. It is greatly appreciated.
1) In a way yes. I am using the connection setting USE_SAPGUI = 1. This is suppose to start the GUI prior to starting the RFC's program run. If this is not correct please let me know.
2) The code is part of the JCo and the RFC library from what I have read. If this is not correct please let me know.
3) I am only testing from my PC at this moment. I have re-installed my SAP GUI and am now at patch level 13 on 7.10.
4) The application passes in the connection information which includes username and password along with the parameters for the RFC call. I would like the SAP GUI to open without the user having to re-enter his/her username and password. I thought that once the RFC is called using the dialog users credentials that the GUI would then open using the connection. I have used the java pooled connection method and it still does not open the GUI.
5) The purpose is to pass Equipment objects, Functional Location objects and Leak Id objects to an RFC to open a list screen from IW39, List Maintenance Order transaction, for display of each at one pass, as well as open Excel with data from classification for the Leak Id's.
Hope this sheds some light on the problem I am having. Please let me know if more information is needed.
Best regards,
Mark

RFC calls with SAP table insert - lock tables

Hi,
I have an external server program, which is calling a rfc function many times the same time with different transaction types. There are transaction types, which are downloading information from SAP (only send data back to the caller), and there are transaction types which are uploading data to SAP (inserting/updating data on SAP).
The function calls are synchronous as the server needs to get feedback directly. The parallel work processes for RFC calls are limited, so a system overload can´t happen.
The problem now is, if the server is down for while and going to be restarted, it´s opening parallel threads and calls the function in SAP at nearly the same time. That means, it will call the function with upload requests (table must be locked), and download requests the same time.
In the upload requests, the table has to be locked, that it can´t occur that we get wrong entries...
I can only enqueue the table with just two fields... I know, that is almost like locking the whole table, but it´s not possible to lock it in a different way.
I tried to use the enqueue function with the parameter WAIT, but it didn´t help, as there where too many parallel calls and after some seconds, they were ending up with an error (Because the table has been locked by another call).
It seems that it´s trying to lock the table again for all parallel calls at exactly the same time....
The calls has to be synchronous, as the server needs to get the feedback directly. Any ideas how top solve this, that it handles all incoming calls parallel and waits for the table is unlocked again?
Thank you for your help!

Hi,
thank you for your answer!
I have investigated something new yesterday:
I thought at the beginning, that the problem just occurs, when the system work processes are reached. The system has for example set up 15 dialog processes and the external server is calling the function 20 times in parallel. Then we normally need 5 dialog processes more. The system is taking then all 15 dialog processes and the locks got stucked.
That means, that I´ll maybe only get 4 or 5 uploads, which have really been updated the tables. All the others couldn´t get the table locked for their process.
But if I now let the server call the function just about 13 times in parallel, nearly all uploads have been updated the table!
From my point of view, the lock from SAP gets stucked, when the limit of dialog processes is reached. It´s not working in the right way anymore...
The same is happening, when you set up in the system, that only 10 work proecesses can be used by RFC. If I have more than 10, it´s going to be critical with the locks....
WEIRD!
Can anybody help me out of trouble?
Thank you!

RFC CALL canu00B4t execute Functions module ??

Hello everybody,
I have a problem with a Function module. The function module should open an link (it´s a Link of a Webdynpro Application).
I have the following constellation.
Bex Analyzer execute a RFC Call to open/execute the Function module. The Function module should open a URL (Webdynpro Application), but it doesn´t work.
I don´t know why. The Connection of the RFC Call is ok. I have tested the RFC with any Object´s and it works (He "answered").
What ist wrong in the Function Module, why can´t the FM open the URL??!
Simple Code of Function Module
call method cl_gui_frontend_services=>execute
exporting
document = 'URL'
exceptions
others = 1.
Endfunction.
A other test
*CALL FUNCTION 'PRGN_GENER_EXECUTE_URL'
*EXPORTING
*NODE_DATA = 'url'.
The VBA Code for RFC
Sub Login()
Dim functionCtrl As Object
Dim sapConnection As Object
Dim theFunc As Object
Dim sReturn As Boolean
Dim l_export As String
Dim objQueryTab As Variant
Set functionCtrl = CreateObject("SAP.Functions")
Set sapConnection = functionCtrl.Connection
sapConnection.Client = "100"
sapConnection.user = "xy"
sapConnection.Language = ".."
sapConnection.SystemNumber = "xy"
sapConnection.ApplicationServer = "xy"
sapConnection.Language = "x"
sapConnection.codepage = "xy"
sapConnection.Destination = "xy"
sapConnection.System = "x"
sapConnection.SystemID = "......"
sapConnection.Password = "xy"
sapConnection.autologon = 1
If sapConnection.Logon(0, True) <> True Then
MsgBox "Keine Verbindung"
Else
Set theFunc = functionCtrl.Add("SS_RFC_URL_TEST")
objQueryTab = "200"
theFunc.Exports("I_PAR") = objQueryTab
sReturn = theFunc.call
If sReturn = True Then
objQueryTab = theFunc.Imports("E_PAR")
End If
sapConnection.logoff
End If
End Sub
>E_PAR is the Exportparameter of the Function module
>I_PAR is the Importparameter of the Function module
Thanks
Edited by: Schwarzenberger Stefan on May 9, 2011 1:59 PM

Hi, I have a similar situation. Within VBA I am calling the RFC 'RFC_CALCULATE_TAXES_DOC'. This RFC is used to communicate with external tax software like Taxware; it gets applicable tax rates, amounts, etc. based on tax jurisdiction code and other data. The RFC is remote-enabled (has to be to talk to Taxware).
This RFC requires an RFC Destination in order to work. Within VBA, I have not been able to figure out the syntax required to enter the Destination name. I saw Shreeram's post saying to use CALL FUNCTION 'PRGN_GENER_EXECUTE_URL' DESTINATION <RFC Destination Name>. However, this looks like ABAP syntax and not VBA syntax.
Does anybody know if this is possible within VBA? Sounds like it's not but wanted to double-check.
Thanks!!
Kory Squire
<<Removed email address>>
Edited by: Matt on May 18, 2011 6:37 AM

RFC call from ECC to SCM -- Debug Steps required

Hello,
The steps being done for this issue is:-
1) In ECC system ,CN22 Transaction Code (Change Networks) --> Click on Schedule (at the Header) and click on SAVE
2) This seems to trigger an RFC call to SCM server (as per the trace log).
3) From SCM, it comes back to ECC server as User 'BATCHRFC'. This has been defined in SM59 correctly.
4) BATCHRFC in ECC system calls an RFC FM 'CIF_PJ_INBOUND' and changed the status of networks to DSEX (date set by External system)
We are trying to understand why is the RFC call being made? I can debug the FM in ECC when an external breakpoint is used.
However, I want to know where in ECC is the RFC call made (to SCM), and how? How can I control it as we do not want this to happen? How can I debug to understand how an RFC call is made?
Your views would be appreciated.
Regards,
Sanjiv

Hi,
What you do is, enter the Tcode, CN22, then in Command window activate debugger by entering /H
It takes u to debugger, from menu > utilities set a break point at Satetment Call Function, it will stop at all the Function modules in debugger, so you can look for the RFC FM in the program where it is called.
And also look for setting in debugger, may be u have some options for RFC FM.
Regards
Bala Krishna

RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'

Hi, All
the system is PI 7.0 EHP1 oraclei Win2003 server, I configured SLD but I run RZ70, having error "RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA' ". I know there are lot of tread about this error, but none of themsolve my problem. all JCO, RFC connections and SDL DATA supplier(VA) seem OK. error message in SM21 is "Could not send SLD data"
detail from SM21
The system could not send the data that has been collected automatical
for the System Landscape Directory (SLD). Check whether the gateway
configured in transaction RZ70 has been started and whether the SLD
bridge has been registered with this gateway.
You can use transaction SM59 to check this in the sending system for t
implemented RFC destinations. The RFC destinations have the standard
names "SLD_UC" for Unicode sending systems and "SLD_NUC" for non-Unico
sending systems. If a different RFC destination has been entered in
RZ70, check this destination instead.
You can use the Gateway Monitor to check the target gateways. In ABAP
systems, this monitor is started with transaction SMGW, or you can use
the external SAP program "gwmon". Check whether the specified gateway
has an active registration.
OF COURSE I checked RFC of SLD_UC and SMGW
any different ideas
Regards
ABH

Hi
Please check the following notes are implemented
Note 906454
Note 907729
You may be aware but if you are not --->RZ70 creates the required SLD* RFCs during runtime - therefore if you have defined these RFCs manually first using the same namespace you can get RFC conflicts which result in a failed submission
Please also check the user in the RFC is known to both systems and has required authorization to write to SLD
Generally with SLD you have to install or select a suitable gateway to handle incoming data supply traffic
Also the gateway you are using has be known to SLD and reflected in RZ70 - i.e these defintions have to be the same
It is also recommended to delete all references to SLD_* RFCs in data supplier and target SLD
after a failed submission attempt to allow RZ70 to recreate these consistently once the above has been checked
Best wishes
Stuart

RFC Call error..

Hi All XI Expert,
I am facing an issue with regard to RFC call from an external system.Business flow is like, Purachase Requisition(PR) is created from Ariba system/application which is passed to SAP via TIBCO Adapter to create Purchase order(PO).As per my understanding the data flow is like this: Ariba PR data's are captured by Ariba Adater and are send to TIBCO ADAPTER.This TIBCO adapter will invoke request-response service from SAP Adapter for operation of SAP RFC calling.Now i am able to successfully create PR/PO from Ariba application with amount(more than $10mn with after decimal value as 00) say $12,000,000.00 / $15,000,000.00. But while creating PR/PO from Ariba application with amount (more than $10mn with after decimal value as other than 00 i.e .99, .78, .05 etc) say $12,000,000.99 / $15,000,000.08, it gives below error which are captured in Ariba side, hence unable to create PR/PO's more than $10mn, however for less than $10mn amount of PR/PO with after decimal value as other than 00 i.e .99, .78, .05 etc, it is successfully getting created.So the problem is amount with more than $10mn PO with after decimal value as other than 00 i.e .99, .78, .05 etc.
Error found in Ariba side for above scenarion:
" Thu Apr 09 12:21:49 EDT 2009 (integrationExternal:error:4745): Received a Tibco generated message: 2009 Apr 9 12:21:49:079 GMT -5 SAPAdapter.SAInboundRFC.psap1 Error Application AER3-000185 CallReceive failed for operation Z_ARIBA_PO_PUSH; exception : Unable to interpret 1.10000005E7 as a number., RFC error; Group/Key/Message: 104/CONVT_NO_NUMBER/Unable to interpret 1.10000005E7 as a number.
Where could be the problem?Does it a TIBCO Adapter config/ SAP adapter Problem / SAP RFC code issue?
FYI....SAP RFC that is getting called doesnot contain any code of "CONVT_NO_NUMBER" .
Awaiting your reply guys

The problem is that in case the value of the amount is greater than $10mn, then it is converting the numeric value into exponential number 1.10000005E7. This is a number but when RFC tries to treat it as a number, it is throwing the exception. At sender Ariba system, you may change some configuration to avoid changing of numeric field to exponential field and problem would get resolved.
Regards,
Prateek

Is BAPI_TRANSACTION_ROLLBACK supported in external RFC applications?

Hello,
maybe someone could shed some light into this.
I am writing an external RFC client application using library librfc32.dll. The application calls a custom RFC module, which inserts a record in a custom Z* table. This RFC module does not invoke, explicitly or implicitly (at least, not that I am aware of) the COMMIT WORK operation.
After this RFC module call the RFC/BAPI module BAPI_TRANSACTION_ROLLBACK is called. The intent is, of course, to rollback the operation from the previous RFC call. Yet the rollback attempt fails and the inserted record is not removed from the table.
An ABAP program making the exact same calls to those RFC modules, however succeeds.
Has anyone an explanation for this behavior? Thank you!

Hi,
In case of a WARNING message, the ROLLBACK wont happen automatically whereas in case of an ERROR message, the ROLLBACK would happen.
But to be on safer side, it is always good to call BAPI_TRANSACTION_ROLLBACK irrespective of the message type ( Warning or Error).
Same is the case with COMMIT. If you dont give an explicit commit work, the data would be COMMITED once the transaction/process is completed without any error/warning messages.
Best regards,
Prashant

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

How to send an idoc of lower release to an External RFC server

Hi All,
I am sending idocs from the sap system to an external rfc server(written using Sap RFC SDK).
When an idoc is sent from the Sap system, I receive an IDOC_INBOUND_ASYNCHRONOUS call in the external RFC server with the Idoc data.
Everything works fine with the latest release of idocs. But if I send an Idoc of lower release number, I am getting the data records properly for the lower release(say 640). But the DOCREL field (in the control record- EDI_DC40) always gives me the latest release number(700)
In my partner profile, I specify the Segment release number to 640 and even then I am receiving the value 700 in DOCREL.
What am I missing here? How can I populate the DOCREL field with the appropriate release number?
Any help would be greatly appreciated.
Thanks
PS: Please feel free to move this post to appropriate category, if this is not the one.

Serigo,
Thanks for your reply and we are not using XI.
I have defined in the port definition giving the path name refering to unix like /outbound/<system name>/<directory name>. But I dont know how to define for C:\temp\, if I define the same way as c:\temp\ do I need define anything anywhere else ?
Kindly let me know.
Thanks,
Kalikonda.

Disable Vertex Tax Jurisdiction Code Validation & RFC Call

We want to disable calling vertex for tax jurisdiction code in some cases based on sales org & division. For a small business unit we are using SAP ECC 5.0 SD module to create customers & sales orders. These orders are placed via a external non-SAP front-end and are entered into SAP via a BAPI/RFC create customer & create sales order call. The front-end calculates all the prices and tax and passes that to SAP via the BAPI call. SAP accepts the prices & tax as-is (due to how we've configured SAP for these types of orders) and does not recalculate price or tax. However, on SAP we have external tax configured to call Vertex Q Series via Translink which we currently use to determine jurisdiction code & sales tax for other business units & for use tax. This external non-SAP front-end does not have any address validation therefore the addresses we receive are not always good (ex. they abbreviate or mis-spell cities, etc...) and therefore when saving customer or order addresses via the BAPI calls we receive errors from SAP indicating that the tax jurisdiction code can not be determined. In these cases we want to NOT call Vertex for automatic tax jurisdiction code check and allow SAP to accept a state level jurisdiction code that we can pass (ex. Minnesota's is 2400000000). How can we turn off the call to Vertex for tax jurisdiction code check? Apparently we can use SAP user exit EXIT_SAPLFYTX_USER_001 include ZXFYTU03 but what is the ABAP code to turn this call off for specific sales org & division?
Regards,
Jeff

Hi,
You can create the custom tables with the same fields on Vertex and maintain those tables with the same values.
You can comment the section of RFC call and add your own validations.
Hope this helps.
Regards,
Kranthi

Tracing an external RFC call

Similar Messages

Maybe you are looking for