No receiver could be determined. (File to Idoc)

Hi,
I am getting below error for my file to idoc scenario.
Receiver determintation: NO_RECEIVER_CASE_ASYNC
Any inputs appreciated.
Thanks
Balaji

Hi,
Now my error message is changed to following:
<?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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_BE_NOT_SUPP</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Only asynchronous processing supported for IDoc adapter outbound processg</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
I have mentioned it as asynchronous in message interface. howcome i am getting this error message?
Thanks
Balaji

Similar Messages

IDoc (Sender ) to File (Receiver): No receiver could be determined

Hi, Dear Friends,
Im implementing scenario Idoc-to-File by means XI.
I try to follow this scenario:
Satish Jaiswal. A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
But I have an error.
In sender system I send IDoc by transaction WE19. After that in transaction WE05 I see IDoc with status 03 (successful).
After that in XI system:
1) in transaction WE05 I don't see any IDoc (IDoc is not received by the Receiver (XI Integration Server))
2) in transaction SXMB_MONI I see my message with error.
Status - System error.
In detail view at stage "Receiver Identification" in item "Error" I see: "No receiver could be determined"
Unfortunately I'm not expert in IDoc.
Can you recommend me what I need to verify?
Or advice me link on another full good example with IDoc.
What I need to read for quick start in IDoc understanding.
Thank you in advance.
Natalia Maslova.

Try these steps:
ALE Settings
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Message was edited by:
Raghavesh Reddy
null

IDOC 2 XI: No receiver could be determined

Hello,
I am glad to send a IDoc to XI!
In IDX5 I got the error:
No receiver could be determined
Many questions:
I wonder there is a "Sender Agengy": bss_lp_idoc an
a "Sender service" bss_lp_idoc
1) Are the names for "Sender Agengy" and "Sender service" generated by the system?
2) What do I have to do to determine a receiver?
additional information:
IDOC has MESTYP = SYIDOC
IDOC has IDOCTYP = SYIDOC01.
IDOC-RCVPRT = LS
Thanks a lot!
Regards Mario

Hi Vishnu,
thank you much.
I know this document. But unfortunately that does not help me.
I got also several documents about sending IDOC to the XI.
But in all documents there are relevant things missing. So I try now to to this step by step by myself.
The first thing I have to know is:
How does the IE try to determine the receiver? Which fields in the origin IDoc are read? What does the XI do next after reading the relevant fields in the IDOC?
Thanks

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

Web Service to IDoc scenario: No receiver could be determined error

Hi. I am working on a web service to IDoc scenario. I am receiving this 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="">
<SAP:Category>XIServer</SAP:Category>
<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>
I've taken the XML message being sent to me and tested the mapping and I've completed the test configuration in the IB. Both work fine. Any ideas? I've been looking into this for a couple of days, so I've been through all the previous posts I could find.
Thank you.
Nicole

hi,
This is not related to receiverdetermination ,whether you creaeted or not.
It is somthing related to receiver systemwhich was configured in Receier determination.
check the target BS is correct or not or the inbound interface.
Did you configured the proper receiver technical system..
OR
Check the Receiver Determination is configured correctly. i.e R/3
Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
You can test your configuration with sample
payload.
In ID goto to TOOLS -
> Test Configuration for testing.
Hope in this way you can still find at which point the interface goes wrong.

File to RFC to File error "No receiver could be determined"

Hi everybody.
I have a errors in BPM ...
<?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">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>
but where i enter in transaction SXMB_MONI_BPE -> Continue Processes Folowing Errors, entered in my item and choose "Send Message Synchronously" appear window "Display work item" in this "Work item information" line Status=Error press button "i Message" appear following message:
No exception defined for fault message
INTERNAL_ERROR INTERNAL_ERROR
Help me what do now?
Anvar.

Hi,
I've browse through your error document and everything seems to be ok. In the menu is this full cache refresh. Remember also to activate all objects in integration directory
Regards,
Wojciech

Acknowledgment error : "No receiver could be determined" !?

HI,
This is my flow :
SAP R/3 sends idoc to a third party through XI. This idoc must be changed in flat file type CSV. This flow works fine but there is a problem in the acknowledgement : "No receiver could be determined".
What is the problem ?
Error :
<SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemAckRequested="false" SystemErrorAckRequested="true" ApplicationAckRequested="true" ApplicationErrorAckRequested="true" SOAP:mustUnderstand="1">
 <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
<SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
 <SAP:TraceLevel>Information</SAP:TraceLevel>
 <SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
<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">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:Error>
Thanks.
Best regards

Sorry but this error desapear. With have a new error : ATTRIBUTE_INV_SND_SERV
We use mapping conversion and CSV file channel.
Thanks

Errors about 'No receiver could be determined'

Hi all:
I am setting up one scenario about ' IDOC to file '.
When I send IDOC from one R3 system to XI , I meet with the following errors.
No receiver could be determined
The SOAP Error is
<?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">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>
The trace is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: KEN</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />
</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = KEN</Trace>
<Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 2B74B179E6789D40BCC4A22D826EBDEF</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0012</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0012</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = KEN</Trace>
<Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="1" type="T">No Relation found - accept given receivers.</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
Could anybody give me some clue to debug this problem ?

Hi Jianhong,
Since you are doing an idoc to file scenario, you would not require a sender idoc adapter, you would have to configure only a receiver file adapter. Since i guess this is your first idoc to file scenario refer this blog to check if you have followed the steps correctly in the repository and directory:
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1819. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] The blog does not talk about partner profile setup, and i hope you are aware of how to do this.
Configure your receiver file adapter according to this:
http://help.sap.com/saphelp_nw04/helpdata/en/95/bb623c6369f454e10000000a114084/content.htm
Do ask if you require further information.
Regards,
Chandra

No receiver could be determined while doing SAP ECC Integraion with MDM 7

Dear All,
Can you please help me to resolve the following issue.
We are doing SAP ECC Integration with MDM 7.1 by using MDM PI Adapter.
Source side we are processing MATMAS.MATMAS05 IDoc and Receiver side we are using MDM PI Adapter to Connect the MDM System.
I have checked the Configuration by using Test Configuration Wizard, it showing every thing fine there.
Is it because of any network connection issue at the Target system (MDM) side?
Plz check the error message for your reference;
<?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">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Mahesh

Hi,
From error looks like it is not failing at receiver determination step. if you all configurations are fine, then this could be because of system cache refresh.
Go to Edit mode in your scenario and again save it and activate it. Do a cache refresh and check if it works.
Regards,
Shiv

No receiver could be determined + MDT Error

Hello,
*1.* I have one scenario for IDoc-XI-Proxy.PI 7.0
When Sending IDoc from SAP1 to XI I am getting below error in SXMB_MONI.
Config seems okay.
<?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">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>
2. While opening Message Display Tool(MDT) it's asking for Username and Password but when it give User/Password it gives me an error.
We are on SP09 PI 7.0.
 SSO logon not possible; logon tickets not activated on the server
 Choose "Logon" to continue A dialog box appears in which you can enter your user and password
 No switch to HTTPS occurred, so it is not secure to send a password
 Client, name, or password is not correct; log on again
Thanks.

Hi Gujjetti,
Please find the details::
SenderService: SAPIDS
MessageInterface: MI_IDES_CREMDM(I tried with CREMDM.CREMDM06 too)
NameSpace: https://www.abcd.com
ReceiverService: SAPECCDEV
MessageInterface: MI_ECC_CREMDM
NameSpace: https://www.abcd.com
I am getting an error in Second Step "Receiver Identification" after "Inbound Message" in SXMB_MONI as 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">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>
Thanks.
RP

No receiver could be determined / NO_RECEIVER_CASE_ASYNC

Dear experts,
I have created a scenario from file to rfc. I have:
- imported the RFC message
- Created a message interface
- Created a message mapping (file to RFC-message)
- Created a interface mapping
Then set up the proxy in the target system (BW).
Then I set up the configuration builder settings. Created a sender agreement (FTP pickup), and a receiver determination. With a receiving RFC comm. channel.
Now I test it, and it gives me: NO_RECEIVER_CASE_ASYNC
And:
No receiver could be determined
Exception of class CX_RD_PLSRV
I have removed it all and created it again. What did I do wrong?
Kind regards.

Schotanus
Can you explain why u generated a proxy? if u are using a file to RFC scenario there is no need for a proxy. try configuring ur ID objects by setting the receiving comm channel as RFC and give the logon parameters there.try running the config test in ID. if you face a problem in this test the it ihas something to do with ur ID objects and not the RFC connection to BW
ArvindR

Error No receiver could be determined in PI71

hello Expert,
i am testing a sample scenario with proxy->xi->file
application BC6, xi server PI71
configuration test is okey.
i used the BC(BS_File) is as the sender and receiver
but after run, the sender name in the record in sxmb_moni is changed BS_EC6.
i never used the bs_ec6 as sender.
so a error with 'no receiver could be determined ' happened
who could tell me why
the sender must be a Businees System?
Best Regards,
Kevin
Edited by: Kevin Gao on Dec 19, 2008 10:00 PM

Sender system must be business system for proxy scenario

BPM sync to jdbc produces No receiver could be determined

Hi,
I am sending a sync select statement from BPM to JDBC adapter but I get the following error: No receiver could be determined.
I checked in MONI and I can see the select statement, even the response but I get this error. I looked at the graphical workflow log and every step "executes successfuly" but in the XML messages list I have 3 messages, 2 with the successful flag and one with a red flag, the red flag displays this error.
Since both interfaces, the BPM abtract interface and the inbound interface for the JDBC adapter are BOTH SYNC, shouldn the response message arrive back at the BPM automatically ? or must I define another reciever determination ?
Cheers.

Hi,
How have you used the send step? In this case it should be used with sync mode.
Selcet the mode property of "send" step as synchronous. Then you will have to give two message types one for request and the other for response.
After this send step you can have a normal send step and you can use this to send response wherever you need.
Regards,
P.Venkat

XI Receiver Adapter: No receiver could be determined

Hello guys,
I'm at the moment connecting Contract Accounts Receivable and Payable 6.00
http://help.sap.com/erp2005_ehp_02/helpdata/en/9c/0d03d4beeb40848e15329b4e63976e/frameset.htm
My scenario has a XI Receiver Adapter. I have set up the receiver agreement, Interface Determination and Receiver Determination as it says in the link provided. I have succesfully tested the configuration with the TEST CONFIGURATION TOOL in ID.
But at the moment of testing a real message, I'm getting in the SXMB_MONI the following 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>M</SAP:Retry>
</SAP:Error>
Does any one knows why if the configuration is correct (according to me and the test tool), I'm getting this error?
Thanks for your help.
Felipe

Hi guys,
I have resolved the issue. Aamir you were rigth, the problem was with the sender attributes.
What happened was that the sender Interface namespace was a differente one from the one in the configuration. In this link
http://help.sap.com/erp2005_ehp_02/helpdata/en/9c/0d03d4beeb40848e15329b4e63976e/frameset.htm it said that the namespace had to be http://sap.com/FICA/Global, but it was using the namespace http://sap.com/xi/PI/FIN/Operational/Global, so I just need it to change.
Thanks guys for your support.
Felipe

Error while process the CPPR-Rfx "No receiver could be determined"

Hi Experts,
We are working on SRM 7.0 Extended Classic Scenario, While testing the CPPR-Rfx process we are getting the error msg in Portal
"No receiver could be determined".
We implemented Badi ME_REQ_SOURCING_CUST & BBP_EBPXML_OUT_BADI
We are getting this ERROR " No receiver could be determined" While clicking the "CREATE RFX" with reference to Purchase Requisition through Hormonized roles.
Pl suggest what could be the problem.
Regards,
Mohan

Check if below settinjgs are in place:
Parameter CV_EXT_RFX_IND is set to true in ME_REQ_SOURCING_CUST to create RFX.
Business functions are activated in backend ECC system.
In backend system Event type linkage is activated for receiver WS53800009, event RFXREQUESTED and BO BUS2105
In Backend system Activate outbound messages for events RFCREQUESTED for object type BUS2105.
RFC user used in PI system is assigned to Purch org in SRM org structure.
Maintain the service call RFQRequestSUITERequest_In in XI/PI.
Maintain transac type for RFx in SRM.
Do you see any entries in XI monitor and queues?
Thanks,
Jagadish

Consume a Web Service: No receiver could be determined

Hello,
I have a successful running Web Service on a JAVA stack. Now I want to consume this web service within the ABAP Stack. For this purpose I generated the appropriate proxy object from the WSDL.
However, while running my ABAP test program I am receiving an error: RCVR_DETERMINATION.NO_RECEIVER_CASE_BE No receiver could be determined
Does anybody know, what to do? Do I need to register the generated proxy somewhere? Or what went wrong?
Best Regards!

you dont need to do any settings in LPCONFIG
just create client proxy and activate the proxy class
then in LPCONFIG
enter the client proxy name and port name (port name can be any text) and check the checkbox "default" and click create and activate the same.
now you are ready to consume the webservice.
Regards
Raja
assigning points to helpful answers by choosing the appropriate radiobuttons in the answers in the SDN way of saying thanks.

No receiver could be determined. (File to Idoc)

Similar Messages

Maybe you are looking for