Dynamic MailAdapter Receiver Agreement using S/Mime

Hi,
I need some help at an specific problem with the SAP XI Mail Adapter.
First a little scenario description:
In our business there are 10 Email addresses and we have 250 businesspartners.
We want to send Emails in a secure way (S/Mime), but we wouldnt configure hundreds of Receiver agreements to specify the exact Certificates which must be used to send an signed and encrypted Mail form A to B.
See
http://s5.directupload.net/file/d/1336/xgadwfu5_jpg.htm
Note:
Schlüsselspeicher = Keystore
Schlüsselspeichereintrag = Certificate-Alias
Signierte Mail-Zertifikate hinzufügen = Add Certifiacate to Mail.
Verschlüsselungsalgorithmus = encryption Algorithm
And now my Question :
Is there any possibility to dynamically set the Configuration settings marked in the picture with a red arrow ?

Any Ideas like an own Adapter, Adapter Modulte, Dynamic Configuration ?

Similar Messages

Problem in creating Receiver Agreement using Integration Directory API

Hello Experts,
We are developing a scenario where we are creating "REceiver Agreement" through Integration Directory API.
This requires certain parameters like Sender component, Interface, Communication Channel & Namespace to be set in the code.The required Communication Channel & Components already exist in Integration Directory .
Our concern is that we are not able to retreive this Communication Channel's ID through the code in order to set it as a parameter for Receiver Agreement generation.
Can anybody pls advice??
Thanks in advance,
Suraj.

Hi Stefan,
We tried using query on communication channel, but could not do it as we could not get a method which accepts name of communication channel as parameter.
We used "CommunicationChannelQueryIn" related methods in the API.
But still could not retreive the Communication Channel ID of an existing Communication Channel.
Please help.

HEADER MAPPING in RECEIVER AGREEMENT use.?

Hi folks,
Can anyone explain me about the HEADER MAPPING in RECEIVER AGREEMENT. In which cases we go for this header mapping.
Give me an example if possible or any links regarding this.
Thanks in advance
Srinivas Reddy.

Dear Srinivas,
Go through the following link and you may get some idea on this.
http://help.sap.com/saphelp_nw70/helpdata/en/b2/1f17419b24f06fe10000000a1550b0/content.htm
Regards,
JP.

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.

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

Dynamic receiver agreement

Hello,
is it possible to set the receiver party in receiver agreement dynamically?
I have about 30-40 receiver agreements with same data except receiver party.
Receiver determinations can be set through extended mapping. Is this also
possible with agreements? The necessary information are contained in the
payload.
thanks
chris

Hey,
like I said, I have 30-40 receiver agreements.
These look like this:
Sender:
Party: -
Service:*
Receiver:
Party: XYParty
Service: Test_Service
Interface: MI_Test_If
Communication Channel: CC_REC_XI
All these information are exactly the same except the receiver Party (here XYParty).
I would like to replace these 30-40 agreements with only one, but I couldn't
set Party to * (of course).
Can this be set dynamically with information from payload?
thanks

When we will use HEADER MAPPINGS in RECEIVER AGREEMENTS?

Hi,
HEADER MAPPINGS appeared when we create RECEIVER AGREEMENTS,So when we will use this option.

Hi Ramana,
The header mapping is made available in the receiver agreement. It is required in the IDoc adapter, for example, because the IDoc adapter does not know any communication parties.
chk this link
http://help.sap.com/saphelp_nw04/helpdata/en/b2/1f17419b24f06fe10000000a1550b0/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Regrads
Sampath

Dynamically change Receiver Business system in message mapping

Dear all,
I would like to change the receiver business system in the message mapping that is used in the interface determination. I do understand there is an enhanced receiver determination where I can use a mapping but that is not what I am looking for.
I think this should be possible if we can change the appropriate value in the SOAP(message) header.
Possible candidates I can think of by looking at the SOAP header in SXMB_MONI are
1. SOAP:Header- SAP:Main- SAP:Receiver- SAP:Service
2. SOAP:Header- SAP:OutboundBinding - SAP:OutboundBindingEntry - SAP:ToServiceName
Q1. Which one of the above is relevant while identifying the receiver agreement ?
Q2. What is the best way to access them from the mapping(preferably from a UDF) ?
Thanks in advance.
Cheers
danus
PS: I have tried to set "http://sap.com/xi/XI/System","ReceiverService" in Dynamic config & ReceiverService, BusinessSystemReceiver and ReceiverSystem in the Containers Transformation Parameters, but didn't get the expected result.

Chidambaram,
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
Go through the following link:
[Receiver Determination enhancement|http://www.****************/Tutorials/XI/RecvDetermination/Enhancement.htm]
Hope your problem gets resolved.
Regards,
Kiran Bobbala
Edited by: kiran Bobbala on May 7, 2008 5:47 PM

Header Mapping in Receiver agreement.?

Hi All,
When we do B2B scenarios using AS2 adapters.
1. Is it mandatory to use Header Mapping in Receiver agreement.?
2. If yes, is it enough if we provide Party Names? or we need to provide Business system or Business service names as well?
3. What is the purpose of this Header Mapping?
Kindly share your answers.
Regards
Deepthi.
Edited by: deepthi reddy on Jan 31, 2008 6:49 AM

Hi Deepthi,
1) Is it mandatory to use Header Mapping in Receiver agreement?
https://www.sdn.sap.com/irj/sdn/forums
2)What is the purpose of this Header Mapping?
The header mapping is important when configuring cross- company processes in which the business partners want to replace the names of their internal business systems with neutral representatives (party, business service).
Example
if you are doing a file to IDoc scenario, now while mapping the data to IDoc in mapping if you map the IDoc segment called EDI_DC40 with all required data then you have to user the Header mapping in the agreement so that whatever data you have mapped will be picked from payload. And if you do not use this header mapping then then XI will take care of it.
You can do the following in the header mapping:
● Specify fixed values
● Define that the conversion of the field values is to be determined dynamically from the message payload
To specify the header mapping for an address field, select the check box for the field name (for example, sender service) and choose Display List of Permitted Values (This graphic is explained in the accompanying text).
There are different editors for specifying the party and service:
● Use the party editor to specify a party
● Use the service editor to specify a service
Caution
Header mappings are only supported by the following receiver adapters at runtime:
IDoc Adapter
Plain HTTP adapter
RNIF Adapter 2.0
RNIF Adapter 1.1
CIDX Adapter
3)If yes, is it enough if we provide Party Names? or we need to provide Business system or Business service names as well?
http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/frameset.htm
Regards
Azeez khan.

Receiver agreement

Hi all,
what is the use of HEADER MAPPING in receiver agreement>?

hi keerthi,
Header mapping
In the header mapping you can map the values of the following key fields of the receiver agreement to other values: sender and receiver party, sender and receiver service. The address fields (sender, receiver) in the message header are then transformed correspondingly during outbound processing.
The header mapping is important when configuring cross-company processes in which the business partners want to replace the names of their internal business systems with neutral representatives (party, business service).
Example
If you want to replace the internal name of a sender business system in the outbound message with a neutral name of a party and service, specify the fields for Sender Party and Sender Service in the header mapping.
You can do the following in the header mapping:
●      Specify fixed values
●      Define that the conversion of the field values is to be determined dynamically from the message payload
To specify the header mapping for an address field, select the check box for the field name (for example, sender service) and choose Display List of Permitted Values (This graphic is explained in the accompanying text).
There are different editors for specifying the party and service:
●      Use the party editor to specify a party
●      Use the service editor to specify a service
Caution
Header mappings are only supported by the following receiver adapters at runtime:
-          IDoc Adapter
-          Plain HTTP adapter
-          RNIF Adapter 2.0
-          RNIF Adapter 1.1
-          CIDX Adapter
pls refer following link also
http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/content.htm
Regards,
Mandeep Virk
Reward if helpful

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

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

Error in BPM (No receiver agreement found from sender to bpm)

Hi all
In a simple bpm scenario, I am getting a error that No receiver agreement found for sender service to bpm integration process.
What might be the reason?

your configuration should like this.
say u are doing File to File using BPM
File to BPM
then BPM to File.
so u need to create RD where sender is fileservice and receiver is BPM.
second u hav to create another RD where BPM is sender and Fileserviceis receiver.
So there should be
one Sender Ag
two RD
two ID
one RA.
Thanks
Farooq.

Dynamic MailAdapter Receiver Agreement using S/Mime

Similar Messages

Maybe you are looking for