Testing RFC (Async RFC to file)

HI,
can we test whether message has reached XI by triggering FM in Sender SAP system just by creating RFC destination in sender SAP and a communication channel in XI with RFC Sender Adapter?
I think, we cant right.
we tested FM in sender SAP but we get short dump error (TCode: ST 22 call_function_remote_error)in sender SAP.
so we just need to do all the steps as usually we do ,right?
is there any way we can test our Async RFC whether data reaching XI system/
thank you.
Babu

Hi babu..
Have you checked the RFC destination? This could be as basic as incorrect password for WF-BATCH.
Use SWU3 to test the RFC destination, then run the verification workflow and choose the "[...] in background" option. If this works, your RFC destination is OK.
refer this...
http://help.sap.com/saphelp_nw04s/helpdata/en/f9/3f69fd11a80b4e93a5c9230bafc767/frameset.htm
regards,
vasanth

Similar Messages

Async RFC to file -data not passsed to PI

Hi all,
Im facing a peculiar problem in Async RFC to File scenario.
I have done all the required configurations for it.
Referred the following blogs :
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/scn/advancedsearch?query=rfctofile+scenario
As soon as I trigger the scenario in R/3 , I get a message in PI but the data is not passed.
The payload I get in PI is with empty tags...

Hi Ramya,
As you are getting the empty payload there is not probelm i nthe connection between R/3 and XI system.
1. Check the logic you used in RFC .. place a break point and check your execution is a getting data properly.
2. Some times due to the re design in the interface the cache needs to be updated properly.. Check this too.
Regards
Sunil.

Issue in Sync-Async bridge(RFC to File) scenario

Hi All,
My scenario id RFC to file synchronous scenario.Following the below link, I configured everything and its working fine. I am working on SAP PI 7.31 Dual Stack.
http://scn.sap.com/blogs/henrique/2007/08/02/syncasync-scenarios-without-bpm
As mentioned in the above link, I created the file with Message Id as file name and correlating with the message id(Using WaitResponse and Notify beans).Its working fine. But I don't want the file name to be as Message Id. Then in that case, please suggest me how can I correlate the request and response messages.What are the possible ways of doing it.
Thanks,
Madhurima

there is not a best way, just what you need to archive, take the file name as you mentioned is not the best practice, so you can use another parameter provided by SAP.
To evaluate the following attributes in the PI message header, set the corresponding indicators:
○ File Name (technical name: FileName)
○ Directory (technical name: Directory)
○ File Type (technical name: FileType)
○ File Encoding (technical name: FileEncoding)
do any of them are good for you?
Rdgs

Error Handling on RFC - XI - File Scenario

I have an R/3 RFC -> XI -> FILE scenario that works, but does not adequately handle the error of my R/3 to XI connection being down.
The RFC call is async since I was under the impression that I had to do a "to file" scenario that way.
    CALL FUNCTION 'ZXO_SAP2RFC'
      IN BACKGROUND TASK
      DESTINATION wa-rfc_dest_1
      EXPORTING
        request          = request
        rfc_header       = rfc_header.
    COMMIT WORK AND WAIT.
    IF sy-subrc <> 0.
      [error handling]
If my rfc destination is down (for example when XI is down), this RFC call is still getting a sy-subrc of '0' (so my error handling does not kick in).
Any suggestions?

Hi Keith,
your scenario is working correctly. If XI is down you will find your message queued in transaction SM58, where you can restart it manually. Usually there should be standard job for report RSARFCEX, which is periodicly trieing to restard the message.
Asynchr Call (tRFC) means that your program continues completly undependent from that call.
Make a test: Change temporary the called machine in SM59 destination to senseless value and execute your programm. Your message should be in SM58. Then correct the destination and wait a few minutes...
Regards,
Udo

RFC to File

Hi
Can anyone give me step by step procedure for creating an RFC to FILE scenario in XI

Hi,
this is just a simple rfc to file (asynchronous scenario).
import RFC from other server to xi server.
http://help.sap.com/saphelp_nw04s/helpdata/en/af/7ad9beab5e824cb2403f6821cde7dd/frameset.htm
create DT,MT,MI(inbound async) for receiver file
create MI(outbound async) for RFC(as its async,u need MI ,else for sycn RFC no need of MI)
create MM between RFC request and File
create IM
Create sender CC,receiver CC,sender agreement,receiver agreement,interface det and receiver det.
hope this may help you in configuring adapters.
http://help.sap.com/saphelp_nw70/helpdata/EN/ae/d03341771b4c0de10000000a1550b0/frameset.htm
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
http://help.sap.com/saphelp_nw70/helpdata/EN/ae/d03341771b4c0de10000000a1550b0/frameset.htm
How to test the RFC to Flat File scenario
How to test the RFC to Flat File scenario
reward points if it is helpful.
regards,
pradeep A.
Edited by: Pradeep Amisagadda on Apr 30, 2008 8:36 AM
Edited by: Pradeep Amisagadda on Apr 30, 2008 8:41 AM

Error 'Program not registered' while testing RFC - SRM to MDM / TCP/IP conn

Hello All,
While testing RFC connection in SRM, we are getting this error. This connection between SRM to MDM. Any inputs will be highly appreciated.
Error Details LOCATION: SAP-Gateway on host <hostname> / sapgw<instance no>
our server OS : windows 2008 server
We are getting error while doing connection test in SRM.
This is sm59 connection (TCP/IP ) connection.
Connection Type: T / RFC destination Name: MDM_API_CATALOG
Registered server program: hostname.MDS
I checked smgw transaction ..Logged on clients...Program id is not showing. Any hint will be helpful.
I Checked this MDM setup also.
MDS setup
In mdm server go to folder F:\usr\sap\DM1\MDS00\config
Open MDM.ini file in notepad
Add the below 2 entries.
SAP RFC Gateways= GWHOST=XXXX.hostnamexxx.xxx GWSERV=sapgw00
Trusted SAP Systems= XXD
This will enable gateway connection between SRM and MDM and will enable trusted connection.
For trusted connections to work, we created a service user called SRM_MDM_API with SAP_ALL in SRM and also created the same user in MDM with Default role.
Error message:
Logon Connection Error
Error Details    Error when opening an RFC connection
Error Details    ERROR: program XXXXXXXXPRD.MDS not registered
Error Details    LOCATION: SAP-Gateway on host XXXXXXXXprd.xx.xxxxxxhostname.xxx / sapgw00
Error Details    DETAIL: TP XXXXXXXXPRD.MDS not registered
Error Details    COMPONENT: SAP-Gateway
Error Details    COUNTER: 77326
Error Details    MODULE: gwr3cpic.c
Error Details    LINE: 1778
Error Details    RETURN CODE: 679
Error Details    SUBRC: 0
Error Details    RELEASE: 700
Error Details    TIME:
Error Details    VERSION: 2
Procedure Tried
1) This procedure is for Linux OS - Similarly we tried in Windows OS ( If any procedure is wrong also, Please correct us)
To register the program login into the OS level as sudo su u2013 <sid>adm and execute the following command.
rfcexec u2013g<program id> -a<gateway host name> -x<gateway service>
rfcexec is the server program name, the <program id> can be obtained from SM59, it is case sensitive and should match with the entry in SM59. The <gateway host name> and <gateway service> can be obtained from the transaction SMGW. When this command is executed it goes to a hanging loop.
The connection will fail once this command is terminated or the user executing this command logs off
2)
To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini
To do this, execute the following command
sudo su u2013 <sid>adm
rfcexec u2013D<destination name>
<destination name> is the RFC destination name in SM59
In order to do above step 2, we could not find saprfc.ini in windows 2008 server. Please let us know path where it will be usually?
3) Already checked the notes sapnote_0000684841
I know that it is generic error..This is happening to specific one of system only.
Thanks
Edited by: saptest2011 on May 20, 2011 5:36 PM

Hello SM,
Thanks for your quick reply.
Thanks for sharing link for document ie Configure the MDM Administration_cockpit. It is helpful. I read that document.
But still issue remain there.
The same RFC connection works between SRM sandbox to MDM sandbox.
Only issue with SRM Prod to MDM Prod (newly built system)
difference between MDM Prod and MDM sandbox.
MDM Prod runs: Windows server 2008 OS
MDM Sandbox runs: Windows server 2003 OS
Landscape: PI7.1, MDM 7.1 and SRM 5.5, SRM-MDM Catalog 3.0
Even i did os01 tcode ping test using host name (specific IP address) from SRM prod to MDM prod, it is fine.
Thanks a lot for your help.
I checked these notes also
Note 353597 - Registering a server program
Note 44844 - No connection to registered RFC program
Note: in smgw tcode in SRM system, the required program id is not showing in logged on clients
Thanks
Edited by: saptest2011 on May 23, 2011 5:00 PM
Edited by: saptest2011 on May 23, 2011 5:39 PM

CC error in RFC to File Scenario

Hi ,
While am trying to do end-to-end test for a RFC to file Scenario. Am getting this below error. Please help me to proceed further.
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '2008-08-13' too long (>8 for 2. column) - must stop', probably configuration error in file adapter (XML parser error)'
Regards,
Hemanthika

Hi,
Please go through this Blog
RFC Scenario using BPM --Starter Kit
check this blog on how to configure sender rfc adapter.
The specified item was not found.
I hope it helps,
Regards,
Surya

[RFC to File]Problem about Changing file name in message mapping.

Hi,
my problem:
    Type:RFC to File
    I change the file name in message mapping.
when I call the RFC to send the data twice at the same time, both of the output file names are changed while I only want to change the second output file name.
    thanks
Sam

In my MM, the input values to these variables (var1, var2 and var3) are (<ZZCOMBI>array,G499999,END_FIFC0029) ,
var1 is an array of input <ZZCOMBI> item list;
var2 is get from a property file by call another UDF;
var3 is constant value.
the test input data :
I send the data for the first time:
- <rfc:Z_IFCFR821_ZIFCTT82100010 xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <T_ZIFCTS82100010>
- <item>
<ZZCOMBI>G000002G000002</ZZCOMBI>
<ZZKYKBN>*</ZZKYKBN>
<ENAME_VE />
<ENAME_Z5 />
</item>
</T_ZIFCTS82100010>
</rfc:Z_IFCFR821_ZIFCTT82100010>
so the input values to these variables (var1, var2 and var3) are (G000002G000002,G499999,END_FIFC0029)
the output file name(File1) :END_FIFC002920090413-171534-053.dat
output record: G000002G000002
because the data what I send is the last record, the system send the dummy data for the second time by program.
- <rfc:Z_IFCFR821_ZIFCTT82100010 xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <T_ZIFCTS82100010>
- <item>
<ZZCOMBI>G499999</ZZCOMBI>
<ZZKYKBN />
<ENAME_VE />
<ENAME_Z5 />
</item>
</T_ZIFCTS82100010>
</rfc:Z_IFCFR821_ZIFCTT82100010>
so the input values to these variables (var1, var2 and var3) are (G499999,G499999,END_FIFC0029)
the output file name(File2) :END_FIFC002920090413-171533-928.dat
output record: G499999
I find that File2(20090413-171533-928) was ouput before File1(20090413-171534-053 ) from the time stamp.
I am not sure about that "XI will create a message ID for each message and the messages are independent." as you mentioned above.
Best regards
Sam
Edited by: YONGHE ZHOU on Apr 15, 2009 3:59 AM

RFC Adapter RFC to File

Hi,
Can somebody help me to view this thread. I am learning XI using RFC to File and I have got some difficulties in undestanding the Adapter Configuration.
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step from Michal.
When I select this thread, I get blank page.
Thanks

Hello MK and Shabarish,
I need a little more help from you.
Here is XI Scenario.
Want to send Material info using RFM from system A to System B via XI.
Process: In System A, I create an RFM and send the data via dest paramter.
It looks like this.
Call Function
     dest 'SYSTEMA_SENDER'
1. I created T - RFC Destination in systemA.
    RFC Name     SYSTEMA_SENDER
    gateway host gbdsc1 ( using smgw)
    serveric          sapgw11
    Program id     SystemA_Sender
                         Registered server program, unicode.
2. In XI box, in Integration configuration, Created RFC sender channel with the following paramter
    Adapter Type   RFC - Sender
    RFC Server Parameter -
             Applcation server(Gateway) gbdsc1    ( As in RFC dest System A )
             App service(gateway)           sapgw11
             Program ID                          SystemA_Sender
    RFC Metadata repository
            Application Servr         ( What do I enter here is it System A)
            System Number
            Logon on User
            Logon pw
            Client
             Language
Finally,
In system A when I do connection test I get the following errors
Error: Program SystemA_Sender not registered
Location SAP-Gateway on gbdsc1/sapgw11
Detail:TP SystemA_Sender not registered
and other errors
Can you identify any correction required for the above RFC destination and RFC configuration?
Do I need to register the program and if so how?
Your help is deeply appreciated.
Regards

Rfc to file scenario error in sm58

rfc to file scenario error in sm58
i get the error as com.sap.aii.afccommunication.RfcAfwException
:look up of alternative

hey
>>i have a doubt do we have to use
starting new task or back ground destination
well it depends upon the logic ur gonna implement,both are used for async RFC so u have to see ur requirement and then decide.
have a look at the following
http://help.sap.com/saphelp_nw2004s/helpdata/en/22/042578488911d189490000e829fbbd/frameset.htm
thanx
ahmad

SenderAgreement not found in RFC to File

Hi,
In RFC - File scenario, i am facing the following error:
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'DEC', toParty '', toService '', interface 'SLDJAVA_ACCESSOR_REQUEST', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_LOTUSNOTES_OUTBOUND_SND_RFC'
I deleted the sender CC and created it again, did a CPACahe Refresh but nothing happened.
could anybody help to solve this issue.
in the ECC side I have coded a RFC which is included in the BAPI, then i am calling this RFC in ABAP program. i created a LS in ECC which has the PI details. RFC is called like below:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
IN BACKGROUND TASK DESTINATION 'DPICLNT100'    -
> this is the PI server
is this correct, or am i missing some steps?
thanks

Hi Siva,
I have done the following for RFC to File scenario:
ECC side:
1. Created a RFC and tagged it to BAPI
2. In the ABAP program, i am calling the RFC like below:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
               EXPORTING
                 INTERFACE       =
IMPORTING
   FILENAME        = FILENAME
   RETURN          = RETURN
TABLES
   ITAB10          = ITAB10
   P_STATUS        = P_STATUS
COMMIT WORK.
3. Created a RFC destination using SM59
RFC detination     : Z_HR_OUTBOUND_DATA2
Connection type    : TCP/IP
Enabled Registered Server Program
Program ID : SAPSLDAPI_DPI -
> not sure whether this correct. but took this vvalue in
on the TCP/IP connection in PI (As mentioned if i am giving any other value say SAPECC etc, then it gives an error while Tst connection * TP sapecc not registered* )
Gateway host : ECC's host number
Gateway service : ECC's service number.
In PI side:
I have created :
1 DT for File Rcvr
1 MT for File Rcvr
1 SI for File Rcvr (async)
1 MM (sender RFC and receiver File)
1 OM
1 CC with RFc as sender with the following parameters:
   Communication component : ECC's component
   application server (gateway) : ecc's gateway
   application server service(Gateway) : ecc's service number
   Program id : SAPSLDAPI_DPI -
> not sure whether this correct.
in on the TCP/IP connection in PI
   inital connections 1
   max. connections 1
And also gave ecc's details in application server , s/y number, auth. mode, logon user ,
pwd, ecc's client number
1 CC with File adapter and file content conversion
1 receiver determination
1 interface determination
1 sender agreement
1 receiver agreement
When i am executing the ABAP program in R/3 I am getting the following error:
*Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException:
lookup of alternativeServiceIdentifier via CPA-cache failed for channel
'CC_LOTUSNOTES_OUTBOUND_SND_RFC' (f455111112de33bba4c3dc3dbf93ed1b, party '', schema
'TechnicalSystem', identifier 'DEC#120')*
Please let me know if any of my steps are wrong and how to rectify this error and make
the scenario working.
Thanks for your help

Rfc to File Adapter

Hi ,
I am using RFC to file adapter.i am facing this error in XML.
com.sap.aii.utilxi.misc.api.BaseRuntimeException
thrown during application mapping
com/sap/xi/tf/_MM_RFC2FILE_: RuntimeException in
Message-Mapping transformatio~
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_RFC2FILE_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
for receiver CC chanel i am using File adapter.Is there nees to use file content conversion for this.

Test the mapping with the payload from MONI, check if your mapping logic works in teh test tab of MM adn do the neccessary correction.
18:46:42 Start of test
Compilation of MM_RFC2FILE successful Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) 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:832) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3)(:main:, row=2, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) 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(Unknown Source) 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:832) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(Unknown Source) 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:832) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) 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(Unknown Source) 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:832) Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3)
18:46:43 End of test
are you sending a XML file or a flat file to the target.If flat file ,
what is the requirement/delimitor and the data format requested by the Receiver system.
i just passind data from R3 RFC to XI,so sujjest what is needded in receiver file adapter.

Problem Executing RFC to File Scenario

Hi,
I am currently working on RFC to File Scenario which is Asynchronous in Nature i.e. The RFC will send some data to XI and then it'll be dumped in an XML File on the shared drive.
Following are the steps which were performed by me :
1. i created an RFC Destination in R/3 using SM59 and entered the Required values as mentioned in the blog
The specified item was not found.
2. Then i entered the same values in the communication channel of the sender RFC adapter.
I tested it from R/3 and the connection was successful.
3. i created an RFC in SE37 in the R/3 and just added an existing table under the "tables" tab. No further code was written in it. I saved it and activated it.
4. All the IR and ID objects were made and activated and then the scenario was run by sending a single data row by pressing F8. The RFC showed a message of "System Failure" and while looking into the XI Server (SXMB_MONI) the message gave absurd values with a error symbol(it a Red Light symbol and there was no Red Flag).
Initially, the XML file was getting posted in the shared drive but after further execution it stopped.
I am unable to figure out the problem. Kindly let me know where i am going wrong and what needs to be done to correct it ?

Hi,
For Sending RFC asynchronously check for these points:
For RFC creation and importing please follow this discussion. Very useful:
Re: RFC to FILE
Specially reply by Udo Martens.
Also for sender RFC, check two things.
1) First step is Register your ProgramId using activiating the communication channel(XI). You should be able to see it in smgw(R/3)
smgw->Goto->Looged on Clients(Check it here)
2) Then use this registered programid in your RFC Destination,in R/3 (it is Case-Sensitive).
These are just common errors i have encountered sometimes.

HTTP-RFC(BPM)-FILE Scenario

I have a problem on using the 'http-RFC(BPM)-File scenario'. When i enter values using the Client http adapter, it displays message telling that "BPE_ADDAPTER.SYNCHONOUS_MESSAGE"
The error msg is displayed below:
Result:
<SAP:Error>
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code>BPE_ADAPTER.SYNCHONOUS_MESSAGE</SAP:Code>
<SAP:Stack>The process does not support the given synchronous interface or does not support synchronous messages</SAP:Stack>
</SAP:Error>
Also in SAP XI monitor, the sender services along with the corresponding sender interfaces.
Expecting this prob will be off soon.
thanks
vinod v

Hi Vinod,
your process is asynchronous (no sync async bridge). But you send "Quality of Service = Best Effort" (Url paramater qos=BE). You should send "Exactly Once" (EO).
Regards,
Udo

MDDataSetBW.GetCellData. See RFC trace file or SAP system log for more...

Ingo,
I am getting below error message in BO Test environment when I refresh WebI document.
MDDataSetBW.GetCellData. See RFC trace file or SAP system log for more details
It was working when we migrated the objects initially. Subsequently when we try to refresh WebI document we are getting the above error message. It still works in BO Dev environment and the no of records are the same in Dev and Test.
I am able run the underlying BEx query in SAP BW Test environment and it does return data.
I checked ST22 and SM21 log, but no details there.
Is it related to Authorization on the Universe or Bex Query?
We are in the middle of UAT and not able to move forward. I would greatly appreciate your input.
Thanks
Ram

Ingo,
I ran the zip file and added the required entries to registry.
And then I tried to reproduce the error, but the files are not generated instead I noticeed below error message on the server:
The description for Event ID ( 7939 ) in Source ( Crystal OLAP Client ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Registry Access Error: , [HKEY_LOCAL_MACHINE]Software\Business Objects\Suite 12.0\MDA\Log\Modules: The system cannot find the file specified..
Does tha t mean we do not have permissons to read the registry?
I would greatly appreciate your input.
Thanks in advance.
Ram

Testing RFC (Async RFC to file)

Similar Messages

Maybe you are looking for