IDOC_ERROR_ILLEGAL_TYPE

Hello,
I am trying to send an IDOC INVOIC to an SAP system. Here I get error Application error: com.sap.mw.idoc.IDoc$Exception: (3) IDOC_ERROR_ILLEGAL_TYPE:
Segment type "E1EDKA1" is not a valid child segment type. But when I print out Meta Data about the root segment, it prints segment "E1EDKA1" and all fields of this segments like PARVW,PARTN,LIFNR,NAME1,NAME2,NAME3,NAME4 etc. So Why I am getting this application error?
If somebody could shed some light on this I will appreciate that.
Thanks,
Ranjith Pillai.

This is not a very java related question, but rather specific to a function module in R/3.  You might have better luck posting this in a different forum.  The ABAP programming forum might be the best place to start.
-Regards,
Steve

Similar Messages

  • IDOC_ERROR_ILLEGAL_TYPE in business connector 4.7

    Hi,
    IDOCS are being sent from sap system to Business connector and conversion to xml is done through bc services
    I am getting the following exceptions in business connector production server.I need to know the rootcauses of these exceptions and how they can be resolved
    2005-11-25 08:15:40 GMT com.sap.mw.idoc.IDoc$Exception: (3) IDOC_ERROR_ILLEGAL_TYPE: The document does not correspond to the associated repository.
         at com.sap.mw.idoc.jco.JCoIDoc$JCoDocumentList.add(JCoIDoc.java:3095)
         at com.wm.pkg.sap.rfc.SAPSession.sendIDoc(SAPSession.java:671)
         at pub.sap.client.sendIDoc(client.java:356)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
         at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
         at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
         at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
         at com.wm.lang.flow.FlowState.step(FlowState.java:430)
         at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
         at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
         at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
         at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
         at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
         at java.lang.Thread.run(Unknown Source)
    Regards,
    priya.

    I am with the same problem and it is apparently caused because the xml file is without encoding,

  • Business connector exceptions(java)

    Hi,
    I am getting java exceptions from Business connector server continously.Need to know the root cause of these errors and how they can be eliminated.
    The error i am getting is as below:
    com.sap.mw.jco.JCO$Exception: (108) RFC_ERROR_INTERNAL: internal error
               at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeCreateTID(Native Method)
               at com.sap.mw.jco.rfc.MiddlewareRFC$Client.createTID(MiddlewareRFC.java:1246)
               at com.sap.mw.jco.JCO$Client.createTID(JCO.java:3903)
               at com.wm.pkg.sap.rfc.SAPSession.createTID(SAPSession.java:768)
               at pub.sap.client.createTID(client.java:373)
               at java.lang.reflect.Method.invoke(Native Method)
               at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
               at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
               at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
               at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
               at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
               at com.wm.lang.flow.FlowState.step(FlowState.java:430)
               at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
               at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
               at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
               at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
               at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
               at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
               at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
               at java.lang.Thread.run(Unknown Source)
    Any help on this regard would be highly appreciated.
    Thanks in advance.
    Regards,
    Priya.

    Hi Astrid,
    thanks for ur reply.
    i will chk that out and by the way the below is the full error log am getting and also there is some data loss in inbound messages to sap due to this error and IDOC exception.can u pls help on this issue
    Error being reported is:
    com.sap.mw.jco.JCO$Exception: (108) RFC_ERROR_INTERNAL: internal error
    at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeCreateTID(Native Method)
    at com.sap.mw.jco.rfc.MiddlewareRFC$Client.createTID(MiddlewareRFC.java:1246)
    at com.sap.mw.jco.JCO$Client.createTID(JCO.java:3903)
    at com.wm.pkg.sap.rfc.SAPSession.createTID(SAPSession.java:768)
    at pub.sap.client.createTID(client.java:373)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
    at com.wm.lang.flow.FlowState.step(FlowState.java:430)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
    at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
    at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
    at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
    at java.lang.Thread.run(Unknown Source)
    and
    com.sap.mw.idoc.IDoc$Exception: (3) IDOC_ERROR_ILLEGAL_TYPE: The document does not correspond to the associated repository.
    at com.sap.mw.idoc.jco.JCoIDoc$JCoDocumentList.add(JCoIDoc.java:3095)
    at com.wm.pkg.sap.rfc.SAPSession.sendIDoc(SAPSession.java:671)
    at pub.sap.client.sendIDoc(client.java:356)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
    at com.wm.lang.flow.FlowState.step(FlowState.java:430)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
    at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
    at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
    at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
    at java.lang.Thread.run(Unknown Source)
    thanks in advance
    regards,
    priya.

  • Business connector idoc error

    hi,
    i am getting these errors continously in bc server after restart of sap due to which there is data loss in the inbound messages to sap.outbound messages were processed every time sap was started.the errors are as follows:
    com.sap.mw.idoc.IDoc$Exception: (3) IDOC_ERROR_ILLEGAL_TYPE: The document does not correspond to the associated repository.
    at com.sap.mw.idoc.jco.JCoIDoc$JCoDocumentList.add(JCoIDoc.java:3095)
    at com.wm.pkg.sap.rfc.SAPSession.sendIDoc(SAPSession.java:671)
    at pub.sap.client.sendIDoc(client.java:356)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
    at com.wm.lang.flow.FlowState.step(FlowState.java:430)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
    at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
    at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
    at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
    at java.lang.Thread.run(Unknown Source)
    and am also getting rfc error as follows:
    com.sap.mw.jco.JCO$Exception: (108) RFC_ERROR_INTERNAL: internal error
    at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeCreateTID(Native Method)
    at com.sap.mw.jco.rfc.MiddlewareRFC$Client.createTID(MiddlewareRFC.java:1246)
    at com.sap.mw.jco.JCO$Client.createTID(JCO.java:3903)
    at com.wm.pkg.sap.rfc.SAPSession.createTID(SAPSession.java:768)
    at pub.sap.client.createTID(client.java:373)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
    at com.wm.lang.flow.FlowState.step(FlowState.java:430)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
    at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
    at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
    at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
    at java.lang.Thread.run(Unknown Source) .
    please let me know rootcause of these errors and wat can be done to resolve it soon
    thanks in advance,
    regards,
    priya.

    Not sure if it will help, but have you tried to flush the structure cache? I think you will have problems if the structure of the IDoc has changed in the R/3 system and the Business Connector is not aware of the change.
    BR,
    Tony.

  • IDOCFlatToXmlConvertor does not recognize Z segements in a Custom Idoc

    Hi,
    Does the module IDOCFlatToXmlConvertor work only with standard idocs. It is not identifying any of the Z segements in a custom idoc. It just gives out illegal idoc type exception for the first Z filed it encounters in the idoc flat file.
    However the other module IDOCXmlToFlatConvertor does recognize the Z segments.
    Is there any SAP note that says that the IDOCFlatToXmlConvertor does not work with Z segments in a custom idoc.
    I have tried editing the control record and sent the valid data in the file to the sender adapter. Kindly let me know your inputs.
    The following error is reported in the adapter audit log:
    Error: com.sap.conn.idoc.IDocIllegalTypeException: (4) IDOC_ERROR_ILLEGAL_TYPE: Segment type "Z1XXXXX" is not a valid child segment type. DOCUMENT: type=CREMAS05, type extension=ZXXXX_CREMAS05, number=0000000000000000; SEGMENT: type=E1LFA1M, definition=E2LFA1M002

    Please check if the IDOC flat file has the IDOC extension details in it. And also check if you have maintained the extension in WE82 tcode of your TargetDestination.
    ~Vaas

Maybe you are looking for

  • Error when compiling xf86-video-ati

    Hello I need to compile this pkbuild xf86-video-ati-6.14.3.tar.bz2 but always gives me the same errors, I tried with gcc4.6 and gcc4.3, but no way always gives the same error, use arch64. If compiled in arch32 works. I tested with other versions xf86

  • 3GS doesn't work correctly with Bluetooth headset?

    Why won't my husband's 3GS work correctly with Bluetooth headset? I have a 4S, and I bought a Plantronics 903  Bluetooth headset, and it plays music great out of headset, but when I tried to do that with my husband's 3GS, only one earpiece plays?

  • Impact of creating org level for PERSA

    Hi, I am currently on a HCM project, and have been requested to make personnel area an org level.  The security currently is working by Personnel area, with their org structure using location on personnel area, and subarea for region.  Because we are

  • Error when running adpatch

    Hi, I am doing upgradation from 11i to 12.1.1. Database is upgraded to 11.1.0.7. Now when applying a patch on application side. I am getting error as below: AD Administration is verifying your username/password. The status of various features in this

  • Time Machine deletes entire previous backup and then back it up from zero!

    my configuration : Time Machine : USB external HD 500G Backing up : 1. internal 160G (90G used) 2. USB external HD 500G (290G used) the problem is, every time I hook up the TM, it backup the internal HD smoothly but deletes its entire previous backup