Receiver agreement fails in Proxy to Mail Scenario ( B2B)

Hi All,
I have a proxy to mail Scenario. It is an B2B scenario. I communicate on the sender side via a Business System and on the receiver via a Business Service.
This is a Proxy to mail scenario. I test via the test configuration tool. The sender agreement, Receiver detemination, Interface detemination runs fine.
The failure occurs in the receiver agreement. It fails saying " NO standard agreement found" .
I did the the following checks
1. Checked whether the Agreement is active
2. Checked the name of the Communication component and Interface. all ran well
What could be the issue. Why can sender agreement fail.
Can anyone please help.
Thanks
Abhishek

Similar Messages

Getting Receiver Agreement issue in IDOC to File scenario

Hi Gurus,
            Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
Error Message:
No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
Error Category : Outbounding
Error ID : CO_TXT_OUTBINDING_NOT_FOUND
My IR design:
Sender:
      Interface : VEND_IDOC_OUT_MI
      Message Type : CREMDM.CREMDM04
Receiver:
      Interface : VEND_FILE_IN_MI
     Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
My ID Config:
1. Sender / Outbound Message: Service Type --> Business System
                                              Service ---> SAPERP
                                             Interface--> VEND_IDOC_OUT_MI
                                             Adapter Type : IDOC
2. Receiver / Inbound Message: Service Type --> Business Service
                                           Service       --> IDOC2FileReceiver
                                           Interface    ---> VEND_FILE_IN_MI
                                           Adapter Type--> File
3. In Sender Agreement : Specified the Sender Communication Channel
                                     VEND_IDOC_OUT_Channel
4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
Can anyone help me identifying what's going wrong. I'm very new to XI and basically this is the first assignment I'm working on.
Regards,
Subhadip

Hi Babu,
           In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
Please find the XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
     <xsd:complexType name="VEND_FILE_DT">
          <xsd:annotation>
               <xsd:appinfo source="http://sap.com/xi/TextID">
               8f584d80456311dccd680018fe79f69b
               </xsd:appinfo>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb0390c11dc843000188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor Code
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb4390c11dc84e800188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor name4
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb5390c11dcbe3400188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor City
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         a8653cb6390c11dc896100188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor PO Box
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         4811db0335fd11dc9e9600188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor House No & Street
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         4811db0435fd11dc98b000188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor Postal Code
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         4811db0535fd11dc870500188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Vendor Country
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7ca8d600403b11dcc9bd00188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Tax Number 1
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7040e611dcce4300188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Telephone number
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7140e611dc8f3900188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         VAT Registration Number
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7240e611dccef700188bd09370
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Account Number of Vendor or Creditor
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         9abaee7340e611dcb3bc00188bd09370
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:minLength value="0" />
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
</xsd:schema>

Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

Hi all,
We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
We are running PI 7.4.
Any help is appreciated.
Thanks,
Pushpa

Hi,
Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
1. Test a fresh message from local SOAP UI tool.
2. Pick 3rd party WSDL file and Import in SOAP UI tool.
3. Put some dummy data for mandatory fields
4. Trigger it msg and ckh if you get successful / response msg.
5. Check if firewall is open and that URL is not blocked.
Hope it helps
Regards,
Azhar

How to configure receiver communication channel in File to mail scenario?

Hi all,
I'm working in FIle-to-Mail Scenario. I did all the required configuration In Integration repository. As per my Scenario whenever a text file stored in Application server of the R/3 system. it should be sent as a attchment with a mail.so i set a sender communication channel with file adapter in sender R/3 system . i dont know which business system should i refer for my receiver communication channel.because my receiver end is a mail server. should i create any third party business system for this one?
can anyone suggest me to define a receiver comm channel in a right manner?
helpful answers will be rewarded.

Hi,
Check these
/people/michal.krawczyk2/blog/2005/11/23/xi-html-e-mails-from-the-receiver-mail-adapter
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
/people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken]
/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure
http://help.sap.com/saphelp_nw04/helpdata/en/3c/b4a6490a08cd41a8c91759c3d2f401/content.htm
Regards
Seshagiri

Two Receiver DB in Synchronous Proxy to JDBC Scenario?

Hey,
Is it possible to develop a synchronous proxy to JDBC Scenario that have two different DBs as Receiver?
The response Datas are insert_count and update_count.
Thank.

Park,
You can't have more than one receivers in Sychronous case. If you designed the scenario , then u will get the error as "TOO_MANY_RECEIVER CASE_BE".
-raj.

Data coming in receiver side by using proxy to jdbc scenario

Hi experts ,
I have scenario Proxy (client proxy) to JDBC (IVR system) Asynchronous method,
I execute se38 its working fine and go SXMB_MONI here also success flag in development server same way I checking PI side also SXMB_MONI everything fine but data not coming IVR side if write select query
In runtime workbench the Communication channel status id green and Message processing completed successfully
My question is when I writing select query like select * from table name ,Why data not coming receiver side ? execute query here IVR side also mention query status is successfully ,but IVR side data not coming, I have access right in receiver side
Please provide valuable inputs.
Thanks
INASH NALLA

Refer the following link for more details:
http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
Also, in the reciever JDBC adapter you dont write a SQL query anywhere but it is the target MT structure and corresponding mapping,which generates the query.
Refer the blog:
http://www.riyaz.net/blog/jdbc-adapter-configuration/technology/ 1200/

Proxy (WithAcknowledgements) to Mail Scenario

Hi,
I am doing Proxy to mail Scenario ..and trying to send the Proxy with Attachments. After executing ClientProxy when i check in PI moni_sxmb.. i got error regarding HTTP...
Can anyone tell me where i have to check regarding this ..
The error in the moni is
- 
- <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="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3 />
<SAP:P4 />
Regards,
Deepthi

check below links.....
HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
HTTP_RESP_STATUS_CODE_NOT_OK - Error in ABAP proxy

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

File to Mail scenario? File not received only namespace

Hi,
I tried to do file to mail scenario. I read blogs and forum questions before posting this.
My problem is that I am sending.dat file in file to mail scenario.
I used XIPAYLOAD and without Mail adapter
When i received mail it contains attachement Untitled.xml and it does not contain my file data it contains only this.
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:Mail xmlns:ns1="http://sap.com/xi/XI/Mail/30" />
I do not know how to create file with payload containing To, from subject, content things. I tried Michal blog and disabled unneccessary fields etc. and when i send email as file but now In RWB it gives error
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: no sender address specified
regards
hussaan

Hi again,
Simple message types and i use ximail30_xsd.txt from sap note as external defination
Message mapping is also simple according to SDN TV.
Adapter: Mail
Transport Protocol: SMTP
Message Protocol:XIPayload
Adapter Engine: Integration Server
smtps://smtp.googlemail.com:465
Authetication Method: Plain
User: complete email address
Mail Attributes:
From: email address
To: email address
Subject: test
Content encoding: base 64
Keep attachement: Option Checked
No other change i did, With this configuration i receive email with untitled.xml attachement which contains only namespace info (no data).
In my other try i changed message mapping and uses to create payload which michal refers by using constants(text to describe TO, from, subject) and text functions(concat) in message mapping fields.
Integration driectory setting for that
Adapter: Mail
Transport Protocol: SMTP
Message Protocol:XIPayload
Adapter Engine: Integration Server
smtps://smtp.googlemail.com:465
Authetication Method: Plain
User: complete email address
Mail Attributes: option checked
Content encoding: base 64
Keep attachement: Option Checked
With this option it gives error in RWB that no sender found
Regards
hussaan

Failed to determine a receiver agreement

Hi All
I am using PI 7.1. My current scenario is from a RFC Sender to a JDBC Receiver. I have configured the scenario on PI. When I execute the SE38 program which calls the RFC I get an error that "Sender Agreement Not Found". When I execute from RWB using the Test Message I get an error that "Failed to determine a receiver agreement". When I test the configuration at Integration Builder, it diagrammatically displays that the entire configuration is fine with the Sender and Receiver Agreement.
I have removed the "*" from the Sender Communication Channel and Sender Agreement. Despite I get the "Sender Agreement Not Found" error when execute from SE38.
Could anyone please help me on this issue? I am not able to move on with this persistent error.
Thank you.

>
John jeyaraj wrote:
> Hi Aashish
>
> I am not using ABAP proxies as Sender. I am using RFC Sender Communication Channel. Also I have created the required RFC Destinations on the application server as Registered Programs. Whenever I fire the RFC through the SE38 program, I am able to trace the error from RWB. This means that the communication with the PI server is established, I suppose.
Yes, Exactly. That means Your communication between Program and SAP PI is establish and they are communicating,
Let us know the error message in SXI_Monitor, so that we can help you further.
Regards
Aashish Sinha

How to create a test scenario for Extended receiver agreement

HI, experts,
I tried to create a test scenario in PI7.1 / Intergration Builder, I already defined 3Operation mapping and 3Message mapping in Enterprise Builder and test good.
1 Operation mapping is reading input, and output in "ReveiverDetermine" structure.
other 2 mappings are real mapping program.
My question is how to create test scenario for it? I know I should create a "Receiver Determine" with "Extended" option, however can anybody point out a good guide with details?
thanks!

Hi,
>>Hence I created 2 MM/OM and one OM/MM (OM3) which uses ReceiverDetermine structure as the target.
You need to create only one OM (add one source interface and two target interface in this) and in that use one MM (add source MT and add the 2 receiver MT in the signature tab of the MM )
>>One bussiness component
One BC for Source and One for target
>>One Receiver Determine (set extended option and select the OM 3 ?)
Yes
>>One sender aggrement
Yes
>>Two or Tree Receiver aggrement
Two Receiver Agreement
Also check this wiki page for step-by-step guiide
https://wiki.sdn.sap.com/wiki/display/SI/StepbyStepguidetoExplainEnhancedReceiver+Determination
Regards
Suraj

First I tried to download Firefox 4 and was refused permission. Then I posted to this forum and received a confirmation link by e-mail, but the link failed.

I downloaded Firefox 4, but when I tried to move it into the Applications folder, I was refused permission. I tried to post this problem to this forum and received a confirmation link by e-mail, but it failed: I got the message "Something is wrong."

If you get an error message that you do not have sufficient permissions to update then easiest is to trash the currently installed version to do a clean install of the new version.
Download a new copy of the Firefox program and save the DMG file to the desktop
* Firefox 4.0.x: http://www.mozilla.com/en-US/firefox/all.html
* Trash the current Firefox application to do a clean (re-)install
* Install the new version that you have downloaded
Your profile data is stored elsewhere in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Firefox Profile Folder], so you won't lose your bookmarks and other personal data.

Problem when creating receiver agreement for File to IDOC scenario

I have done the following :
1. Created two business systems one for the file system and other for the R3 system and also I created two communication channel, one as sender communication channel and one as receiver communication channel.
2. Created the receiver determination
3. Created the interface determination
4. Created the sender agrement
5. Now when I was trying to create the receiver agreement I want to assign the receiver communication channel i have created to the receiver agreement but the F4 help gives me no records and I am thus stuck at this point.
Please suggest me how to proceed forward from here.

Hi ,
<i>5. Now when I was trying to create the receiver agreement I want to assign the receiver communication channel i have created to the receiver agreement but the F4 help gives me no records and I am thus stuck at this point.</i>
Make sure that your created communication channel for reciever is under the respective reciever business system and give the same while creating the reciver agrement.
sekhar

Message not received in Proxy to SOAP scenario

Hi All
I have a proxy to SOAP scenario. It is not working from past few days.
When a message is sent, there is a checkered flag in SXMB_MONI.
In component monitoring of RWB, i see that the status is 'Success' and description is 'Message status set to DLVD'.
But, it is not reaching its destination. Can you tell me where else i have to check, to find out the problem?
Thanks in Advance
Chandra Sekhar

hi, just do it
this kind of error is related with an authentification problem against WS. to check it do it:
1 take the inbound message from Moni, do a test mapping.
2 download XML Spy (altova) and create a new SOAP request.
put the WS URL and select the proper soap action.
3 paste the test mapping result XML and send the soap request.
4 put user and pass.
5 if the interface is async, XML Spy will retrn you an empty response else if the scenario is sync it will return you the proper response.
thanks
Rodrigo

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

Receiver agreement fails in Proxy to Mail Scenario ( B2B)

Similar Messages

Maybe you are looking for