If you want to develop a module for sender/FTP adapters and access the file name in the module, check out SAP 819761. 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. HI Yeeloonkhoo, First of all, I would like to thank you for writing the blog below, which is very helpful, I was tempted from your blog to follow my IDOC to REST Asy/Sync, as you mentioned in your blog for some reason in the REST receiver it hasn`t replaced setting name interface module, as stated in your blog to use the synchronous interface name (as used in the 1st scenario), but if I use the synchronous interface name in the agreeemnt transmitter, in the interface of its undetermined operation mapping, I thought I`d take some advice from you. ? At least the name of the interface and the sending service must be qualified in the shipping agreement. All other fields are optional under the general rules for defining shipping agreements. Error: the shipping agreement was not found, the search for fixing by CPA-CACHE for the type of adapter RFC failed. CS for the first scenario of FILE2RFC: CS for the second scenario of RFC2FILE: ID objects for the first scenario of FILE2RFC: ID objects for the second scenario of RFC2FILE: CC_DUMMY_BRIDGE_FILE_SND is just an empty file adapter, unutilized. Try if I turn off this adapter, it always works well. Logically, the interface should be SI_FULLNAME_OUT_ASYNC, but the module processing will try to find “SI_FNAME_LNAME_IN_SYNC” suitable for the transmitter agreement stage. To solve the problem, I went to SI_FNAME_LNAME_IN_SYNC.
Need the virtual receiver to maintain with the original transmitter of the first scenario, which is “BC_Sender, the shipping agreement tries to find appropriate “BC_Sender” and fails if not “BC_Sender.” Enter the actual recipient “BC_Receiver”: Assign the RFC message MT_FULLNAME: Write in the output file at the CC_FILE_RCV: 1. Have you created an issue agreement for your scenario? The chain agreement has not been found? But the Channel Response channel says that “No proper channel agreement found” error. So why does one of B-IP`s calls suddenly use the WS channel when there is no shipping agreement? What other configuration could this cause? 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. scn.sap.com/community/pi-and-soa-middleware/blog/2014/03/27/bridges-construction-site-part-13-asynchronous-synchronous-bridge For Interface determination: In this 2nd Flow for OM_RFC2FILE, i`m using the Sync interface from 1st flow to determine the OM, you should inable to achieve similar results using in this way.