SAP XML Parser

Hi,
Can anyone tell me how the SAP XML Parser works in Abap?
And how to use it?
Thanks & Regards,
Jeba.

hi jeba,
Prior to SAP ERP 6.0 Enhancement Package 2 (EhP2), loading data for Central Contractor Registration (CCR) was a two-step process: data was first read from a flat file and preloaded into SAP tables, then a separate program was executed to create or update vendor master records by means of CREMAS05 iDoc. When EhP2 is installed, new CCR programs (FMFGCCR_CREATE and FMFGCCR_UPDATE) can be customized by means of an enhancement implementation to access CCR data in real time – for example, using Point-to-Point or XI interface with the CCR server (see the documentation and sample implementation classes for enhancement spot FMFG_CCR_PROCESS).
New CCR create/update programs available in EhP2 receive and process CCR data which includes creating and updating SAP vendor master records based on the provided mapping of CCR fields into SAP vendor master fields as well as creating/updating records in the SAP CCR tables. Design of the main program RFFMCCRVENDORCREATE01 is independent of the data source and of the method of processing the data. Default method of creating CCR records in SAP is defined by the default implementation of Enhancement Spot FMFG_CCR_VENDOR_MAINTAIN - FMFG_CCR_VENDOR_MAINTAIN_IMPL and is based on the method call to method MAINTAIN of vendor master class interface VMD_EI_API.
The data source as well as mapping from the data source to SAP CCR table fields and SAP vendor master fields is completely customizable and has to be defined in a custom implementation of Enhancement Spot FMFG_CCR_PROCESS.
We deliver two sample implementations for a CCR interface: one is based on SAP Exchange Infrastructure (XI) and one is a Point-to-Point (P2P) interface. You can define other data sources, such as a flat file or an RFC call to another system, yourself.
The XI sample solution includes XI interface with XML based mapping for Request and Response messages to and from the CCR server. The SAP CCR create/update program calls a proxy method, which is automatically generated based on the CCR XML schema used in XI, to request and receive CCR data through the XI middleware. Use of XI allows interfacing with additional systems as part of the CCR interface as well as provides extensive XML parsing, mapping, validation, and error handling features. Setting up XI based interface requires some minimal XI configuration and implementation of the XI based sample BAdI implementation CL_FMFG_CCR_PROCESS_SAMPLE for enhancement spot FMFG_CCR_PROCESS.
The P2P sample solution defines a P2P interface directly between the ERP layer and the CCR server by means of an HTTP communication protocol. This method might be more appealing to the customers who cannot use XI in their SAP landscapes. Here all XML mapping and parsing are defined in the custom implementation of the method GET_DATA.
New CCR Tables
The following new CCR tables were introduced in EhP2
●      FMCCRVENDOR_HDR (CCR Vendor Header)
●      FMCCRVENDOR_CORP (CCR Vendor Corporate Information)
●      FMCCRVENDOR_GS (CCR Vendor Goods and Services)
Table FMCCRTVENDOR is not populated by the new CCR programs.
Please reward if helpful.

Similar Messages

  • XML Parse error while loading an XML file

    HI Folks,
    I was trying to load and XML file into BODS.. The XML file is well-formed and the same when tested in other tools  is getting loaded without any issues..
    I have created a XML-File format with the corresponding XSD..
    But here in BODS it is giving - Parse error
    1) when i try to view the data of the source XML in my dataflow ..it is giving "XML Parser Failed".. and not able to show data..
    2) When I run my job i get the same pares error - with details as under..
    ---> Error here is "Unable to recognize element 'TAB' " or some time is say " Element TAB should be qualified"
    Please guide with this if you have any info..thanks
    I'm pasting the XML source file format here for your reference:--
      <?xml version="1.0" encoding="iso-8859-1" ?>
    - <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
    - <asx:values>
    - <TAB>
    - <items>
    + <CUSTOMER_RECORD>
      <CUSTOMER_NUMBER>1111111111</CUSTOMER_NUMBER>
      <NAME_1>ABC</NAME_1>
      <NAME_2>OFM/COMMERCIAL ACCOUNTS</NAME_2>
      <STREET_1>31 CENTER DRIVE MCS2045</STREET_1>
      <STREET_2 />
      <CITY>BETHESDA</CITY>
      <STATE_CODE>MD</STATE_CODE>
      <POSTAL_CODE>20892-2045</POSTAL_CODE>
      <COUNTRY_CODE>US</COUNTRY_CODE>
      <ORDER_BLOCK />
      <ERP_CREATE_DATE>20040610</ERP_CREATE_DATE>
      <ERP_CREATED_BY>DGUPTA</ERP_CREATED_BY>
      <ERP_MODIFY_DATE>20120201</ERP_MODIFY_DATE>
      <ERP_MODIFIED_BY>LWOHLFEI</ERP_MODIFIED_BY>
      <INDUSTRY_CODE>0103</INDUSTRY_CODE>
      <ACCOUNT_GROUP_ID>0001</ACCOUNT_GROUP_ID>
      <SALES_NOTE />
      <ADDRESS_NOTE />
      <CUSTOMER_CLASSIFICATION_CODE>02</CUSTOMER_CLASSIFICATION_CODE>
      <GLN_NUMBER />
      <PREVIOUS_ACCT_NO />
      <ACCOUNT_TYPE />
      <GAG />
      <SDI_ID />
      <HOSP_ID />
      <HIN />
      <DUNS />
      <PO_BOX />
      <POB_CITY />
      <POB_ZIP />
      <PHONE_NUMBER>77777</PHONE_NUMBER>
      <EMAIL_DOMAIN />
      <REQUESTER />
      <ERP_SOURCE_SYSTEM>ECC</ERP_SOURCE_SYSTEM>
      </CUSTOMER_RECORD>
    - <SALES_ORG_DATA>
    + <item>
      <CUSTOMER_NUMBER>1111111111</CUSTOMER_NUMBER>
      <SALES_ORG>0130</SALES_ORG>
      <CUSTOMER_GROUP>03</CUSTOMER_GROUP>
      <ORDER_BLOCK_CODE />
      <ERP_SOURCE_SYSTEM>ECC</ERP_SOURCE_SYSTEM>
      </item>
    + <item>
      <CUSTOMER_NUMBER>1111111111</CUSTOMER_NUMBER>
      <SALES_ORG>0120</SALES_ORG>
      <CUSTOMER_GROUP>11</CUSTOMER_GROUP>
      <ORDER_BLOCK_CODE />
      <ERP_SOURCE_SYSTEM>ECC</ERP_SOURCE_SYSTEM>
      </item>
      </SALES_ORG_DATA>
      </items>
      </TAB>
      </asx:values>
      </asx:abap>

    Pierre,
    Depending on the object "myLastFile", the method openDlg might not even exist (if the myLastFile object is not a File object, for instance). And I do not see any need for the myLastFile anyhow, as you are presenting a dialog to select a file to open. I recommend using the global ChooseFile( ) method instead. This will give you a filename as string in full path notation, or null when no file was selected in the dialog. I am not sure what your ExtendScript documentation states about the return value for ChooseFile, but if that differs from what I am telling you here, the documentation is wrong. So, if you replace the first lines of your code with the following it should work:
    function openXMLFile ( ) {
        var filename = ChooseFile ( "Choose XML file ...", "", "*.xml", Constants.FV_ChooseSelect );
    While writing this, I see that Russ has already given you the same advice. Use the symbolic constant value I indicated to use the ChooseFile dialog to select a single file (it can also be used to select a directory or open a file - but you want to control the opening process yourself). Note that this method allows you to set a start directory for the dialog (second parameter). The ESTK autocompletion also gives you a fifth parameter "helplink" which is undocumented and can safely be ignored.
    Good luck
    Jang

  • How to Push the into SAP ( XML data converted into IDOC )

    Hi
    i am getting XML file from Non SAP system.I need to push XML data into SAP on daily basis with out using XI as the middleware.
    I know if i get text file will use BDC's or LSMW. But i am getting data in XML format and then i need to converted into IDOC format and stored in to sap data base tables.
    Thanks for advance.
    srini

    Is the XML an IDOC-XML or custom XML that you need to post as an IDOC??
    If it is IDOC-XML you need to defined XMLFile port to process the IDOC-XML without any mapping.
    If it is a custom XML, parse the XML data into an internal table (as required) & continue with BDC or IDOC posting as you wish.
    Check for XML parsing programs..
    -Siva Maranani

  • Looking for some basics/fundamentals of XML Parsing in ABAP

    Hello SAP gurus
    I have to start workign on a project that involves Variant Configuration stuff that will be sent as XML document. I have to parse the XML document and save the needed data in some custom tables. I heard that there are some standard functions that we can use to do this job. I tried searching SDN for string XML parsing and got tons of postings regarding this. I tried to go through them one by one but it was way beyond my understanding at this time. I am looking for the fundamentals or how to start from scratch.
    I would appreciate if anybody can guide me to find some kind tutorial or basic info on where and how to start.
    Thanks a lot in advance
    Ram

    XML parsing through CALL TRANSFORMATION is one of the easiest method. A transformation needs to be created as per your XML data in transaction XSLT_TOOL and the transformation needs to be called in ABAP program using "CALL TRANSFORMATION" statement.
    Kindly search in internet for XSLT/simple transformations.

  • Exception in XML Parser (format problem?)

    Hi Experts,
    I am working on IDOC -> AS2 Configuration and the AS2 Configuration has the below structure
    <RecordSet>
         <Row1>
                       <row1 - field1>
                       <row1 - field2>
                       <row1 - field3>
         </Row1>
         <Row2>
                       <row2 - field1>
                       <row2 - field2>
                       <row2 - field3>
         </Row2>
         <Records>
              <Record1>
                        <Record1-Field1>
                        <Record1-Field1>
                        <Record1-Field1> 
              </Record1>
              <Record2>
                        <Record2-Field1>
                        <Record2-Field1>
                        <Record2-Field1> 
              </Record2>
         </Records>
    </RecordSet>
    We are getting the expected Structure when we AS2 Receiver has the xml format. But while doing module development with the strctxml2Plain, we are getting the below error  in RWB CC Monitoring.
    Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException'
    Any ideas, why this error we are getting.....
    Thanks in advance,
    Regards,
    Vasu

    Hi Vasu,
    Not in the Mapping of IR.
    In BIC Mapping Designer you have to test with the standard Mappings by providing the sample file whether the Conversion is happening correctly or not.
    You have to take the same input file that what ever you are having now.
    So that it will say clearly what is the problem in converting the XMLto the required EDI Format...
    Check whether you have any Date Format Values are comming from the input file.
    Regards
    Seshagiri

  • Message processing failed in XML parser

    This is IDoc to file integration. When I test (WE19), I did not put any value in the 'Quantity' field (which is 6 characters long).In the message mapping I put a condition to see if the value is empty then put zero, and it did not give any error. I have given all the fixed field lengths in the file adapter but still getting the following error:
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value 'TABLERO DE CONTROL' too long (>6 for 2. column) - must stop', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value 'TABLERO DE CONTROL' too long (>6 for 2. column) - must stop', probably configuration error in file adapter (XML parser error)'

    When I enter value in the 'Quantity' field, the integration works fine. The value 'tablero de control' is the 'Description'  which is the next field. My Content Conversion is like;
    Field1, Field2, Quantity, Description
    (where Field1 and Field2 are mandatory and Quantity and Description are optional)
    When I provide all 4 values, the integration work just fine, when I do not provide 'Quantity' it fails.

  • Attempt to process file failed with Exception in XML Parser-format problem

    Hi all,
    Iam getting an unusual error in the J2EE stack in XI.
    And the message is:
    006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)' 2006-11-30 17:31:07 Error Exception caught by adapter framework: null 2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
    My scenerio iam posting IDOC to a flat file with content conversion in the receiver side,the mapping got executed successfully and in the audit log i found that the error was after the 'Start converting XML document content to plain text'.
    This means that error occured during content conversion of XML to the prescribed file format.
    Can anyone suggest any better approach using which we may trace the junk data in IDoc. Manual adhoc approach could take time and is error prone.
    Thanks in advance...
    karun

    Hi Bhavesh,
    Thanks for the early reply. I checked the mapping and everything is fine and the output is also in valid XML format.
    The audit log shows that the mapping got executed successfully and the error is after the step 'Start converting XML document content to plain text '. Is there any constraint in the file adapter regarding the message size for parsing.
    2006-11-30 17:30:50 Success Transfer: "BIN" mode, size 2912595 bytes, character encoding -
    2006-11-30 17:30:50 Success Start converting XML document content to plain text
    2006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)'
    2006-11-30 17:31:07 Error Exception caught by adapter framework: null
    2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
    2006-11-30 17:31:07 Success The asynchronous message was successfully scheduled to be delivered at Thu Nov 30 17:36:07 GMT 2006.
    2006-11-30 17:31:07 Success The message status set to WAIT.
    2006-11-30 17:31:08 Success Acknowledgement creation triggered for type: SystemErrorAck
    2006-11-30 17:31:08 Success Acknowledgement sent successfully for type: SystemErrorAck
    2006-11-30 17:36:08 Success Retrying to deliver message to the application. Retry: 1

  • XML Parser error Invalid Char

    When using proxy to download data from ECC to XI -- XML parser throws this error --
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0x1a(:main:, row:1, col:50831067) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException
    Is there are setting to handle such hexadecimal charaters?
    Right now the option is to use java code to scan this XML document for such char's and replace with space before message mapping....I am eager to know a better solution .Thanks

    Hi,
    Did you ever get an answer to this question?
    I'm seeing a similar issue where ECC is sending an invalid character 0x13 in an XML message.  I would have expected the adapter to encode this properly in an XML document.
    Isn't this basic, foundational stuff?  It's preparing and sending an invalid XML document.
    What am I missing and/or what is ECC missing?

  • Mapping Error - XML Parser Exception

    We have a scenario where an ABAP Client Proxy sends a message to PI. This message is transformed into the mail package format and an email sent via the mail adapter.
    The Interface Mapping has 2 steps. The 1st step uses an XSL transformation to format the <Content> as html. This step also sets the <Subject>, <To> and <Content_Type> fields. The 2nd step uses a graphical message mapping to dynamically set the <From> field based on the sender system.
    We are experiencing the following intermittent error with this scenario:
    <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_EUK_MM_MailFrom_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
    This relates to the 2nd mapping step (graphical message mapping) described above.
    The message trace provides the following detail
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Entity 'lt' undefined(:main:, row:3, col:227) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException
    This suggests that the XML produced by the XSL transformation is invalid.
    The strange thing is that it is very difficult to replicate the error as it doesn't always occur even with the same payload! If the message is restarted it processes successfully. Testing the interface mapping in the IR, with the same payload, works successfully.
    I would welcome any ideas you may have on this.
    Thanks
    Mark

    Hi Mark,
    thing i know now why it works at "restart".
    When the message comes first you get the character '&lt;' in your xml for example: '&<(0'
    and you get the ParserException.
    Now the message is stored for queueing in the db. I assume the characters are now stored in the 'right way': '&amp;amp;&amp;lt;(0'
    When the message now will be restarted everything works fine.
    Regards,
    Olaf

  • XML Parser Exception on Punch Out Setup Request

    I am on the supplier side of the procurement process. Recently I was tasked with bringing on a new buying group, but we have encountered a strange issue. The buyer set up my company in their ERP system, however they are getting an error when trying to punch out to my website...which is listed below.
    Error Code: 400 Invalid XML Format In Login Response Document Unable to parse the Login Response XML.
    XMLParserException
    oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'meta'.
    at oracle.xml.parser.v2.XMLError.flushErrors1
    After some investigation, I am confident the problem resides in the buyers BrowserFormPost URL. The problem seems to be that instead of using "&amp;" for ampersand between the URL variables, it is passing in the & symbol (& is a protected character in XML), which is causing the Oracle XML parser to throw this exception. As a result, the set up request is never getting to me.
    The buyer has opened a couple of tickets now with Oracle support, but both times the ticket has been closed and the buyer has been instructed to contact the supplier (me). I don't know enough about the buyer side Oracle system to instruct them on how to fix this issue. Any help would be greatly appreciated.

    Hi Rakesh,
    You need to have an S-User ID to access SAP Notes. For your convenience, I am pasting the content of SAP Note 954035.
    Process, block and CO could not be created in GP
    Symptom
    After upgrade of SAP-EU component to version 7.0 SP8 in Guided Procedures process, block and callable object could not be created. On design time screen   appears error message:
    com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
    During attempt to start process through the Runtime screen you will get an error message:
    Cannot load callable object container:
    Failed to get Related Model Object for the object
    com.sap.caf.eu.gp.ui.actions.decpage.
    CDecisionPageInterfaceViewdecisionPageUsage1,relation View
    In SP9, the following message could be found:
    Failed to get Related Model Object for the object com.sap.caf.eu.gp.ui.co.exec.decision.COExecDecision
    Proceed as stated for SP8.
    Other terms
    This is WebDynpro problem caused by an inconsistency of versions.
    Solution
          1. Redeploy the SCA SAP-EU (if redeployment does not help undeploy and deploy again) components:
              o caf/eu/gp/ui/dt/comp/cons,
              o caf/eu/gp/ui/dt/comp and
              o caf/eu/gp/ui/actions  from software component SAP-EU
    or
          2. Apply the SP8 patch 1 if you upgrade to SP8. Both components mentioned below will be updated:
              o caf/eu/gp/ui/dt/comp/cons
              o caf/eu/gp/ui/dt/comp
    See if it solves your problem.
    Bye
    Ankur

  • XML parse Exception when running when dynpro

    Hello,
    When I try to run my web dynpro I get the following error.
    org.xml.sax.SAXException: Fatal Error: URI=:main: Line=7: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: = expected in attlist(:main:, row:7, col:50)
    The error occured after I reimported my model. We're on SP13 on both the Developer Studio and WAS.

    I found something interesting on the error page, it seems I'm missing SapDictionaryGenerationCore.
    SapDictionaryGenerationCore 6.4012.00.0000.20050331142541.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:59:41[UTC], changelist=339145, host=PWDFM026.wdf.sap.corp) sap.com/tc~wd~dispwda
    No information available
    sap.com/tc~wd~corecomp
    No information available
    SapDictionaryGenerationTemplates 6.4012.00.0000.20050331142541.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:59:52[UTC], changelist=339145, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4012.00.0000.20050407155601.0000 (release=630_VAL_REL, buildtime=2005-04-21:20:06:39[UTC], changelist=340806, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4012.00.0000.20050414173816.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:53:54[UTC], changelist=342170, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4012.00.0000.20050414173816.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:53:45[UTC], changelist=342170, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4012.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:57:09[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4012.00.0000.20050121170001.0000 (release=630_VAL_REL, buildtime=2005-04-21:20:03:01[UTC], changelist=322883, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4012.00.0000.20050419173537.0000 (release=630_VAL_REL, buildtime=2005-04-21:20:19:03[UTC], changelist=342907, host=PWDFM026)
    SapWebDynproGenerationCore 6.4012.00.0000.20050407155601.0000 (release=630_VAL_REL, buildtime=2005-04-21:20:07:08[UTC], changelist=340806, host=PWDFM026.wdf.sap.corp)

  • Error: XML parser (in SXMB_MONI)

    Dear Friends,
       I'm doing file to IDoc scenario. The file is picked from source directory and functional acknowledgement is coming for that picked file. Then next process is purchase order creation. In this I used java mapping. In SXMB_MONI I got the error as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!-- Call Adapter -->
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
    <SAP:Category>XIAdapter</SAP:Category>
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
    <SAP:P1>XML parser: Error in row 1 column 1, error unexpectedend-of-file</SAP:P1>
    <SAP:P2/>
    <SAP:P3/>
    <SAP:P4/>
    <SAP:AdditionalText/>
    <SAP:ApplicationFaultMessage namespace=""/>
    <SAP:Stack>Error: XML parser: Error in row 1 column 1, error unexpectedend-of-file</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    Here upto Message Branch step payload contains xml file and the following steps having payload without any xml.
    Please give me the solution for this problem.
    Regards,
    Jagan.

    that means that the structure defined in MT is diferent that the one which arrive to PI.
    check whehter the inbound strcture has the namespace in main segment or not. please paste the inbound strcture you get from SXI_monitor and the inbound structure in your MM
    Thanks
    Rodrigo

  • Provider com.sun.xml.parser.DocumentBuilderFactoryImpl not found

    During the deployment process using deploy tool i frequently get this error :
    Exception is:
    java.lang.RuntimeException: javax.xml.parsers.FactoryConfigurationError: Provider com.sun.xml.parser.DocumentBuilderFactoryImpl not found.
    and when i restart the server then the home page of the server displays the following message:
    com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application sap.com/com.sap.engine.docs.examples
    Can anybody please help in rectifying this problem .It is urgent.

    Alezander,
    First off thanks for resposnding. Following are the further details.
    1. Engine version: 6.30
    2. No, I tried even simple applications which doesnot have any XML parsing at all.
    3. Bellow is the full stack track
    04/07/08 15:16:23 -  ***********************************************************
    04/07/08 14:52:08 -  Start updating EAR file...
    04/07/08 14:52:08 -  EAR file updated successfully for 265ms.
    04/07/08 14:52:08 -  Start deploying ...
    04/07/08 14:52:08 -  EAR file uploaded to server for 78ms.
    04/07/08 14:52:08 -  ERROR: NOT deployed. Deploy Service returned ERROR:
                         For detailed information see the log file of Deploy Service.
                         Exception is:
                         java.lang.RuntimeException: javax.xml.parsers.FactoryConfigurationError: Provider com.sun.xml.parser.DocumentBuilderFactoryImpl not found
                              at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:99)
                              at com.sap.engine.lib.xml.StandardDOMParser.<init>(StandardDOMParser.java:68)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.getDescriptor(EARReader.java:190)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.<init>(EARReader.java:89)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.<init>(DeploymentTransaction.java:127)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:452)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                              at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
                              at com.sap.engine.lib.xml.StandardDOMParser.<init>(StandardDOMParser.java:81)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.getDescriptor(EARReader.java:190)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.<init>(EARReader.java:89)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.<init>(DeploymentTransaction.java:127)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:452)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                              at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
    04/07/08 14:52:08 -  ***********************************************************
    04/07/08 14:57:38 -  Start updating EAR file...
    04/07/08 14:57:38 -  EAR file updated successfully for 187ms.
    04/07/08 14:57:38 -  Start deploying ...
    04/07/08 14:57:39 -  EAR file uploaded to server for 140ms.
    04/07/08 14:57:39 -  ERROR: NOT deployed. Deploy Service returned ERROR:
                         For detailed information see the log file of Deploy Service.
                         Exception is:
                         java.lang.RuntimeException: javax.xml.parsers.FactoryConfigurationError: Provider com.sun.xml.parser.DocumentBuilderFactoryImpl not found
                              at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:99)
                              at com.sap.engine.lib.xml.StandardDOMParser.<init>(StandardDOMParser.java:68)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.getDescriptor(EARReader.java:190)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.<init>(EARReader.java:89)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.<init>(DeploymentTransaction.java:127)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:452)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                              at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
                              at com.sap.engine.lib.xml.StandardDOMParser.<init>(StandardDOMParser.java:81)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.getDescriptor(EARReader.java:190)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.<init>(EARReader.java:89)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.<init>(DeploymentTransaction.java:127)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:452)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                              at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
    04/07/08 14:57:39 -  ***********************************************************
    04/07/08 14:57:57 -  Start updating EAR file...
    04/07/08 14:57:58 -  EAR file updated successfully for 187ms.
    04/07/08 14:57:58 -  Start deploying ...
    04/07/08 14:57:58 -  EAR file uploaded to server for 78ms.
    04/07/08 14:57:58 -  ERROR: NOT deployed. Deploy Service returned ERROR:
                         For detailed information see the log file of Deploy Service.
                         Exception is:
                         java.lang.RuntimeException: javax.xml.parsers.FactoryConfigurationError: Provider com.sun.xml.parser.DocumentBuilderFactoryImpl not found
                              at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:99)
                              at com.sap.engine.lib.xml.StandardDOMParser.<init>(StandardDOMParser.java:68)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.getDescriptor(EARReader.java:190)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.<init>(EARReader.java:89)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.<init>(DeploymentTransaction.java:127)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:452)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                              at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
                              at com.sap.engine.lib.xml.StandardDOMParser.<init>(StandardDOMParser.java:81)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.getDescriptor(EARReader.java:190)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.<init>(EARReader.java:89)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.<init>(DeploymentTransaction.java:127)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:452)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                              at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
    04/07/08 14:57:58 -  ***********************************************************
    04/07/08 15:04:16 -  Start updating EAR file...
    04/07/08 15:04:16 -  EAR file updated successfully for 266ms.
    04/07/08 15:04:16 -  Start deploying ...
    04/07/08 15:04:16 -  EAR file uploaded to server for 94ms.
    04/07/08 15:04:16 -  ERROR: NOT deployed. Deploy Service returned ERROR:
                         For detailed information see the log file of Deploy Service.
                         Exception is:
                         java.lang.RuntimeException: javax.xml.parsers.FactoryConfigurationError: Provider com.sun.xml.parser.DocumentBuilderFactoryImpl not found
                              at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:99)
                              at com.sap.engine.lib.xml.StandardDOMParser.<init>(StandardDOMParser.java:68)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.getDescriptor(EARReader.java:190)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.<init>(EARReader.java:89)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.<init>(DeploymentTransaction.java:127)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:452)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                              at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
                              at com.sap.engine.lib.xml.StandardDOMParser.<init>(StandardDOMParser.java:81)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.getDescriptor(EARReader.java:190)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.<init>(EARReader.java:89)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.<init>(DeploymentTransaction.java:127)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:452)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                              at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
    04/07/08 15:04:16 -  ***********************************************************
    04/07/08 15:16:23 -  Start updating EAR file...
    04/07/08 15:16:23 -  EAR file updated successfully for 204ms.
    04/07/08 15:16:23 -  Start deploying ...
    04/07/08 15:16:24 -  EAR file uploaded to server for 62ms.
    04/07/08 15:16:24 -  ERROR: NOT deployed. Deploy Service returned ERROR:
                         For detailed information see the log file of Deploy Service.
                         Exception is:
                         java.lang.RuntimeException: javax.xml.parsers.FactoryConfigurationError: Provider com.sun.xml.parser.DocumentBuilderFactoryImpl not found
                              at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:99)
                              at com.sap.engine.lib.xml.StandardDOMParser.<init>(StandardDOMParser.java:68)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.getDescriptor(EARReader.java:190)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.<init>(EARReader.java:89)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.<init>(DeploymentTransaction.java:127)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:452)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                              at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
                              at com.sap.engine.lib.xml.StandardDOMParser.<init>(StandardDOMParser.java:81)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.getDescriptor(EARReader.java:190)
                              at com.sap.engine.services.deploy.ear.jar.EARReader.<init>(EARReader.java:89)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.<init>(DeploymentTransaction.java:127)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:452)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                              at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
    04/07/08 15:16:24 -  ***********************************************************
    Thanks,
    Abilash

  • Xml parser certificate

    QA1: In our project, we used the third-party xml tool such as Jdom to process the xml document. Is this kind of action break the rule of certification?
    QA2: if the answer to QA1 is true, is it possible to integrate third-party xml tool in project and meanwhile conform to certification?

    Hi Thorsten
    Here the certification means "NW-XI-AF certification" (Netweaver XI Adapter Framework certification). The referenced document is named "NW-XI-AF3.0 Test Catalog for Certification".
    In chapter 3.2.7 J2EE Resource Access
    The usage of J2EE resources instead of native Java resources can hardly be tested. Hence
    the vendor has to answer the following questions:
    1. If the adapter must be able to parse XML documents, do you use the SAP J2EE XML
    parser libraries (e.g. SAXParser)?
    2. Do you use the SAP J2EE application threads?
    3. Do you use the SAP J2EE Transaction Manager?
    If one of them is answered with “No” the certification is not possible. In future this
    questionnaire might be replaced by test cases.
    while in our adapter development, we used other xml processing tools, this is where the question comes from.
    Best Regards
    Mints

  • XI XML Parser: tag content with "'", single apostrophe: invalid character

    Hi all,
    we import XML-documents with the file adapter in a sender channel. everything works well.
    But if one of the XML-tag contents contains a single apostrophe ( ' ), then the XML parser stops with an error "An invalid character was found inside an entity reference. ". The message can not be processed. If I test the message content in the mapping -> no error.
    When the single apostrophe is dereferenced by an additional single apostrophe the XML-File can be processed.
    Question: does anybody know how this can be handled because it is not very nice of SAP XI to send single apostrophes in outgoing messages but cannot handle it in incoming messages from other systems? special adapter settings?
    Thank you very much
    regards
    Hans

    check bhavesh reply
    Suppress Special Character
    also check
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9420 [original link is broken] [original link is broken] [original link is broken]
    Implementing a Java Mapping in SAP PI to remove Escape Sequences from a file

Maybe you are looking for

  • How to get data  from an internal table in some other program

    I would like to get data from the internal table in the other program. When I using FM "LIST_FROM_MEMORY" to get the data, it doesn't work and the exception is not fount. If any special code need in the other program, like write data to memory . Many

  • How do I Add Pages to Chapters?

    I am trying to lay out a book with about 15 chapters.  I start by ading some text to a chapter page but that only accepts a few lines.  I thought iBooks Author would add pages automatically as I added more text but that doesn't seem to be the case. I

  • Installing 7.0.1

    I am having trouble installing the new update. It seems to download the package fine and I go through all the prompts and says its been installed successfully yet the update has not taken effect. I'm sure I'm missing something simple.

  • Toplink returning EST time in GMT

    Hi, I built a CRUD web app using Toplink in NB6.9. It is a UI for an oracle table. When the user edits a record, I am updating the 'LastUpdate' column via code. The problem is that the time is saved in EST, but when it is retrieved back, it shows 4 h

  • I lost my wireless printability

    When I got my Airport Extreme Base Station, I plugged my printer into it and seemed it seemed to switch automatically to being able to print wirelessly to my printer without even doing anything to set it up.  I don't have to be wireless from my deskt