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

Similar Messages

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

Receiver Determination - Configuration Overview for Receiver Determination

Hi All,
I was trying on some tutorial for Calling RFC(sender) and creating a File at Receiver site.
I've configured all the required setting at the Design: Integration Builder.
As for Configuration: Integration Builder. Until the Step where I required to setup the Receiver Determination, there is this part "Configuration Overview for Receiver Determination". where i have to maintain the "Receiver Service", else i will hit this error "Enter the receiver service".
The steps which i followed was :
1. Create 2 Communication Channel for Sender/Receiver in the Business System.
2. Create a Sender agreement.
3. Create a Receiver agreement.
4. Create a Interface determination.
5. Lastly "Configure the Overview for Receiver Determination" for Receiver Determination
The problem which I'm facing now is I have nothing in the "Configure the Overview for Receiver Determination" at all even i have created the sender/receiver agreement and interface determination.
While some troubleshooting, under the If No Receiver Is Found, Proceed as Follows: I tried choosing the "Continue Message Processing with the Following Receiver" radio button and choose the Receiver for the Service then hit the save button.
The error "Enter the receiver service". pop up but now, the Receiver service was shown under the "Configure the Overview for Receiver Determination". When i try choosing back the "Terminate Message Processing with Error (Restart Possible) and hit the Save button. The Receiver service goes missing again.
Any Idea what happen ? or anything i missed out ? thanks in advance.

Hello
Check if you have the issue in the kba #1538009 Error When Executing Open - Object not found.
Also see note #1466011 Usability Improvements in Directory:
o Don't show deleted objects in navigation tree
When you delete an object in Directory the link to this object is not
automatically deleted from Configuration Scenario. You need to manually
open every scenario and remove such 'broken' link. In scenario editor
broken links are displayed in grey font and therefore can be easily
identified. Unfortunately the navigation tree in 7.1 (in contrast to
XI3.0) doesn't make difference between existing and broken links and
shows them as they all leads to existing objects.
Regards
Mark

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

Problem in receiver rule of configured receivers in receiver determination

Hi, Experts!
Can anyone please help me with an issue regarding the receiver determination part of IB? I currently have 2 different receiver rules, each having a different condition but under the same communication component. When I check the message status in the runtime workbench however, both rules are considered and thus 2 messages are sent instead of just 1 from the selection. Please help me send the message according to the selected interface. Thanks!

Hi Brent,
You may write the rule as follows:
if (Receiver='CHDB') OR (Receiver='CIF') then send the incoming message to the relevant Receiver Business Component/System.
You may use the X Path editor for configuring this rule in the Content based Receiver Determination of your scenario.
I hope this will help.
Regards, Gaurav

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

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

Problem configured users in receiver determination

I am configuring idoc to proxy. My scenario is working fine without condition RCVPRN SR4CLNTDRY . But if i give condtion it is showing this error in runtime workbench
Error Category
IDOC_ADAPTER
Error Code
ATTRIBUTE_INV_SND_SERV
bye

Check the point no 5:
Troubleshooting File-to-IDOC Scenario in XI.
chirag

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

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

Receiver Determination, Configure Receivers, Condition configuration alert

Hello Colleagues,
when i try to configure condition area under Configured Receivers at Receiver Determination i get following notification:
Message Interface does not exist in any software components installed on this business system.
Could tell me someone where is the problem?
Many thanks in advanced!
Regards,
Jochen

> Hi Krishna,
>
> the message type "INTERNAL_ORDER.INTERNAL_ORDER01"
> exist under Software Componenten Version\Imported
> Objects\IDocs at IR and is activated.
>
> Regards,
>
> Jochen
Under which SWCV it exists in IR?
As pointed by Bhavesh, you have to add the product that contains this SWCV to Technical System which contains the Business System you're trying to use that interface with. It's done in SLD.
When you select the product, make sure you mark the proper SWCV in the left panel, then save it. It'll be added to that Technical System. But you still need to go into the specific Business System and select that SWCV, in order to properly associate it to the BS.
In the future, as a project best practice, make sure you follow these steps b4 starting IR/ID development.
1. define your project SLD (Technical/Business Systems);
2. create/import the Products/SWCVs you're going to work with;
3. associate the Products/SWCVs to the relevant Technical/Business Systems in SLD.
Regards,
Henrique.

Parties and Services in Configuration Scenarios

Hi,
I think I understand the distinctions between parties, business-systems, and -services.
If I define an integration scenario in the repository and check the checkbox b2b-communication, I have to use parties in the directory integration scneario configurator.
Do I then also have to provide a partner for my own company and assign my business-systems and services under this node? I otherwise get problems when I assign the services to the application systems in the configurator and my receiver determinations get wrong.
Any thoughts and information about this topic is welcome.
Thanks,
Hans

Hi Hans,
it is not necessary to define your 'own' party if you only have 'intra-enterprise message exchange'. The big deal about parties is the possibility to define 'additional' IDs like DUNS-numbers to the Party - this is necessary whenever an Adapter is used that requires specific IDs (these are typically B2B Adapters only). The Receiver-Adapter (for messages coming into the Integration Server) will map from an additional ID to the XI-Party name and the Sender Adapter (for messages sent out of the IS) will map from the XI-Party name to the additional ID as defined within the Sender channel.
In other words: parties are needed, whenever one Communication Partner's message format expects meaningful values according to a specific schema - not only in the payload but also in the message header (liek RNIF).
Please be also aware, that the Scenario Configurator tries to capture typical use cases - it can not handle everything so it is possible that one has to change objects afterwards.
regards, frank

ACK for receiver determination with 2 interface determination

Hi Forum,
I have a XI scenario, with a BPM, where i have a Send step,
this send step corrsponds to a receiver determination in Configuration, and this receiver determination has 2 interface determination,
because the send step is like,
BPM to Receiver1, through sender message interface MI_Sender1, but there are 2 different receiver message interface namely MI_receiver1, and MI_receiver2,
.......hence 2 interface determination and 2 interface mappings accordingly,
and now when in BPM, i choose "transport acknowledgement" for this send step, my BPM stucks while waiting for the acknowledgement, but...in MONI, i am receivng both the acknowledgement, but in PE, workflow descrition, it waits for acknowledgement and finally fails,
what's the reason,

check the workitems of both sender/receiver (ack) in moni (problem might be in BPM config).

Receiver Determination Enhancement

what is Receiver Determination Enhancement?
how will i use it?

Hi,
Enhanced Receiver Determination
In IR
Have you imported Receiver Determination in the SAP BASIS --> http://sap.com/xi/XI/System.
Have you created 2 message mapping
1) input_output_mm on input_mt and output_mt
2) input_receiverdet_mm on input_mt and Receivers
Have you created interface mapping under input_mi and ReceiverDetermintion message interface as source mt is your input_mt and target mt is your Receivers
In RD
Sender name->Your source BS
Sender interface->your source MI
Choose the option Extended ->
Choose interface mapping name under your namespace.
Before that Check whether you have activated everything properly.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/enhancedReceiverDeterminationinSAP+XI&
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
A typical usage case is if you do not yet know the names of the receivers at configuration time.
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
Illustration of Enhanced Receiver Determination - SP16
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
Enhanced Receiver Determination for Synchronous Scenarios
/people/jin.shin/blog/2007/12/11/sap-netweaver-process-integration-enhanced-receiver-determination-for-synchronous-scenarios
Enhanced Receiver Determination
http://help.sap.com/saphelp_nw04s/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
Thanks,
RamuV

Configuration Scenario Builder - Receiver Determination Problem.

Similar Messages

Maybe you are looking for