Reciever determination probem

hi,
for idoc to file scenario iam getting sender service and reciever service same in mesaage moni in rwb
plz help me

Vijender,
Check your receiver determination whether you are using the correct message interface and correct business service or not.
Also for business service you have to manually add your sender and reciever message interface. Then you will be able to configure your receiver determination. So please check all this.
---Satish

Similar Messages

Reciever Determination condition error in PI7.1

Hi Experts,
I done File to File scenario in XI with multiple recievers based on FileName in Reciever Determination, i use context object(FileName, http://sap.com/xi/XI/System/File) in Expession editor, this condition was working in XI, but in PI7.1 it is not working, it is giving error like below.
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem evaluating a condition: An exception has occurred.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem evaluating a condition: An exception has occurred. Problem evaluating a condition: An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. Problem extracting values from the Payload: Check line 2 column 1 of the XML document</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anyone please help me out of this.
<removed_by_moderator>
Edited by: Juan Reyes on Oct 1, 2010 2:53 PM

Hello ,
I have the same issue with PI system and all IDOCS in PI are in error state.
The issue in our case was the condition for the interface was visible from integration directory in receiver determination , but its not replicated in ABAP stack ( tcode sxi_cache ).
so we have gone in receiver determination in Integration builder-->Receiver Determination
Select a object --> click on Edit mode
Add a space in the description , click on SAVE. Then activate it.

Reciever Determination: No reciever could be determined in SXMB_MONI

Reciever Determination: No reciever could be determined
Hello people,
When I tried transfering PO to supplier this error happened in XPP system.
Don't know how to solve this.
Is this a problem with the supplier.
Please give a solution.

Hello Deepak,
You getting error in XI system right while executing SXMB_MONI? If that is the case it looks like issue with XML mapping and determining supplier information from the xml message.
Please check your xml schema mapping you should able to identify issue.
Thank you
Ritesh

Configuration overview for Reciever Determination Error

Hi friends !!
while creating Reciever determination... at configuration Overview for reciever determination (tab) Reciever(Partner / Service) showing Not Defined
can anybody suggest me why this issue is coming
Regards
Abhishek Agrahari

Hi Abhishek,
while creating Reciever determination... at configuration Overview for reciever determination (tab) Reciever(Partner / Service) showing Not Defined
This shows as undefined because you may not have selected the Service in the Configured Receivers in the window above configuration Overview ......once u select the receiver service and save the data then u need to go to the configuration Overview space and right click on the not defined link and select NEW SPECIFIC and there select ur receiver service....do the same for mapping and receiver agreement....This will serve ur purpose.
Thx
Ravijeet

Enhanced Reciever Determination Map problem

Hi,
i am working on enhanced reciever determination, i followed this blog for reference
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
after the mapping recievers MT (predefined from BASIS) . i have tested with the following payload and it is working fine.i got my ERD is working
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_SampleFile_sx xmlns:ns0="urn:TestScenario">
 <Person>
 <name>mr</name>
 <age>123</age>
 </Person>
 <Person>
 <name>ms</name>
 <age>12</age>
 </Person>
</ns0:MT_SampleFile_sx>
if i give the payload with more mr or ms node like below, i am getting error.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_SampleFile_sx xmlns:ns0="urn:TestScenario">
 <Person>
 <name>mr</name>
 <age>123</age>
 </Person>
 <Person>
 <name>mr</name>
 <age>12</age>
 </Person>
 <Person>
 <name>ms</name>
 <age>1256</age>
 </Person>
</ns0:MT_SampleFile_sx>
ERROR: Cannot produce target element /ns1:Receivers/Receiver[3]/Service. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
can any one help me to solve this problem
Thank You,
Madhav

Hi,
I had checked UDF. As per UDF you want to give ,
<name>mr</name>
instead
<name>Mr</name>
Change the payload and map like below,
Receiver:
Name(Change Context to parent)--SplitByValue(ValueChange)--CollapseContext--Receiver
Service:
Name(Change Context to parent)--ServiceDetermination(UDF)--SplitByValue(EachValue)--Service
Regards,
Prakasu.M

Problem in Multiple Reciever Determination

I am working on the scenerio in which i have to send data to different system depending upon the sending payload....
to brief about it..
i am using 2 mappings!! one for reciever determination and other for normal functionality
/ns1:Receivers=/ns0:MT_ABAPPROXY= /ns1:Receivers/Receiver=/ns0:MT_ABAPPROXY/header= /ns1:Receivers/Receiver/Service=SplitByValue([type=Each value]iF(const([value=BS_AED]), stringEquals(/ns0:MT_ABAPPROXY/header/EMPNO=, const([value=000000000023])), const([value=BS_AED_210])))
the logic was like i need if the employe number = 000000000023 , th ereciever should be BS_AED_210 else it shoud be BS_AED.
The other mapping which performs the functionality of the Scenerio:
Messages-> Messages->
 Message1-> Message1->
 MT_PROXY->(1..1) (a) ZTEST1(0..unb)
 (a) header-> (0..unb) Data
 (b)EMPNO (b) EMPNO
 (c)EMPNAME (c) EMPNO
where ztest is my Customized RFC...
in ID Type of Recvr Det is Extended
And mapping i have put is my first mapping where i determine my Reciever
In Interface Det1: reciever was BS_AED
In Interface Det2: reciever was BS_AED_210
The data is gettign branched and Split sweetly it is not sending into diff syst.
as my data is like
EMPNO = '000000000022'.
EMPNAME = 'B'.
EMPNO = '000000000023'.
 IT_HEADER-EMPNAME = 'C'.
the logic say 23 one should go to one specific system BS_AED_210 and the other to BS_AED ... but it sending both the data in both the systems...
I hope i have clarifiy my problem..
Kindly help me out in solving this issue....

the logic say 23 one should go to one specific system BS_AED_210 and the other to BS_AED ... but it sending both the data in both the systems
--->
You need to write a UDF for that
Did you see this blog
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
Following code will help you to route msg to corresponding receiver
int mr = 0;
int ms = 0;
for( int j = 0 ; j < a.length ; j++ )
 if( a[j]==000000000022 && mr == 0)
 result.addValue("1");
 mr = 1;
 if( a[j]=000000000023 && ms==0)
 result.addValue("2");
 ms = 1;
You may have to do little modification to code acc to your logic

Using Extended Reciever determination

Hi All,
We can configure a receiver determination in such a way that the receivers of the message are determined dynamically at runtime by a mapping.
This enhanced funtionality of receiver determination is only useful in case of asynchronous communication, because the standard Receiver determination interface provided by SAP in BASIS Software component is asynchronous.
But What if we want to dynamically determine a single receiver in a mapping program and call it synchronously?
what is the workaround for using the Enhanced Receiver determination functionality in Synchronous communication.
Using BPM is one of the option but, I want to call only one reciever synchronously(not multiple receivers), so I want to avoid BPM. And this receiver will be determined dynamically based on a mapping program.
Is this possible using Enhanced Receiver determination.
Thanks,
Yomesh

Hi Yomesh,
you can find the receiver by an X-Path expression of the payload. Click in the receiver determination on Service, in the the popup on button "extended", then choose XPath and put there for example //myReceiver. The receiving service will be the content of field "myReceiver".
Regards,
Udo

Sender party of reciever determination is getting used in IDOC receiver

Hi All,
i am having a very strange problem in my XI scenarios.
i have 2 scenarios: S1 and S2.....S1 scenario is running on production.......S2 scenario is on development....both S1 and S2 are similar in the sense, they are sending IDOC to SAP R/3.......
s1 scenario is having in recever determination :
sender party A
sender service A1
receiver service R/3 by IDOC adapter - in this apply control rec values from payload is checked.......This S1 scenario is running fine on production.....
s2 scenario is having in recever determination :
sender party B
sender service B1
receiver R/3 bY IDOC adapter - in this when i check apply control rec values from payload, then in SXMB_MONI i get error :Unable to convert sender XI party http://sap.com/xi/XI/XIParty/B to an IDoc partner....So you see the sender party B is getting used in the IDOC comm channel......But when i uncheck control rec values from payload, then my msg is successfully processed in SXMB_MONI...
Now my question is : why S1 is runnig fine and S2 is not running fine on check apply control rec values from payload option......both are having party and service in sender.........So has it to do something with the definition of party......
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

Hi Bhavesh,
my scenario is file - idoc........basically it is XI msg->IDOC scenario....the source xi msg i am getting from another XI system.....but on dev, i cannot connect to that external XI system, so on dev i am having file sender adapter to send the source file to be mapped to IDOC and then to be send to R/3 dev..........
i saw the control rec values of both S1 of prd and S2 of dev........
S1 scenario is similar to S2 in the sense it also has XI msg from that external system.....but since prd is connected to that external XI system, so we have created a party and a business service in it.......it has in IDOC adpatere the option of appy control rec checked........
i saw that the control rec of both S1 and S2 msgs were similar......moreover the control rec values of S2 msg with and without the option of appy control rec checked were similar.........the only issue is when the apply control rec option is checked, then it gives error that "Unable to convert sender XI party http://sap.com/xi/XI/XIParty/B to an IDoc partner"......
But in S1 prd scenario, it is not giving this error on checking the option of appy control rec.......
Can you suggest why this is happening - why party B of S2 is considered differently from party A of S1......moreover these parties are simple parties created in ID.........
Thanks,
Rajeev Gupta

Interface Mapping not listing in the Extended Reciever Determination

Hi,
The Interface Mapping is not shown in my Extended receiver determination. I have created and activated the IM & MM using the MT - Receivers within the SAP Basis.
Regards
Unni

Hi,
You can only choose the Interface mapping for the Enhanced recevier determination in the extended tab of Receiver determination. & I dont see the Interface mapping in the select list.
Where do I have to check for the proper outbound message???
Regards

Conditional Routing in Reciever Determination: Best Practise

Hi ALL
I am doing a File to EDI scenario....
And based on the vendor name in the file... I will be routing the EDI to
various vendor destination hosts.
Here is the Scenario
A file which is coming from a single sender is being routed to
multiple hosts(vendors); I am currently using conditional routing by
specifying the Vendor name as the filter
condition in the Receiver Determination and
routing it to the corresponding vendor party.
single sender FILE (ECC) -> multiple EDI relievers.
Filter Condition for routing to vendor party:
Vendor name / Vendor Code specified inside the file
as one of the fields.
However, my vendor list might increase to about 50 ...In this case would
this be the best approach to do the conditional routing ... or can you please
suggest any better method.
Thank you,
Patrick.

Hi! ALL
Thank you for the response....
Most of the receivers are file (FTP) - 90%; some of them are AS2(HTTP protocol) - 10%.
Also, here is an overview of the scenario:
ECC would write IDOC's in batch mode
in a .xml file (each .xml file would have
3 or 5 Idoc's for a particular vendor).....So, PI
file adapter will pick up this .xml file and write
in to an EDI structure;
the header of the IDOC will have the vendor
name and all the IDOC's under a particular .xml.
All Idoc's under a file will belong to the same vendor.
Can you please explain to me:
How we could use a value mapping for the above scenario to route the EDI to the
right receiver(vendor party) in my configuration.....As, the vendor name would be in
the header of the IDOC in the .xml file...I might be missing
something here...would like to get an understanding as
how I can link the value mapping to the IDOC of a particular vendor?
Your help is greatly appreciated!!
Regards,
Patrick

Reciever Determination error

Hi,
My scenarion is File->XI->FILE based communication.
I am using the SAP XI3.0 SP12. I am testing the configuration in the Integration Directory(ID) using the "Test Configuration" functionality in 'Tools' menu of ID.I am getting an error at step 2: Received Determination. Here is the error I see:
Internal Error java.io.IOException
Your changelist is not empty. Activate changes before simulation
I have seen on sdn that for this we should check url of the Adapter engine on our XI Server.From where and how we can check the url of adapter engine on xi server.
If there is some other reason for this problem plz help me out for that.
I would appreciate your comments and suggested remedies for the error situation.
Thanks,
Rekha

Hi Rekha,
>>> have seen on sdn that for this we should check url of the Adapter engine on our XI Server
- open SLD
- go to the business system of your XI server
check if the pipeline url looks like this:
http://host:HTTPport/sap/xi/engine?type=entry
HTTPport is like 80(XX) where XX is the instance number
you can check the HTTPport of your XI:
a) TCODE - SMICM
b) goto
c) Services
Regards,
michal

XI Reciever Determination

Hi
This is a typical problem we are facing your help will be immensely appreciated .we are using SOAP adapter and passing data to a legacy system which is web service enabled.In the context of exchange of data we are finding it that by using SXMB_Moni we could see chequered flag informing data has been passed but while reciever which actually consumes this data do not seems to recieve any thing neither there is any error.
Reciever configuration
Transport Protocol Http
Message protocol soap 1.1
Target Url:IP address of the webservice.
though the sender and reciever are at different location connected through WAN.
SAP data extract is success ful but not XI to reciever .
Please do help us in this contextasap
with regards
subrato kundu

Hi,
do you see success call in messaging system
(adapter monitor for messages)
http://hostname:portnumber/MessagingSystem/monitor/monitor.jsp
in SXMB_MONI you only see that the messages was passed
to the AFW if you don't have any acknowledgments
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Reciever idoc adapter Determination error

Hi,
I have scenario File-XI-R/3.I am using Idoc adapter to send data to R/3.
I am getting Reciever determination error.I have done all the steps according to the below weblog.
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
When I test my steps in configuration with test tool it is succesfull but give me error at runtime.
Below is error description.
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</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>M</SAP:Retry>
</SAP:Error>
Plz help me out if any one has some idea abt it.
Thanx
Rekha

Hi Rekha,
The End Point Type for your scenario should be an IDoc Adapter with parameters from your RFC destination in SM59.
The most common reason for this error is:
1. An error in configuration of sender adapter/proxy: wrong sender business system or namespace or interface name. Look, all this information you must put manually so be carefull on typos (one wrong or ommited letter and you can spend hours looking what is wrong). Copy (from Repository) and paste procedure is strongly recommended.
2. An error in Directory (Endpoint Configuration). Be careful to specified the correct host and port!!!
Hope this helps.
Regards
Suraj

Adding a new reciever to an existing integration scenario of conf in PI7.0

Hi SapAll.
here i have got a requirement to add one more reciever to an existing integration scenario in Integration Directory(Configuration).
this Integration scenario is for sending the idoc MATMAS.MATMAS05 From 5 Different SAP-R/3 Systems to 2 Recievers.
here iam using 5 different business systems with idoc communication channels for sending idocs and 2 business systems for recieving idocs in file format with file adapters.
so when iam trying to create new reciever detarmination or Interface Determination, it says object already exists.
but i can created reciever agreement without any error.
so can anybody guide me on how to create the Interface,Reciever Determinations without any error.
regards.
Varma

now i just created a new business system with file communication channel
Why have a Business System for a FILE channel? We normaly use Business Component/ Service.
You mentioned IDOC SENDER channels....why? For IDOC we just create Receiver channels...unless you want to specify IDOC packaging.
when iam trying to create a reciever detarmination from one of the existing sender system say like BUS_SENDER2 to new
reciver system ex:NEW_BUS_RECIEVER it says object already exists.
Receiver Determination can have the same BUS_SENDER2 system/ service as sender....but it should not have the same Interface Name....this is where PI is throwing the error.
There already exists a Receiver Detremination with BUS_SENDER2 as source system and the same message interface.
You can reuse the same RD by just entering one more receiver system/ service below the already existing one (in the RD)
In short just search your ID and you will see a RD created with the source details which you are trying to use.
If you want to see a difference, then create a new sender service/ system and then use this to create the RD!
Regards,
Abhishek.

Using File Name to determine the Receiver

Hi All,
I have to determine the receivers based on the Input file name. I am using the context object File Name in the condition editor. But based on the first 4 characters of the FileName I have to route the file. Can anybody please help how to formulate this expression in the condition editor?
Thanks,
Geetha

Hello Geetha,
         You need to specify this in you mapping as in condition editor you can not specify values at runtime. What you need to do is
-> Select the Extended Reciever Determination in ID
->In IR specify the mapping for determining the receiver (You need to use the another mapping for this)
        . Here copy the MessageType 'Receivers' from the component as your target MT
          SAP BASIS 7.0 (Depends on your version)-> "htt://sap.com/xi/XI/System" namespace.
       . Define Message Mapping between Outbound Message Type(The one with your filename) and
         Standard Message Type u201CReceiversu201D which is as Inbound message type and which is in the SAP
         BASIS -->http://sap.com/xi/XI/System
       . In mapping specify your service based on your First 4 character of your file name(Use SubString)
IF filename -> SubString(0,4) ->Equals ->   filename -> SubString(0,4) Then Select Your Service ( Service in Constant value). ELSE (your logic)
Once you finish this remaining as usual in IR, while InterfaceMapping you select two mapping programs.
Remmber to use the Extended Interface Determination in ID, This resolves your issue.
Regards,
Pasanna

Reciever determination probem

Similar Messages

Maybe you are looking for