No receiver could be determined - ERROR

Folks - I am getting this error - "No receiver could be determined" when testing using an SAP provided HTTP client for us. I have input the following parameters in the URL:
http://srvhousapdemo:8013/sap/xi/adapter_plain?namespace=http%3A//www.wellogix.com/PIDX_12/R3_46&interface=Z_PO_Create&service=XIS_eFT&QOS=BE&sap-user=bmills&sap-password=xxxxxxxx&sap-client=200&sap-language=EN
ServerHost     - srvhousapdemo
ServerPort     - 8013
Client         - 200
SenderService - XIS_eFT
QOS            - BE
SenderInterface - Z_PO_Create
SenderNamespace - http://www.wellogix.com/PIDX_12/R3_46
ServiceUser     - xiappluser
Password        - xxxxxxxx
Any pointers will be appreciated!
Thanks.
-Cal

Just to confirm...
You have the following entries in the configuration :-
1.Receiver Determination
Sender service - XIS_eFT
Sender Interface - Z_PO_Create
Sender Namespace - http://www.wellogix.com/PIDX_12/R3_46
Configured Receivers - <Receiving_Service>
2. Interface determination
Sender service - XIS_eFT
Sender Interface - Z_PO_Create
Sender Namespace - http://www.wellogix.com/PIDX_12/R3_46
Receiver Service - <Receiving Service>
Configured Inbound Interfaces - <Inbound_interface> / <Interface_Mapping>(may or maynot be there)...
3. Receiver Agreement
Sender service - XIS_eFT
Receiver Service - <Receiving Service>
Receiver Interface - <Inbound_interface>
Receiver Namespace - <Inbound_interface_Namespace>
Receiver Communication Channel - <reciever_comm_channel>

Similar Messages

NO_RECEIVER_CASE_BE - No receiver could be determined error

Hi Experts,
Scenario: SOAP to JDBC BPM Scenario
Error: When I tried to execute the scenario, I am getting the below error. The interface mentioned in Integration Directory and SXMB_MONI are different. Where to do the correction?
Note :Refreshed the cache in SXI_CACHE and Administrator screen. I couldn't see the Integration Process in SXI_CACHE
<?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>
Regards
Sara

What was the resolution?

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.

No receiver could be determined Error - PurchaseOrderChangeRequest_Out

Hi,
I am working on SRM to SUS communication. When a PO change request has been sent from SRM to SUS via PI, I am receiving 'No Receiver could be determined' eror. I checked Integration Builder and we are missing the mapping.
When I tried to do the mapping, I did not find the PurchaseOrderChangeRequest_Out interface in ESR. I tried to download ESR content from swdc. But not sure which content to download. Is there a way to find that out?
Thanks,
SG

Hi,
You can downloaded from marketplace.
Please check the below threads which guides you ...
Re: SRM to PI/XI Integration
SRM And XI Integration
Also, refer to below document.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/601d4fee-719f-2910-4f86-fa030ab07358?QuickLink=index&overridelayout=true
Thanks and Regards,
Naveen.

No receiver could be determined error in AAE - File Adapter

Dear Friends,
We have PI 7.1, EHP1.
We are doing migration of our existing configuration scenarios into AAE.
While do testing the interfaces after migration, we face one issue.
In a File to SOAP scenario (Async), once the file is polled from the source directory and failed with the error 'No Receiver Determination' in the sender channel, the source file will not be moved to the archive directory. (Processing Mode : Archive).
Due to this problem, the source file is keep on polling with the intervals specified in the channel and failed. We see this error in Sender Communication Channel.
But, If the receiver is determined, this problem will not come. File is picked up, moved to the archive directory and processed successfully.
Friends, can you clarify how to solve this issue? (We tried with Processing Mode as 'Delete' , in that case also file is not deleted when error 'No Receiver determination')
Thanking you,
Kind Regards,
Jegathees P.

Hello Friends,
Thanks for your reply. For the testing purpose, I removed the condition to determine receiver, to force the message fail. Purpose is to test how AAE behaves for different errors.
My doubt is, in the classical method, for the same error, the file will be moved to the archive directory and further polling will not happen, we know that. In this new method, why the system did not move the file to archive directory though the error comes.
Kind Regards,
Jegathees P.

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

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

System Error: No receiver could be determined

Hi,
When i logged into the portal and click on Time management link which takes you to the time entry application (HRESS_C_CATS),and the below mentioned message is displayed. "System Error: No receiver could be determined ".
Could you pls let me know why this error shown.? This error appeared when a functional guy changed the employee profile.
Any idea how to solve this error?
Thanks,
Lakshmi.
Edited by: Lakshmi Atukury on Feb 13, 2012 7:30 AM

Check siddarth reply in below thread
http://forums.sdn.sap.com/thread.jspa?threadID=2135503
Regards
Srinivas

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 + 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

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

Error:No receiver could be determined

Hi Experts,
While monitoring XML messages, I am getting one error "No receiver could be determined" for sender interface catalogupdatenotification_out. Please let me know how i can maintain receiver for this interface. I am SRM consultant and know very little about PI and we are not having any PI consultant this month.
Thanks for your help.
Regards,
Raj Saini

Hi Raju
As you are new go through the below link to understand a simple XI Scenario
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1345
specific to your error , you need to check why there are no receivers for the inteface , either there are filter conditions in Receiver determination which are not satisfied or your configuration scenario is cofigured in appropiratly ,refer above blogs and try to configure correctly,
Also for your reference , you can find a lot of information in the bleow link (may be its lot of information for you at this stage)
http://wiki.sdn.sap.com/wiki/display/XI/PI7.0and7.1Mapping-Blogs%2CArticles%2CWiki%2CCodeSamplesandVideos+Collections
Regards
$rinvias

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

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

No receiver could be determined - ERROR

Similar Messages

Maybe you are looking for