Soap Sender and RFC Adapter receiver getting APPLICATION_ERROR

Hi, all,
I have a webservice soap sender and RFC Adapter receiver scenario, it works fine with RFC "RFC_SYSTEM_INFO", When i tried the RFC "RFC_READ_TABLE", getting the following error message, <SAP:Code area="RFC_ADAPTER">APPLICATION_ERROR</SAP:Code> in
SXI_MONITOR, in webservice client, i am getting error message like this:
<faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <rfc:ZZTEST_RFC_READ_TABLE.Exception xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
               <Name>TABLE_NOT_AVAILABLE</Name>
               <Text>QUERY_TABLE not active in Dictionary</Text>
            </rfc:ZZTEST_RFC_READ_TABLE.Exception>
Thanks a lot!

Hi
Its not compulsory but its good to wrap it as Z object.
Well if you are facing problem with SOAP data. Then try to do one thing. Check with the data you received from SOAP message. If this works
Then try to check in mapping is it passing the data correctly or not. With this check with the user authorization PIAPPLUSER. if its having less authorizations to execute this BAPI in ECC
Thanks
Gaurav

Similar Messages

XI3 SOAP sender and Receiver

Hi
I am stuck with a connecting to scenarios using SOAP channel. In short there is one business scenario that based on some conditions must start other scenarios (each one built around one business process). I am trying to send asynchronous SOAP message within the same XI and treat it as a External XI system to start another Business Scenario (using XI adapter does not work as the system discovers the message as being in a loop).
Everything would be fine if there would be 1 target scenarios but I have 1:n. For asyncronous transport I have defined different Message Interfaces to be used for on each case. So XI should determine the right business process based on the message interface that uses the communication channel.
So I have configured a SOAP sender and a receiver channel. As I understood from SOAP adapter FAQ I checked "Use Encoded Headers" and "Use Query String" for both - sender and receiver channel. And ofcourse receiver channel is pointed to http://:/XISOAPAdapter/MessageServlet?channel=:{system name}:{receiver channel name} but when I start the initiating scenario the asyncronous message is sent of but nobody is catching it.
In RWB Message monitoring / adapter engine I found the the message receives an exeception:
SOAP: response message contains an error XIServer/UNKNOWN/ModuleUnknownException -
com.sap.aii.af.mp.module.ModuleException: either no channelID
specified or no channel found for the specified party, service, and channel name,
MessageServlet(Version $Id: //tc/aii/30_REL/src/_adapters
/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#15 $) at
com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl....
runServlet(HttpHandlerImpl.java:401) at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl....
handleRequest(HttpHandlerImpl.java:266) at
com.sap.engine.services.httpserver.server.RequestAnalizer....
startServlet(RequestAnalizer.java:387) at
com.sap.engine.services.httpserver.server.RequestAnalizer....
startServlet(RequestAnalizer.java:365) at
com.sap.engine.services.httpserver.server.RequestAnalizer....
invokeWebContainer(RequestAnalizer.java:944) at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at
com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160) at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener....
process(ApplicationSessionMessageListener.java:33) at
com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) 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:170)
Any ideas... how to make XI to send SOAP messages so that the same XI system would be able to pick them up?
Or what have I done wrong?
Best wishes,
Heiko

hi,
What is the format that u are using for the sender URL....The error message you are getting either because the names that you have mentioned in the sender URL are wrong or the URl format itslef is wrong.....if the format is the one that you have mentioned in the first post then it is not the desired format.
Use the following format to create the URL to send the request:
http://<servernameORserverIPaddress>:<portNumber>/XISOAPAdapter/MessageServlet?channel=:<senderservice>:<snederCCname>&version=3.0&Sender.Service=<senderservice>&Interface=<IRnamespace>%5E<senderMI>
Replace
with
& amp;
(no space inbetween the two words) in the above URL.
How to configure SOAP communication channels (sender and receiver) so that two XI instances could communicate and (more important) use different message interfaces on the same channel?
While creating a Receiver communication channel there is no need to specify the interface name and hence it can be used in different scenarios....however a sender communication needs the sender interface to be specified (as in SAP XI.....not in SAP PI).....so a sender channel can be used in different scenarios but with only the same interface.....
Regards,
Abhishek
Edited by: abhishek salvi on Feb 17, 2009 2:50 PM

RFC Sender problem between 46D and RFC adapter

Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
    CALL FUNCTION 'ZSD_DCF_SEND_TAG'
      IN BACKGROUND TASK
      DESTINATION 'XISYSTEM_TRFC_DCF'
      EXPORTING
        pt_filing_info = gt_filing.
    COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
Torstein

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
<i>Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".</i>
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

Problem between SOAP Sender and JDBC Receiver

Hi,
I have a asynchronous scenary between SOAP Sender and JDBC Receiver.
The idea is sending an ID for updating one register.
Table structure is:
TABLE AS_PERSONA
    (P_RUT                         VARCHAR2(10) NOT NULL,
    P_NOMBRE                       VARCHAR2(50),
    P_APELLIDO                     VARCHAR2(50))
The ID is the P_RUT field.
The structure of message that I send by SOAP, is the following:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Body>
          <m:MT_CONS_SOAP xmlns:m="urn:prueba:voliva">
               <CONSULTA>
                    <P_RUT>15445</P_RUT>
               </CONSULTA>
          </m:MT_CONS_SOAP>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The JDBC receiver structure is:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_CONS_PERSONA xmlns:ns0="urn:prueba:voliva">
     <Statement>
          <AS_PERSONA action="UPDATE">
               <table>AS_PERSONA</table>
               <access>
                    <P_NOMBRE>DELETE_BY_XI</P_NOMBRE>
                    <P_APELLIDO>DELETE_BY_XI</P_APELLIDO>
               </access>
               <key>
                    <P_RUT>15445</P_RUT>
               </key>
          </AS_PERSONA>
     </Statement>
</ns0:MT_CONS_PERSONA>
When I do a call to SOAP by XMLspy, it returns a message without data, that means succesfull reply.
I see message monitor and see the succesfull flag. But in the database it doesn't update the register.
This scenario was proved using the File Sender and same JDBC Receiver, then result was succesfull.
I proved SOAP Sender with a File Receiver, storing information from SOAP sender in an archive, and works well.
Then I imagine that exist some problem between SOAP and JDBC. what could be happening ?
Thanks.

Hi,
Looks like the problem is with the JDBC receiver...try updating the value in the table by using a File-JDBC scenario..does it work..check the adapter monitor in RWB..
Regards,
Sushumna

RFC Sender and RFC Receiver Sync Scenario . Help required.

Hi,
I need to make RFC Sender and RFC Receiver Sync Scenario.
Any docs/links for it.
Regards

Hi,
I have CRM (r/3) and DM (r/3)system.
Data from differnent tables of CRM system needs to go to
DM system different tables , data will be saved there and then return response back to CRM system.
For this I have given one RFC for CRM system
For this I have given one RFC for DM system
So I have to make Sync Outbound Interface
and Sync Inbound Interface.
So I think so no BPM is required.I am correct?
Adapter -- RFC Sender and RFC Receiver Adapter.
Regards
Edited by: Henry H on Jan 29, 2008 11:20 AM

HTTP and RFC Adapter are not Required Sender

Hi All,
I have one dought....
Why Plain HTTP and RFC Adapter are not Required Sender Communication Channel and Sender Agreements...
I Know this two Adapter are in ABAP Stack....
Please clarify my dought...
Regards

Idoc Adapters do NOT require Sender Communication Channel.
The Sender System identifies itself at the Integration Server, with the fields SNDPOR and Client of the Control Record.
Sender Communication channels are used for communication betweeen the Application System and the Integration Server.
In the case of Idocs, all idocs are tranferred to the Integration Server pipeline and NOT to the regular EDI/IDOC interface.
The RECEVIER DETERMINATION is based on the values in the Control Record.
If you are doing ALE, then you have to maintain the idoc types which are NOT to be transferred to the Integration server by executing report IDX_SELECT_IDOCTYP_WITHOUT_IS.
By maintaining the Idoc Types using this report, only these idoc types are sent to the regular EDI/IDOC interface.

Help Need on SOAP (Sender) to RFC Scenario(Synchronous Communication)

Hi All
I have a requirement of <b>SOAP(Sender) to RFC</b> scenario(Syncronous Communication). The scenaio goes like this........
I have a web service through which I have to create a SAP Notification in SAP system and the Notification ID created and other details have to be returned back to the webservice from the BAPI. I have identified the relevant BAPI for the scenario.
I have a wsdl file which I have uploaded it. What are the next steps to be done?
Please let me know what all(e.g., Data types, Message Types, Message Interface) I have to create in Integration Repository and what all configurations I have to make in Integraion Directory.
FYI, I have a gone through a list of Blogs, but didn't get enough info.
Please help me out in providing your valuable answers.
Thanks,
Vijay
P.S. Rewards points are sure .....

Hi Vijay,
   If at all you have uploded wsdl file for the webservice you no need to create data types for the same even for the same as RFC also.
     Create message mapping and drag the wsdl file which you have imported as External Definiations and there you will be having request and response parameters..Do the mapping accordingly(according to your requirement).
Mapping like:
    Wsdl(Request)---->RFC (Input parametrs)
    RFC (out parameters)------>wsdl(Response)
Create message interface with Synchronous for outbound
    No need of DT,MT if at all if you import the wsdl file.
   Hope i am clear.
Please let me know if you have any queries..!
Thanks and Regards,
Chandu.
null
null

How to use IDOC and RFC adapter in 1 scenario?

We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and what are the design and configuration objects we require to create?

To achieve this you have to use
Two Interface Determinations
Two Communication Channels (IDOC & RFC)
& Two Receiver Aggrements.
Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

RFC Adapter Receiver - change SAP User for each call

Hi guys,
I need to create one connection between PI and SAP, all right, i can use RFC Adapter Receiver, no problem.
But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
Can anybody help me, please?

hi,
>>But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
sure we can help you but no in this way:)
it is possible to change the user for RFC adapter but using
principal propagation:
/people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
this is the way you need to go and not send password in XML payload
(this is certainly not the way and no client will approve it)
why use a password is anyone can see it ?
Regards,
Michal Krawczyk

RFC adapter receive queue performance

We currently using XI 3.0 on NetWeaver 6.40 with a lot of asynchronous interfaces from JDBC <-> RFC.
After some load we experience that message received in RFC adapter queue are processed after a long time. The messages has status "To Be Delivered" and XI is processing other messages the same time.
2010-01-07 15:25:28     Success     Message successfully received by messaging system. Profile: XI URL: http://mlrxiprod:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2010-01-07 15:25:28     Success     Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2010-01-07 15:25:28     Success     Message successfully put into the queue.
after 1 1/2 hour ...
2010-01-07 17:01:10     Success     The message was successfully retrieved from the receive queue.
2010-01-07 17:01:10     Success     The message status set to DLNG.
2010-01-07 17:01:10     Success     Delivering to channel: NAV_FICANCEL_RFC_RECEIVER
2010-01-07 17:01:10     Success     RFC adapter received an asynchronous message. Attempting to send tRFC for ZXI_FI_CANCEL_WRAP with TID XIps}UGFk94TwD}G0O}ZGR2m
2010-01-07 17:02:32     Success     The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
2010-01-07 17:02:32     Success     The message status set to DLVD.
Can you explain why it takes so long the message to picked up and processed from the queue. All messages will be processed but the performance is unacceptable. No errors are found in SMQ2.

Hi,
It looks like msgs take very long time to be picked up from the queue(s) ! Is there enough threads allocated (according to SAP recommendations, which I can't remember) ?
How many system & application threads have been allocated ?
Rgds
Chris

Jco.webas.ignore_jdsr_error=1 in the sender side RFC adapter of RFC to SOAP scenario

Hello Team,
I am doing RFC to SOAP scenario after configuring the scenario i have checked the sender side communication channel it is not throughing any errors and it shows the status as green but it is displaying a short message
it is the short log displayed while checking the sender side RFC communication channel it shows that "jco.webas.ignore_jdsr_error=1" can please any one suggest me how we can solve the issue.
Regards,
Avinash.

Hi Avinash - I don't think that is an error instead it just displays your system configuration.
your RFC adapter should work i believe..
Are you facing any issues?
(I think the parameter is nothing but the value @ nwa/java system properties/XPI Adapter:RFC -> ignoreJrfcJdsrError(true/false))

Only HTTPS requests are working for SOAP Sender and HTTP not working

wHi Experts,
We have enabled our HTTPS port ( SSL ) in NWA -- >> Security -- >> SSL and Key stores. So understanding is HTTPS port is now enabled on top of HTTP. So PI should be able to cater requests at both ports.
Now, we have developed a synchronous SOAP to RFC scenario and downloaded WSDL file. This file has both links -
a. http:<host>:<port>
b. https:<host>:<port>
We intend to make a PI system where both ports can work. Now questions.
1. When we test web service exposed from PI using SOAPUI tool, only HTTPS works fine and gets the response back. If we try HTTP URL, an error is encountered - HTTTPS scheme is required.
2. Is this whole understanding that both ports ( HTTP, HTTPS ) should be able to operate simultaneously correct ? Or this is not at all possible ?
3. In SOAP Sender, we tried selecting all 3 options - 1. HTTP 2. HTTPS without client authentication 3. HTTPS with client authentication.
None of the options have any effect on testing, Each time, only HTTPS request works and HTTP doesn't.
Can anyone please provide some hints for troubleshooting ?
Thanks..
regards,
Rajagopal.

The error "HTTPS scheme is required" is normally returned when the HTTP Security Level on the SOAP adapter is not set to "HTTP". I can see you have mentioned you have tried all these, maybe a cache refresh has gone wrong? Could try recreating the channel with just HTTP specified as security level and this should allow HTTP or HTTPS
I assume you are using a different port number for your HTTP and HTTPS requests from SOAP UI. Normally the HTTPS port is the same as the HTTP port number but the final zero changed to a 1 i.e. https://<host>:50001 instead of http://<host>:50000.
You should be able to confirm both HTTP and HTTPS work OK by loading some of the system webpages in a browser over HTTP and over HTTPS i.e. http://<host>:<port>/nwa and https://<host>:<port>/nwa
Chris

XI and RFC adapter

Hi
The RFC Adapter configuration has been done successfully and the adapter starts up successfully.
In our scenario, we attempt to receive an xml message from my local machine through a file adapter, and pass this along to the RFC Outbound adapter to execute a RFC on the CRM box.
The following error message is encountered in the XI monitoring tool.
==============================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="connection closed (no data)" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (connection closed (no data))</SAP:Text>
</SAP:ErrorHeader>
===================================================================================================
I then stop the RFC adapter and attempt the scenario again. I get the following error message in XI monitoring tool.
================================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n)</SAP:Text>
</SAP:ErrorHeader>
==================================================================================================================

Hi Eduardo ,
Please check wether the following steps are done in BPM:
1.Async Recieve
A.Properties :
Please set the following
Message:Message 1
Mode:asynchronous
B.Container Data :
Declare Message 1 as asynchronous abstract interface with message type of outbound interface(File Structure).
2.Sync Send
Pre-Requisite:
Copy the inbound Syncronous Interface to Sync_interface_abstract by changing the direction in the message interface of Interface object in the Integration Repository.
A.Properties
Mode:Synchronous
Request:Message 1
Response:Message 2
Syncronous Interface:Sync_interface_abstract
Recievers From :Send Context
B.Container Data:
Message 2 should be declared as the asynchronous message interface with Response message type in inbound interface(Rec Syst Interface).
3.Async send
A.Properties:
Mode:Asynchronous
Message:Message 2
Acknowledgment:None
Recievers From :Send Context
Integration directory has to be configured to send data forth and back to BPM.
1.Send MESSAGE From Outbound interface to BPM.
OutBound and Abstract Interface needs to be mapped in the interface determination and Abstract interface has to be binded to Business Process Name in the repository.
Outbound->Your OutBound Interface(File Interface)
Abstract->Message 1
Reciever Service-> Your Business Process Name
2.Send MESSAGE From BPM to Inbound interface.
Abstract and Inbound interface needs to be mapped in the interface determination and Abstract Interface has to be binded to the Receiver Service/Business System.
Abstract->Message 1
Inbound->Your Inbound Interface(RFC)
Reciever Service-> RFC SYSTEM(SAP)
These are the general steps to follow for Async/sync pattern.
Please let me know if all the steps are configured.

SOAP Sender to RFC Scenario WSDL File

Hi,
I am working on SOAP -> PI -> RFC Scenario. I generated WSDL from sender agreement and gave to the client that can consumed by the third party system. But client is not ready to consume the WSDL. He provided WSDL and asking me to use that. Could you please suggest whether WSDL given by the client can be used in SOAP -> PI -> RFC Scenario. If it is possible, could you please provide steps how it can be done?
Thank you.
Regards,
Cdr.

Thank you Hareesh & Divya,
When we generate WSDL from PI, it gives soap action and soap address location based on the interface we use for SOAP -> PI -> RFC.
When we import WSDL given by the client as external definition, we get messages(Structures). But where do we pass the soap action or address location. I do not see any option in the soap sender communication channel. I am not visualize the link.
Can somebody share their knowledge if they have done in this way.
Thank you.
Regards,
Cdr.

JDBC to File and RFC adapter

Hi All,
In my scenario, i am sending file from a database system to SAP system. Here I am using JDBC/ webserveices adapter at outbound side to query the database and FILE and RFC at inbound side to send file and workflow notification.
my requirement is to send file as batch to SAP system(after business hours), send workflow notiication to the responsible person, and when the file is stored on application server then only i should send the notification to the person.
I know this can be acheived by BPM by using wait step but I am not sure how to do it only for RFC adapter to kick the notification once the file has stored and confirmed.
Can anyone help me in this issue.
Reg
Sre.

>
sre wrote:
> Hi All,
>
> In my scenario, i am sending file from a database system to SAP system. Here I am using JDBC/ webserveices adapter at outbound side to query the database and FILE and RFC at inbound side to send file and workflow notification.
> my requirement is to send file as batch to SAP system(after business hours), send workflow notiication to the responsible person, and when the file is stored on application server then only i should send the notification to the person.
>
> I know this can be acheived by BPM by using wait step but I am not sure how to do it only for RFC adapter to kick the notification once the file has stored and confirmed.
>
> Can anyone help me in this issue.
>
> Reg
> Sre.
There are two options,
1. With BPM you can have the send step for file request an acknowledgment and then have the send step for the RFC call after the previous file send step.
2. Without BPM, use the same Business system (single receiver det.) and have multiple interface determination (file&RFC). Use the option maintain order at runtime and have the file interface above the RFC. This will act like an EOIO.

Soap Sender and RFC Adapter receiver getting APPLICATION_ERROR

Similar Messages

Maybe you are looking for