If you want to develop a module for sender/FTP adapters and access the file name in the module, check out SAP 819761. I set up an RFC adapter for the IFL transmitter with a specific program ID. This RFC adapter is available in the integration directory under a WebAS ABAP business system. I checked the configuration in IP and sxi_cache in B. I assumed that either would display a sending agreement with the WS channel (for the wrong confirmation message from B to PI) and that something in it would be misconfigured. But there isn`t one! No shipping agreement in IP and none in sxi_cache, and the xi-hide is up to date. The number of seconds the adapter has to wait if no file is found for processing. 1. Have you established a sending agreement for your scenario? The chain agreement has not been found? One thing in all of the implementation that I`ve noticed is that I had to keep a separate RFC channel for each transmitter interface, simply because the way RFC works for the sender needs an independent channel, as RFC can`t share a common channel between ECC and IP. I have the solution and I wanted to share with everyone what I did. The RFC setup steps can easily be found on Michal Krawczyk`s blog com.sap.aii.aii.afcommunication.Rfc.RfcAFWException: senderAgreement not found: CPA cache fixing search failed for adapterType RFC, dapterNS sap.com/xi/XI/System, DIRECTION INBOUND, party “, fomService `HORIZONISU`, to Party toServ HI Yeeloonkhoo, first of all I would like to thank you for writing the blog below, which is very helpful, I was tempted to follow your blog to make my IDOC at REST Asy/Sync as you mentioned in your blog for some reason in the REST receiver, it did not replace the name of the interface interface, as stated in your blog mentions you to use synchronous interface names (as in 11. Scenario used), but if I synchronized interfacename in the agreeemnt transmitter, in determining the interface its non-identifying operation mapping, I thought I`d take some advice from you. The scenario is – IP must select data from the view of an hana database.
I use jdbc channels for that. (32) If found, select all lines. UserIDs add to the role The solution is IP creates channels and the sending agreement always with party “. In particular, if you use the assistant to run the setup. So if you implement an RFC transmitter adapter. So copy the communication channel and the empty (star-free) transmission agreement. MSGGUID 00155D011001E58AF4F4C7AC2011C4: Day MESSAGEHEADER found IDOC BEGIN- Hello Rajiv, “but if I sync interfacename in the agreeemnt transmitter, in the destination of the sound interface do not identify the mapping operation” For the sender agreement: So you have the same behavior with mine. Recently I tried D`Async/Sync bridge with Sync REST adapter not working.
This blog by Alexey Pitroff also mentioned Async /Sync Bridge with Sync RFC will not work in which instead need to use the module on the transmitter adapter. See the comment in figure 26 of his blog.