IDOC_ERROR_METADATA_UNAVAILABLE

Hi
I have an idoc from ecc system to PI which then sends to another system using idoc adapter which in turn refers to RFC destination in xi.
The interface was working fine , but all of a sudden has the error IDOC_ERROR_METADATA_UNAVAILABLE.
Is this due to cache or any user authorization as this is not new interface and pretty old interface which was working fine.
I tried reimporting the metadata, checked st22, no luck.
Regards
Sam

HI Sam,
Please refer the following link:
Error IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "null" with extension xxx is unavailable
IDOC Outbound processing using SAP BC
Sending IDoc from SAP ECC6 to SAP BC: IDOC_ERROR_METADATA_UNAVAILABLE
http://wiki.scn.sap.com/wiki/display/TechTSG/(PI)+com.sap.conn.idoc.IDocMetaDataUnavailableException+error+when+using+the+IDOCFlatToXmlConvertor+module
They are similar to your error.
Hope it helps.
THanks & Regards,
Tejas Bisen

Similar Messages

  • Error:  IDOC_ERROR_METADATA_UNAVAILABLE

    Hi Everybody,
    I need experts advice for receiving  custom IDOCS from ECC4.6 to PI 7.4 single stack Java.
    Issue: we have one scenario, where my sender system is ECC 4.6 is sending custom IDOC to PI 7.4 but unfortunately PI is unable to receive the same and it got stuck in sender ECC (It is an legacy UNICODE system) SM58 with error "IDOC_ERROR_METADATA_UNAVAILABLE". where as PI able to receive standard IDOC from the same system.
    Even when we checked in NWA logs  & errors showing the same  error like " IDOC_ERROR_METADATA_UNAVAILABLE".
    We checked have reimported the meta data and refreshed the cache even though getting the same error and also we have implemented notes 1767710 ,1473183 ,1529038 & 1405466 but there is no use.
    Am very much thankful to every one who can contribute to resolve the same.
    Regards,
    Chandu :-)

    Hi,
    If issue not solved. Try
    1. get IDO Cnumber from message failed in SM58. then delete entry in sm58 and try to resend IDOC from we19. (if IDOC status is Green)
    2. Some time this issue may occur in consistent SLD entries. like
    the Business system may not have the software component related to your IDOC configuration.
    So check the sender tab of business system in ID. will it has your IDOC is in outbound interafces list.
    if not check SLD --> Busienss system-->installed software
    Reagrds,
    Prasanth

  • Sending IDoc from SAP ECC6 to SAP BC: IDOC_ERROR_METADATA_UNAVAILABLE

    Hello,
    I am posting an IDoc (COSMAS01) from SAP Backend to SAP BC 4.8.
    I am getting this Exception:
    2010-04-01 12:17:08 CEST com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "??????????????????????????? ?" with extension "  COSSAPRGL RGI_0          ???" is unavailable.
         at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:126)
         at com.sap.conn.idoc.jco.rt.JCoIDocDocument.<init>(JCoIDocDocument.java:92)
         at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
         at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
         at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
         at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
         at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
         at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
         at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run(TimeWrappingProvider.java:40)
         at com.wm.pkg.sap.rfc.ListenerThread.run(ListenerThread.java:70)
    2010-04-01 12:17:09 CEST com.sap.conn.jco.JCoException: (104) RFC_ERROR_SYSTEM_FAILURE: IDocException occurred (raised by system AS-RGAG-01|a_rfc)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:639)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcS
    I have manually loaded the IDoc definition in the DDIC cache of the SAP BC, but this was of no help.
    For me it looks like an encoding problem as the the JCO adapter seems not to be able to even identify the basic IDoc type, or what else can this mean?:
    The meta data for the IDoc type "??????????????????????????? ?" with extension "  COSSAPRGL RGI_0          ???" is unavailable.
    It is a simpe COSMAS01 IDoc with no extension, btw I tryed other IDoc types as well but I am allways getting this weired message.
    Any ideas?
    Thanks
    Matthias

    Hello Rajesh,
    as far as I know, I do not have to do this bevorehand.
    Normally, the SAP BC is creating a routing rule on the first reicipt of an unknown message (IDoc) .
    But in order to do so, it needs to interpret sender | receiver | message type , on which it in my case seems to fail.
    Thanks Matthias

  • IDOC error:IDOC_ERROR_METADATA_UNAVAILABLE

    I had followed the "How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener" atricle to setup IDOC Listenser completely.
    When SAP ERP sent MATMAS message IDOC to SAP MII,I found error message in Netweaver as below:
    com.sap.conn.idoc.IDocRuntimeException: IDocException occurred?
    at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:111)?
    at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6643)?
    at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6605)?
    at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6763)?
    at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:959)?
    at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:937)?
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)?
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2630)?
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2307)?
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2139)?
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2021)?
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:1912)?
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)?
    at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:321)?
    at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)?
    at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7233)?
    at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)?
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)?
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)?
    Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "" is unavailable.?
    at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:132)?
    at com.sap.conn.idoc.jco.JCoIDocDocument.<init>(JCoIDocDocument.java:74)?
    at com.sap.conn.idoc.jco.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:117)?
    at com.sap.conn.idoc.jco.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)?
    at com.sap.mw.jco.jra.idoc.JRAIDocRuntime.createIDocDocumentList(JRAIDocRuntime.java:104)?
    at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:69
    Please give me any solution to resolve this problem.
    Thanks

    Hello Vincent,
    Just make sure that you have hit the update button in MII Message Listeners after configuring IDOC listener in NWA.
    Any changes made to listener in nwa will not get reflected unless you do update in message listeners.
    Hope this helps!!
    Regards,
    Adarsh

  • JAVA CODE  NOT CREATING IDOC

    Hi all
    I m facing problem to upload data through idoc.the scenario is like we receive electric meter reading in flat file format. And to upload that data JAVA code is written which will create an IDOC FILE this authorization is only give to 2-3 person in organization and to basis guy also as user changed it’s password in SAP and in JAVA the java code is not going to create the IDOC file and data is not going to upload. after changing user password in sap system ,user not able to upload the data.
    ISU_MR_UPLOAD01 is the idoc file generated. So is there any authorization issue, password issue how to see and view IDOC IN SAP, can any one help me out into this.
    The error with java throws is as;
    1ST ERROR IN TRACE FILE
    ERROR file opened at 20061109 133610 India Standard, SAP-REL 640,0,59 RFC-VER 3  MT-SL
    T:2736 ======> User TR has no RFC authorization for function group SYST .
    T:2736 <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
    2ND ERROR ON COMMAND PROMT
    C:\j2sdk1.4.2_07>cd bin
    C:\j2sdk1.4.2_07\bin>java sandsupload
    Creating IDoc...Exception in thread "main" com.sap.mw.idoc.IDoc$Exception: (2) I
    DOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ISU_MR_UPLOAD01
    " is unavailable.
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:233)
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:187)
            at com.sap.mw.idoc.jco.JCoIDoc.createDocument(JCoIDoc.java:10521)
            at sandsupload.main(sandsupload.java:35)
    the part of java code
    try {
                //create a JCo client pool
                JCO.addClientPool( "MyPool",    //pool name
                                   3,           //maximum pool connections
                                   "333",       //SAP client
                                   " TR",    //user ID
                                   " XYZ",  //password
                                   "EN",        //language
                                   " 1.1.1.1   ", //app server host name
                                   "00" );   //system number
                //create an IDoc repository
                IDoc.Repository idocRep = JCoIDoc.createRepository("MyIDocRepository", "MyPool");
                //create a new and empty MATMAS02 document
                System.out.print("Creating IDoc...");
         Line where it shows error
                IDoc.Document doc = JCoIDoc.createDocument(idocRep, "ISU_MR_UPLOAD01");
                //get the root segment from the document
                //The root segment does not contain any fields or data. It is only
                //used as the standard parent segment and won't be transmitted when
                //the document is sent to an SAP system.
                IDoc.Segment segment = doc.getRootSegment();
                //create and add a new and empty child segment of type E1MARAM
                //and fill the segment data

    Hi Gaurav,
    Same exception on the same line has been reported and marked as solved here :
    IDOC_ERROR_METADATA_UNAVAILABLE:
    Btw, I think this forum is not visited often by JCO and ABAP connectivity experts, so maybe you could get a faster response to your problems while posting in "Java Programming" or maybe in some forum under the category ABAP Development.
    HTH
    Peter

  • Idoc flatfile to IDOC xml issue with new PI7.11 module SAP_XI_IDOC/IDOCFlat

    Hi,
    I am trying to develop a scenario as mentioned in the blog using the new module available in PI7.1,but I am getting this error
    "Error: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ORDERS05" is unavailable."
    I have made every configuration correct and IDOC meta data available in both SAP R3 and PI,but it is still complaning about the meta data does not exist.
    Blog:  http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13743%3Fpage%3Dlast%26x-order%3Ddate
    did anybody face issue with the new module available "SAP_XI_IDOC/IDOCFlatToXmlConvertor",please help me or give me mre information why I am getting this meta data error.
    Thank you,
    Sri

    Hi Sri,
    To Convert IDOC Flat file into IDOC xml from the given blog, the IDOC flat file should be present in standard format like:
    E2EDK01005                    0000047110815000000000001.........
    E2EDKA1003                    0000047110815000000000002.........
    E2EDKA1003                    0000047110815000000000003..........
    E2EDKA1003                    0000047110815000000000004........
    The Flat file have relationship as IDOC Number "000004711081500000" and segment sequence "0000001".
    If your flat file is not in this formate so i don't think that module is able to convert into IDOC xml. and if your file is already in this format then it may be issue with destinations which are created in NWA.
    Thanks
    Harish

  • Metadata upload issue in PI 7.4 Java stack

    Hello All,
    I need your help.
    We are using PI 7.4 single stack and for one Idoc scenario, we wanted to upload idoc metadata from ECC system with Version 4.6.
    we are facing Error : IDOC_ERROR_METADATA_UNAVAILABLE. We have successfull connection in place because we can successfully upload other standard Idoc metadata from same ECC, but issue is only with custom Idoc
    Kindly suggest how to proceed further.
    Thanks,
    Shiv

    Hello All,
    Small update here, here now we have uploaded metadata successfully but when idocs are sent from ECC(its unicode system ), they are failing in tRFC queue of ECC system  with error " IDOC_ERROR_METADATA_UNAVAILABLE.". and i have implemented below notes as well but seem no luck .
    sap notes 1767710 ,1473183 ,1529038 & 1405466.
    I have gone through
    SAP ECC-SM58 Error-IDOC Metadata unavailable
    Thanks,
    Shiv

  • "jco.server.unicode" is gone in JCO 3.0.5??!!

    Recently  we have migrated from   JCO 2.1.8  to  3.0.5.   Currently we are witnessing some problems with communications from non-Unicode Sap systems.
    In the previous version  (JCO 2.1.8)  JCoIDoc.Server had a property "jco.server.unicode"  in the latter one the property  is gone.
    AS far as I  understand, JCo3 Server based on the data sent form a client recognizes encoding and applies proper conversion. However when we try to establish a non-Unicode connection ( from a Unicode enabled system),  through setting In the SM59 transaction (tab MDMP & Unicode) u201ECommunication Type with Target Systemu201D  to Non-Unicode, we are getting  the following error :
    com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "??????????????????
    ????????å å" with extension "     SAPCFL CF5CL          ???" is unavailable.
            at com.sap.conn.idoc.rt.DefaultIDocDocument.(JCoIDocDocument.java:92)
            at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
            at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
            at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
            at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
            at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
            at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
            at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
            at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
            at java.lang.Thread.run(Thread.java:619)
    11:15:20,062 ERROR   Sap server details
    Class: com.syncron.bpe.engine.extinterface.sap.idoc.SapIDocServer
    Program id: GIM
    Thread name: JCoServerThread-1
    Registered (at gateway) connection count: 5
    Max thread count: 1
    Exception occured
    com.sap.conn.jco.JCoException: (104) RFC_ERROR_SYSTEM_FAILURE: IDocException occurred (raised by system karbie-nc6400|a_rfc)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:639)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2395)
            at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
            at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
            at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
            at java.lang.Thread.run(Thread.java:619)
    Caused by: RfcException: karbie-nc6400
        message: IDocException occurred
        Return code: RFC_FAILURE(1)
        error group: 104
        key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by karbie-nc6400|a_rfc
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2785)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
            ... 4 more
    Caused by: RfcException: karbie-nc6400
        message: IDocException occurred
        Return code: RFC_FAILURE(1)
        error group: 104
        key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by karbie-nc6400|a_rfc
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3329)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
            ... 7 more
    Caused by: com.sap.conn.idoc.IDocRuntimeException: IDocException occurred
            at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:151)
            at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
            ... 8 more
    Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "???????
    ???????????????????å å" with extension "     SAPCFL CF5CL          ???" is unavailable.
            at com.sap.conn.idoc.rt.DefaultIDocDocument.(JCoIDocDocument.java:92)
            at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
            at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
            at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
            at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
            ... 10 more
    With JCO 2.1.8  we used to solve it through setting the mentioned "jco.server.unicode"   to 1, in the  current one it seems that there is not much to configure regarding encoding.
    Please advice.

    In unicode ABAP backend systems you always have to set the destination in SM59 to "Unicode" if the communication partner is JCo. There is no choice for setting the Non-Unicode option. It won't work.
    JCo3 does not require a manual setting of the "jco.server.unicode" property any longer. Therefore the property has been deleted. In JCo3 you don't have to take care for this anymore.

  • JCO Error - SAP ER

    Dear all,
    I'm facing this issue during the SAP reconciliation.
    Could you please help me?
    [2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] ================= Start Stack Trace =======================
    [2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] oracle.iam.connectors.sap.common.parser.SAPIDOCListener$ThrowableListener : serverExceptionOccurred
    [2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
    [2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] Description : (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
    [2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable. (raised by system hgrs-hbk-s0340|a_rfc)[[
         at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:664)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2443)
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
         at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
         at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
         at java.lang.Thread.run(Thread.java:736)
    Caused by: RfcException: [hgrs-hbk-s0340|a_rfc]
    message: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by hgrs-hbk-s0340|a_rfc
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2832)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2646)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2537)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2358)
         ... 4 more
    Caused by: RfcException: [hgrs-hbk-s0340|a_rfc]
    message: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by hgrs-hbk-s0340|a_rfc
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3378)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2827)
         ... 7 more
    Caused by: com.sap.conn.idoc.IDocRuntimeException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
         at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:240)
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3349)
         ... 8 more
    Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
         at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:126)
         at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
         at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
         at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:143)
         at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.createIDocDocumentList(DefaultJCoIDocServerWorker.java:301)
         at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:199)
         ... 10 more
    [2012-09-18T13:54:32.482+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] ================= End Stack Trace =======================

    Hi Arun,
    I did that step as well,
    4.copy the Sapjco3.jar into the "CIA" directory of mercury folder and copy the sapjco.dll into the c:\windows\system32 file.
    Any clues?
    why this error?

  • IDOC Outbound processing using SAP BC

    Hello Experts,
    I am trying to develop a simple IDOC outbound processing scenario using SAP BC. In this an IDOC from SAP ECC server will be sent to an external webserver via SAP BC, for this i have done all the setup i.e Establishing connection between SAP BC & SAP ECC,  ALE settings, creating a new Routing rule, but when i try to run this scenario, i am getting the following error 'IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE' , is there any way to import the IDOC metadata, just like how we do in SAP XI using IDX2. Please Help...
    Thanks & Regards,
    Amit Naik

    Hi Michal,
    Following is the error which i am getting :-
    2009-03-12 21:56:59 IST com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "" is unavailable.
         at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:132)
         at com.sap.conn.idoc.jco.JCoIDocDocument.<init>(JCoIDocDocument.java:74)
         at com.sap.conn.idoc.jco.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:117)
         at com.sap.conn.idoc.jco.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
         at com.sap.conn.idoc.jco.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:88)
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:141)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2621)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2298)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2130)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2012)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:1903)
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:258)
         at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:320)
         at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:219)
         at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run(TimeWrappingProvider.java:40)
         at com.wm.pkg.sap.rfc.ListenerThread.run(ListenerThread.java:70)
    Thanks & Regards,
    Amit

  • JCo IDoc: SAP Business Connector required?

    On my searching for the error IDOC_ERROR_METADATA_UNAVAILABLE i have found this thread:
    BC 4.7 -IDOC_ERROR_METADATA_UNAVAILABLE
    "As of SAP BC 4.7 the SAP Adapter (the piece dealing with the SAP system(s)) uses the new SAP IDoc Java API which uses other function modules to retrieve the definition data of the IDocs.
    You need new permissions in the SAP system, especially
    S_IDOCDEFT:EDI_TCD=WE30,ACTVT=03,EDI_CIM=,EDI_DOC=
    S_CTS_ADMI:CTS_ADMFCT=TABL"
    Does JCo Idoc require the Business Connector installed to execute the JCoIDoc.createDocument() method? I guess not, but i can not see other reasons for the error message. If i read it correctly, the BC needs the permissions in SAP, but the JCoIdoc library does not depend on the BC.
    Mike

    No, it is not required.  At my company we use a third party software to handle all faxes.  Really it is setup SAP as an output device, so it is just like printing to a printer.  THe only differences is we need to have a header page in the sapscript which gives all of the details of the fax to the third party software.  This software then strips off this first page and faxes the rest of the pages.
    It is called RightFax and it runs on a separate server.
    Regards,
    Rich Heilman

  • SAP java connector SAPJCO problem..

    Hi Friends..
    <BR><BR>
    *Can some one help me to solve this problem,<BR>
    I am just trying to connect our SAP server using SAPJava connector i,e, sapjco3. in windows (XP) platform.<BR>
    I am facing below mentioned problem...*
    <BR>
    <BR>
    checkTID called for TID=0A0211C64C364B8158DA000C<BR>
    >>> Error occured on IDS800 connection 1-axsids00|sapgw00|IDS800<BR>
    com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "??????????????????????????u2020 u2020" with extension "  PAYSAPIDL LS_CO          ???" is unavailable.<BR>
         at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:126)<BR>
         at com.sap.conn.idoc.jco.rt.JCoIDocDocument.<init>(JCoIDocDocument.java:90)<BR>
         at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:168)<BR>
         at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:78)<BR>
         at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:198)<BR>
         at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:96)<BR>
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3276)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2756)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2574)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2465)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2286)<BR>
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:270)<BR>
         at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:333)<BR>
         at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:231)<BR>
         at java.lang.Thread.run(Thread.java:619)<BR>
    rollback called for TID=0A0211C64C364B8158DA000C>>> Error occured on IDS800 connection 1-axsids00|sapgw00|IDS800
    com.sap.conn.jco.JCoException: (104)<BR> RFC_ERROR_SYSTEM_FAILURE: IDocException occurred(Raised by D00120|a_rfc)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:639)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2371)<BR>
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:270)<BR>
         at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:333)<BR>
         at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:231)<BR>
         at java.lang.Thread.run(Thread.java:619)<BR>
    Caused by: RfcException: [D00120-DCCCMS|a_rfc]<BR>
        message: IDocException occurred<BR>
        Return code: RFC_FAILURE(1)<BR>
        error group: 104<BR>
        key: RFC_ERROR_SYSTEM_FAILURE<BR>
    Exception raised by D00120-DCCCMS|a_rfc<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2761)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2574)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2465)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2286)<BR>
         ... 4 more<BR>
    Caused by: RfcException: [D00120|a_rfc]<BR>
        message: IDocException occurred<BR>
        Return code: RFC_FAILURE(1)<BR>
        error group: 104<BR>
        key: RFC_ERROR_SYSTEM_FAILURE<BR>
    Exception raised by D00120|a_rfc
    <BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3305)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2756)<BR>
         ... 7 more<BR>
    Caused by: com.sap.conn.idoc.IDocRuntimeException: IDocException occurred<BR>
         at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:140)<BR>
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)<BR>
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3276)<BR>
         ... 8 more
    Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3)<BR> IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "??????????????????????????u2020 u2020" with extension "  PAYSAPIDL LS_CO          ???" is unavailable.
         at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:126)<BR>
         at com.sap.conn.idoc.jco.rt.JCoIDocDocument.<init>(JCoIDocDocument.java:90)<BR>
         at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:168)<BR>
         at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:78)<BR>
         at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:198)<BR>
         at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:96)<BR>
         ... 10 more
    <BR>
    <BR>
    <BR>
    Regads,
    Salil

    Hi Mani,
    Please if u can help me. Do let me know how you got the solution for it.Please
    Regards
    Laku

  • Send PO via rfc XML with BC 4.7

    Hi Gurus,
    I have to send the Purchase Order to vendor via rfc XML with business connector 4.7. The vendor should receive the order via ebp XML. We are not using XI we use xCBL. SRM Server 5.5 Standalone.
    i use zbbp_PO_send_xml badi for this purpose.  We are able to send the data as rfc XML.  But the smartform attachment is not working.
    Can any one specify me the exact steps involved in this.
    Please reply asap as there is an urgency in the task.
    Points assured to helpful answers.
    Cheers,
    Lokesh

    We are getting a similar error -
    Any ideas on what parameters we need to pass or configure?
    JCO.ServerThread-1 [13:15:27:437]: [JNI-LAYER] RFC.incomingRequestHandler() before dispatchRequest("IDOC_INBOUND_ASYNCHRONOUS")
    JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.nativeConnect()                                          enter, [SUCCESS]
    JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.nativeConnect() before RfcOpenEx("CLIENT="110" USER="ALEWM1" PASSWD=********** LANG="EN" SYSNR="00" ASHOST="atlun02.celanese.com" R3NAME="atlun02.celanese.com" TRACE="1" TOUPPER="0"")
    JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.nativeConnect() after  RfcOpenEx("CLIENT="110" USER="ALEWM1" PASSWD=********** LANG="EN" SYSNR="00" ASHOST="atlun02.celanese.com" R3NAME="atlun02.celanese.com" TRACE="1" TOUPPER="0"") = 0
      with error: RFC_ERROR_PROGRAM No entry for 'atlun02.celanese.com' found in 'C:\WINDOWS\sapmsg.ini'
    JCO.ServerThread-1 [13:15:27:515]: [JAV-LAYER] JCO.PoolManager.releaseClient: Cannot release client equals null
    JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.incomingRequestHandler() caught the following exception: com.sap.mw.idoc.IDoc$Exception: (2) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "LOIPRO01" is unavailable.
    JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.incomingRequestHandler() Exception.message = "The meta data for the IDoc type "LOIPRO01" is unavailable."
    JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.abort()                                                  enter, [SUCCESS]
    JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.abort() before RfcAbort(1,"The meta data for the IDoc type "LOIPRO01" is unavailable.")

  • IDoc problem :: PI - JCO

    Hi when we post an SAP standard Idoc to JCO a receiving system this happens:
    1. IDoc pass through with confiruration only = success
    2. one-to-one mapping with no conversions or anything = error
    we have done a filecompare and everything is identical. - still we get this error in sm58 when using mapping (we have tried everything related to IDX2):
    "IDOC_ERROR_METADATA_UNAVAILABLE: Matching meta data for segment definition "E2BPIBDLVHDR001"
    not found when processing IDoc no. 0000000000006011 of type "SHP_IBDLV_SAVE_REPLICA04" ."
    Any good ideas?
    Please advice
    Thanks

    thanks guys - but agian, I don't think this has something to do with metadata. We have checked everything - the error occurs on Jco site, maybe because of some differences in the message (when having a mapping step) and in the loaded metadata. Jco actually loads metadata from ECC and not PI.
    When we have no mapping everything works fine.
    please advice
    Thanks

  • IDoc to Java -- not calling 'handleRequest'

    Hello,
    I try to send IDocs from SAP to a JCoIDoc.Server. I tried to use JCoIDocSample3.java out of sapidocjco-1.0.6
    IDoc goes out correctly, in my IDoc-Server the overriden method 'protected void handleRequest(IDoc.DocumentList documentList)' is never called.
    In method 'void dispatchRequest(Function function)' the following exception occures:
    com.sap.mw.idoc.IDoc$Exception: (2) IDOC_ERROR_METADATA_UNAVAILABLE: The meta da
    ta for the IDoc type "LOIPRO01" is unavailable.
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:326)
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocumentList.<init>(JCoIDoc.java:3072)
            at com.sap.mw.idoc.jco.JCoIDoc$Server.dispatchRequest(JCoIDoc.java:10267
    Can anybody help me with this problem?
    C. Stephani

    Hi,
    I'm trying to receive IDOc from SAP. I'm using JCoIDocSample3.java program. I'm not able to receive the IDoc from SAP. I'm getting the following message
    <b>Started MyIDocServer.
    MyIDocServer is listening now...
    Incoming IDoc list request containing 0 documents...</b>
    Can anyone tell me what is the problem... can anyone send me the sample code...
    Thanks in advance
    -Booshan.

Maybe you are looking for