File to file scenario receiver determination

Hi experts,
While I am working on file to file scenario from the source it is deleting the file but
it is not able to create the file again because in the receiver aggrement I given
parameters to create and even I am not able to see any message in the sxmb_moni transaction it is simply saying no message i am in confusion that whether my process is wrong or it is installation problem.
Thanks in advance,
Srinivas.

Hi Srinivas,
Check the status of file adapter in RWB.
Follow this link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/08438c77-0501-0010-50a0-e39fe8fa0446
and check this weblog as well.
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
Sachin

Similar Messages

File to RFC scenario - receiver determination problems

Hi ,
Im trying to work out a flat file to RFC scenario, and am facing problems in configuring the receiver determination .
While creating my receiver determination, in the configured receivers, when i click on the F4 help to select service, i do not see the business system that i configured in SLD .
This system i have configured as an WAS ABAP system and provided all relevant data. I can also import objects from this system into IR, so i dont think i have set it up wrongly. I have also created RFC destination .
Is there some setting that has to be made that im missing ? Could somebody point out why im not able to see this system in the list of business services available at receiver configuration time ?
Thanks,
Joe
I also cleared the SLD cache by the way.. that didnt work either .
Message was edited by:
Joe Stein

Thanks a lot for you replies guys , but problems still not solved ;
1. I looked at the blog given and ive done everything pretty much as given . My problem lies in not finding the business system itself in the list of services for the configured receiver. How to implement this has not been shown in the blog.
2. I tried refreshing the cache and checking again, but it still doesnt show me the necessary step.
SOS !
I checked in the inbound system , and found that an RFC wasnt created for the XI system . I created that but i still cant see this system as a business system when i try to create the receiver determination . Do i need to recreate the technical system in the landscape to incorporate this change ?
Any pointers at all ??
Message was edited by:
Joe Stein

File To File Scenario - Receiver Channel Adapter Module

Hello,
We have PI 7.4 in our landscape.
There is one File To File scenario which needs to be implemented.
In this scenario, at source diretory we have multiple files (country wise) which needs to be read and put into mutiple folders (country wise) at the target directory.
Please note we are not making any objects in ESR and directly configurations need to be done in Integration Directory.
At sender side we can read mutiple files using a single Sender File adapter using the the "Advanced Selection for Source File" option.
At receiver side we are planning to implement a custom Adapter Module which will put the files in their corresponding country wise folders.
We are using NWDS 7.3 EHP 1 SP12 for building the adapter module.
Suggestions are required for below mentioned points:
1. Is the approach follwed is most suitable as we do not want to make mutiple reciever channels for each folder.
2. How to read the file name in the receiver adapter module as Namespace will not be created (we will put a dummy namespace in ID).
3. If any body has already implemented such logic or any suggestions for the same.
All the suggestions are welcome and thanks in advance.
Regards,
Ujjwal Kumar

Hi Ujjwal
Yes, that is the correct namespace as long as you are using the File adapter.
Your code is nearly there, just need the new keyword when creating a new object instance. Below is the sample
// Get Dynamic Configuration
MessagePropertyKey fileNameKey = new MessagePropertyKey("FileName", "http://sap.com/xi/XI/System/File");
String fileName = msg.getMessageProperty(fileNameKey);
// Set Dynamic Configuration
String targetDir = "/blah/blah/blah";
MessagePropertyKey dirKey = new MessagePropertyKey("Directory", "http://sap.com/xi/XI/System/File");
msg.setMessageProperty(dirKey, targetDir );
You can refer to the following SAP JavaDocs for more infomration on the Message class (which you use to get/set the property)
Message
Rgds
Eng Swee

Using conditions on CSV files in Receiver Determination

Hi,
We're reading EDI files from a directory and turning them into IDocs. We've got an ABAP class that converts the EDI to XML for us, we're calling that as the first step in the Operation Mapping.
However, several different EDI files are dropped in the same directory, regardless the type and version. Luckily this can be found in the UNB segment in the EDI message. Now we want to make the split in the Interface Determination, but to do he'll need to read the EDI file's first line, determine what exactly it is, and then send it to the correct operation mapping.
Is there a way to read a non-XML file using XPath in the Condition part of the Interface Determination?
What I basically want to do is something like this:
File content :
UNB+93A:ORDERS:etc.
UNH+347843243:etc.
What I want to have my condition on is on the 93a and on ORDERS. So I'll need a double condition with AND (I know how to do that part) but on substrings of the data, which I don't know what to do. I only know that the UNB line will always be the first line.
So IF pos 5-7 EQ '93a' AND pos 9-14 EQ 'ORDERS' THEN Operation Mapping, etc.
Any ideas if this is possible, and how?
Kind regards,
Frederik-Jan.

hi,
>>>Is there a way to read a non-XML file using XPath in the Condition part of the Interface Determination?
yes this is possible
but it would be much easier if you'd just create an adapter module (especially if you have more complex conditions)
that would check the content of the file (parsing it in java) and fill out any of the adapter specific attributes
on the basis of which you could easily do the receiver determination
I used this approach for VDA (also non XML files) and it worked very nicely
Regards,
Michal Krawczyk

Idoc to File scenario: receiver content conversion

Hi,
I have a Idoc to file scenario in which each segment is to be sent in a new line.
Also, even if the segment is not present in Idoc, comma separated blank values are to be sent.
Till now I have been fllowing this blog
File Content Conversion for Multi Hierarchical Structure
But in this case, blank values csv line are not created.
When I used mapWithDefault for parent WPA12 then only 1 instance is created.
For eg.
WPA01
-WPA02
--WPA12
WPA01
-WPA02
--WPA12
There are no values in WPA12 segment
Output
WPA01,a,a,a,a
WPA02,b,b,b,b
WPA12,,,,,
WPA01,c,c,c,c
WPA02,d,d,d,d
Can I make any change in the approach as in the blog to get the desired output?
Regards,
Anirudh.

Hi,
To explain more a bit..
My requirement is to create a flat file from multiple hierarchical xml structure.
Additionally, if the values are not present for some nodes then also I have to send the blank values in flat files. If entire segment is not present then also blank csvs needed to be sent.
regards, Anirudh.

Extended Receiver Determination

Hi
I have scenario like this.
Sending order file into SAP through XI
If the order is there in SAP it needs to be send mail along with details of
order else if this is new order then it needs to posted into SAP and create IDOC .I need to use RFC function module which is developed in SAP that returns 0 or 4
If SUBRC=0 then need to send mail as I mentioned above
If SUBRC=4 then need to create Idoc in SAP system.
Note : without BPM - Need a solution
Let me know how to use extened Receiver determination.
Till now I have designed like this:
In the IR :
I have created 3 message mappings for this.
1st one is to decide receiver.
           Source - file
           Target - Receiver determination (structure - which available in SAP
Basis software componenet)
2nd one is to create IDOc
            Source - file
             Target - Idoc
3rd one is to create mail
            Source - file
            Target - Mail ( External defination)
In ID:
I am using extended receiver determination , their i have given the mapping program which ti determine the receiver.
Next i have created 2 Interface Determinations,Sender as well as Receiver agreements.
Finally Activated all .
While testing i am getting message in the MONI No Receiver agreement found
Could pls help this case.
Cheers
MMV

Hi Mrutynjaya,
Rest all seems to be fine, but are you using 2 sender agreements??? You need only 1 sender agreement,as you have only 1 sender. Correct me if i am wrong.
Regards,
Sanjeev.

Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all

Hello,
I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
Iam reading a flat file and trying to write into an XML in the same FTP server
I have a 1 to 1 Mapping as follows
And my Content Conversion at Sender side Looks like this
After running the configuration Iam getting following error message
Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
My System is the SAP Netweaver Process Intgration 7.4 single Java stack
Do you have any idea how to fix this issue?
Many thanks in advance
Khadim

Hi evrybody
I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
<ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
<Recordset>
<header>
     <gesellschaft>03</gesellschaft>
     <filiale>000</filiale>
     <satzart>11</satzart>
     <datum>00000000</datum>
     <kennzeichen>1</kennzeichen>
</header>
</Recordset>
</ns:hartgeldbest_ERP_KT>
The issue is on detrmining the RECEIVER in the Main-XML
<sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
<sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
<sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/>
<sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
</sap:Sender>
<sap:Receiver>
<sap:Party agency="" scheme=""/>
<sap:Service/>
</sap:Receiver>
<sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
</sap:Main>
Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
Any idea?
Thx
Khadim

Regarding receiver determination problem in IDOC-XI-XML file scenario

Dear All ,
In IDOC-XI-xml file scenario , I have configured SLD , IR . But in ID , after file adapter , reciever agreement configuration when I am doing receiver determination configuration I am not able to insert mapping program in configuration overview of receiver determination as I am not getting "New Specific" option in mapping .
Can anybody suggest what could be the reason behind this .
Thanks in Advance
Prabhat

Hi PRabhat,
In RCVR determination, you need to select the party & service (as appropriate) save the obeject
then refresh the configuration overview of recr det.
then you can see the partner/service
then you can open it & add the necessary objects.
Regards
Vishnu

How many Receiver determination in File to SOAP scenario

Hi,
I am trying a File -SOAP-File scenario, where file will be send to PI asynchronous. BPM is configured to receive the file and
call the web services and get the response (Synchronous call) .After that BPM send the file asynchronous to File via FTP .
It is basically asynchronous/ Synchronous bridge scenario.
To do this I have have configured the BPM & created 3 Communication channel . 1 sender (File) & 2 receivers ( SOAP & File)
But i got confused in Receiver determination. How many Receiver determinations do we require in this step? 2 or 3. If 3 how they will look like. I believe Interface determination is same as Receiver determination. I am suing Business System to send & recv the file.
Points will be rewarded for suitable answer.
Thanks

hi,
You require 3 receiver determinations.
one from File to BPM(XI)..
another from BPM to SOAP and other from SOAP to FILE.
This is exactly the same scenario.
RFC Scenario using BPM --Starter Kit
Thanks,
Vijaya

Receiver Determination Problem In Mail to File Scenario.

Hi All,
I am trying to do Mail to File Scenario. I defined two business systems, one s/w component in SLD and in IR I defined a DataType , MessageType and Two MessageInterfaces. In ID these are mail adapter settings I gave :-
Message Protocol :- POP3
Message Protocol :- XIPAYLOAD
MAIL ATTRIBUTES -- Enabled checkbox for "Use Mail Package"
                                Content Encoding - "base64"
                                Enabled checkbox for "Keep Attachments"
DEFAULT XI PARAMTERS --
                                Default Interface Namespace -- http://mtf
                                Default Interface Name         -- mtf_mi1
And in Modules Tab I also defined the "PayloadSwapBean" module and swap.keyName and swap.keyValue.
Infact I followed all the steps specified in /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
But in SXMB_MONI this is the error I am getting :-
<b><?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error></b>
Please help me out.
Thanks All,
Madhu.

Hi,
Please verify letter by letter if you haven't make a typo here:
Default Interface Namespace -- http://mtf
Default Interface Name -- mtf_mi1
please also make a test of your scenario in integration directory
please also do not use best efort quality of service
/wg
Message was edited by:
        Wojciech Gasiorowski

No receiver could be determined in Proxy----File Scenario

Hi All,
Iam doing Proxy---File scenario
Every thing i got success in SAP R/3 side MONI
I got this Error in XI side MONI as No receiver could be determined
I check the Sender Service in MONI--- SOAP Header ---Main( Both R/3 side & XI side also)
Here it is showing like sapdev as my sender service, but actually my sender Business system is Sub_Dev_ssd.
How to get it rectify
Regards
Vamsi

Hi Chirag & Santosh,
As i said the problem is when i check in XI side MONI
The sender service is showing sapdev BUT it shld be Sub_Dev_SSD which i have selected in the Receiver Determination Step also.
The same is showing in the SAP R/3 side MONI also
According to my understanding , The Correct Business system which is there in the SLD & which i want to use is not Picking in the SAP R/3 side and so thats why iam getting the Service as sapdev & the same sapdev Service is passing to XI also
I think the Business system from the SLD is Not comming into picture.
What to do for this??
Regards
Vamsi

Condition check (based on sender file name) at receiver determination step

Hi,
My scenario is File to AS2 (Sender side file adapter and receiver side AS2 adapter)
We have 5 customers, but the source location is same to pick the files, Here we are not using any ESR objects.
Based on the source file name PI need to determine to whoom this file need to send at receiver determination step
Craeted objects
1 Sender CC,
1 Sender agreement,
1 Receiver determination
5 Interface determinations
5 Receiver agreements
5 Receiver CCs.
Could you please provide me your valuable inputs.
Thanks
Ramesh

Hi Venkataramesh,
I understand your scenario as, picking files (different file naming standard for different target customer) from one source folder. Based on file name, that payload should be sent to corresponding target customer. You have mentioned u201CHere we are not using any ESR objectsu201D. I can see two reasons for this decision
1. PI is used to route the messages, i.e., no need to transform the payload. OR
2. Files can binary files like PDF, ZIP, JPG, GIFu2026
Now I can see two possible solutions
1.     Simple solution, as proposed by u201CPrabhu Rajesh Janardananu201D, make it into 5 different scenarios (5 sender channels).
2.     Bit complex solution, only one sender channel, using extended receiver determination
Step 1:- In Sender File channel check u201CAdapter u2013 Specific Message Adapteru201D in Advanced tab. File Name should be checked.
Step 2:- In Receiver Determination, Select Type of Receiver Determination as u201CExtendedu201D. http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a423a8e5430e10000000a42189b/frameset.htm
Step 3:- Do a Graphical Mapping (use it Operation Mapping in Receiver Determination).
Step 4:-
Source and target of graphical mapping will be same (below), because you donu2019t want to access input payload (it can be XML, flat file, JGP, GIF and you donu2019t have its structure).
<Receivers>
   <Receiver>
      <Party agency="" scheme=""></Party>
      <Service></Service>
   </Receiver>
</Receivers>
Step 5:- Write a UDF in Graphical mapping as below. http://help.sap.com/saphelp_nwpi71/helpdata/EN/43/03612cdecc6e76e10000000a422035/frameset.htm Pay attention to method declaration
public String Determine_Receiver( Container container) throws StreamTransformationException
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create(u201Chttp://sap.com/xi/XI/System/Fileu201D,u201CFileNameu201D);
String valueOld = conf.get(key);
//Put your logic here
if (valueOld.equal(u201Cuser1u201D)) {
return u201Cuser1u201D;}
if (valueOld.equal(u201Cuser2u201D)) {
return u201Cuser2u201D;}
if (valueOld.equal(u201Cuser3u201D)) {
return u201Cuser3u201D;}
Step 6: Now use this UDF to map to u201CReceiveru201D and u201C Serviceu201D.
This solution need more fine tuning.
Regards,
Raghu_Vamsee
Edited by: Raghu Vamsee on Jan 8, 2011 5:56 PM

IDoc TO File: Receiver Determination did not find any receivers at all

Hi,
We have IDoc to file scenario, where based on attributes present in IDoc we have configured different receivers.
Everything was working fine and files were getting created based on the receiver determination criteria.
But there is one change done in custom IDoc to re position the attributes.
Idoc before changes was having NAME1 and NAME2 above KATR6 and KATR7 and after change it looks like below:
So there is no change in segment and no change in mapping but the attributes KATR6 and KATR7 are used to determine the receiver.
Cache refresh is done for both ESR and ID. I have re - entered the receiver determination criteria just to ensure that change should reflect.
But still when I am triggering outbound IDoc from ECC to PI, the transaction is getting errored out with below error:
"ErrText": "Processing error = Receiver Determination did not find any receivers at all",
Can any one providee some idea what could be the reason and what is the right approach to resolve this issue.
Thanks,
Vertika

Hi Krupa,
I have marked your answer as helpful answer and delete of metadata wasn't required.
Reload works . But thanks for your suggestion.
Thanks,
Vertika

Getting Receiver Agreement issue in IDOC to File scenario

Hi Gurus,
            Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
Error Message:
No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
Error Category : Outbounding
Error ID : CO_TXT_OUTBINDING_NOT_FOUND
My IR design:
Sender:
      Interface : VEND_IDOC_OUT_MI
      Message Type : CREMDM.CREMDM04
Receiver:
      Interface : VEND_FILE_IN_MI
     Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
My ID Config:
1. Sender / Outbound Message: Service Type --> Business System
                                              Service ---> SAPERP
                                             Interface--> VEND_IDOC_OUT_MI
                                             Adapter Type : IDOC
2. Receiver / Inbound Message: Service Type --> Business Service
                                           Service       --> IDOC2FileReceiver
                                           Interface    ---> VEND_FILE_IN_MI
                                           Adapter Type--> File
3. In Sender Agreement : Specified the Sender Communication Channel
                                     VEND_IDOC_OUT_Channel
4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
Can anyone help me identifying what's going wrong. I'm very new to XI and basically this is the first assignment I'm working on.
Regards,
Subhadip

Hi Babu,
           In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
Please find the XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
     <xsd:complexType name="VEND_FILE_DT">
          <xsd:annotation>
               <xsd:appinfo source="http://sap.com/xi/TextID">
               8f584d80456311dccd680018fe79f69b
               </xsd:appinfo>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb0390c11dc843000188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor Code
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb4390c11dc84e800188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor name4
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb5390c11dcbe3400188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor City
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb6390c11dc896100188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor PO Box
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         4811db0335fd11dc9e9600188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor House No & Street
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         4811db0435fd11dc98b000188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor Postal Code
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         4811db0535fd11dc870500188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor Country
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7ca8d600403b11dcc9bd00188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Tax Number 1
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7040e611dcce4300188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Telephone number
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7140e611dc8f3900188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         VAT Registration Number
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7240e611dccef700188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Account Number of Vendor or Creditor
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7340e611dcb3bc00188bd09370
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
</xsd:schema>

Webservice to file (receiver determination problem)

Hi ...
I am doing webserive to file scenario in PI7.0 server. I have completed doing the scenario. But there is a problem in receiver side. In SXMB_MONI it is showing the below error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Could you please help me out in this.

hi,
When you have used the WSDL wizard in the Integration Directory and have clicked on "Propose URL" in the second screen, did you ever wonder, why the URL does not point to a sender SOAP adapter channel, it is the URL of the Integration Server instead?
When you want to use the inbound channel of the Integration Server, you have to use following URL for the web service client:
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
The namespace must be written with escaped characters. (%5E stands for "^")
Note: The WSDL wizard creates an address with the escape sequence & instead of &. Some SOAP clients (for example XPLSpy) do not automatically restore the character and you have to do this manually.
By default the SOAP call is treated as a synchronous call. If you want an asynchronous call, you have to add &QualityOfService=ExactlyOnce to the URL.
Additionally your web service client must provide the HTTP header parameter "SOAP action" = http://sap.com/xi/WebService/soap1.1
The Web Service Wizard of the Integration Repository creates a WSDL concerning this URL and this SOAP action automatically. Only for asynchronous calls you need to change the URL inside the WSDL file with an editor and add &QualityOfService=ExactlyOnce.
Advantage
When you send SOAP messages directly to the Integration Server, you reduce the message load on the adapter engine. This can improve the performance.
Restrictions
The SOAP inbound channel of the Integration Server does not support attachments. SOAP messages with content type "multipart" are rejected.
Hint
For testing purpose it is possible to add logon data directly to the URL. The parameters are the same as in the HTTP sender adapter: &sap-user=<username>&sap-password=<password>
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
regards
chandra

File to file scenario receiver determination

Similar Messages

Maybe you are looking for