IDoc Adapter throws error

We are trying to send data to SAPR/3 47 IDES using IDoc Adapter.
the data is sent to XI from SQL database thro JDBC adapter and then to R/3 thro IDoc adapter.
All this is in Asynchronous mode and at no point we chose synchronous (IDoc adapter does not suppost Asynchronous process right).
But we are getting the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>B7685EB2-42F1-554B-80CC-6ADFC86C7975</SAP:MessageId>
<SAP:RefToMessageId>35A42550-81F9-11D9-AFC7-00C09F450580</SAP:RefToMessageId>
<SAP:TimeSent>2005-02-18T22:05:33Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>S70_812</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS04</SAP:Interface>
</SAP:Sender>
<?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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_BE_NOT_SUPP</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Only asynchronous processing supported for IDoc adapter outbound processing</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
We are not sure where from this synchronous is being picked?
Please advise.
Thanks,
Bhaskar and Anil

In the Processing Parameters section of the JDBC adapter, make sure you have Exactly Once (Asynchronous) selected.

Similar Messages

Reciever idoc adapter Determination error

Hi,
I have scenario File-XI-R/3.I am using Idoc adapter to send data to R/3.
I am getting Reciever determination error.I have done all the steps according to the below weblog.
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
When I test my steps in configuration with test tool it is succesfull but give me error at runtime.
Below is error description.
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Plz help me out if any one has some idea abt it.
Thanx
Rekha

Hi Rekha,
The End Point Type for your scenario should be an IDoc Adapter with parameters from your RFC destination in SM59.
The most common reason for this error is:
1. An error in configuration of sender adapter/proxy: wrong sender business system or namespace or interface name. Look, all this information you must put manually so be carefull on typos (one wrong or ommited letter and you can spend hours looking what is wrong). Copy (from Repository) and paste procedure is strongly recommended.
2. An error in Directory (Endpoint Configuration). Be careful to specified the correct host and port!!!
Hope this helps.
Regards
Suraj

IDoc Adapter and Error Management

Hi Experts,
I don't understand tha management of business logic error.
My External System communicate with SAP ERP via SAP PI IDOC Adapter (HTTP protocol, asynchronous mode).
SAP ERP sends an IDOC via PI to my system, my system receives IDoc, an error occurs during business operation in my system.
What should I do?
In my scenario there are not message of error or IDOC to communicate a problem.
Thanks,
Marco Genova
Edited by: m.genova on May 21, 2009 6:41 PM

Hi,
For the same wrong rfc destination i've got
in sxmb_moni : <SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with ARS Name or password is incorrect. Please re-enter FM NLS_GET_LANGU_CP_TAB</SAP:P1>
OR
in sm58 : XIAFUSER IDOC_INBOUND_ASYNCHRONOUS ARS 17.02.2006 15:57:33 Name or password is incorrect. Please re-enter
It's so strange ?
Regards,
Vincent

IDOC Serialization(EOIO) using IDOC Adapter throwing Mapping error

Hello SDN Gurus,
The scenario I am working on is IDOC(PAYEXT & EUPEXR) --> XI (ABAP Mapping) --> Flat File (IDOC Structure).
The IDOCS produced in Appl system may be in the following order
PAYEXT
PAYEXT
EUPEXR
PAYEXT
PAYEXT
PAYEXT
EUPEXR
I need them to be processed in the same order into flat file.
The scenario is working good except for the serialization. So I did the following
Created two entries in IDXQUEUE one for each message type with the same Queue name in XI system.
Created a new rule for the queue and an associated function module. Used this rule in partner profile for both the message types. I used the following link to create the above two steps.
/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
The SAP system in based on WAS 6.4.
I can see the queue name & EOIO in the inbound message header.
I am getting a mapping error in ABAP program. If I inactivate the queue(in Appl system SAP ECC), I don't get any error.
Does anybody had this problem earlier? Please advice.
Thanks
Srini Vaidyam

I found an OSS note to resolve my issue. The note number is 1057573.
Whenever the queue is activated, the sender system will not send the <TABNAM> field value in EDI_DC40 structure. This note addresses this problem.
I found out this by comparing the results from SXI_MAPPING_TEST individually for the message that failed after queue is activated and the message that was successful if the queue is inactivated.
Only thing I noticed now is even if you selected the radio button "Trasfer Immediately" in Partner profile of Appl. system, the messages are not sent. They are getting collected. So we need to manually push them out using WE14.
This forum Rocks.
Thanks.
Srini Vaidyam

Email Adapter Throwing Error

Hi,
I'm using a sender email adapter. But its throwing the following error.
error occured: exception caught during processing mail message; java.io.IOException: invalid IMAP status response; not finding * STATUS, but 001I NO The requested item could not be found.
Can somebody let me know why does this happen? I'm using IMAP4, XIPAYLOAD and Plain Authentication mode.
Thanks,
Sandeep

Hi all
Just for your interest : I had same issue and it was due to a incorrect URL in the mail adapter ( I used my mailbox name and didn't specify the IMAP folder INBOX ):
e.g. imap://mailserver/INBOX
worked for me ( the individual mailbox is apparently found via the username/password ) with microsoft exchange as mail server
hope it can still helps anyone,
regards
Dirk

JDBC Adapter throws error for Null Data

Hi All,
I am running a interface Proxy to JDBC. But in case if proxy has no new data, the message which goes to the database is:
 <?xml version="1.0" encoding="utf-8" ?>
- <ns1:MT_Material xmlns:ns1="urn:sce-com:xi:fi:UnitEstimateData">
- <Insert_Material>
- <dbTableName action="INSERT">
<table>SCEI_UE_MATERIALS</table>
</dbTableName>
</Insert_Material>
</ns1:MT_Material>
and I get the error in RWB as Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SCEI_UE_MATERIALS' (structure 'Insert_Material'): java.sql.SQLException: FATAL ERROR document format in structure 'Insert_Material': expected 'access' tag(s) not found.
Is there a way so that the JDBC adapter doesn't throw any error if there is no access node??
Pls advice...
XIer

Xier,
Why it will create multiple Insert_Material nodes? Use like this
Mandatory segment ->Remove context->Collapse Context ---> Exists -
>insert_material.
Try the above and let me know if it doesn't helps!!
raj.

BizTalk : MQSeries adapter throwing error after 30 minutes idle time

We have BizTalk and windows MQSeries on separate servers. As long someone logged on to MQseries server, BizTalk able to communicate with MQSeries server and able to receive and send messages to MQs. If there is no session active on MQSeries server,
after 30 minutes BizTalk strat throwing following error. Once you log back to MQSeries server, it will work 30 more minutes.
Error: The adapter "MQSeries" raised an error message. Details "Retrieving the COM class factory for remote component with CLSID {....} from machine 192.... faied due to the following error : 8000401a 192....
Has any one encountered similar issue?
Thanks,
Chirag

Hi,
This seems to be permission issue. Please refer the similar thread
http://social.msdn.microsoft.com/Forums/en-US/biztalkgeneral/thread/13427a41-edd7-45fc-9d43-69838720d923
http://www.biztalkgurus.com/biztalk_server/biztalk_2006/f/10/p/5085/26750.aspx
Hope it can help you

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

DB adapter throws error while inserting ORABPEL-11616

Hi,
I am using SOA suite 10.1.3.5.
I have configured the BPEL DB adapter to insert into table AP_INVOICES_INTERFACE and i am getting the following error.
I tried inserting record manually to the table and it is getting inserted.
Any help in this regard is highly appreciated.
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="code">
<code>17002
</code>
</part>
-<part name="summary">
<summary>
file:/D:/SOA/Oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_EbizUpdate_1.11_bb3df4d0da2922b72119a0476c70a10b.tmp/UpdateEbizInvoicesInterfaceTable.wsdl [ UpdateEbizInvoicesInterfaceTable_ptt::insert(ApInvoicesInterfaceCollection) ] - WSIF JCA Execute of operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception.
insert failed. Descriptor name: [UpdateEbizInvoicesInterfaceTable.ApInvoicesInterface]. [Caused by: Io exception: Software caused connection abort: socket write error]
; nested exception is:
 ORABPEL-11616
DBWriteInteractionSpec Execute Failed Exception.
insert failed. Descriptor name: [UpdateEbizInvoicesInterfaceTable.ApInvoicesInterface]. [Caused by: Io exception: Software caused connection abort: socket write error]
Caused by Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.5.0) (Build 090715)): oracle.toplink.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Io exception: Software caused connection abort: socket write errorError Code: 17002
Call:INSERT INTO AP_INVOICES_INTERFACE (INVOICE_ID, INVOICE_NUM, INVOICE_DATE, VENDOR_NUM, VENDOR_SITE_CODE, INVOICE_AMOUNT, INVOICE_CURRENCY_CODE, ATTRIBUTE1, ATTRIBUTE2, ATTRIBUTE4, ATTRIBUTE5, ATTRIBUTE6) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
 bind => [4, 1113, 2010-09-27 00:00:00.0, 147, MUMBAI, 1000, USD, 2010-09-27T00:00:00.000+05:30, 1156804, 1000, 1000, 2010-09-27T00:00:00.000+05:30]
Query:InsertObjectQuery(<ApInvoicesInterface 4 />).
</summary>
</part>
-<part name="detail">
<detail>
Internal Exception: java.sql.SQLException: Io exception: Software caused connection abort: socket write errorError Code: 17002
Call:INSERT INTO AP_INVOICES_INTERFACE (INVOICE_ID, INVOICE_NUM, INVOICE_DATE, VENDOR_NUM, VENDOR_SITE_CODE, INVOICE_AMOUNT, INVOICE_CURRENCY_CODE, ATTRIBUTE1, ATTRIBUTE2, ATTRIBUTE4, ATTRIBUTE5, ATTRIBUTE6) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
 bind => [4, 1113, 2010-09-27 00:00:00.0, 147, MUMBAI, 1000, USD, 2010-09-27T00:00:00.000+05:30, 1156804, 1000, 1000, 2010-09-27T00:00:00.000+05:30]
Query:InsertObjectQuery(<ApInvoicesInterface 4 />)
</detail>
</part>
</remoteFault>
With Regards,
Harshwardhan

Having multiple versions of BPEL process accessing single DB conn factory is OK. That doesn't create any issue.
You must use the same version of JDeveloper as the SOA Suite Version you are accessing. Similar to your example you will face issues if you use JDeveloper 10.1.3.1 for SOA Suite 10.1.3.4. You will find lot of issues here in forum realted to different versions of soa suite and Jdeveloper.

WCF-SAP Adapter throwing errors after SAP Upgrade from ECC 5 to ECC6 Release 640 to 700

Hello Everyone,
We were able to communicate(Send and Receive Idoc's) to SAP via WCF-SAP Adapter in BizTalk 2010.
SAP Servers were upgraded to ECC5 to ECC 6 and we started facing below issue communicating on send and receive both.
I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDP01006GRP   IDOCTYP: ORDERS05
Release: 700    CIMTYP: . Ensure that your message xml validates against the operation schema.
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.
Thanks,
Vikingss

I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
For this issue, you can contact Microsoft support directly(http://support.microsoft.com).

MQ6 Drivers for JMS Adapter throwing error

Per note 747601 of SAP, we got the jar files for MQ6.
MQ 6.0 with SAP XI 3.0 JAR files needed
We prepared the .sda file
When we try to deploy it through SDM, we are getting errors:
Summary:
========
There were 1 archives selected.
0 archives successfully loaded.
   Loading of 1 archives failed.
Details:
========
1) Error loading archive
    C:\aii_af_jmsproviderlib.sda
    (server side name is: C:\aii_af_jmsproviderlib.sda)
    com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component
found in the SDA C:\aii_af_jmsproviderlib.sda is either missing or incomplete!
Manifest attributes are missing or have badly formatted value:
attribute keylocation is missing
attribute keyname is missing
attribute keyvendor is missing
attribute keycounter is missing
Please advise.
Thanks,
Bhaskar
Here is how this got resolved:
We added drivers for MQ6 in the sda file.
Then isntalled MQ client on the XI server (I am not sure why we need to do this).
Then in the Communication Channel provided the User ID and PAssword for the MQ Server box (the windows log in information). It took us a while (a couple fo weeks) to find this out.
I am not sure if this is the real solution, but it is working fine for us now.
So thoguht of posting this here.
Thanks,
Bhaskar

not sure about this but i guess Craig is a better person to let you know !!!
Contact - [email protected]

Metadata EDISDEF not maintained - Idoc adapter error

hi,
In our scenario, SenderParty->XI->R/3, we are using custom idoc to post into R/3. The idoc adapter throws an error, Metadata EDISDEF for port SAPXXX, IDoc type ZKAGXXX and CIM type not maintained, but when i use standard idoc, i don't get this error. We even applied oss note 837595 to fix authorization issue, but it didn't help.
Any ideas or suggestions.
Thanks
Pandari

One LAST suggestion. Looking at Note 837595, it doesn't seem to specify a value for authorization group (DICBERCLS). Try authorization group 'SS' (without quotes). So:
Object: S_TABU_DIS
Activity: 03
Auth. Group: SS
I recall now that a customer recently had this issue and (for them), this helped.
Jin

SP14 Multi-mapping - error in receiver idoc adapter

Hi,
I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
When testing the setup 'real life' the message fails. The error message in the monitor says:
- 
- <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>InterfaceCollection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
If trying to send multiple XML records, i get the following error:
- 
- <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="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
Also the Idoc is also being used as Inbound interface - so no mistakes here either.
I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
Best regards,
Daniel

Hi Daniel,
I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only
However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
I hope that helped you a little further - if you find out more I'd be happy to learn about it.
regards,
Peter

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

Error using IDOC adapter

Hi All,
I'am trying to run the following scenario:
FILE --> XI --> IDOC (r/3).
Data is read and mapped towards an internal format. Then a mapping from the internal format to MATMAS_BAPI01 is done.
I disabled EDI_DC40 and did the needed mappings.
When I execute the scenario I get the following error.
<?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_RUNTIME</SAP:Code>
<SAP:P1>MSGGUID CA9DC2E01F1211DA9EED000D56B9D8A6: Control record must start with tag EDI_DC40, not E1BPMATHEAD</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: MSGGUID CA9DC2E01F1211DA9EED000D56B9D8A6: Control record must start with tag EDI_DC40, not E1BPMATHEAD</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I expected that the XI system would automaticly fill in the needed info in EDI_DC40.
Does anyone has an idea what is going wrong?
Kind regards
Message was edited by: Geert Wouters

hi,
most probably your idoc message
has a wrong format
when you import your new idoc to integration repository
does it have EDI_DC40 at the beggining?
BTW
try without disabling the edi_dc40
you cna also have a look at my weblog:
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
Regards,
michal
Message was edited by: Michal Krawczyk

IDoc Adapter throws error

Similar Messages

Maybe you are looking for