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

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

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

Extended Receiver Determination problem

Hi,
I am making use of extended receiver determination to send 1 source to multiple target systems. When I was testing so that the interface would just send to 1 target system while still making use of the extended receiver determination, I got the following error CO_TXT_OUTBINDING_NOT_FOUND and "No receiver agreement found". The red flag error occurs during Technical Routing and when I checked the details SOAP Header -> Main, I found that the following:
Sender Service: ServiceA (correct)
Sender Interface: InterfaceA (correct)
Sender namespace: NamespaceA (correct)
Receiver Service: ServiceB (correct)
Receiver Interface: InterfaceA (wrong)
Receiver namespace: InterfaceA (wrong)
It seems that extended receiver determination was able to successfully determine the receiver service but fail in determining the correct receiver interface and receiver namespace. Does anybody know why this happen and how to correct the problem?
Some investigation that I already done:
1.) I temporarily changed the extended receiver determination to a standard receiver determination and specifying the 1 target system explicity without changing any other object in both IR and ID as well as using the same test file. The result is that this worked and the file was sent succefully to my intended target system. This tells me that the problem might either be in the extended receiver determination or in the message mapping or message interface Receivers. Also, this means that all the other objects in ID for this interface is configured correctly.
2.) I tried hard coding the target system as a constant in the message mapping for the Receivers message type and still make use of the extended receiver determination and I got the same problem mentioned above.
3.) I tried deleting the receiver determination, activating the changes, re-create the object and activate it and I still got the problem
4.) I tried checking sxi_cache and everything is up to date and correct
Any suggestions is highly appreciated.

Elbert,
I you are doing only standard receiver determination only and using certain condition you are sending to different targets. If yes check this url:
/people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
Can you please put the payload after message mapping and the xpath condition you mentioned. or if you are doing enhanced receiver determination please check this:
Re: Error in enhanced receiver determination
---Satish
Edited by: Satish Reddy on Jun 23, 2009 9:08 AM

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

Configuration Scenario Builder - Receiver Determination Problem.

Hi I am Follows configurates Integration Scenario to SRM-SUS scenario in XI
In Model Configuration. when I try create Object Bottom in Simulation Process . generate the report show the next message for
Component View Connection
Receiver Determination light yellow color SRD_009 | PurchaseOrderRequest_out
Analisys ; Requiered Communication Component | SRD_009
                a receiver determination was found for connection
                Reciever are missing in the receiver determination found
Results ; the reuse receiver determination is already assigned to the configuration scenario
               the missing receivers were inserted into receiver determination found
               added receiver communication component SRD_008
Notes;      Check the conditions for all receivers of the receiver determination. the default result value for the generated condition
                is TRUE:
thanks.

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

File2file Receiver Determination Problem

Hi All,
I am doing File2file my IR part is activated in ID part I creater 2 CC in Business Service sender with FCC and Receiver with Normal XMLfile after this step Iam trying to create my Receiver Determination Its showing that NO OBJECTS FOUND in interface and Namesapce column.
Regards,
Eswar.

In case your doubt is still not cleared:
When you create Receiver Determination (ID --> New --> receiver Dtermination), in the pop-up window you select the Sender Business Service and the corresponding Sender Message/ Service Interface .....now this message interrface should be first assigned to the Business Service.....now after we create the RD, we enter the corresponding Receiver Service/ System thereby creating the first relationship between the Sender and Receiver Service/ System in XI/ PI.
The above selection holds true for any scenario developed in XI/ PI.
Regards,
Abhishek.

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

RFC to WebService Receiver Determination Problem

Hi,
I am doing RFC to WebService with the help of this weblog
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2 In Interface Determination - when picking Inbound interface is coming as No objects found.
How to resolve it?
regards,
Ansar.

Ansar,
In RFC to Web service the inbound interface should be the WSDL.
Did you import WSDL under 'External Definations'.
After importing you need to create a inbound message interface of the Message within the WSDL that you need to use.
Regards,
Ashish
Message was edited by:
Ashish Goyal

File Receiver Adapter problem

Hello Friends,
I am doing a simple File to File scenario. The scenario has succussfully gone through the pipeline steps and so it is successful in sxmb_moni. But the output file has not been generated. I have checked the communication channel monitoring for the receiver file adapter. There, its status is "green" and "functioning", but under "Processing Details for Cluster Node" i am not getting any logs/messages which tells us when the process has statred and ended.
In message monitoring, the status is "To be delivered" and its not getting changed.
Please guide me to solve this issue.
Thanks & Regards,
Senthil.

Hi
First check
1) Receiver FTP Details if it is correct (Floder having right credentials to write file)
2) In Message Monitoring "To be delivered status" u can send it from there itself "Resend"
If not happening delete all Messages of "To be delivered status" and resend again it would work
Moreover check Smq1 / smq2 Queues if it is stuck
For processing u have for sure clear off all messages in "To be delivered state' first r else all messages will be in pipeline
Better ---> SXMB_ADM --> Deactivate / Activate Queues
Rgds
Srini

Unable to download a pdf file. received message-problem with program with acrobat reader-103-103

unable to download a pdf file using acrobat reader X. received message-there is a proble with program with acrobat reader 103-103.

Download the file with your web browser (Safari, Firefox, Chrome). Then attempt to open the PDF file in Reader or Acrobat.
It may not be a real PDF file, or it may be damaged.

File Receiver - before message processing *urgent*

Hello experts,
I have a scenario where i need to execute a script in File receiver adapter.
problem: "i send an xml file to target system, but as long as there is a .xml file in the directory, it should not send.
He should wait and send only then when there is no .xml file in the directory."
Is that possible with "run operating system command before" in the receiver adapter or i need for this issue BPM?
Best wishes,
FK

Hi,
File receiver adapter has a "Run Operating System Command Before/After Message Processing" feature, so you could use it for such purpose :
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
I think it could be better to use a script than using BPM (it will save resources at XI level).
Chris

Receiver determination - Xpath expression problem with count

I am working with a scenario where I pick up records from a JDBC connection and if the number of records I pick up is less than a certain number I want to call a webservice. If it is greater than the number I want to write out a file to be processed by a different process on the receiving end. I have created the receiver determination condition with the following conditions:
(/p1:MT_HOG_Data/row[count(row) > 3] EX)
(/p1:MT_HOG_Data/row[count(row) <= 3] EX)
The integration is always processing the second condition no matter how many records come in. I have tried with and without the multiline option. Can anyone help with this?
I have searched through the forum and checked the following links without any resolution:
http://wiki.sdn.sap.com/wiki/display/XI/XpathConditioninReceiverDetermination
http://help.sap.com/saphelp_nwpi71/helpdata/EN/ab/13bf7191e73a4fb3560e767a2525fd/frameset.htm
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
I can't find any examples where a count of records is checked in the expression editor. Thanks in advance for any help.

You can not use the EX operator in that case, because that is used only for node existence checks, not for value checks.
Do you have a row number in your structure ? Then you could write the xpath expression with that counter tag and value
Example: you want to send to receiver A if count > 3, else to B:
you set /rowNumber EQUAL 4 for sender A
and /rowNumber NOT EQUAL 4 for sender B
The condition is applied to the whole document. If one of the node/values are true for that condition, then the whole condition is set to true.
Problem with that is that the second condition also will be true because nodes for that condition will be found
better would be to have a rowcount tag in the structure. If that is not possible, you can use the "Enhanced Receiver determination" where you can define a mapping which determines the receivers. There you can do anything complicated you want.
CSY

Problem in receiver determination

hi experts
I am working on a idoc to file bypass scenario where i am using extended receiver determination ,abap class is being used for abstract interface mapping ,It is working fine with other interfaces.but on a particular idoc its started showing error in sxmb_moni that"Error when determining the receiver: Problem wh
determining receivers using interface mapping:
Error in mapping program
/GLB/CL_ZGTIS_GNERIC_ROUTING (type SAP-ABAP,
kernel error ID CREATE_OBJECT_CLASS_NOT_FOUND)" so can u tell where is the problem i have crosscheked the abap class very well all entries r right.
plz update its urgent

hey i have done a mistake in writing the class name in the mapping ............

Failed Receiver Determination on empty file

I have seen suggestions matching the solution I have tried, but it is not working in my scenario.
The scenario is an empty CSV file inbound to 3 receivers. In the standard receiver determination, I created a context condition for the 'SAP system' receiver, which uses RFC adapter. The condition is: 'Sourcefilesize not equal 0'. For an empty file, the 'SAP system' receiver should not be selected because it has mapping to the RFC structure. The other 2 receivers are SFTP and file, and the client requires they receive the empty input file.
I see the file size is captured in the dynamic configuration in the MONI:
namespace: XI/System/File.....name="Sourcefilesize">0<SAP:record...
The error is: Problem while determining receivers using interface mapping: Error while determining root tag of XML: BOM / charset detection failed.
The system is PI 7.1, the sender comm channel is Advantco with namespace override and content conversion. I have tried using file type 'binary' and type 'text', with UTF-8 encoding - results in the same error either way.
The file is coming from an external vendor - I do not believe they will make any changes to it, so hopefully this can be resolved in PI.
All suggestions are appreciated. Thank you.

Hareesh and Osman, thank you for your replies.
I should have pasted the entire message. When testing in the IB, it fails in receiver determination..
""Error when determining the receiver: Problem while determining receivers using interface mapping: Error while determining root tag of XML: BOM / charset detection failed Error while parsing an XML stream: 'BOM / charset detection failed&#39""
Only the SAP system RFC receiver has message mapping - the SFTP and file receivers do not. (I have changed only namespace and system names in screen below)
Receiver determination -
Interface Determination XXXX_D
Interface Determination Archive_D
Interface Determination SAP system

Webservice to file (receiver determination problem)

Similar Messages

Maybe you are looking for