cancel
Showing results for 
Search instead for 
Did you mean: 

Xi sending the IDOC to R/3: Error

nisarkhan_n
Active Contributor
0 Kudos

Hi

I am sending the idoc from XI, i am getting following error " <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>".

Kindly let me know have i done anything wrong in configuration in XI and r/3 for posting IDOC.

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

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>

<SAP:P1>MI_In_IDOCDebmas</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to interpret IDoc interface MI_In_IDOCDebmas</SAP:Stack>

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

</SAP:Error>

Accepted Solutions (0)

Answers (3)

Answers (3)

nisarkhan_n
Active Contributor
0 Kudos

Hi Moorty

Thanks for the reply....

Firstly i am not using the external defination for mappings, and in the message interface i am using the IDOC itself, the link which you had given points to the error caused by using the external definitation in the message interface.

I am configuring the Ecc6 and XI i am stcuk in IDOC scenario, i am just running this test to check the connectivity with IDOC's.

and also i am trying to send the idoc from ECC6 to XI, when i trigger the idoc from R/3 the idoc ststus is 03 but idoc is not entering the XI. in SM50 i am getting the error poiniting the trfc port created. but the port is working fine.

Kindly let me know if i am missing anything else.

Former Member
0 Kudos

Hi,

Can you check RFC destination( From R3 -> XI & XI -> R3) in both the systems using SM59 and also check partner profiles and Port.

In SM59,check whether you can able to login by clicking on 'Remotelogon' in both systems.If it is asking for any password,then there is a prblem in your RFC destination .

Regards,

Srinivas

nisarkhan_n
Active Contributor
0 Kudos

Hi Srinivas

My RFC destinations are proper in both R/3 pointing to Xi and viceversa, i am able to perform remote logon.

Partner and port looks fine.

regards

Nisar

Former Member
0 Kudos

> I am configuring the Ecc6 and XI i am stcuk in IDOC

> scenario, i am just running this test to check the

> connectivity with IDOC's.

>

> and also i am trying to send the idoc from ECC6 to

> XI, when i trigger the idoc from R/3 the idoc ststus

> is 03 but idoc is not entering the XI. in SM50 i am

> getting the error poiniting the trfc port created.

> but the port is working fine.

>

> Kindly let me know if i am missing anything else.

I am also dealing with a problem with sending IDocs from ECC 6.0 to XI.

Can you check SM58 on R/3 for an error message?

CHRIS

nisarkhan_n
Active Contributor
0 Kudos

On the Sm50 TC on R/3 it gives me an error pointing the port created on the XI, the port name on XI pointing to R/3 is SAPECC6, but when i check the RFC destinatino on the port i am able to ping to R/3

Former Member
0 Kudos

Hi Khan,

In XI create the port name as SAP<SYSID>

<SYSID> will be three digit. Example : SAPRD1 , where RD1 is the sys id.

Try the same and let us know..

In the IDOC receiver adapter mention the newly created port.

Regards,

Sumit

nisarkhan_n
Active Contributor
0 Kudos

Hi Sumit

I changed the port name to SAPSID and updated in the IDOC receiver but still i am getting same error.

If control record information is not right then idoc should be created with error right?

regards

Nisar

nisarkhan_n
Active Contributor
0 Kudos

Hi All

Thanks for all the replies...

the problem got solved......i had given the PORT name in XI as SAPECC6 i shd have given SAPECC and then i reimported the IODC into XI and Reimported the Metadata of IDOC in IDX2 it worked.

Does the port name must always be SAP<SID>?

regadrs

Nisar

Former Member
0 Kudos

Hi Nisar,

Does the port name must always be SAP<SID>?

Yes.

Regards,

Sumit

Former Member
0 Kudos

Hi Khan,

Did the solution i mentioned helped u ?

If it did you forgot something from your side.

Regards,

Sumit

Former Member
0 Kudos

Hi

Please see the below weblog.

/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii

Sorry, Please refer the blog

/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get

U can do IDOC tunneling in order to achieve the same.

Thanks !!!

moorthy
Active Contributor
0 Kudos

Hi,

did you import correct IDOC type in the Integration Repository?

do u have external definition created for mapping ? Check those all are correct?

Re-import the IDOC into the IntegratioN Repository and activate again..

Also make sure that you are using IDOC itself as an Message Interface during Interface Mapping. No need of creating new Message Interface for the IDOC.

I think you have done mistake in creating the Message Interface for the IDOC. It is not required Use the same IDOC itself

related tips:

Hope this helps,

rgds,

Moorthy

Message was edited by:

Krishna Moorthy P