Multiple receiver agreement detection.

Hi,
Well i am developing a test application, which would be testing a system by sending a test idoc message from XI to the XI itself.
1. A HTTP client is used to a idoc as a xml file to the SAP XI.
2. Later the message is processed in the XI with the mappings etc & has to be transferred to a suitable receiver.
3. In order to do the step 2, i need to determine whether the message is a test message or some other normal message. Hence in the Receiver determination, i need an appropriate condition.
4. My problem is that i can search for a particular xml tag in the XPath of the test-idoc but i cannot determine whether its a normal message or not with an xpath expression. for example
my condition for the test receiver determination:
A)
/Z_C_ADDADDRESS01/IDOC/EDI_DC40/SNDLAD = TestMessage_Tool
B)
/Z_C_ADDADDRESS01/IDOC/EDI_DC40/SNDLAD =/ TestMessage_Tool
(=/ is not equals, i have no other symbol here).
The condition A is valid, but for a normal message B) has a problem. Since the tag SNDLAD does not exist at all in a normal message, it fails here. i also tried to check if there is anything like tag does not exist condition. but it is also not available.
Has anybody done something similar to this before. if yes please do write back. if its necessary i shall elaborate more in detail.
Thanks,
Srinu.

Hi Srinu,
I was reading through the help on condition editor and saw this....
EX Exists
You use this operator to check the existence of the expression (in the left operand). This enables you to find out whether a substructure represented by the expression exists.
You can use this operator if you want to check whether a particular element exists in the payload, for example. To do so, enter the element you want to check in the left-hand operand and leave the right-hand operand empty. <b>You can also use the = operand for this check.</b>
I was thinking, it might be worth while giving a shot by using "not equals" and donot give anything in the right operand field....(as the "equals" with right operand blank check for "exists")...
if you have already tries this....ignore my reply.
btw..Welcome to SDN!
Thanks,
Renjith.

Similar Messages

Any possiblity to use single Inbound Service Interface with multiple Receiver Agreements

Hi All,
Scenario: PROXY to FILE.
Requirement is to receive to two locations.
Is it possible to use single Inbound interface with multiple Receiver Agreements. I tried using two operation in the Inbound Service Interface, and Operation Specific in Determination. But couldnt proceed further. Do I need to use seperate Service Interface for two receiver locations?
Please suggest some solution.

Hi Naveen,
There is a possibility but in the case in the same server location with dynamic configuration: Placing file in two different directories using single receiver communication Channel
With different location you would need to develop a new adapter module as Amit Srivastava explains and develops here Send File to Two Different Locations using Adapter Module
Regards.

Multiple receiver agreement

Hi!!!
I want to send the message to diferents receiver agreement,
depending of data in the message mapping, someone have a tutorial or link can help me!!!

This blogs illustrates how to use the enhaced Receiver determination...here the receiver is determined by the Mapping program...
if you dnt see the Interface mapping program in the when you click the enhanced button....then
1. Make sure the Interface mapping and mapping program are active.
2. Do the cache using SXI_Cache......then check the namesapce and SWCV from the drop down list.
and about sending the same mapping proogram to differnt Communcaiton channel in the Receiver agrement....
coopy the same mapping program in the differnet Interface mapping in simple words make serveal copuies of the interfcace mapping program (which has the mapping you want to send) and then use this in the interface determintain and then in the Reciver agrement....
if the Mapping program is also same then you dnt have to create the different Communiction channels for this....just make th copy of the CC which you have created and use that in the Reciever agrement.
Message was edited by:
Nisar Khan

1 Receiver Agreement, multiple Receiver Determinations

Hi Gurus,
Is this possible?
1 Receiver Agreement, multiple Receiver Determinations
I can't create a new receiver agreement because the object already exists.
I can't see the receiver agreement that was created before in the new receiver determination that i created.

Hi,
yes you can have one receiver agrement for multiple Receiver determinations..
let me explain one example.
Sender System File(BC_FILE) and receiver System SAP ECC.
suppose you have multiple secnerions between File System to SAP ECC,but mutiple scenarions sending data to ECC in the form of ORDERS IDoc, in this case you will crearte N number of receiver determinations but only one receiver agrement.
i hope i got you query correcttly.
Regards,
Raj

Web service scenario - Missing or Invalid Receiver Agreement

Dear,
We are on SAP PI 7.11 SP11 and facing a problem with a synchronous scenario SOAP <-> SAP PI <-> ABAP proxy.
The Service Interfaces contain multiple operations and operation/message mappings are in place.
Also, configuration on the ID side is done.
The WSDL is retrieved from the sender agreement and imported into soapUI.
All seems there and the cache is ok, but still we face the error Missing or Invalid Receiver Agreement in the message monitor.
I already found OSS note 1739173, describing the problem, but that seems to be for asynchronous messages only with QoS EO and EOIO.
Or do we need that anyway?
Any leads what could solve this strange problem?
thanks a lot.
Dimitri

Hi,
Both outbound and inbound service interface have multiple operations.
The configuration:
ESR
Outbound and inbound service interfaces containing 5 operations each.
All synchronous, interface pattern stateless.
Outbound service interface is linked to an external message.
The Inbound service interface is linked to a message type.
For every operation, a operation mapping and message mapping is available.
Integration Directory
seperate configuration objects. No ICO is used.
Sender Agreement
no validation
Software Component Version of Sender Interface is pointing to the SWCV, containing the outbound service interface
sender SOAP communication channel
HTTP
SOAP 1.1
Do not use SOAP envelope enabled
QoS is best effort
Receiver Determination
software component version left blank. So, no operation-specifics mentioned.
type of receiver determination is standard
receiver is the SAP back end system (business system)
Interface Determination
Software Component Version of Sender Interface is pointing to the SWCV, containing the outbound service interface
for each operation, a operation mapping, inbound service interface and namespace is indicated
Receiver Agreement
receiver XI adapter
HTTP 1.0
XI 3.0
HTTP destination to the SAP back end
Transfer hop list enabled
Software Component Version of receiver Interface is pointing to the SWCV, containing the inbound service interface
Please note
the message mapping is a XSLT mapping
tests with single-operation service interfaces are successful.
Kind regards,
Dimitri

Conditional base routing to multiple receiver's for syncronous interface

Hi All,
I have a requirement of sysnchronous interface where i need to send the message to 2 diffrent systems based on the routing condition. Based on routing condition we will determine the receiver to send message and response shloud send back to sender.
Please let me know my requirement is possible using sysnchromous call i.e sending to multiple receiver's based on conditon. Thanks.
Regards,
KK
Message was edited by:
kalpana k

Aamir,
I dont think BPM is required here,XI always use mesasgeID as the reference.
lets say you sent a request then XI generates message ID :11111 (for Ex)
and for the response XI again generate another message ID:22222(for Ex),but referencing to MessageID:11111,it cant be to some other request message ID.(always reference is maintained by XI for Sync calls)
so we dont need to maintain any relationship between request and respone ,explicitly.it is being taken care by XI itself for sync calls.
response1 for a request1 wont go to someothers request2.
I dont know whether you get my point what I was trying to say.
and just using Xpaths in receiver determination would give the solution.but need to have two Receiver agreements.
I might be wrong !
thank you,
regards,
Babu Sri

Receiver Agreement error

Hi friends,
I have few scenarios on jdbc-rfc.. for now i can say 6 similar kind at the receiver.. and the rfc is also same..
Now first interface is sucessfull. for the second one i am trying to create new receiver agreement then it is saying it is already exits,,, now what to do.. for this..
for each and evey scenario i have use the same comunication channel then my first scenario out is going to second one..i have faces this... here i can create onley one receiver agreement. please tell me how can we create many receiver agreement

Create the Interface mapping-Here your target Interfae will have "N number of Message Interfaces" for each N message Types. Use the 1:N Mapping done as before.
Now go ahead with other configuration. In Interface Determination select the RB_SPLIT/Extended option use this Interface Mapping over there. If multiple Receivers are required , then go with conditions.
Here i am giving 2 possible ways based on your requirement
In both of the following cases you need to have 2 separate message mappings and 2 interface mappings
Source1_message----
target1_messages - Message mapping(1)
Source1_message----
target2_message - Message mapping(2)
Source1_interface -
target1_interface - use mapping(1)
Source1_interface -
target2_interface - use mapping(2)
1.If 2 receiver messages will be going to same receiving system
a)In Receiver determination no need to specify any condition to determine receiving systems(bcoz you have only one receiving system)
b)But you need to give condition in interface determination.In this case one interface determination is enough
2.If 2 receiver messages will be going to different receiving systems
a)You need to give condition in receiver determination to determine receiving systems
b)In this case, 2 interface determinations required one for each receiving system without any condition
For example
Sender
Service: Source system1
Interface:Source1_interface
Receiver
Service: Receiver1
Inbound interface interface mapping
Target1_interface Source1_interface_to_ Target1_interface
Same as this do for receiver2
Check the following links:
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
http://help.sap.com/saphelp_nw2004s/helpdata/en/42/f3b31d48fb1bc8e10000000a11466f/frameset.htm
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

Receiver Agreements

Hii,
I Want to Send Messages to Multiple Receivers, I am Multicast BPM. I am not defining any Condition.
In ID, For the same Receiver Business System, I have Defined 3 File Receiver Communication Channels.
In Receiver Determination Also, There will be only one Receiver.
Now How do I define Receiver Agreement for the Respective 3 Communication Channels. When I am trying to define the second Receiver Agreement, It says "Object Already Exists".
Regards,
Varun

Hi Santhosh,
Thanks for the Reply.
1. But Can we define the FTP path in the Command Line. (If so, how should I define)
2. Do I need to Specify the Path In the Receiver Communication Channel(Target Directory)
3. Should I select this Option In sender Comm Channel or receiver Comm Channel Run Operating System Command After Message Processing
4. Also In creating the Batch File, How do I sfecify the FTP path in th File
5. If I select this Option, then Should I define the BPM for Mulple Receivers
Regards,
Varun
Edited by: Varun on Oct 1, 2008 1:00 PM

Dynamic Receiver Agreements

Hi,
I have a situation where I have a message mapping that populates a JDBC insert statement. Basically this is just a message interface that gets sent through to a JDBC receiver adaptor.
Now, there are multiple databases sitting on the WAN. This message interface could be sent through to any of the the multiple databases. So the only difference in the receiver agreement would be the actual communication channel being used (i.e. the communication channel created for each of the different databases).
Now at the time of the message mapping, I know which communication channel to use. Would I be able to change the communication channel being used in the 1 receiver agreement, to which ever communication channel I want?
This would then allow me to have multiple communication channels (1 for each of the databases), but only have 1 receiver agreement.
Thanks,
Miguel

The cardinality of Receiver Comm Channel and Receiver agreement is 1:1
So for every Comm channel you have created for Receiver , You should create as many as Receiver Agreement.
But Dynamic Receiver can be identified by using either Conditional Receiver Determination or Enhanced Receiver Determination.
Enhanced Receiver Determination
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
Enhanced Receiver Determination
/people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
Enhanced Receiver Determination     https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/enhancedReceiverDeterminationinSAP+XI&
Multiple receiver
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
Enhanced Receiver Determination
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
Dynamic Receiver Determination
/people/robin.schroeder/blog/2006/11/15/using-dynamic-receiver-determination-with-sync-interface

Is it possible to attach two receiver agreement in the same Service?

when i configure the receiver determination
there is one receiver service and one inbound interface
but i want to send it out with two different agreements
it seems that i cannot use the two agreement
except i have two service.
Is there some advice to handle this?
Thank you in advance

<i>there is sender service A, and the receiver service B, but i have two receiver agreements
in the receiver determination, i only can choose one receiver agreement
which i want to use the two at the same time </i>
>>
A is sender and B is receiver. Then why do you need 2 receiver agreements ?
there will be one sender agreement for your sender A
there will only be one recv. agreement. ie a combination of sender service + your inbound interface + your receiver service while you create the recv. agreement for your recv. B

No Receiver agreement found for Sender

Hello,
I have a scenario like this : sending an IDoc from R/3 4.6c to R/3 4.7 through XI 3.0.
I am struck up with the follwoing Error in SXMB_MONI
"outbound binding exception: No outbound binding found for , R46, , ENT, urn:sap-com:document:sap:idoc:messages, ORDERS.ORDERS04"
The Complete TRACE is as follows:
<?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">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 SAPR46</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 = XI3</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = SMART01</Trace>
<Trace level="1" type="Timestamp">2004-12-27T20:08:46Z 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 = F0EAB201EEA5F74A814EF22C32394FD0</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 : XBTI0009</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0009</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 = XI3</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = SMART01</Trace>
<Trace level="1" type="Timestamp">2004-12-27T20:08:46Z 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>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_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_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - 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>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <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_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO____0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</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">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 = XI3</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = SMART01</Trace>
<Trace level="1" type="Timestamp">2004-12-27T20:08:46Z 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="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <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_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">No mapping required</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING" />
- 
<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_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="1" type="T">processing the outbound binding</Trace>
<Trace level="1" type="T">search outbound bindings</Trace>
<Trace level="1" type="T">outbound binding exception: No outbound binding found for , R46, , ENT, urn:sap-com:document:sap:idoc:messages, ORDERS.ORDERS04</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
I have made neccesary Configurations for the Receiver agreement in the Configuration Directory...
Anybody could please help me out...
Regards,
Romit Arun Shankar

Hi Frank,
Many Thanks for your reply.The problem got sorted out and the IDoc(ORDERS04) which i send in SAP 4.6c gets into SAP 4.7 AS ORDERS04 but i have a new problem now....
I didnt use any mappings until now...but now i have to have the segment E1EDK14 filled up for Sales organisation, Distribution Channel, Division details as well as the material number. These segments will not be filled up when a PO is sent from the source system.These segments has to be filled only in the XI system...Is it ? or is there any other solution for it....
Now how we can have this segment E1EDK14 which can occur any number of times with constant values for SORG,DV,DC in the mapping process....
Waiting for ur replies....
Bye,
Romit Shankar Arun.
For this

"No receiver agreement found" for BPM ???

Hi everybody
I think this could be an issue in the cache. I have a ccBPM and when I am sending the message who starts the BPM to the Integration Engine I got the following error:
<SAP:Stack>No receiver agreement found for sender -BS_SQL_Database to receiver -IP_ScanningStatus_01,http://xxxx.com/common/scanning.MI_JDBC_Response_Asyn_ABS</SAP:Stack>
IP_ScanningStatus_01 is an integration process and you do not need a receiver agreement ("not required" in receiver determination) to send a message to an integration process. Two weeks ago the process work and the very strange is, that in sxi_cache it shows the 31.07.2006 as last change/activation, but I did an activation yesterday. A full cache refresh did not change anything and the status of the cache is "up to date". We are on SP14 (:-<)
Regards Oliver

Hi Udo
yes, that is exacly my problem.
I deleted the corresponding processes in the repository and in the configuration. I recreated the process in the repository under the same name and after that I tried to import the porces in the configuration under the same name, but now I got the following error:
Unable to transport object Integration Process IP_ScanningStatus_01 | http://xxxx.com/common/scanning (CE_ONESAP_ACETATE_MFG_xx, 1.0 of celanese.com) of type RepBProcess from application REPOSITORY on system REPOSITORY. Detailed information: Attempt to serialize the generic part of object Integration Process IP_ScanningStatus_01 | http://xxx.com/common/scanning failed(serialization problem)
Any Ideas?
How can I delete the old process out of cache?
Regards Oliver

No receiver agreement found.

Hi Experts,
I am doing one scenario i.e idoc to file .
I am getting an error that is "no receiver agreement found" in sxmb_moni, but i did the test configuration in ID which is working fine.
can any one help on this.

Hi,
Check the following.
1. Any cache problems in the ABAP stack and java stack.
2. Check your receiver whether it is case sensistive.
3. Check the receiver determination pipeline step in soap header whether the sap receiver anything filled in or blank. If blank, definitely there is an error in your config.
Since you have tested it in ID, I would assume it would be cache problem.
Regards
Krish

Error in AEX Itegrated Configuration Testing "No receiver agreement found."

Hi,
          I am working on PI 7.3, doing a File to Idoc by using the AEX(Advance Adapter Engine Extended). While doing the configuration testing i am getting the below error "
Problem occurred in receiver agreement for sender -BC_XXXXXXX to receiver -BS_XX5_100,urn:XXXX.com:POC:MasterData:Article:ECC:Sender.SI_OA_POC: No receiver agreement found for , BC_xxxxx, , BS_xx5_100, urn:xxxx.com:POC:MasterData:Article:ECC:Sender, SI_OA_POC."
        I gone through the SDN but not got usefull links. I tryied to recreating whole scenario, Cache refresh, but no luck. Can you pls let me know where is the problem. Do i need to do any additional configuration other than creating RFC in Java stack for AEX?
Thanks & Regards,
Dev

Hi RK,
        Thanks for your reply.
              Yes i have created the Idoc_AAE channel and assigned this channel in my Outbound Processing tab.
What do you mean by java channel in Inbound Processing? My sender is File so i created File channel and assigned in the Inbound processing tab.
@ Raghu,
            I have created the Receiver channel. I no need to create Receiver agreement because i am using the ICO so if i give the Receiver and Inbound interface details that is enough. And one more thing i am doing testing in ID Test confiuration.
Thanks ,
Dev

No Receiver Agreement found - IDOC RCVPRN = Party

Hello,
I have created all the receiver agreements required and they are in the configuration scenario.
I have a receiver determination that is using the IDOC vendor number (RCVPRN) to determine the party for delivering purchase orders and another RD with the same config for delivering po changes.
In tests my POs are sending successfully and my PO Changes are failing even though they use the same party setup/config. In SXMB_MONI I can see that the receiver determination for the POs are creating the correct party:
PO Results:
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Ventura</SAP:Party>
But the PO Changes seem unable to connect the vendor number to the party:
PO Change Results:
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">0000557129</SAP:Party>
In the sample above the party Ventura is set up under the party identifiers as follows:
Agency:
http://sap.com/xi/XI
http://stc.com/pi/SAPR3
Scheme:
XIParty
Vendor
Name:
Ventura
0000557129
How is it that PI 7.10 is getting the same value in RCVPRN and assigning the Party correctly in one case and incorrectly in another?
Any ideas?
Thanks,
Matt

Sometimes you just need to walk a way for a day or two... I rechecked the standard configurations over and over. But I didn't review the Party Extended selection. In the Receiver Determination I chose to use RCVPRN to identify the Party but upon further investigation I realized I was using the wrong scheme and agency on the Party extension.
So my party had the following:
Agency:
http://sap.com/xi/XI
http://stc.com/pi/SAPR3
Scheme:
XIParty
Vendor
Name:
Ventura
0000557129
My Receiver Determination was not using http://stc.com/pi/SAPR3 Vendor 0000557129 to determine the Party it was attempting to use http://sap.com/xi/SI XIParty Ventura. So it was unable to find a matchinig party using the Vendor Numbers.
Thanks for all the help.
Matt

Multiple receiver agreement detection.

Similar Messages

Maybe you are looking for