cancel
Showing results for 
Search instead for 
Did you mean: 

ATTRIBUTE_WRONG_INTF

Former Member
0 Kudos

This is my error

<?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>IDOC_REC</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

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

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

</SAP:Error>

i created my logical systems & RFC dest & port no's, every thing is working fine...evn there is no problem with my bussiness systems also....

can any one explain me how to rectify this problem...

please its very urgent......

thanks in advance

j.john wesly

Accepted Solutions (0)

Answers (3)

Answers (3)

aashish_sinha
Active Contributor
0 Kudos

Hi Jhon,

Try this link.

/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change

also there is trick like give the name of the target message interface as the Original Idoc. dont use your own interface, Then your problem will be solved.

Regards

Aashish Sinha

PS : reward points if helpful

aashish_sinha
Active Contributor
0 Kudos

Agreed.. that is what i suggested earlier that "give the name of the target message interface as the Original Idoc. dont use your own interface"

Hope this solve your problem

Aashish

Former Member
0 Kudos

hi ...

i did wt u said........

so no problem in XI...

one more doubt...while creating partner...we hv to mention the user which we are using in RF dest..?

while testing IDOC in we19 iam not able to send an idoc..

i ceated...

SM59 to XI its working fine..

WE21 for RFC dest..

WE20 for Sender Logical system...and for receiver Logical system..

in XI

SM59 for R3

IDX1 for RFC dest..

IDX2 for metadata

former_member208856
Active Contributor
0 Kudos

At xi create entry in IDX1 and for IDOC matadata (Cremas) in IDX2.

check your partner profiles at R/3 system. the entry of idoc should be available there.

Reward points, if helpful,

Sandeep Kaushik

Former Member
0 Kudos

HI ...

+R3**+

BD54 for 2 Logical systems SENDER & Receiver

SM59 for connection to XI

WE20 for port

WE21 for sender IDOC

*XI*

IDX1 for port

IDX2 for metadata..

SM59 for conection to R3

remaining every thin in IR and ID are correct...

prateek
Active Contributor
0 Kudos

Make sure that u have not created any message interface for Idoc. In interface mapping and in ID, while selecting the idoc interface, u have to select the Idoc name (e.g. CREMAS.CREAMS03) for the "imported objects" list and not any other message interface

Regards,

Prateek

Former Member
0 Kudos

hi....

here, my scenario is Idoc to file...

so i created a sender interface as u told with Cremas.cremas04 and all the IR part and ID part are perfect , because if there is a mistake in IR we cant proceed in ID.

my question is this error is occuring in the CALL ADAPTER step in Pipe line....

what is the resaon.....

thx for ur valuable reply..

any ans..with my que..

john wesly

prateek
Active Contributor
0 Kudos

so i created a sender interface as u told with Cremas.cremas04

U dont have to create a Message Interface for idoc. In Directly use the name Cremas.cremas04 from the imported objects list

Regards,

Prateek

Former Member
0 Kudos

hi..

i did that but whn i testing IDoc with we19

iam gting an error with ststus 37..Entry in outbound table not found

i added CREMAS in outbound parametrs...

can u help wtz da mistake is..

john