JDBC - No 'action' attribute found in XML document - error

Hi,
I'm trying to write to SQL Server form File
I successfully read from file, but fail to write.
<b>My XML is :</b>
<?xml version="1.0" encoding="UTF-8"?>
<ns0:SD_NEZIGA_OUT_MT xmlns:ns0="ssss.co.il:SD:Office_core_Neziga"><statement2 action="INSERT"><table>Employees</table><access><ID>000009</ID><Name>&#1497;&#1493;&#1504;&#1505;&#1497; &#1512;&#1493;&#1514;&#1497;</Name><Phone>972528288840</Phone><Manager>001037</Manager><DistManager>001037</DistManager><Password>D</Password><UserType>0</UserType><miskalID>0000</miskalID></access></statement2></ns0:SD_NEZIGA_OUT_MT>
<b>Error from JDBC adapter:</b>
TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
Help me please.
Best regards, Natalia.

Hey
Ur XML is not correct,it must be something like this
<root>
<StatementName1>
<dbTableName action=”UPDATE” | “UPDATE_INSERT”>
<table>realDbTableName</table>.....
</StatementName1>
if u look at the receiver structure of /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 this blog,action is an attribute of TEST and not STATEMENTNAME,for ur structure its an attribute of Statement2
can u send ur receiver structure?
thanx
ahmad
Message was edited by:
        Ahmad

Similar Messages

  • JDBC receiver adapter: No 'action' attribute found in XML document

    Hi this is my target structure getting generated at the Receiver JDBC adapter
    I have checked the XML doc, still unable to figure out why in the RWB its showing the following error:
    "Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)"
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_IF001 xmlns:ns0="http://vodafone.com/xi/IF001">
    <Statement>
    <OPCO_VPC_PO action="UPDATE">
    <access>
    <SO>0060000090</SO>
    <SO_ITEM>000010</SO_ITEM>
    </access>
    <key>
    <OPCO_PO>0002002291</OPCO_PO>
    <OPCO_PO_ITEM>00010</OPCO_PO_ITEM>
    </key>
    </OPCO_VPC_PO>
    </Statement>
    </ns0:MT_IF001>
    Kindly Help !!
    Thanks !!

    Hi,
                 Clearly stating that no action attribute .So, please take a look at the structure please do like this at your Data Type specification
    <i><b><b><root>
      <StatementName1>
    <dbTableName action=”UPDATE” | “UPDATE_INSERT”>
        <table>realDbTableName</table>
    <access>
    <col1>val1</col1>
    <col2>val2new</col2>
    </access>
    <key1>
    <col2>val2old</col2>
    <col4>val4</col4>
    </key1>
    <key2>
    <col2>val2old2</col2>
    </key2>
    </dbTableName>
      </StatementName1>
    </root></b></b></i>
        refer the  following link
    http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
    **Assign points if you found helpful
    Regards.,
    V.Rangarajan

  • Error processing request in sax parser  No 'action' attribute found in XML

    Hi All,
            I am doing a FILE to JDBC Scenario.  I just want to send a data from file to Sql Db table. For this I have written a stored procedure to insert the row in a table.
    This is the message mapping for FILE to JDBC ….
    Sender                                                                   Receiver
    *FILESENDER_MT  1..1    FILESENDER_DT     * SPRECEIVER_MT    1..1
        .NO                    1..1    xsd:string                    * Statement           1..1   string
        .Name                1..1    xsd:string                      *user_PROC       1..1                                                                               
    action            1..1required
                                                                                *No                                                                               
    isInput        1..1  string
                                                                                    type           1..1  string
                                                                                *Name
                                                                                    isInput        1..1  string
                                                                                    type           1..1  string 
    Mapped Values....
    Statement is mapped with <b>FILESENDER_MT</b>
    action attribute is mapped with "<b>EXECUTE</b>" Constant
    No is mapped with <b>NO</b>
    Name is mapped with <b>Name</b>
    for both isInput is mapped with <b>TRUE</b>
    for both type is mapped with <b>CHAR</b>
    Here is the my stored procedure.....
    CREATE PROCEDURE [dbo].[user_PROC]
    @NO char(10),  @Name char(10)  AS
    insert into FILE2JDBC values('a','ab')
    GO
    when i run this stored procedure in Sql directly it was executed successfully....
    I have checked In SXMB_MONI status is showing green...
    xml messages from SXMB_MONI ....
    this is the message from payloads of Inbound Message
    <PRE> <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:FILESENDER_MT xmlns:ns0="http://www.prospectadelhi.com/DELHI_FILE2JDBC">
      <NO>111</NO>
      <NAME>murthy</NAME>
      </ns0:FILESENDER_MT></PRE>
    this is the message from payloads of Request Message Mapping
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:SPRECEIVER_MT xmlns:ns0="http://www.prospectadelhi.com/DELHI_FILE2JDBC">
    - <Statement>
    - <user_PROC>
      <action>EXECUTE</action>
    - <NO>
      <isInput>TRUE</isInput>
      <type>CHAR</type>
      </NO>
    - <Name>
      <isInput>TRUE</isInput>
      <type>CHAR</type>
      </Name>
      </user_PROC>
      </Statement>
      </ns0:SPRECEIVER_MT>
    this is the error showing in runtime workbench>component monitoring->communication channel monitoring-->Receiver Communication Channel....
    <b>Error while parsing or executing XML-SQL document: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)</b>
    Can any body tell me whether the problem is in Mapping or in Data Type Structure..
    Please resolve this issue....
    Thanks in Advance,
    Murthy.

    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:SPRECEIVER_MT xmlns:ns0="http://www.prospectadelhi.com/DELHI_FILE2JDBC">
    - <Statement>
    <b>- <user_PROC>
    <action>EXECUTE</action></b>
    - <NO>
    <isInput>TRUE</isInput>
    <type>CHAR</type>
    </NO>
    - <Name>
    <isInput>TRUE</isInput>
    <type>CHAR</type>
    </Name>
    </user_PROC>
    </Statement>
    </ns0:SPRECEIVER_MT>
    The Action should be a Attribute of Element user_Proc as,
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:SPRECEIVER_MT xmlns:ns0="http://www.prospectadelhi.com/DELHI_FILE2JDBC">
    - <Statement>
    <b>- <user_PROC action="Execute"></b>- <NO>
    <isInput>TRUE</isInput>
    <type>CHAR</type>
    </NO>
    - <Name>
    <isInput>TRUE</isInput>
    <type>CHAR</type>
    </Name>
    </user_PROC>
    </Statement>
    </ns0:SPRECEIVER_MT>
    Likewise isInput and Type should be Attributes and not Elements .
    Regards
    Bhavesh

  • JDBC Adapter: Action Attribute Missing problem

    Hi
    I am passing data from SAP R/3 though JDBC Adapter. In SXMB_MONI everything is fine and it shows Success Message. Though Database is not updated, but in Message monitoring I get the error 'No "Action" attribute found in XML document'
    I have specified the Database table in Communication Channel and the table name is specified as the Tag.
    The XI payload is as follows. Where Tag FCP_PROGNOSEDATA is the table name and action tag is specified as INSERT.
    kindly let me know what went wrong and why i am getting this error message
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns53:FCPBW_MT xmlns:ns53="http://pdk/fcp/Prognoses">
    - <Statement>
    - <<b>FCP_PROGNOSEDATA</b>>
      <action><i><b>INSERT</b></i></action>
    - <access>
      <DATO>05-12-2004</DATO>
      <ORG_ENHED_NR_A>0704</ORG_ENHED_NR_A>
      <PROGNOSE_TYPE>1</PROGNOSE_TYPE>
      <ANTAl_MS>821.0</ANTAl_MS>
      <ANTAl_SH>10444.0</ANTAl_SH>
      </access>
      </<b>FCP_PROGNOSEDATA</b>>
      </Statement>
      </ns53:FCPBW_MT>
    Regards
    Swetank

    Hi Swetank,
    The ACTION should be an "attribute" in your JDBC XML.I think you have created it as a TAG.
    For Example:
    <StatementName2>
    <dbTableName action=”INSERT”>
    <table>realDbTableName</table>
    <access>
    <col1>val1</col1>
    <col2>val2</col2>
    </access>
    <access>
    <col1>val11</col1>
    </access>
    </dbTableName> 
      </StatementName2>
    Regards,
    Sridhar
    Message was edited by: Sridhar Rajan Natarajan

  • JDBC adapter: action attribute is missing

    This is my XML, could anyone please tell me what's wrong there???
    <?xml version="1.0" encoding="utf-8" ?>
    <root>
       <zzz ACTION="INSERT">
          <access>
             <a>PR00035371</Ia>
             <b>555555</b>
             <c>2006</c>
             <d>76.50</d>
          </access>
       </zzz>
    </root>
    and the error message is:
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)</SAP:AdditionalText>
    I'm sending data to oracle 10.0.1.x and using ojdbc14.jar.
    Many thanks,
    Milan

    check for the strucutre as below:
    <root>
      <StatementName1>
    <dbTableName action=”UPDATE” | “UPDATE_INSERT”>
        <table>realDbTableName</table>
    <access>
    <col1>val1</col1>
    <col2>val2new</col2>
    </access>
    <key1>
    <col2>val2old</col2>
    <col4>val4</col4>
    </key1>
    <key2>
    <col2>val2old2</col2>
    </key2>
    </dbTableName>
      </StatementName1>

  • No "action" attribute found

    I am getting the following error messages.  I have checked through the SDN and found many notes on the subject, but I am still unable to figure out why I am getting the following errors.  Can anyone help please?
    2007-06-14 13:51:52 Error No "action" attribute found in XML document ("action" attribute missing or wrong XML structure)
    2007-06-14 13:51:52 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
    2007-06-14 13:51:52 Error Exception caught by adapter framework: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
    2007-06-14 13:51:52 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure).

    Skip,
    I really don't know whether the below change make sense or not, but can u try it?
    Please change <skip_test action="insert"> as <skip_test action="INSERT"> .
    If it doesn't helps , is it ok for you to create a sql string and do the same as you did? If you want consider below.
    Create Data type as
    Statement  <b>0..Unbounded</b>
        TABNAM <b>1..1</b>(Sub-element of Statement)
            Action  <b>required</b> (Attribute of TABNAM)
            Access <b>1..1</b> (Sub-element of TABNAM)
    Create simple UDF with three inputs(as per your structure)
    <u>UDF</u>
    return "INSERT INTO skip_test(vendor_data1,vendor_data2,vendor_data3) Values ('john', 3/3/2007','Ford')" ;
    Map Constant([]) to Statement
    Map Constant([SQL_DML]) to Action
    Map Inputs - UDF- Access
    If you have multiple source records and you want the data to be inserted with single statement  then please follow the below logic as I suggested in the other thread.
    See below links for more info.
    http://www.flickr.com/photo_zoom.gne?id=549186611&size=o
    http://www.flickr.com/photo_zoom.gne?id=549186651&size=o
    Consider the logic and apply for ur strcture.
    I hope it helps you !!!!
    Best regards,
    raj.

  • Unsupported action attribute value 'EXCECUTE' found in XML document

    Hi
    I am working on IDOC->XI->DB2 scenairo
    I am getitng error following error whe i try to insert and execute the stored procedure.
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Unsupported action attribute value 'EXCECUTE' found in XML document
    Following is the payload....
      <?xml version="1.0" encoding="UTF-8" ?>
    - <I805_Abstr_CustOutlet_MT>
    - <StatementInsert>
    - <STATUS action="INSERT">
      <table>BI5FILMM.BSOMSAPP</table>
    - <access>
      <OUTLET_NO>12</OUTLET_NO>
      <OUTLET_RF>20</OUTLET_RF>
      <OMFUNC>CRT</OMFUNC>
      <STATUS>N</STATUS>
      <IFCEDATE>1080626</IFCEDATE>
      <IFCETIME>094220</IFCETIME>
      </access>
      </STATUS>
      </StatementInsert>
    - <StatementProce>
    - <STATUS action="EXCECUTE">
      <table>CC5PTF.BSOMPSAP</table>
      <Para1 IsInput="true" type="CHAR">BI5FILMM</Para1>
      <Para2 IsInput="true" type="CHAR">BMIJOBD</Para2>
      </STATUS>
      </StatementProce>
      </I805_Abstr_CustOutlet_MT>

    Check ur XML format with the one mentioned in this
    http://help.sap.com/saphelp_nw2004s/helpdata/en/4d/8c103e05df2e4b95cbcc68fed61705/content.htm

  • Large XML Document Error

    We are using Oracle's XSQL servlet engine 9.0.2.0.0A to query an Oracle Database using xsql:include-owa. This xsql document uses a custom serializer to write the resulting XML to a file on the webserver. We have run into a problem with writing XML documents larger than approximatly 7MB. The file is written but just contains a Malformed XML Document error. We have tried tracking down the problem and it seems to be occuring before the custom serializer is given control of the document. Attached below is the xsql document and the Java source of our serializer if it would be of any help.
    -Eric Dalquist
    <?xml version="1.0"?>
    <?xml-stylesheet type="text/xsl" href="simple_transform_xml.xsl" serializer="XMLWriter"?>
    <BASE_TAG connection="XXXXXXXX" xmlns:xsql="urn:oracle-xsql">
        <xsql:set-page-param name="save-file" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/applInfo.xml"/>
        <xsql:include-owa >
            STUDEV.STUADMSDSET.P_GET_RECRUIT_INFO('A','C');
        </xsql:include-owa>
    </BASE_TAG>-----------------------------------------
    * Author:        Eric Dalquist
    * E-Mail:        [email protected]
    * Date Created:  10-03-2001
    * Last Modified: 10-03-2001
    * Modified By:   Eric Dalquist
    * Description:   This class writes out the contents of the final document produced by the xsql servlet.
    package com.mtu.XSQLSerializers;
    import java.io.FileOutputStream;
    import oracle.xml.xsql.*;
    import oracle.xml.parser.v2.XMLDocument;
    import org.w3c.dom.Document;
    * <P>
    *    XMLWriter is an implementation of the abstract XSQLDocumentSerializer class. It is passed a refrence to a DOM Document
    *    and the servlet environment. The XMLWriter takes the document and writes it out to the servlet's output stream. There
    *    is also the option that the saveFile xsql page parameter can be set to a fully qualified path and file name to write the
    *    document to.
    * </P>
    * <P>
    *    Here is an example of setting the saveFile page paramter. This line would be the first tag inside the root xsql servlet tag.
    * </P>
    * <PRE>
    *    &#060;xsql:set-page-param name="save-file" value="/u01/oracle/ias10210/xdk/java/xsql/Repository/Course_List/XMLDocument.xml"/&#062;
    * </PRE>
    * @author  Eric B. Dalquist
    * @version 1.0 10/03/2001
    public class XMLWriter implements XSQLDocumentSerializer
        /** the header we send if we are returning XML */
        private static final String MIME_XML = "text/xml";
        /** the name of the page parameter we look for to get the path and name to save the XML document to */
        private static final String ATTR_FILE = "save-file";
         * The serialize is called by the servlet engine and is passed the DOM Docuement result
         * from the XSLT transformation if there was one and a refrence to the XSQL servlet environment
         * @param doc The document representation of the XML output of the xsql servlet.
         * @param env A refrence to the servlet's environment.
         * @throws Throwable Any unhandled error is handled by the servlet by default.
        public void serialize(Document doc, XSQLPageRequest env) throws Throwable
            System.out.print("start ... ");
            FileOutputStream fos = null;
            String reqType = env.getRequestType();
            String saveFile = env.getParameter(ATTR_FILE);
            if (!reqType.equals("Command Line"))
                env.setContentType(MIME_XML);
                ((XMLDocument)doc).print(env.getOutputStream());
                env.getOutputStream().close();
            if (saveFile != null && !saveFile.equals("") && saveFile.indexOf("..") == -1 && saveFile.indexOf("~") == -1)
                fos = new FileOutputStream(saveFile);
                ((XMLDocument)doc).print(fos);
                fos.close();
            System.gc();
            System.out.println("end");
    }

    Technically DBMS_XMLSAVE and it's alter ego DBMS_XMLQUERY are not considered part of XML DB. DBMS_XMLSAVE and DBMS_XMLQUERY are legacy Java implementations.
    In 9.2.x these routines were replaced by DBMS_XMLSTORE and DBMS_XMLGEN which are written in 'C' and should be much faster in most cases and address a number of limitations inherant in the older implementations. DBMS_XMLSTORE and DBMS_XMLGEN are part of XML DB and the minimum supported release for XML DB is 9.2.0.3.0.
    DBMS_XMLSAVE issues are addressed in the TECH/XML forum
    http://forums.oracle.com/forums/category.jspa?categoryID=51

  • TP Agreement Not Found -- OAGIS XML document over AS2

    Hi,
    I am getting TP Agreement not found error while receiving OAGIS XML document over AS2. Below is error message.
    Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND
    I am not sure why it says null-INBOUND. It appears like it is not able to identify Document Version. DOCTYPE_REVISION=7.2.1 is being passed in the AS2 transport headers but still it does not recognize the version.
    I am not sure what is missing. Please give some ideas hints.
    Below is the Business Message:----
    Id     AC12149513F1F78141400000E7DEDE00
    Message Id     AC12149513F1F78136200000E7DED800
    Refer To Message     Refer To Message
    Sender Type     AS2 Identifier
    Sender Value     SOALocal
    Receiver Type     AS2 Identifier
    Receiver Value     PowellIndustries
    Sender     SOALocal
    Receiver     Powell
    Agreement Id     
    Agreement     
    Document Type     PROCESS_INVOICE_002
    Document Protocol     OAG
    Document Version     7.2.1
    Message Type     REQ
    Direction     INBOUND
    State     MSG_ERROR
    Acknowledgement Mode     NONE
    Response Mode     ASYNC
    Send Time Stamp     06/07/2013 11:28:49 AM
    Receive Time Stamp     06/07/2013 11:28:50 AM
    Document Retry Interval(Channel)     0
    Document Remaining Retry(Channel)     0
    Document Retry Interval(Agreement)     
    Document Remaining Retry(Agreement)     
    Native Message Size     10788
    Translated Message Size     
    Business Action Name     
    Business Transaction Name     
    Xpath Name1     
    Xpath Value1     
    Xpath Expression1     
    Xpath Name2     
    Xpath Value2     
    Xpath Expression2     
    Xpath Name3     
    Xpath Value3     
    Xpath Expression3     
    Correlation From XPath Name     
    Correlation From XPath Value     
    Correlation From XPath Expression     
    Correlation To XPath Name     
    Correlation To XPath Value     
    Correlation To XPath Expression     
    Wire Message     Wire Message
    Application Message     Application Message
    Payload Storage     Payload Storage
    Attachment     Attachment
    Label     
    Collaboration Id     AC12149513F1F7813BF00000E7DEDB00
    Collabration Name     
    Collabration Version     
    Business Action Name     
    Exchange Protocol Name     AS2
    Exchange Protocol Version     1.1
    Interchange Control Number     
    Group Control Number     
    Transaction Set Control Number     
    Error Code     B2B-50547
    Error Description     Machine Info: (pwl.pri) Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
    Error Level     ERROR_LEVEL_COLLABORATION
    Error Severity     ERROR
    Error Text     Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
    Below is the Wire Message:----
    Id     AC12149513F1F78115400000E7DED600
    Message Id     AC12149513F1F78115400000E7DED600
    Business Message     AC12149513F1F78141400000E7DEDE00
    Packed Message     Packed Message
    Payload     Payload
    Protocol Message Id     <38383939373331343630313931303737@SOALocal>
    Refer To Protocol Message Id     
    Protocol Collaboration Id     
    Protocol Transport Binding     ChannelName=SOALocal dcID=CHANNEL_nlzbB-7511847722850817684 AS2-To=PowellIndustries DOCTYPE_NAME=PROCESS_INVOICE_002 TE=trailers, deflate, gzip, compress DOCTYPE_REVISION=7.2.1 Date=Fri, 07 Jun 2013 16:28:49 GMT AS2-Version=1.1 Accept-Encoding=gzip, x-gzip, compress, x-compress AS2-From=SOALocal url=http://pwl.pri/b2b/transportServlet Content-Transfer-Encoding=binary Message-ID=<38383939373331343630313931303737@SOALocal> Content-type=application/pkcs7-mime; smime-type="enveloped-data" MSG_RECEIVED_TIME=Fri Jun 07 11:28:49 CDT 2013 ECID-Context=1.71b9d2a41e5aaef0:-10db6371:13f1ee6cb74:-8000-000000000000276d;khvE MIME-version=1.0 tpName=PowellIndustries User-Agent=AS2 Server Oracle HTTPClient Version 10h Content-Length=13663 Host=pwl.pri:8001 Connection=close, TE useProxy=false From=SOALocal additionalHeaders=DOCTYPE_NAME=PROCESS_INVOICE_002#DOCTYPE_REVISION=7.2.1
    Message Digest     Message Digest
    Digest Algorithm     md5
    Transport Protocol     HTTP
    Transport Protocol Version     1.1
    Url     http://pwl.pri:8001/b2b/transportServlet
    security     
    Transport Headers     ChannelName=SOALocal dcID=CHANNEL_nlzbB-7511847722850817684 AS2-To=PowellIndustries DOCTYPE_NAME=PROCESS_INVOICE_002 TE=trailers, deflate, gzip, compress DOCTYPE_REVISION=7.2.1 Date=Fri, 07 Jun 2013 16:28:49 GMT AS2-Version=1.1 Accept-Encoding=gzip, x-gzip, compress, x-compress AS2-From=SOALocal url=http://pwl.pri:8001/b2b/transportServlet Content-Transfer-Encoding=binary Message-ID=<38383939373331343630313931303737@SOALocal> Content-type=application/pkcs7-mime; smime-type="enveloped-data" MSG_RECEIVED_TIME=Fri Jun 07 11:28:49 CDT 2013 ECID-Context=1.71b9d2a41e5aaef0:-10db6371:13f1ee6cb74:-8000-000000000000276d;khvE MIME-version=1.0 tpName=PowellIndustries User-Agent=AS2 Server Oracle HTTPClient Version 10h Content-Length=13663 Host=pwl.pri:8001 Connection=close, TE useProxy=false From=SOALocal additionalHeaders=DOCTYPE_NAME=PROCESS_INVOICE_002#DOCTYPE_REVISION=7.2.1
    certificates     certificates
    State     ERROR
    Reattempt Count     
    Error Code     B2B-50547
    Error Description     Machine Info: (pwl.pri) Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
    Error Text     Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
    exchangeRetryInterval     
    exchangeRemainingRetry     
    Message Size     10788
    Thanks
    Ismail M.

    Hi Anuj,
    Here is the payload from the wire message. We are using 11.1.1.6.0
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <PROCESS_INVOICE_002 xmlns="http://www.openapplications.org/171_process_invoice_002">
      <CNTROLAREA xmlns="">
        <BSR>
          <VERB value="PROCESS">PROCESS</VERB>
          <NOUN value="INVOICE">INVOICE</NOUN>
          <REVISION value="002">002</REVISION>
        </BSR>
        <SENDER>
          <LOGICALID>POWELLIND</LOGICALID>
          <COMPONENT>B2B</COMPONENT>
          <TASK/>
          <REFERENCEID/>
          <CONFIRMATION>0</CONFIRMATION>
          <LANGUAGE>ENG</LANGUAGE>
          <CODEPAGE/>
          <AUTHID>oracle B2B</AUTHID>
        </SENDER>
        <DATETIME qualifier="CREATION">
          <YEAR/>
          <MONTH/>
          <DAY/>
          <HOUR/>
          <MINUTE/>
          <SECOND/>
          <SUBSECOND/>
          <TIMEZONE/>
        </DATETIME>
      </CNTROLAREA>
      <DATAAREA xmlns="">
        <PROCESS_INVOICE>
          <INVHEADER>
            <AMOUNT qualifier="DOCUMENT" type="T" index="1">
              <VALUE>5413</VALUE>
              <NUMOFDEC>2</NUMOFDEC>
              <SIGN>+</SIGN>
              <CURRENCY>USD</CURRENCY>
              <DRCR>D</DRCR>
            </AMOUNT>
            <DATETIME qualifier="DOCUMENT" index="1">
              <YEAR>2013</YEAR>
              <MONTH>03</MONTH>
              <DAY>15</DAY>
              <HOUR>00</HOUR>
              <MINUTE>00</MINUTE>
              <SECOND>00</SECOND>
              <SUBSECOND>0000</SUBSECOND>
              <TIMEZONE>-0500</TIMEZONE>
            </DATETIME>
            <DOCUMENTID>1000182</DOCUMENTID>
            <DESCRIPTN/>
            <DOCTYPE/>
            <PAYMETHOD/>
            <REASONCODE/>
            <USERAREA/>
            <PARTNER>
              <NAME index="1">Powell US Operating Unit</NAME>
              <ONETIME/>
              <PARTNRID/>
              <PARTNRTYPE>Supplier</PARTNRTYPE>
              <SYNCIND/>
              <ACTIVE/>
              <CURRENCY/>
              <DESCRIPTN/>
              <DUNSNUMBER/>
              <GLENTITYS/>
              <NAME index="1">Powell US Operating Unit</NAME>
              <PARENTID/>
              <PARTNRIDX/>
              <PARTNRRATG/>
              <PARTNRROLE/>
              <PAYMETHOD/>
              <TAXEXEMPT/>
              <TAXID/>
              <TERMID/>
              <USERAREA/>
              <CONTACT>
                <NAME index="1">No Sales Credit</NAME>
                <CONTCTTYPE/>
                <DESCRIPTN/>
                <EMAIL/>
                <FAX index="1"/>
                <TELEPHONE index="1"/>
                <USERAREA/>
              </CONTACT>
            </PARTNER>
            <PARTNER>
              <NAME index="1">PO Box 843823, Dallas, Dallas, TX, 75284-3823, United States</NAME>
              <ONETIME/>
              <PARTNRID/>
              <PARTNRTYPE>RemitTo</PARTNRTYPE>
              <SYNCIND/>
              <ACTIVE/>
              <CURRENCY/>
              <DESCRIPTN/>
              <DUNSNUMBER/>
              <GLENTITYS/>
              <NAME index="1">PO Box 843823, Dallas, Dallas, TX, 75284-3823, United States</NAME>
              <PARENTID/>
              <PARTNRIDX/>
              <PARTNRRATG/>
              <PARTNRROLE/>
              <PAYMETHOD/>
              <TAXEXEMPT/>
              <TAXID/>
              <TERMID/>
              <USERAREA/>
              <ADDRESS>
                <ADDRLINE index="1">PO Box 843823</ADDRLINE>
                <ADDRTYPE/>
                <CITY>Dallas</CITY>
                <COUNTRY>United States</COUNTRY>
                <COUNTY>Dallas</COUNTY>
                <DESCRIPTN/>
                <FAX index="1"/>
                <POSTALCODE/>
                <REGION/>
                <STATEPROVN>TX</STATEPROVN>
                <TAXJRSDCTN/>
                <TELEPHONE index="1"/>
                <URL/>
                <USERAREA/>
              </ADDRESS>
              <CONTACT>
                <NAME index="1"/>
                <CONTCTTYPE/>
                <DESCRIPTN/>
                <EMAIL/>
                <FAX index="1"/>
                <TELEPHONE index="1"/>
                <USERAREA/>
              </CONTACT>
            </PARTNER>
            <PARTNER>
              <NAME index="1"/>
              <ONETIME/>
              <PARTNRID/>
              <PARTNRTYPE>Carrier</PARTNRTYPE>
              <SYNCIND/>
              <ACTIVE/>
              <CURRENCY/>
              <DESCRIPTN/>
              <DUNSNUMBER/>
              <GLENTITYS/>
              <NAME index="1"/>
              <PARENTID/>
              <PARTNRIDX/>
              <PARTNRRATG/>
              <PARTNRROLE/>
              <PAYMETHOD/>
              <TAXEXEMPT/>
              <TAXID/>
              <TERMID/>
              <USERAREA/>
              <ADDRESS>
                <ADDRLINE index="1"/>
                <ADDRTYPE/>
                <CITY/>
                <COUNTRY/>
                <COUNTY/>
                <DESCRIPTN/>
                <FAX index="1"/>
                <POSTALCODE/>
                <REGION/>
                <STATEPROVN/>
                <TAXJRSDCTN/>
                <TELEPHONE index="1"/>
                <URL/>
                <USERAREA/>
              </ADDRESS>
              <CONTACT>
                <NAME index="1"/>
                <CONTCTTYPE/>
                <DESCRIPTN/>
                <EMAIL/>
                <FAX index="1"/>
                <TELEPHONE index="1"/>
                <USERAREA/>
              </CONTACT>
            </PARTNER>
            <DOCUMNTREF>
              <DOCTYPE>INV</DOCTYPE>
              <DOCUMENTID>10005:21009</DOCUMENTID>
              <PARTNRID/>
              <PARTNRTYPE>Supplier</PARTNRTYPE>
              <DESCRIPTN/>
              <DOCUMENTRV/>
              <LINENUM/>
              <NOTES index="1"/>
              <SCHLINENUM/>
              <SUBLINENUM/>
              <USERAREA/>
            </DOCUMNTREF>
            <INVTAX>
              <AMOUNT qualifier="TAX" type="T" index="1">
                <VALUE>413</VALUE>
                <NUMOFDEC>2</NUMOFDEC>
                <SIGN>+</SIGN>
                <CURRENCY>USD</CURRENCY>
                <DRCR>D</DRCR>
              </AMOUNT>
              <AMOUNT qualifier="TAXBASE" type="T" index="1">
                <VALUE>5413</VALUE>
                <NUMOFDEC>2</NUMOFDEC>
                <SIGN>+</SIGN>
                <CURRENCY>USD</CURRENCY>
                <DRCR>D</DRCR>
              </AMOUNT>
              <QUANTITY qualifier="PERCENT">
                <VALUE/>
                <NUMOFDEC/>
                <SIGN/>
                <UOM/>
              </QUANTITY>
              <DESCRIPTN/>
              <LINENUM/>
              <TAXCODE/>
              <TAXJRSDCTN/>
              <USERAREA/>
            </INVTAX>
            <PYMTTERM>
              <AMOUNT qualifier="DISCNT" type="T" index="1">
                <VALUE/>
                <NUMOFDEC/>
                <SIGN/>
                <CURRENCY/>
                <DRCR/>
              </AMOUNT>
              <DATETIME qualifier="DISCNT" index="1">
                <YEAR/>
                <MONTH/>
                <DAY/>
                <HOUR/>
                <MINUTE/>
                <SECOND/>
                <SUBSECOND/>
                <TIMEZONE/>
              </DATETIME>
              <DATETIME qualifier="DUE" index="1">
                <YEAR>2013</YEAR>
                <MONTH>04</MONTH>
                <DAY>14</DAY>
                <HOUR>00</HOUR>
                <MINUTE>00</MINUTE>
                <SECOND>00</SECOND>
                <SUBSECOND>0000</SUBSECOND>
                <TIMEZONE>-0500</TIMEZONE>
              </DATETIME>
              <DATETIME qualifier="PYMTTERM" index="1">
                <YEAR>1952</YEAR>
                <MONTH>01</MONTH>
                <DAY>01</DAY>
                <HOUR>00</HOUR>
                <MINUTE>00</MINUTE>
                <SECOND>00</SECOND>
                <SUBSECOND>0000</SUBSECOND>
                <TIMEZONE>-0600</TIMEZONE>
              </DATETIME>
              <DESCRIPTN>Net Due in 30 Days</DESCRIPTN>
              <TERMID>30 NET</TERMID>
              <USERAREA>
                <AMOUNT qualifier="TOTAL" type="T" index="1">
                  <VALUE>5413</VALUE>
                  <NUMOFDEC>2</NUMOFDEC>
                  <SIGN>+</SIGN>
                  <CURRENCY/>
                  <DRCR>D</DRCR>
                </AMOUNT>
              </USERAREA>
            </PYMTTERM>
          </INVHEADER>
          <INVLINE>
            <AMOUNT qualifier="EXTENDED" type="T" index="1">
              <VALUE>50</VALUE>
              <NUMOFDEC/>
              <SIGN>+</SIGN>
              <CURRENCY/>
              <DRCR>D</DRCR>
            </AMOUNT>
            <OPERAMT qualifier="UNIT" type="T">
              <VALUE>5</VALUE>
              <NUMOFDEC/>
              <SIGN>+</SIGN>
              <CURRENCY/>
              <UOMVALUE>1</UOMVALUE>
              <UOMNUMDEC>0</UOMNUMDEC>
              <UOM/>
            </OPERAMT>
            <QUANTITY qualifier="ITEM">
              <VALUE>10</VALUE>
              <NUMOFDEC/>
              <SIGN>+</SIGN>
              <UOM/>
            </QUANTITY>
            <LINENUM>1</LINENUM>
            <DESCRIPTN>11GA SHEET STEEL HOT ROLLED-PICKLED-OILED COMMERCIAL QUALITY.</DESCRIPTN>
            <ITEM>11GA SHEET STEEL HOT ROLLED-PICKLED-OILED COMMERCIAL QUALITY.</ITEM>
            <ITEMTYPE/>
            <ITEMX>11HRPO</ITEMX>
            <OPENITEM/>
            <PROJACTVTY/>
            <UNIT>LB</UNIT>
            <UPC/>
            <USERAREA/>
            <DOCUMNTREF>
              <DOCTYPE>LINE</DOCTYPE>
              <DOCUMENTID>10005:21009:19019</DOCUMENTID>
              <PARTNRID/>
              <PARTNRTYPE>Supplier</PARTNRTYPE>
              <DESCRIPTN/>
              <USERAREA/>
            </DOCUMNTREF>
            <DOCUMNTREF>
              <DOCTYPE>SalesOrder</DOCTYPE>
              <DOCUMENTID>600813</DOCUMENTID>
              <PARTNRID/>
              <PARTNRTYPE/>
              <DESCRIPTN/>
              <USERAREA/>
            </DOCUMNTREF>
            <DOCUMNTREF>
              <DOCTYPE>PurchaseOrder</DOCTYPE>
              <DOCUMENTID>TEST123</DOCUMENTID>
              <PARTNRID>N/A</PARTNRID>
              <PARTNRTYPE>Customer</PARTNRTYPE>
              <DESCRIPTN/>
              <DOCUMENTRV/>
              <LINENUM/>
              <SCHLINENUM/>
            </DOCUMNTREF>
          </INVLINE>
        </PROCESS_INVOICE>
      </DATAAREA>
    </PROCESS_INVOICE_002>

  • No default attributes while Parsing XML document

    Hellow.
    I have such a problem:
    I have XML document that uses XSD-schema.
    In XSD-schema there is element that have two atributes:
    <xsd:complexType name = "El1">
          <xsd:attribute name = "atr1" xsd:default = "0" type = "xsd:boolean"/>
          <xsd:attribute name = "atr2" default = "0" type = "xsd:boolean"/>
    </xsd:complexType>And in XML document I write:
    <El1 atr1 = "1"/>According to the XSD-schema parser must add to El1 second attribute "atr2" with its default value because it has default value. But when I do such a code:
    factory = DocumentBuilderFactory.newInstance();
    builder = factory.newDocumentBuilder();
    doc = builder.parse(new File("file1.xml"));
    Element pEl;
    pEl = doc.getDocumentElement()
    NamedNodeMap Attribs = pEl.getAttributes();In the list of attributes "Attribs" - there is no attribute "attr1"!!!
    What I have to do???

    Hello All
    I am new to this parsing world. I have a doubt. I have an XML like
    <xml>
    <platform name = "windows">
    <computer>
    <hostname> hostname1 </hostname>
    <IPAddress>127.0.3.03 </IPAddress>
    </computer>
    <computer>
    <hostname> hostname2 </hostname>
    <IPAddress>127.0.3.04 </IPAddress>
    </computer>
    </platform>
    <platform name = "unix">
    <computer>
    <hostname> hostname6 </hostname>
    <IPAddress>127.0.3.08 </IPAddress>
    </computer>
    <computer>
    <hostname> hostname7 </hostname>
    <IPAddress>127.0.3.09 </IPAddress>
    </computer>
    </platform>
    </xml>
    If i want to get details about individual computer under each platform as a string how do i do that?
    Which parser would be ideal to be used DOM or SAX.

  • Building XML document error

    Hi.
    I am bulding a XML Document but i am getting this error: Error in building: Not logged in. Why? In my PC it works well, but when I try run on NT server I get the error.
    The class is very simple:
    import org.jdom.Document;
    import org.jdom.Element;
    import org.jdom.JDOMException;
    import org.jdom.input.SAXBuilder;
    import org.xml.sax.InputSource;
    public class ReadXmlDocument {
    private Document objXmlDocument;
    public void setXmlDocument() throws JDOMException {
    if ( getFileName() != null ) {
    SAXBuilder builder = new SAXBuilder();
    objXmlDocument = builder.build( getFileName() );
    } else {
    throw new NullPointerException("File name has not been setted");
    Thanks.

    For those that care, I found the solution/workaround.
    This is an actually bug........... http://developer.java.sun.com/developer/bugParade/bugs/4880236.html
    THe workaround is listen in the prroblem statement and is really simple.
    Instead of passing a File into the pass a FileInputStream
    CUSTOMER SUBMITTED WORKAROUND :
    /** Since the java 2 sdk java.io.* package is keen on UNC paths the following
    workaroung is quite simple and effective*/
    java.io.File fileHandler = new
    java.io.File("\\\\Network_name\\Share_name\\file_name.xml");
    javax.xml.parsers.DocumentBuilderFactory factory =
    DocumentBuilderFactory.newInstance();
    try {
    javax.xml.parsers.DocumentBuilder builder = factory.newDocumentBuilder();
    //Create a new FileInputStream from the file handler
    java.io.FileInputStream FIS = new java.io.FileInputStream(fileHandler);
    //The parse function takes an InputStream as well
    org.w3c.dom.Document xmlDoc = builder.parse(FIS);
    catch (SAXException sxe) {
    System.err.println("SaxException");
    } catch (ParserConfigurationException pce) {
    System.err.println("ParserConfigurationException");
    } catch (IOException ioe) {
    System.err.println("IOException");
    This worked for me with SAXBuilder too

  • XML document error - ELEARNING TRAINING MATERIAL

    Hi,
    Using SOLAR_LEARNING_MAP i was trying to create Training Material for a particular process (creating sales order as example). I attached a SAP Tutor also for that. The document is displaying from the tcode without any issue, but if i click OPEN BROWSER the following error is coming:
    The XML page cannot be displayed
    Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
    XML document must have a top level element. Error processing resource 'http://hostname.domain:8002/sap/bc/solman/defaul...
    Anybody tried this feature ?
    Thanks,
    Murali.

    Since no answer for long time, i am closing it now

  • Attribute "action" missing or wrong XML structure

    Does anyone know what's the problem of below XML format ?   I want to triggle a stored procedure in AS/400 from SAPXI after receiving records.  But the message "No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)" is found
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_t1 xmlns:ns0="http://cxx.xxx.hk/zxxxpxx/jdbc">
       <storedProcedurename>
          <action>EXECUTE</action>
          <table>LIBRARY.PROCNAME</table>
          <TRNX_TYPE IsInput="true" TYPE="CHAR">content 1</TRNX_TYPE>
          <TRNX_NO IsInput="true" TYPE="CHAR">content 2</TRNX_NO>
       </storedProcedurename>
    </ns0:MT_t1>

    Dear all,
    Thanks for your help and now I can submit a stored procedure via SAP XI by using below XML format.  I try to define two output parameters at the end of this XML. How to get the return value ? Should I define a response message type ? and what is the XML format ?
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_SYN_t1 xmlns:ns0="http://xxx.xxu.hk/zxxxpgs/jdbc">
       <update>
          <storedProcedurename action="EXECUTE">
             <table>LIBRARY.PANSYTEST</table>
             <TRNX_TYPE IsInput="TRUE" TYPE="CHAR">4</TRNX_TYPE>
             <TRNX_NO IsInput="TRUE" TYPE="CHAR">2</TRNX_NO>
             <ACTIN IsInput="TRUE" TYPE="CHAR">23</ACTIN>
             <RCRT_DATM IsInput="TRUE" TYPE="CHAR">3</RCRT_DATM>
             <RCRT_USER IsInput="TRUE" TYPE="CHAR">8</RCRT_USER>
             <STUD_ID IsInput="TRUE" TYPE="CHAR">8</STUD_ID>
             <AWD_SEQ IsInput="TRUE" TYPE="CHAR">6899</AWD_SEQ>
             <AW_PSDATE IsInput="TRUE" TYPE="CHAR">89</AW_PSDATE>
             <AW_PEDATE IsInput="TRUE" TYPE="CHAR">99</AW_PEDATE>
             <OUT_TRNX_TYPE IsOutput="TRUE" TYPE="CHAR">4</OUT_TRNX_TYPE>
             <OUT_TRNX_NO IsOutput="TRUE" TYPE="CHAR">2</OUT_TRNX_NO>
          </storedProcedurename>
       </update>
    </ns0:MT_SYN_t1>

  • JDBC Adapter error"no action attribute find"

    hi,
    thnks 
    i checked the structure for sending and receiving both for JDBC and file i m getting this error AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)</SAP:AdditionalText>

    Hi Aruna,
    I think you have missed the action attribute in the data structure.
    Please see the below structure.You need to map <b><i>'Action'</i></b> attribute with the kind of action you want to perform like select or update or delete etc.
    <root>
      <StatementName1>
    <dbTableName action=”UPDATE” | “UPDATE_INSERT”>
        <table>realDbTableName</table>
    <access>
    <col1>val1</col1>
    <col2>val2new</col2>
    </access>
    <key1>
    <col2>val2old</col2>
    <col4>val4</col4>
    </key1>
    </dbTableName>
      </StatementName1>
    </root>
    Hope that helps!!
    Regards
    Sunita

  • JDBC Receiver action Select

    Hello together
    I have some Problem with a JDBC Receiver Adapter. I want make a synchrony Process form a Web service to TeraData Database. The deployed driver are working and i can get Data with JDBC Sender Adapter.
    No I get the Error no action :
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Aufruf eines Adapters
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    But the structure are the same as on the sap help
    <M_VerlagSelect>
    <verlag action="SELECT">
      <table>verlag</table>
      <access>
      <Objekt />
      <Objekt_Bezeichnung />
      <Level />
      </access>
      <key1>
      <Verlag>10000</Verlag>
      <Level>O</Level>
      </key1>
    </pvg_usrObjekt>
    </M_VerlagSelect>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm">JDBC Adapter Receiver</a>
    Can some body help me?
    Best Regards Tom

    Hi,
    The problem is you have missed the STATEMENT tag,
    <M_VerlagSelect>
    <b><STATEMENT></b>
    <verlag action="SELECT">
    <table>verlag</table>
    <access>
    <Objekt />
    <Objekt_Bezeichnung />
    <Level />
    </access>
    <key1>
    <Verlag>10000</Verlag>
    <Level>O</Level>
    </key1>
    </pvg_usrObjekt>
    <b></STATEMENT></b>
    </M_VerlagSelect>
    I am assuming here that M_VerlagSelect is the ROOT tag of the strucutre.
    Also take a look at my blog,
    /people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    Regards,
    Bhavesh

Maybe you are looking for