ERROR: "IDOC_ADAPTER" / "ATTRIBUTE_IDOC_METADATA"

Dear SAP experts,
Good day!
Can i seek your advise regarding the error i am getting in sxmb_moni?
It seems that XI cannot deliver the IDoc to SAP system (in our case, Q40011).
We are in GDA (Acceptance).
The error log is,
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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_IDOC_METADATA</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPQ40, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPQ40, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The user SAPXI0RFC have already been unlocked in Q40011.
But, when i've checked the monitoring now, it is still error.
Kindly advise regarding my issue.
Thank you very much!
Fred

Check the receiver communication channel (Created using IDOC adapter). In this communication channel check if the two mandatory parameters are passed correctly.
Following is further info on those two mandatory parameters.
(i)Check if the RFC destination which is created in XI to connect the target SAP R/3 system is working fine.
(ii)Check if the port that has been created in XI is in the form SAP<SID of R/3 system>. If not, create in the form of SAP<SID of R/3 system>. To this port, specify the above RFC Destination.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

Similar Messages

Receiver IDOC adapter - IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA

Scenario:
EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
I'm getting an error (below) at the Call Adapter stage:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Then I went to IDX2 and deleted the IDOC (in this case, ORDERS05) and tried to create the IDOC again, but I get a pop up window with
I::000
and thus the IDOC can't get recreated.
Need to mention that both PI and ECC enviroments that I'm working in are sandboxes (XS1400 and RS1400) that are copies of our Development environment (XD1400 and RD1400).
Can someone please shed some light?

Hi,
Addition to the above
Check the port name you are mentioned in the receiver idoc adapter it should not be with client no...
it should be only SAPSID..(SID is your system name..)
HTH
Rajesh

IDOC_ADAPTER ATTRIBUTE_IDOC_METADATA

Hi Experts,
We have a scenario cXML to IDoc using BPM, which is working ok in Development environment.
But when it is transported to SIT environment got failed. please see the details below
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>You have no authorization for extensions (activity 03)</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: You have no authorization for extensions (activity 03)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Please suggest on how to resolve the issue.
Thanks in advance.
MK

hi mk
logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
In transaction PFCG, extend the role of the logon user by adding the following authorizations:
Authorization object S_RFC
 Field name RFC_TYPE value FUGR
 Field name RFC_NAME value EDIMEXT, SDTX
 Field name ACTVT value 16
Authorization object S_IDOCDEFT
 Field name ACTVT value 03
 Field name EDI_CIM value ' '
 Field name EDI_DOC value TXTRAW01
 Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
 Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
 Field name ACTVT value 03
 Field name DICBERCLS value
Note: You can activate the display of the technical names of objects and fields in authorizations maintenance by choosing the 'Technical Names' function from the 'Utilities' menu.
Then save and execute the 'Generate' function. Then choose 'Back' to return to role maintenance and switch to the 'Users' tab. Press the 'User comparison' button to execute this function
reward points if helpfull
rgrds
kummari
Edited by: kummari on Jul 8, 2008 7:40 AM

Error in attribute_idoc_metadata

hi all
i am doing the file to idoc scenario. designing and configuration is ok but i am getting the error in attribute_idoc_metadata
Can anyone solve it...
it is very urgent ...
i am getting the error code as
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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_IDOC_METADATA</SAP:Code>
<SAP:P1>Name or password is incorrect. Please re-enter</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Name or password is incorrect. Please re-enter</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
thanks a lot

hi varun
the error log is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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_IDOC_METADATA</SAP:Code>
<SAP:P1>IDoc XML data record: In segment attribute occurred instead of SEGMENT</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: IDoc XML data record: In segment attribute occurred instead of SEGMENT</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error
still i am not able to rectify the problem.

Error:IDOC_ADAPTER" ATTRIBUTE_INV_SND_PARTY : File to IDOC scenario .

Dear XI experts ,
Issue : Error to a new implementated SAP ERP SYSTEM . File to IDOC Scenario
Business Scenario : Exchange Rates from Thomas REuters (XML) - > XI-> SAP 1 , SAP 2 ERP Systems ( 2 diff SAP ERP systems)
SAP 2 is a new system set up for a new plant of our Organization.
The Excahnge rate is gettiong updated by IDOC: EXCHANGERATE.EXCHANGE_RATE01 in two SAP Systems
Each one is configured with diffrent IDOC receiver .
The Error is : for the SAP 2 system . The MEssage gets branched and one message is successfully sent to SAP1 , and turns an error : in SXMB_MONI for SAP2 system
I had been thropugh few blogs have performed the below steps:
-IDOC metadata : IDX2 have configured in XI
-checked the port of EGP , Partner Profile in SAP 2 ERP system
-Checked IDX1 , IDX2 of SAPEGP in XI .
-Refreshed business system .
-Tried to send the xml data from the start point through File Zilla(FTP)
Could somehow help as this is Production issue ans this is affecting the business.
Error from SXMB_MONI:
<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_INV_SND_PARTY</SAP:Code>
<SAP:P1>http://sap.com/xi/XI</SAP:P1>
<SAP:P2>XIParty</SAP:P2>
<SAP:P3>Reuters</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI / XIParty / Reuters to an IDoc partner</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Reuters : is the Sender Party of Exchange Rates. I have seen in blogs to craete agency / schema , but since thsi scenario is 2 seperate SAP ERP systems , my question is do i need to create agency , schema for sender party .
Appreciate your Input
Thank you,
Vara
Edited by: Varalakshmi SB on Oct 26, 2011 12:14 PM
Edited by: Varalakshmi SB on Oct 26, 2011 12:16 PM

agency and scheme are used when your doing B2B scenarios.

SYSTEM ERROR, IDOC_ADAPTER, Unable to convert ALE to logical system

Hi,
I just wanted to check when i am using SXMB_IFR for monitoring then in message monitoring ---> if i check for Integration server as a whole i Find error as SYSTEM ERROR but if i check only for Adapter engine I get all the idocs successful.
So what we have to monitor the whole integration server or adapter engine only

saras,
When you see successful in the Adapter Engine, what it impliesis that the Adapter Engine has picked up the message ( file in your case ) and then passed it to the Integration Engine for processing ( this is where the actual pipeliining steps take place). As far the adapter Engine is concerned the message has been passed to the integration engine and so its job is done.
The error you see in Integration Server is becuase it includes the status of the messge in both the adapter Engine and the Integration Engine. You messages has errored out in the Integration Engine and so the problem!
Just rememebr this terminology --> Integration Server is the runtime of XI which in turn contains the Adapter Engine and the Integration Engine.!!
Regards,
Bhavesh

Problem with extension of idoc in XI

Hello All,
I've extended an Idoc in R/3 with new segment.
That new idoc extension i've mentained in t/code IDX2
Also, i've imported the new extended idoc in XI in IR.
Next i've done the related mapoping for the new segment in IR.
In ID, do i need to change the old idoc name with new extension idoc which i'm using in the Receiver Agreement
After doing all these above modifications..i've receving the below mentioned error message
- <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_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Pls. let me know how i need to proceed further.
Thanks in advance!!!
Regards
Prasad

Hello Prasad,
Go through these discussions....
<IDOC_ADAPTER> ATTRIBUTE_IDOC_METADATA
Re: ERROR: "IDOC_ADAPTER" / "ATTRIBUTE_IDOC_METADATA"
File2IDoc Adapter Error
Hope the above links are very helpful to you..
Thanks,
Satya Kumar

Time display in Alerts

Hi,
i have done Alert configuration and everything is going fine except time. I have used SYST-UZEIT to display time. But its not working. I'm able to display date using SYST-DATUM.
Instead of time its displaying &SYST-YZEIT&
Error: IDOC_ADAPTER.ATTRIBUTE_IDOC_METADATA Occured in Interface which is From XXXXX / XXXXXXXXXX_Outbound_Async_MI on 08.12.2008 at &SYST-UZEIT&
Please give me some suggestions..
Regards,
Sandeep.

Hi
System date and time you can't use in alert categories.look no such type exist.
http://help.sap.com/saphelp_nw04/helpdata/en/d0/d4b54020c6792ae10000000a155106/content.htm

IDOC ADAPTER , ATTRIBUTE_IDOC_METADATA Error

Hi everyone!
XI have sent Idoc to SAP A5P.
But there is an error log,
"IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA
> Metadata EDISDEF for port SAPA5P, IDoc type ORDERS02 and CIM type ZORDERS2 not maintained
Kindly advise what is wrong with our configurations.
Thank you very much!
Fred

hi,
Your error is IDOC metadata related
(probably incorrect entry in IDX1 - or RFC to R3 is ont working)
download your idoc in IDX2 to check it
Also check if you are using the right port in IDX1.
else,
Goto ID and open the relevant Business system.
Goto --->Menu tab "Service" --->Adapter Specific Identifiers.
Check if the proper logical system details have provided.
Refer
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
SAP Network Blog: Troubleshooting File-to-IDOC Scenario in XI.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Thanks
Swarup

Error: EDI: Error while assigning IDoc number

Hi Everybody,
using XI 3.0 on Linux 64 bit SLES9 with Oracle I got some probleme sending messages from mq series to sap:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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_IDOC_METADATA</SAP:Code>
<SAP:P1>EDI: Error while assigning IDoc number</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: EDI: Error while assigning IDoc number</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What is missing here?
Kind regards,
Michael

Hi Jayakrishnan,
thanks a lot for your answer.
SM59 is working finde. In IDX1 I got the the correct RFC destination entered and a double click works fine also.
The other way around R3 -> XI -> mq series is working fine. Here we are trying mq -> XI -> R3 and it stops sending from XI to R/3.
How to check the IDOC type?
Regards,
Michael

File-to-Idoc error (using business sender service)

Hello,
My scenario is Flat file to IDoc. I am using a business service as my sender system. I did put in a logical system name in the business service and I have added the logical system in SALE.
The error I am getting is <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>MSGGUID 526719BA7E874E3906EEF45B43806D5C: Tag CULL_GR_RECORD found instead of tag IDOC BEGIN=</SAP:P1>
This is confusing to me because the CULL_GR_RECORD is the name of my data record of the file that is converted into an idoc within XI.
Can someone please help me with this? I would really appreciate it. I need to solve this tonight.
Thank you.

Hi,
>> I am using a business service as my sender system.
This is fine as ur sender is file.
I suggest deleting the matadata in IDX2 and then rerun the entire interface.
Make sure ur IDoc is imported properly to the IR. If yes, test ur mapping locally once.
Regards,
Divija.

Error: Sender Not in Payload

Dear All,
I m doing FILE_XI_IDOC(CREMAS03) scenario. I am getting the following error in SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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_IDOC_METADATA</SAP:Code>
<SAP:P1>Copy sender from payload: Sender not in payload</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Copy sender from payload: Sender not in payload</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have seen some already posted queries (ATTRIBUTE_IDOC_METADATA : Sender not in payload) regarding this and they suggest to Populate SNDPRN with the valud Sender Partner Name in the mapping and then process the IDOC.
But I am not able to get where we have to update this value. Please guide me regarding this.
Warm Regards,
N.Jain

hi,
1. you can put the sender field in your mapping
open EDI_dc40 semgne of your IDOC (cremas)
and find SNDPRN field
2. you can also have a look at my blog:
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
3. for IDOC-XI scenario you can also
have a look at my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
you can also make disable the edidc40 segment in mapping
and uncheck - use sender from the payload
in idoc receiver adapter and it will be filled with defaults
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

XI Business content for MDM - Syntax error in IDOC adapter

Hi mates,
I'm trying out the Master Data Harmonization scenario for Vendor data with R/3 as the client system. I'm using SAP delivered XI Business content for MDM. The mapping program is generating ADRMAS and CREMAS IDocs but the IDOC adapter reports that there is a syntax error in ADRMAS IDOC. Find below the details.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Generated ADRMAS IDOC is
 <?xml version="1.0" encoding="utf 8" ?>
<ADRMAS02>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1" />
<E1ADRMAS>
<OBJ_TYPE>LFA1</OBJ_TYPE>
<OBJ_ID>0000500140</OBJ_ID>
<CONTEXT>0001</CONTEXT>
<E1BPAD1VL SEGMENT="1">
<FROM_DATE>00010101</FROM_DATE>
<TO_DATE>99991231</TO_DATE>
<NAME>Swift Transportation</NAME>
<COUNTRY>US</COUNTRY>
<COUNTRYISO>US</COUNTRYISO>
<LANGU>E</LANGU>
<LANGU_ISO>EN</LANGU_ISO>
<SORT1>SWIFT TRANSPORTATION</SORT1>
<TIME_ZONE>CST</TIME_ZONE>
<E1BPAD1VL1 SEGMENT="1">
<LANGU_CR>E</LANGU_CR>
<LANGUCRISO>EN</LANGUCRISO>
<ADDR_GROUP>BP</ADDR_GROUP>
</E1BPAD1VL1>
</E1BPAD1VL>
</E1ADRMAS>
</IDOC>
</ADRMAS02>
Strangely, the control record is blank. I looked at the XSLT program, it is coded that way. I do not understand the reason. Is the error pointing to the control record?
Look at the code sample from XSLT mapping program
<xsl:for-each select="IDOC/*/E1ADRMAS">
 <IDOC BEGIN="1">
 
 <EDI_DC40 SEGMENT="1"/>
 <xsl:apply-templates select="."/>
 </IDOC>
</xsl:for-each>
How can an IDOC w/o control record be posted?
Did anyone come across this error? Whats wrong/missing?
I appreciate ur inputs.
thx in adv
praveen

Moorthy,
I tried reloading the IDOC metadata from IDX2. Still I get the same error.
Regd, IDOC w/o control record, can u elaborate on "dynamic value while posting IDOCs". From where, XI message SOAP header with Business System replaced by corresponding logical system names?
Thanks
Praveen

ATTRIBUTE_IDOC_METADEATA Error: File to IDOC Java Mapping

I have done a Java Mapping from File to Idoc and I get the following error in sxmb_moni:
<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_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The Idoc structure that I generate in my mapping makes no fullfil of the IDOC tags.
For example:
<IDOC BEGIN="1">
 <EDI_DC40 SEGMENT="1">
 <TABNAM/>
 <MANDT/>
 <DOCNUM/>
 <DOCREL/>
 <STATUS/>
 <DIRECT/>
 <OUTMOD/>
 <EXPRSS/>
 <TEST/>
 <IDCOTYP/>
 <CIMTYP/>
 <MESTYP/>
 <MESCOD/>
 <MESFCT/>
 <STD/>
 <STDVRS/>
 <STDMES/>
 <SNDPOR/>
 <SNDPRT/>
 <SNDPFC/>
 <SNDPRN/>
 <SNDSAD/>
 <SNDLAD/>
 <RCVPOR/>
 <RCVPRT/>
 <RCVPFC/>
 <RCVPRN/>
 <RCVSAD/>
 <RCVLAD/>
 <CREDAT/>
 <CRETIM/>
 <REFINT/>
 <REFGRP/>
 <REFMES/>
 <ARCKEY/>
 <SERIAL/>
 </EDI_DC40>
Should I complete these values in my mapping program?
Which values should I complete?
Thank You.

Antonio,
you can ignore whole EDIDC Segement make disabled in our mapping still it works . but the problem is not with this is our meta data chekc in IDX2 t/c code of XI box.
 it has some problem the strcuture you generate and R/3 accepts are not same their is mismatch in structure
Regards
Sreeram.G.Reddy
Message was edited by:
 Sreeram Reddy

Error in call of IDOC adapter

Hi!
I am facing with very strange IDOC error in adapter call.
Can some one help me to solve this problem please?
- <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_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thank you very much!
regards
Thom

I hope you have loaded the IDOC Metadata in IDX2?
Please check the SAP Note 940313 the problem C in this Note (Below are content)
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
 Activities in sender system ABC:
 Transaction SM21 contains entries for failed logons.
 Activities in the central XI system:
 Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
 In Transaction SM21, you will find entries relating to authorization problems and more exact details.
 Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
 In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
 The most common errors are:
 - IDoc type or segments not released
 - Segments that no longer exist are listed in the IDoc type
 - Data elements that do not exist in the DDIC are assigned to fields
 in the segment.
 Contact your system administrator and correct these errors in the IDoc type.

ERROR: "IDOC_ADAPTER" / "ATTRIBUTE_IDOC_METADATA"

Similar Messages

Maybe you are looking for