cancel
Showing results for 
Search instead for 
Did you mean: 

Idoc2file error while testing.

Former Member
0 Kudos

Hi,

I have Idoc2file scenario where I did not have any IR objects and just have ID configuration and I've configrued RFC and everthing on both ECC and XI when I send the idoc from ECC (using We19) I can see that's been received by XI but I get this error. I was looking in the sxmb_moni and here is the error that I'm seeing in there. Any help is really appreciated.

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

Thanks,

Joe.P

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hey

Here is the deal with bypass scenario,your sender and receiver namespace and interface names must be identical otherwise the bypass scenario(without IR) wont work.

in your case since you have sender interface and namespace of type IDOC(SAP standard) and the receiver interface and namespace of custom type(File) you might not be able to achieve your scenario without IR.

Thanx

Aamir

Former Member
0 Kudos

Amair,

Thanks for responding to my post. Just want to clarify are you saying that I need have my IR objects to correct this problem.

Thanks,

Joe.P

Former Member
0 Kudos

Yes,the reason is that standard namespace for IDOC is urn:sap-com:document:sap:idoc:messages and message interface name is ORDERS05(depending upon IDOC) etc,since you can't use the above mentioned namespace or interface name for any other custom structure(file in your case).you can't do this without IR

Thanx

Aamir

Former Member
0 Kudos

But here is the problem if I use IR objects the IDOC will be convereted to XML which I don't want to. If we do Idoctunneling will I still have the same problem since I don't have the IR objects.

Thanks,

Joe.P

Former Member
0 Kudos

Hey

In IDOC tunneling IDOC structure is not at all converted to XML.so your sender and receiver system must both understand the IDOC format which means both need to be SAP system(or a system which understands IDOC).

Since you have a receiver file which will not understand IDOC format(coz its not a SAP system) you can't do tunneling

Thanx

aamir

Former Member
0 Kudos

No in my case I have a 3rd party company who can take IDOC files and they can process on their end. So all they wanted is just a file representation of IDOC without XML conversion. It's like dumping the Idoc into a file and then ftp the file to the client.

thanks,

Joe.P

Former Member
0 Kudos

>>So all they wanted is just a file representation of IDOC

Representation of IDOC format is not an actual IDOC format.

Its the same way as creating a Data type which looks exactly like ORDERS05 IDOC(but this is just a rep. of IDOC its not an IDOC)

>>It's like dumping the Idoc into a file and then ftp the file to the client.

In that case you can dump the IDOC on a file server and then do a File to file bypass scenario(not IDOC to file scenario)

/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm

after implemeting this blog do a bypass file to file scenario

Thanx

Aamir

Former Member
0 Kudos

Hi,

check this forum link

Thanks

vIKRANTH

Former Member
0 Kudos

Hi,

It looks like none of these threads are not moved to answered so I presume the problem is not resolved. In my case I did checked the LS and BS are properly configured. I don't see anything wrong with that. I've checked and re imported Metadata using IDX2, but still having the same problem. I do strongly believe this is has nothing to do with my BS or LS since I've been using the same BS and LS for other Scenarios.

Thanks,

Joe.P

Former Member
0 Kudos

Check this...seems they had the same discussion here..

Please reward if helps..

Thanks,

Vijaya.

former_member240483
Contributor
0 Kudos

Check the Business system u defined..and the dummy namespace u using for the interface also.

Former Member
0 Kudos

Hi Rao,

I don't see anything wrong with my business systems and the namespace, since I have other scenarios which are using the same business systems and are in the same namespace. I don't see these problems with those when I ran the test.

Thanks,

Joe.P

Former Member
0 Kudos

Try importing metadata manually using IDX2.

Gaurav Jain