cancel
Showing results for 
Search instead for 
Did you mean: 

Party and Service not found

Former Member
0 Kudos

Hi

I am trying to implement IDOC to File scenario following the below blog.

<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters:///people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

In config I created

Receiver communication channel

Receiver Agreement

Receiver Determination

Interface Determination

as specified in the blog.

Sender agreement is not required as per the blog.

RFC destination

I created an tRFC port

added partner profile

when I try to test it using transaction code we19

Standard outbound processing

I filled the sender port, partner no and partner name

it asks me for Receiver port which I have no idea what to use?

I used the same port as I used for Sender

When I checked in message monitoring using SXMB_MONI i see the red flag with error as

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Message Branch According to Receiver List

-->

- <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">PARTY_SERVICE</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Party and service not defined</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Please let me know if I am missing something or going wrong any where.

Thanks

Pavan

Accepted Solutions (1)

Accepted Solutions (1)

moorthy
Active Contributor
0 Kudos

HI,

Create a RFC destination in SM59 pointing to XI box. Then

Did you configure Partner Profiles in WE20 ? Before this did you do WE21 - port creation.

Receiver Port should be port created in the WE21.

For more-

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c...

Rgds,

Moorthy

Former Member
0 Kudos

Hi Moorthy,

I already created RFC dest in SM59

configured Partner Profile for that specific outbound message type

used the the same port i created in we21

Bipin,

I configured the port maintainance steps using idx1 and idx2 I dont know what do you mean by meta data download. Please do let me know.

Thanks

Pavan

Former Member
0 Kudos

TCode IDX2 is used to download the Metadata of the IDOC type you want to use for the data exchange.

This is done after you have defined the port in IDX1.

Bipin

Former Member
0 Kudos

Hi,

During the testing in we19 where should I mention the receiver service, I was thinking the terms of Party and Service not defined and I never mentioned anywhere which service it should send the IDOC. Please let me know if I am missing something

Thanks

Pavan

moorthy
Active Contributor
0 Kudos

Hi,

check out correct business system is associated and pointing to correct R/3 system. Check the Integration Diretcory>Open Business System>Adapter Specific Identifier and check teh logical system name mentioned. Does this point R/3 system ?

just cross verify with steps given in the document, mentioned in my earlier post.

regd. metadata in IDX2, it is not required always.

Go thru these Error Analysis Steps so that you can get to know-

http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

Rgds,

Moorthy

Former Member
0 Kudos

Hey guys

I did a small mistake in parter profile I made the profile for US not LS. It works great now.

Thanks a lot

Pavan

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Pawan,

Please check if you have done port settings and meta data download of the respective Idoc in IDX1 and IDX2

Bipin