JDBC Adapter : no key element found

Hi experts,
while going through my Idoc to JDBC scenario, I am facing the following problem :
when I send an Idoc, in the RWB, it goes through the integration engine with no problem, but once in the adapter engine I got the following error:
Unable to execute statement for table or stored procedure. 'TBL_IN_TCLIENT' (Structure 'Statement1') due to java.sql.SQLException: FATAL ERROR document format: structure 'Statement1', no key element found
I have no idea where this could come from. My mapping works fine, my tests configuration as well.
Does anyone know where this might come from ?
Thanks,
Regards,
Jamal

Here is the xml of my target message type (hope its explicit):
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pomona/xi/in/ET/VT433_CLIENT_POUR_ET" targetNamespace="http://pomona/xi/in/ET/VT433_CLIENT_POUR_ET">
<xsd:element name="MT_VT433_CLIENT_SAP_ET" type="DT_VT433_CLIENT_SAP_ET"></xsd:element>
<xsd:complexType name="TBL_IN_ADV">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8c900f31649c11ddb2650050568b4d2e
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="table" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4a23cd40589311ddc780001b387a26b0
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="access">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64d157e411ddc522001b387a26b0
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Code" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
d34ec57058b611ddb303001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
numéro de client
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="OC" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64d257e411dda5c3001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
orga. com.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Canal" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64d357e411dd87ab001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
canal de distribution
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SA" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64d457e411dd8fd4001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
secteur d&apos;activité
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Branche" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64d557e411ddc175001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
branche
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TGR" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64d657e411dd94f5001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
niveau de TGR
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="GPV" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64d757e411dda36d001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
groupe de vendeur
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="GPV2" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64d857e411dd8110001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
libellé groupe de vendeur
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Agence" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64d957e411ddc186001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
agence commerciale
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Promo_Reg" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64da57e411dda201001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
type de promo régionale
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="action" type="xsd:string" use="required">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0f0f64d057e411ddaff8001b387a26b0
</xsd:appinfo>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:complexType name="TBL_IN_TCLIENT">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8c925922649c11dd88a20050568b4d2e
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="table" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6157d411ddcd78001b387a26b0
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="access">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6257d411ddbca7001b387a26b0
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Code" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6357d411ddc0dc001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
numéro de client
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Nom" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6457d411ddabb0001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
nom
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Ville" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6557d411dd9371001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
localité
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CP" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6657d411dda83c001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
code postal
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Adresse" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6757d411dd932a001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
rue et numéro de rue
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR1" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6857d411dd8bae001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
attribut 1
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR1T" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6957d411dd973d001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
désignation attribut 1
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR2" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6a57d411dd8441001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
attribut 2
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR2T" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6b57d411ddcffd001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
désignation attribut 2
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR3" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6c57d411ddb64e001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
attribut 3
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR3T" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6d57d411ddc982001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
désignation attribut 3
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR4" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6e57d411dd85f3001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
attribut 4
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR4T" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6f57d411ddbfe9001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
désignation attribut 4
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR5" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae7057d411ddb2b7001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
catégorie
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR5T" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae7157d411dda25c001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
désignation catégorie
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR6" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae7257d411ddab8b001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
sous-segment
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="KATR6T" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae7357d411dda876001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
désignation sous-segment
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Date" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae7457d411dd8e6d001b387a26b0
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Promo_Nat" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
17ecb6e057fb11dd8725001b387a26b0
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
type de promo nationale
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="action" type="xsd:string" use="required">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1be8ae6057d411dda41f001b387a26b0
</xsd:appinfo>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:complexType name="DT_VT433_CLIENT_SAP_ET">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8c8b5442649c11dda43d0050568b4d2e
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Statement1">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
74a974a057e611dd8490001b387a26b0
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="TBL_IN_TCLIENT" type="TBL_IN_TCLIENT">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
74a974a157e611ddc27c001b387a26b0
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Statement2" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
74a974a257e611dd9747001b387a26b0
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="TBL_IN_ADV" type="TBL_IN_ADV">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
74a974a357e611ddadb8001b387a26b0
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Similar Messages

  • JDBC Adapter Invalid level 4' found

    Hi all,
    I have the following XML messages send to a JDBC adapter and I get an Invalid Level 4' found:
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:ATL_JDBC_SQL_MAT_BOM_IN_MT xmlns:ns0="http://atlantis.com/material.bom">
    - <Statement1>
    - <dbTableName action="UPDATE_INSERT">
      <table>SAP_MATERIAL_BOM</table>
    - <access>
      <IDOC hasQuot="YES">0000000000003670</IDOC>
      <CODE hasQuot="YES">0183654</CODE>
      <ROWMATCODE hasQuot="YES">0183685</ROWMATCODE>
      <ROWMATQTY hasQuot="YES">8.000</ROWMATQTY>
      <CH_OK hasQuot="YES">0</CH_OK>
      </access>
      </dbTableName>
    - <key>
      <CODE hasQuot="YES">0183654</CODE>
      </key>
      </Statement1>
      </ns0:ATL_JDBC_SQL_MAT_BOM_IN_MT>
    Does anybody have an idea what might by wrong? Thanks.
    ....Socrates>>

    We are using XI3.0 sp18. The communication channel (JDBC RECEIVER) has the following error when receive the above XML message:
    11/9/06 3:21:49 PM 4c54613a06b71c409b86d27d7df80ce3 Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SAP_MATERIAL_BOM' (structure 'Statement1'): java.sql.SQLException: FATAL ERROR document format: invalid level 4' found (structure 'Statement1')
      11/9/06 3:21:49 PM 4c54613a06b71c409b86d27d7df80ce3 Processing started
    That's all the Info I have...

  • File to JDBC Adapter

    Hi All
    I am trying to configure File to JDBC Adapter to insert data in the database .I am having problem with message mapping.I  get the error with the statement field in mapping .Please can anyone let me know what mapping changes need to be done
    My Mapping is as follow
    SOURCE                                                          TARGET
    MT_INFO_DATA----
    >MT_JDBC_REC
    Header----
    > Statement
                                                               TABLENAME
    Update_insert----
    >Action
      T_EMPLOYEE(TABLE NAME)----
    > TABLE
                                                                   ACCESS
    EMP_NO----
    >EMP_NO
    COMP_ID----
    >COMP_ID
    BRANCH----
    >BRANCH
    Error: TransformException error in xml processor class: Error processing request in sax parser: Error when executing statement for table/stored proc. 'T_EMPLOYEE' (structure 'STATEMENT'): java.sql.SQLException: FATAL ERROR document format: structure 'STATEMENT', no key element found
    Please can anyone let me know what is to be mapped with the field STATEMENT.
    Thanks
    Amit

    Hi Bhavesh
    I did as suggested but still i am getting the following error
    Error: TransformException error in xml processor class: Error processing request in sax parser: Error when executing statement for table/stored proc. 'T_EMPLOYEE' (structure 'STATEMENT'): java.sql.SQLException: ORA-01861: literal does not match format string
    - 2007-05-24 06:21:17 IST: Processing started
    - 2007-05-24 06:07:48 IST: Error: TransformException error in xml processor class: Error processing request in sax parser: Error when executing statement for table/stored proc. 'T_EMPLOYEE' (structure 'STATEMENT'): java.sql.SQLException: FATAL ERROR document format: structure 'STATEMENT', no key element found
    - 2007-05-24 06:07:48 IST: Processing started
    - 2007-05-24 06:05:48 IST: Error: TransformException error in xml processor class: Error processing request in sax parser: Error when executing statement for table/stored proc. 'T_EMPLOYEE' (structure 'STATEMENT'): java.sql.SQLException: FATAL ERROR document format: structure 'STATEMENT', no key element found

  • 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

  • Specify Keys in Data Type for receiver JDBC adapter

    Hi guys,
    I have the following issue:
    In a proxy to JDBC scenario, I want to specify somehow the key values for the SQL statement in the data type that I define for the receiver JDBC adapter. Thus, I am using the following structure in data type:
    root
        Statement
               dbTable
               action
               table
               access
                      CustomerID
                      Name
                      HouseNo
               Key
                      CustomerID
    But in the SQL statement that is produced (I can see that in RWB, CC Monitoring, Audit Log), the "Key" segment is translated into "OR". E.g. UPDATE_INSERT ("A100" "Evaggelos Gkatzios" "El Alamein 19") OR ("A100")
    Do you have any ideas ?

    Hi,
    Its clear from the statement in RWB (in CC monitoring's auditlog) you are using UPDATE_INSERT as the action.
    Please correct me if this is OK. Now the interpretation of input xml file will be like this,
    If the input XML is in the following format
    <root>
    <Statement>
    <dbTable action=UPDATE_INSERT>
    <table>EXAMPLE</table>
    <access>
      <CustomerID>ABC</CustomerID>
      <Name>xyz</Name>
      <HouseNo>123</HouseNo>
    </access>
    <key>
      <CustomerID>DEF</CustomerID>
    </key>
    </dbTable>
    </Statement>
    </root>
    Resultant SQL after parsing the XML file will be,
    1. It will first check with the condition WHERE CustomerID = DEF. If it finds the record with this condition then it will update the record with CustomerID=ABC, Name =xyz & HouseNo=123.
    2. If it doesn't find any record with that CustomerID then, it will insert a new record with the same details.
    In auditlog, you will find two SQL statements like,
    1.UPDATE EXAMPLE SET CustomerID=ABC, Name =xyz & HouseNo=123 WHERE CustomerId=DEF
    2.INSERT INTO EXAMPLE VALUES(ABC,xyz,123)
    hope this has given clear information about your query,
    Regards,
    Soorya

  • JDBC Reciever key element

    I read that the <key> element of the Defined XML documents allows me to perform verious actions as part of the constructed SQL query.
    Does the <key> element can be used for non key values?
    For example to perform the isNull= TRUE  on a specific "non key field"
    Appriciate your advise.
    Nimrod.G

    Hi Nimrod,
    >>isNull=TRUE can be used with WHERE clauses
    Yes they can be used only with WHERE clause
    >>A statement with the action INSERT must have at least one <access> element. It cannot have a <key> element.
    As per help.sap.com. http://help.sap.com/saphelp_nw04/Helpdata/EN/2e/96fd3f2d14e869e10000000a155106/content.htm
    So you cannot use isNull with INSERT
    Regards
    Suraj

  • XI3 Jdbc Adapter

    Hello,
    we try to get access to a database like hsqlDB.
    If we want to use the Jdbc Adapter we get the folling error message:
    (com.sap.aii.af.ra.ms.api.DeliveryException: java.lang.Exception:
    database connection )
    We configurated the channel prober and deployed at the SDM the hsql driver jar exactly like it is recommended at the Xi3 documentation.
    Our database works fine so it must be a problem with the jdbc deployment.
    Some help would be nice!
    Here is the full Monitoring error::
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!-- Aufruf eines Adapters
    -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
    wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000"
    SOAP:mustUnderstand="1" wsu:Id="wsuid-main-
    92ABE13F5C59AB7FE10000000A1551F7">
    <SAP:MessageClass>SystemError</SAP:MessageClass>
    <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
    <SAP:MessageId>DAF75920-28E7-11D9-A5A9-000EA6B4552F</SAP:MessageId>
    <SAP:RefToMessageId>8F008041-83D0-D52F-E100-
    0000C0A88572</SAP:RefToMessageId>
    <SAP:TimeSent>2004-10-28T13:47:06Z</SAP:TimeSent>
    - <SAP:Sender>
    <SAP:Service>COM_PLBPRODUCTDB_T</SAP:Service>
    <SAP:Interface namespace="http://plecto.com/com/xibank/plb-
    products_db">insert_inb</SAP:Interface>
    </SAP:Sender>
    - <SAP:Receiver>
    <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
    <SAP:Service>COM_PLBPRODUCTDB_T</SAP:Service>
    <SAP:Interface namespace="http://plecto.com/com/xibank/plb-
    products_db">http_put</SAP:Interface>
    </SAP:Receiver>
    <SAP:Interface namespace="http://plecto.com/com/xibank/plb-
    products_db">insert_inb</SAP:Interface>
    </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    SystemErrorAckRequested="true" SOAP:mustUnderstand="1">
    <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
    </SAP:ReliableMessaging>
    - <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="PARSING">GENERAL</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException:
    java.lang.Exception: database connection missing</SAP:AdditionalText>
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack />
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2004-10-28T13:46:58Z" wasRead="false">
    <SAP:Engine type="IS">is.00.sapxi3</SAP:Engine>
    <SAP:Adapter
    namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
    <SAP:MessageId>8F008041-83D0-D52F-E100-0000C0A88572</SAP:MessageId>
    <SAP:Info>host:192.168.133.114:8000::remote-
    addr:192.168.133.72</SAP:Info>
    </SAP:Hop>
    - <SAP:Hop timeStamp="2004-10-28T13:46:58Z" wasRead="false">
    <SAP:Engine type="IS">is.00.sapxi3</SAP:Engine>
    <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
    <SAP:MessageId>8F008041-83D0-D52F-E100-0000C0A88572</SAP:MessageId>
    <SAP:Info>3.0</SAP:Info>
    </SAP:Hop>
    </SAP:HopList>
    - <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    SOAP:mustUnderstand="1">
    <SAP:Status>Error</SAP:Status>
    <SAP:Category>permanent</SAP:Category>
    </SAP:Ack>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Date>20041028</SAP:Date>
    <SAP:Time>154658</SAP:Time>
    <SAP:Host>sapxi3</SAP:Host>
    <SAP:SystemId>XI3</SAP:SystemId>
    <SAP:SystemNr>00</SAP:SystemNr>
    <SAP:OS>Linux</SAP:OS>
    <SAP:DB>ADABAS D</SAP:DB>
    <SAP:Language />
    <SAP:ProcStatus>000</SAP:ProcStatus>
    <SAP:AdapterStatus>000</SAP:AdapterStatus>
    <SAP:User>WSC</SAP:User>
    <SAP:TraceLevel>3</SAP:TraceLevel>
    <SAP:Logging>1</SAP:Logging>
    <SAP:LogSeqNbr>000</SAP:LogSeqNbr>
    <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
    <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
    <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
    <SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineEle
    mentId>
    <SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
    <SAP:QIdInternal />
    <SAP:CommitActor>A</SAP:CommitActor>
    <SAP:SplitNumber>0</SAP:SplitNumber>
    <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
    <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
    <SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine>
    <SAP:PlsrvExceptionCode />
    <SAP:EOReferenceRuntime type="TID" />
    <SAP:EOReferenceInbound type="TID" />
    <SAP:EOReferenceOutbound type="TID" />
    <SAP:MessageSizePayload>138</SAP:MessageSizePayload>
    <SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
    <SAP:PayloadSizeRequest>138</SAP:PayloadSizeRequest>
    <SAP:PayloadSizeRequestMap>336</SAP:PayloadSizeRequestMap>
    <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
    <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
    <SAP:Reorganization>INI</SAP:Reorganization>
    <SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
    <SAP:AdapterOutbound>AENGINE</SAP:AdapterOutbound>
    <SAP:RandomNumber>54</SAP:RandomNumber>
    <SAP:AckStatus>000</SAP:AckStatus>
    <SAP:SkipReceiverDetermination />
    </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
    <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134658.554363</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134658.574832</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134658.658371</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134658.675398</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134658.695891</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134658.713369</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134658.751765</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134658.7664</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134658.788744</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134704.21443</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134704.253736</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134704.278098</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134704.303583</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134706.126445</SAP:Timestamp>
    </SAP:RunTimeItem>
    </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    SOAP:mustUnderstand="1">
    <SAP:TraceLevel>Information</SAP:TraceLevel>
    <SAP:Logging>Off</SAP:Logging>
    </SAP:Diagnostic>
    - <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    - <SAP:OutboundBindingEntry version="30">
    <SAP:OutboundBindingObjectId>A486A55969723803BA4C52A896A8BF83</SAP:Outbo
    undBindingObjectId>
    <SAP:FromPartyName />
    <SAP:FromServiceName>COM_PLBPRODUCTDB_T</SAP:FromServiceName>
    <SAP:ToPartyName />
    <SAP:ToServiceName>COM_PLBPRODUCTDB_T</SAP:ToServiceName>
    <SAP:ToInterfaceName>insert_inb</SAP:ToInterfaceName>
    <SAP:ToInterfaceNamespace>http://plecto.com/com/xibank/plb-
    products_db</SAP:ToInterfaceNamespace>
    - <SAP:OutboundBindingAttributes>
    <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    </SAP:OutboundBindingAttributes>
    - <SAP:HeaderMapping>
    <SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    </SAP:HeaderMapping>
    - <SAP:ChannelEntry version="30">
    <SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    <SAP:ServiceName
    xmlns:SAP="http://sap.com/xi/XI/Message/30">COM_PLBPRODUCTDB_T</SAP:Serv
    iceName>
    <SAP:ChannelName
    xmlns:SAP="http://sap.com/xi/XI/Message/30">jdbc2</SAP:ChannelName>
    <SAP:AdapterName
    xmlns:SAP="http://sap.com/xi/XI/Message/30">JDBC</SAP:AdapterName>
    <SAP:AdapterNamespace
    xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System<
    /SAP:AdapterNamespace>
    <SAP:AdapterSWCV
    xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A11
    45A5</SAP:AdapterSWCV>
    <SAP:AdapterEngineType
    xmlns:SAP="http://sap.com/xi/XI/Message/30">AE</SAP:AdapterEngineType>
    <SAP:AdapterEngineName
    xmlns:SAP="http://sap.com/xi/XI/Message/30">af.xi3.sapxi3</SAP:AdapterEn
    gineName>
    <SAP:MessageProtocol
    xmlns:SAP="http://sap.com/xi/XI/Message/30">XML_SQL</SAP:MessageProtocol
    >
    <SAP:MessageProtocolVersion
    xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0.0527</SAP:MessageProtoco
    lVersion>
    <SAP:TransportProtocol
    xmlns:SAP="http://sap.com/xi/XI/Message/30">JDBC</SAP:TransportProtocol>
    <SAP:TransportProtocolVersion
    xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    <SAP:ChannelDirection
    xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
    <SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    <SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    <SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    <SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    - <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
    <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    </SAP:ChannelAttributes>
    </SAP:ChannelEntry>
    </SAP:OutboundBindingEntry>
    </SAP:OutboundBinding>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <Trace level="1" type="B" name="CL_HTTP_PLAIN_INBOUND">
    <Trace level="1" type="T">server-protocol HTTP/1.1</Trace>
    <Trace level="1" type="T">user-agent Java/1.4.2_04</Trace>
    <Trace level="1" type="T">host 192.168.133.114:8000</Trace>
    <Trace level="1" type="T">content-type application/x-www-form-
    urlencoded</Trace>
    <Trace level="1" type="T">content-length 138</Trace>
    <Trace level="1" type="T">remote-addr 192.168.133.72</Trace>
    </Trace>
    <Trace level="1" type="T">COMMIT is expected by application !</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!-- ************************************
    -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!-- ************************************
    -->
    <Trace level="3" type="T">XMB was called with external pipeline PID =
    ENTRY</Trace>
    <Trace level="3" type="T">Getting type of XMB...</Trace>
    <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
    <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
    <Trace level="3" type="T">Start pipeline found</Trace>
    <Trace level="2" type="T">Switch to external start pipeline PID =
    CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
    <Trace level="3" type="T">No triggers found. OK.</Trace>
    </Trace>
    <Trace level="1"
    type="T">****************************************************</Trace>
    <Trace level="1" type="T">* *</Trace>
    <Trace level="1" type="T">* *</Trace>
    <Trace level="1" type="T">XMB entry processing</Trace>
    <Trace level="3" type="T">system-ID = XI3</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = WSC</Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET</Trace>
    <Trace level="1" type="T">* *</Trace>
    <Trace level="1" type="T">* *</Trace>
    <Trace level="1"
    type="T">****************************************************</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!-- ************************************
    -->
    <Trace level="1" type="T">Message-GUID =
    8F00804183D0D52FE1000000C0A88572</Trace>
    <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
    <Trace level="1" type="T">QOS = BE</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!-- ************************************
    -->
    <Trace level="1" type="T">Get definition of external pipeline
    CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    <Trace level="3" type="T">External PLID = CENTRAL</Trace>
    <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="T">Corresponding internal pipeline
    SAP_CENTRAL</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">Pipeline attributes</Trace>
    <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
    <Trace level="3" type="T">ENABLE = 1</Trace>
    <Trace level="3" type="T">TRACELEVEL = 0</Trace>
    <Trace level="3" type="T">EXEMODE = A</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T" />
    <Trace level="3" type="T">Pipeline elements</Trace>
    <Trace level="3" type="T">ELEMPOS = 0001</Trace>
    <Trace level="3" type="T">PLSRVID =
    PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">FL_DUMMY = 0</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">ELEMPOS = 0002</Trace>
    <Trace level="3" type="T">PLSRVID =
    PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">FL_DUMMY =</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">ELEMPOS = 0003</Trace>
    <Trace level="3" type="T">PLSRVID =
    PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">FL_DUMMY =</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">ELEMPOS = 0004</Trace>
    <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">FL_DUMMY =</Trace>
    <Trace level="3" type="T" />
    <Trace level="3"type="T">ELEMPOS = 0007</Trace>
    <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">FL_DUMMY =</Trace>
    <Trace level="3"type="T" />
    <Trace level="3" type="T">ELEMPOS = 0008</Trace>
    <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
    <Trace level="3" type="T">FL_DUMMY =</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">ELEMPOS = 0009</Trace>
    <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">FL_DUMMY =</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-
    WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="2" type="T">Persisting original message</Trace>
    <Trace level="3" type="T">Message-Version = 000</Trace>
    <Trace level="3" type="T">Message version 000</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET Begin of
    pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET Start of
    pipeline service processing PLSRVID=
    PLSRV_RECEIVER_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service:
    PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service
    specification...</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">Pipeline service specification (table
    SXMSPLSRV)</Trace>
    <Trace level="3" type="T">PLSRVID =
    PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
    <Tracelevel="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
    <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG =</Trace>
    <Trace level="3" type="T">FL_DUMMY = 0</Trace>
    <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
    <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O
    N</Trace>
    <Trace level="1" type="T">Cache Content is up to date</Trace>
    <Trace level="2" type="T">Start without given receiver</Trace>
    <Trace level="2" type="T">Check conditions for rule line no.
    1</Trace>
    <Trace level="2" type="T">...valid Receiver w/o Condition: -
    COM_PLBPRODUCTDB_T</Trace>
    <Trace level="2" type="T">Number of Receivers:1</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET End of
    pipeline service processing PLSRVID=
    PLSRV_RECEIVER_DETERMINATION</Trace>
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-
    WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call</Trace>
    <Trace level="3" type="T">Message-Version = 001</Trace>
    <Trace level="3" type="T">Message version 001</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET Start of
    pipeline service processing PLSRVID=
    PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service:
    PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service
    specification...</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">Pipeline service specification (table
    SXMSPLSRV)</Trace>
    <Trace level="3" type="T">PLSRVID =
    PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
    <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG =</Trace>
    <Trace level="3" type="T">FL_DUMMY = 0</Trace>
    <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
    <Trace level="1" type="T">I N T E R F A C E - D E T ER M I N A T I O
    N</Trace>
    <Trace level="1" type="T">Cache Content is up to date</Trace>
    <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If)
    COM_PLBPRODUCTDB_T insert_inb</Trace>
    <Trace level="2" type="T">...valid InbIf without Condition:
    insert_inb</Trace>
    <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET End of
    pipeline service processing PLSRVID=
    PLSRV_INTERFACE_DETERMINATION</Trace>
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-
    WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call</Trace>
    <Trace level="3" type="T">Message-Version = 002</Trace>
    <Trace level="3" type="T">Message version 002</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET Start of
    pipeline service processing PLSRVID=
    PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service:
    PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service
    specification...</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">Pipeline service specification (table
    SXMSPLSRV)</Trace>
    <Trace level="3" type="T">PLSRVID =
    PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS =
    CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
    <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG =</Trace>
    <Trace level="3" type="T">FL_DUMMY = 0</Trace>
    <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-
    ENTER_PLSRV">
    <Trace level="3" type="T">Case handling for different plsrv_ids
    PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="2" type="T">got property produced by receiver
    determination</Trace>
    <Trace level="1" type="T">number of receivers: 1</Trace>
    <Trace level="1" type="T">Single-receiver split case</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET End of
    pipeline service processing PLSRVID=
    PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-
    WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call</Trace>
    <Trace level="3" type="T">Message-Version = 003</Trace>
    <Trace level="3" type="T">Message version 003</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET Start of
    pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service:
    PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service
    specification...</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">Pipeline service specification (table
    SXMSPLSRV)</Trace>
    <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
    <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG =</Trace>
    <Trace level="3" type="T">FL_DUMMY = 0</Trace>
    <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
    <Trace level="2" type="T">......attachment XI_Context not
    found</Trace>
    <Trace level="1" type="T">Interface Mapping
    http://plecto.com/com/xibank/plb-products_db http_to_productdb</Trace>
    <Trace level="3" type="T">Object ID of Interface Mapping
    F90D4E058EFD371E806F0C9E0307E1CE</Trace>
    <Trace level="3" type="T">Version ID of Interface Mapping
    6E2DC920107611D98FEAE42AC0A88572</Trace>
    <Trace level="3" type="T">Mapping Steps 1 JAVA
    com/sap/xi/tf/_http_to_jdbc_</Trace>
    <Trace level="2" type="T">Mode 0</Trace>
    <Trace level="3" type="T">Creating Java mapping
    com/sap/xi/tf/_http_to_jdbc_.</Trace>
    <Trace level="3" type="T">Load 6e2dc920-1076-11d9-8fea-e42ac0a88572,
    http://plecto.com/com/xibank/plb-products_db, -1,
    com/sap/xi/tf/_http_to_jdbc_.class.</Trace>
    <Trace level="3" type="T">Search com/sap/xi/tf/_http_to_jdbc_.class
    (http://plecto.com/com/xibank/plb-products_db, -1) in swcv 6e2dc920-
    1076-11d9-8fea-e42ac0a88572.</Trace>
    <Trace level="3" type="T">Loaded class
    com.sap.xi.tf._http_to_jdbc_</Trace>
    <Trace level="2" type="T">Call method execute of the application Java
    mapping com.sap.xi.tf._http_to_jdbc_</Trace>
    <Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
    <Trace level="3" type="T">Document start</Trace>
    <Trace level="3" type="T">Start tag [ns9:sql_insert]</Trace>
    <Trace level="3" type="T">Add raw attribute [
    xmlns:ns9="http://plecto.com/com/xibank/plb-products_db"]</Trace>
    <Trace level="3" type="T">Start tag [Statement1]</Trace>
    <Trace level="3" type="T">Start tag [PRODUCTTABLE]</Trace>
    <Trace level="3" type="T">Add attribute: [action]=[update]</Trace>
    <Trace level="3" type="T">Start tag [table]</Trace>
    <Trace level="3" type="T">Put value [productdb:PRODUCTTABLE]</Trace>
    <Trace level="3"type="T">Close tag [table]</Trace>
    <Trace level="3" type="T">Start tag [access]</Trace>
    <Trace level="3" type="T">Start tag [productCategoryId]</Trace>
    <Trace level="3" type="T">Put value [4444]</Trace>
    <Trace level="3" type="T">Close tag [productCategoryId]</Trace>
    <Trace level="3" type="T">Close tag [access]</Trace>
    <Trace level="3" type="T">Start tag [key]</Trace>
    <Trace level="3" type="T">Start tag [productid]</Trace>
    <Trace level="3" type="T">Put value [000001]</Trace>
    <Trace level="3" type="T">Close tag [productid]</Trace>
    <Trace level="3" type="T">Close tag [key]</Trace>
    <Trace level="3" type="T">Close tag [PRODUCTTABLE]</Trace>
    <Trace level="3" type="T">Close tag [Statement1]</Trace>
    <Trace level="3" type="T">Close tag [ns9:sql_insert]</Trace>
    <Trace level="3" type="T">Document end</Trace>
    <Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
    <Trace level="2" type="T">Java mapping com/sap/xi/tf/_http_to_jdbc_
    completed. (executeStep() of com.sap.xi.tf._http_to_jdbc_</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:47:04Z CET End of
    pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-
    WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call</Trace>
    <Trace level="3" type="T">Message-Version = 004</Trace>
    <Trace level="3" type="T">Message version 004</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
    <Trace level="1" type="Timestamp">2004-10-28T13:47:04Z CET Start of
    pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service:
    PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service
    specification...</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">Pipeline service specification (table
    SXMSPLSRV)</Trace>
    <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">PLSRVTYPE =</Trace>
    <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
    <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG =</Trace>
    <Trace level="3" type="T">FL_DUMMY = 0</Trace>
    <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
    <Trace level="1" type="T">processing the outbound binding</Trace>
    <Trace level="1" type="T">search outbound bindings</Trace>
    <Trace level="2" type="T">search outbound binding for:</Trace>
    <Trace level="2" type="T">... sender party =</Trace>
    <Trace level="2" type="T">... sender service =
    COM_PLBPRODUCTDB_T</Trace>
    <Trace level="2" type="T">... receiver party =</Trace>
    <Trace level="2" type="T">... receiver service =
    COM_PLBPRODUCTDB_T</Trace>
    <Trace level="2" type="T">... receiver interface namespace =
    http://plecto.com/com/xibank/plb-products_db</Trace>
    <Trace level="2" type="T">... receiver interface name =
    insert_inb</Trace>
    <Trace level="2" type="T">outbound binding found</Trace>
    <Trace level="2" type="T">outbound channel is:</Trace>
    <Trace level="2" type="T">... party =</Trace>
    <Trace level="2" type="T">... service = COM_PLBPRODUCTDB_T</Trace>
    <Trace level="2" type="T">... name = jdbc2</Trace>
    <Trace level="2" type="T">no header mapping defined</Trace>
    <Trace level="1" type="T">outbound bindings found</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:47:04Z CET End of
    pipelineservice processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-
    WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call</Trace>
    <Trace level="3" type="T">Message-Version = 005</Trace>
    <Trace level="3" type="T">Message version 005</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
    <Trace level="1" type="Timestamp">2004-10-28T13:47:04Z CET Start of
    pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service:
    PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service
    specification...</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">Pipeline service specification (table
    SXMSPLSRV)</Trace>
    <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
    <Trace level="3" type="T">ADRESSMOD = SD</Trace>
    <Trace level="3" type="T">P_CLASS =</Trace>
    <Trace level="3" type="T">P_IFNAME =</Trace>
    <Trace level="3" type="T">P_METHOD =</Trace>
    <Trace level="3" type="T">FL_LOG =</Trace>
    <Trace level="3" type="T">FL_DUMMY = 0</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">Unknown channel type: JDBC</Trace>
    <Trace level="3" type="T" />
    <Trace level="3" type="T">Pipeline service specification (table
    SXMSPLSRV)</Trace>
    <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
    <Trace level="3" type="T">ADRESSMOD = SD</Trace>
    <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
    <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG =</Trace>
    <Trace level="3" type="T">FL_DUMMY = 0</Trace>
    <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
    <Trace level="3" type="T">Channel for adapter engine: JDBC</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
    <Trace level="2" type="T">Get logon data for adapter engine
    (SAI_AE_DETAILS_GET): af.xi3.sapxi3</Trace>
    <Trace level="3" type="T">URL =
    http://sapxi3:50000/MessagingSystem/receive/AFW/XI</Trace>
    <Trace level="3" type="T">User = XIISUSER</Trace>
    <Trace level="3" type="T">Cached = X</Trace>
    <Trace level="3" type="T">Creating HTTP-client</Trace>
    <Trace level="3" type="T">HTTP-client: creation finished</Trace>
    <Trace level="3" type="T">Security: Basic authentication</Trace>
    <Trace level="3" type="T">Serializing message object...</Trace>
    <Trace level="3" type="T">HTTP-client: sending http-
    request...</Trace>
    <Trace level="3" type="T">HTTP-client: request sent</Trace>
    <Trace level="3" type="T">HTTP-client: Receiving http-
    response...</Trace>
    <Trace level="3" type="T">HTTP-client: response received</Trace>
    <Trace level="3" type="T">HTTP-client: checking status
    code...</Trace>
    <Trace level="3" type="T">HTTP-client: status code = 200</Trace>
    <Trace level="3" type="T">Deserializing message object...</Trace>
    <Trace level="3" type="T">HTTP-client: closing...</Trace>
    </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:47:06Z CET End of
    pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-
    WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call</Trace>
    <Trace level="3" type="T">Message-Version = 006</Trace>
    <Trace level="3" type="T">Message version 006</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-
    WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <!-- ************************************
    -->
    <Trace level="2" type="T">Persisting original message</Trace>
    <Trace level="3" type="T">Message-Version = 000</Trace>
    <Trace level="3" type="T">Message version 000</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </SAP:Trace>
    </SOAP:Header>
    - <SOAP:Body>
    <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:xlink="http://www.w3.org/1999/xlink"
    xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
    wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-
    5CABE13F5C59AB7FE10000000A1551F7" />
    </SOAP:Body>
    </SOAP:Envelope>

    Hi werner,
        You will have to check the jar file deployment and see if its deployed properly ...By the way which XI document did u refer too..
    -admin

  • CLOB Datatype with JDBC Adapter

    Hi,
    we try to fill a Clob Datatype to JDBC Database.
    We try 2 ways with the JDBC Adapter:
    action="SQL_DML" with an SQL Statment and $placeholders$
    But how can i say the key element that it is a CLOB type?
    He used this a VARCHAR and there a not more than 4k Chars allowed.
    second way is action="EXECUTE" to call a Stored Procedure, but there we got the error that CLOB type is an Unsupported feature.
    Any Idea?
    Regards,
    Robin
    Message was edited by: Robin Schroeder

    Ok i will check this...
    But i'm right when i say that the only way to fill CLOB Type is to use a Stored Procedure ?
    or is there any possibility to do this with action="SQL_DML" ?
    Regards,
    Robin

  • Receiver jdbc adapter:how to implement the insert or update action in a sql

    Hi,gurus:
    I'm using receiver jdbc adapter now.
    You know, we have to gave the action the value 'update' or 'insert',but in our case,the action is variant--update or insert.It decides whether the record exists in the outer database.
    Can stored procedure do this?If I use stored procedure,then must I create a stored procedure in the outer database?
    Or some other ways to solute my issue?
    THanks in advance.

    Hi
    Use Action UPDATE_INSERT .
    This action check if a record exist with same key value then update that record. In case no record with key value found in database then record inserted to database.
    look receiver structure
    http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

  • JDBC Adapter - DELETE operation not working in receiver backend system

    Hi All,
    In my scenario ,I want  to delete entire records of the table from one backend system.
    I have created the inbound message and after mapping it is as below:
      <?xml version="1.0" encoding="UTF-8" ?>
    <ns0:abc_delete xmlns:ns0="http://abc/xi/BACKEND/IB_IF_18/100">
    <STATEMENTNAME>
      <F12345 action="DELETE" />
      </STATEMENTNAME>
      </ns0:abc_delete>
    here F12345 is the table name.
    When I execute this scenario I get black and white flag in XI SXMB_MONI but in backend system (SQL Server) no records get deleted the table is as it is.

    Please have a look on this (same mentioned by Bhavesh)...
    http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/frameset.htm
    <b><b>  <StatementName3>
    <dbTableName action=”DELETE”>
    <key1>
    <col2>val2old</col2>
    <col4>val4</col4>     
    </key1>
    <key2>
    <col2>val2old2</col2>
    </key2>
    </dbTableName> 
      </StatementName3></b></b>
    &#9679;      action=DELETE
    Statements with this action cause existing table values to be deleted. One or more <key> elements formulate the condition for which table values are deleted. The names of <key> elements are arbitrary. Column values within a <key> element are combined with a logical AND; different <key> elements are combined with a logical OR.
    The corresponding SQL statement for StatementName3 in the example above is as follows:
    DELETE FROM dbTableName  WHERE ((col2=’val2old’ AND col4=’val4’) OR (col2=’val2old2’))
    The response document contains the following element:
    <delete_count>count</delete_count>
    If there is no <key> element, or if there is a <key> element but it is empty, then no condition is specified and the entire table is to be deleted. This may not be permitted by the configuration of the JDBC adapter for security reasons and will therefore result in an error during message processing and an appropriate error message.
    Thanks
    Farooq.

  • Strange behavior of JDBC Adapter

    Hello everybody!
    I found a pretty strange behaviour of JDBC Receiver Adapter during problems with network (big thanks to our Basis). According to the status in Adapter Engine, the message wasn't processed. In the database I can see these inserts. However, there are more lines in the XML than lines in the database. So, how it is possible that adapter commits only part of inserts. Logs and settings see below.
    My XML includes a SQL_DML statement and a few INSERT statements, each contains many inserts.
    It looks like that:
    <?xml version="1.0" ?>
    <MyMessage>
        <statement>
            <table1 action="SQL_DML">
                <access>here I delete old values</access>
            </table1>
        </statement>
        <statement>
            <table2 action="INSERT">
                <access>some data</access>
            </table2>
        </statement>
        <statement>
            <table3 action="INSERT">
                <access>some data</access>
            </table3>
        </statement>
    </MyMessage>
    Part of adapter log is here:
    Information
    Message successfully put into the queue
    Information
    The message was successfully retrieved from the receive queue
    Information
    Message status set to DLNG
    Information
    Delivering to channel: Adapter_Name
    Information
    MP: processing local module localejbs/CallSapAdapter
    Information
    Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
    Information
    JDBC Adapter Receiver Channel Adapter_Name: Processing started; party / service BS
    Information
    Database request processed successfully
    Error
    MP: exception caught with message Ack handling failed: creation of messageFactory failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection JDBC_http://sap.com/xi/XI/System is currently not started.
    Error
    Exception caught by adapter framework: Ack handling failed: creation of messageFactory failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection JDBC_http://sap.com/xi/XI/System is currently not started.
    Error
    Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Ack handling failed: creation of messageFactory failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection JDBC_http://sap.com/xi/XI/System is currently not started.
    Information
    Message status set to WAIT
    Information
    The asynchronous message was successfully scheduled to be delivered at ...
    Information
    Message status set to TBDL
    Information
    Retrying to deliver message to the application. Retry: 1
    Information
    The message was successfully retrieved from the receive queue
    Information
    Message status set to DLNG
    Information
    Delivering to channel: Adapter_Name
    Information
    MP: processing local module localejbs/CallSapAdapter
    Information
    Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
    Information
    JDBC Adapter Receiver Channel Adapter_Name: Processing started; party / service BS
    Error
    Unable to execute statement for table or stored procedure. 'Table' (Structure 'statement') due to com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'fields'. Cannot insert duplicate key in object 'Table'. The duplicate key value is (field values).
    Error
    JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'Table' (structure 'statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'fields'. Cannot insert duplicate key in object 'Table'. The duplicate key value is (field values).
    Error
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'Table' (structure 'statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'fields'. Cannot insert duplicate key in object 'Table'. The duplicate key value is (field values).
    Error
    Exception caught by adapter framework: Error processing request in sax parser: Error when executing statement for table/stored proc. 'Table' (structure 'statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'fields'. Cannot insert duplicate key in object 'Table'. The duplicate key value is (field values).
    Error
    Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'Table' (structure 'statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'fields'. Cannot insert duplicate key in object 'Table'. The duplicate key value is (field values).
    Adapter settings:
    Maximum concurrency: 20
    Persistence: Local
    Conflict Resolution: Redo
    Advanced Mode: On
    Number of Retries of Database Transaction on SQL Error: 0
    Transaction Isolation Level: serializable

    Dear All,
    Follow the steps below to resolve the "Connection JDBC_http://sap.com/xi/XI/System is currently not started." issue:
    1. Log in to NWA
    2. Navigate to Operations -> Systems -> Start & Stop
    3. Click on Java Services tab
    4. Search  the service Service "XPI Adapter: JDBC"
    5. Select the service XPI Adapter: JDBC and click on Restart button
    With the restart of JDBC Service in NWA, the channels should start working properly
    Regards,
    Shreyansh

  • Access an Oracle DB using JDBC adapter

    Hi, I'm trying to make an simple test for checking if the connection between XI and Oracle DB is working fine and following the weblog nr. 2018 ( Save Time with generalized JDBC datatypes ) i've made my structures in order to achived that. I've declared the field action as SELECT than the table name ... and in the IB set the needed configurations. So when i exec my interface i've got the black/white flag bur if i look at the adapter engine i see that the JDBC adapter is achieved but i got 2 errors " <b>No 'action' attribute found in XML document('action' attribute missing or wrong XML structure)</b> and <b>Exception caught by adapter framework: error processing request in sax parser: No 'action' attribute found in XML document('action' attribute missing or wrong XML structure)</b>. Can anybody provide me some help ??? Thanks in advance.
    JMMatos

    Hi,
    This is how my DT looks like:
    Structure           Category      Type
    Data_JDBCReceiver   Complex Type
      Statement
        Table_name
          action        Attribute
          table
        access                        Data_FileSender
          cod
        key                           Data_FileSender
          cod
    This is my DT and in MM i fill field <b>action</b> with constant value(SELECT/INSERT), field <b>table</b> with the name of the corresponding DB table, fields <b>access/key</b> with constant value(empty). At this moment, I got the following error <b>Exception caught by adapter framework: Error processing request in sax parser: Error when executing statement for table/stored proc. 'v01_sap_xi' (structure 'Statement'): java.sql.SQLException: FATAL ERROR: Column 'cod' does not exist in table 'v01_sap_xi'</b>; according with the people responsible for the DB this column named <b>cod</b> does really exist !! What can I do ?!?!? Some help will be ... Thanks !!!

  • Action attribute in jdbc adapter

    Hi
    I have been working on jdbc adapter. Till now I have been using action attribute in jdbc receiver adpater for insertion only. Now I'd like to know what are the possible values can u we in "Action"?

    Hi,
    s the attribute action with the value INSERT, UPDATE, UPDATE_INSERT, DELETE, or SELECT. If you use the optional <table> element, the value specified is used as a database table name.
    1.Action=UPDATE
      Statements with this action cause existing table values to be updated. Therefore, the statement corresponds to an SQL UPDATE statement.
    The corresponding SQL statement for StatementName1 in the example above is as follows:
    UPDATE dbTableName  SET col1=u2019val1u2019, col2=u2019val2newu2019 WHERE ((col2=u2019val2oldu2019 AND col4=u2019val4u2019) OR (col2=u2019val2old2u2019))
    2. Action=UPDATE_INSERT
    The statement has the same format as for the UPDATE action. Initially, the same action is executed as for UPDATE. If no update to the database table can be made for this action (the condition does not apply to any table entry), values of the table described in the <access> element are inserted in accordance with the description of the action INSERT. <key> elements are ignored in this case.
    3.Action=DELETE
    Statements with this action cause existing table values to be deleted. One or more <key> elements formulate the condition for which table values are deleted.
    The corresponding SQL statement for StatementName3 in the example above is as follows:
    DELETE FROM dbTableName  WHERE ((col2=u2019val2oldu2019 AND col4=u2019val4u2019) OR (col2=u2019val2old2u2019))
    4.action=SELECT
    Statements with this action cause existing table values to be selected. Therefore, the statement corresponds to an SQL SELECT statement.
    5.Action=EXECUTE
    Statements with this action result in a stored procedure being executed. The name of the element is interpreted as the name of the stored procedure in the database.
    regards,
    ganesh.

  • Sync Receiver JDBC Adapter

    Hi All,
    I was trying to make a synchronous call to a receiver jdbc adapter with the help of
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3928. [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    I am getting the following error in jdbc adapter.
    <i>com.sap.aii.af.ra.ms.api.DeliveryException: ERROR:Processing request: Error when executing statement for table/stored proc. 'MISDetails': java.sql.SQLException: FATAL ERROR document format: structure 'STATEMENT', key element 'FiscalYear' contains no values</i>
    My Source message is
    <i><?xml version="1.0" encoding="UTF-8"?>
    <ns:MT_FILE_OUT xmlns:ns="urn:ters">
      <REQUEST>
        <FISCALYEAR>2007</FISCALYEAR>
        <YEARMONTH>1</YEARMONTH>
        <OPERATION>EQ</OPERATION>
      </REQUEST>
    </ns:MT_FILE_OUT></i>
    And JDBC request message is ..
    <i><?xml version="1.0" encoding="UTF-8"?>
    <ns:MT_JDBC_REQ xmlns:ns="urn:ters">
    <STATEMENT>
    <TABLENAMEACTION="SELECT">
    <TABLE>MISDetails</TABLE>
    </TABLENAME>
    <ACCESS>
    <FiscalYear> </FiscalYear>
    <YearMonth> </YearMonth><ProductCode> </ProductCode><TargetVolume> </TargetVolume>
    </ACCESS>
    <KEY>
    <FiscalYear compareOperation="EQ">2007</FiscalYear>
    </KEY>
    </STATEMENT>
    </ns:MT_JDBC_REQ></i>
    Regards,
    Sumit

    Sumit, the problem is that </TABLENAME> is closed ealier than necessary.
    This is how the JDBC datatype should be,
    <?xml version="1.0" encoding="UTF-8"?>
    <ns:MT_JDBC_REQ xmlns:ns="urn:ters">
    <STATEMENT>
    <TABLENAME ACTION="SELECT">
    <TABLE>MISDetails</TABLE>
    <ACCESS>
    <FiscalYear> </FiscalYear>
    <YearMonth> </YearMonth>
    <ProductCode> </ProductCode>
    <TargetVolume> </TargetVolume>
    </ACCESS>
    <KEY>
    <FiscalYear compareOperation="EQ">2007</FiscalYear>
    </KEY>
    <b></TABLENAME></b>
    </STATEMENT>
    </ns:MT_JDBC_REQ>
    The TABLE, ACCESS and KEY come under the TABLENAME tag.
    Regards,
    Bhavesh

  • JDBC adapter to SAP: select & join from multiple tables ???

    Hello,
    I have a task to get an aggregating information from two tables and send it into SAP.
    I use XI JDBC sender adapter to access to MSSQL DB.
    I know how to construct SQL quiery:
    (something like that)
    SELECT  table1.Date  SUM(table1.sum) from table1
    INNER JOIN table2
    ON table1.Number = table2.Number
    But I don't understand how to construct  Data Type for this complex select operator?
    How does it look like?
    Where to store and how to map the selected data?
    Please give me an example or an advice.
    Thank You.

    Hi,
    Use your structure like this.
    <StatementName4>
    <dbTableName action=”SELECT”>
    <table>realDbTableName</table>
    <access>
    <col1/>
    <col2/>
    <col3/>
    </access>
    <key1>
    <col2>val2old</col2>
    <col4>val4</col4>
    </key1>
    <key2>
    <col2>val2old2</col2>
    </key2>
    </dbTableName>
    </StatementName4>
    action=SELECT
    Statements with this action cause existing table values to be selected. Therefore, the statement corresponds to an SQL SELECT statement.
    The <access> block contains the column names to be selected, a <key> element contains the columns whose values must be identical with the specified value to get the new column values. The name of the <key> element is arbitrary. Column values within a <key> element are combined with a logical AND; different <key> elements are combined with a logical OR.
    A statement with the action SELECT must have exactly one <access> element. The number of <key> elements with arbitrary names is not restricted.
    The corresponding SQL statement for StatementName4 in the example above is as follows:
    SELECT col1,col2,col3 FROM dbTableName WHERE ((col2=’val2old’ AND col4=’val4’) OR (col2=’val2old2’))
    If there is no <key> element, or if there is a <key> element but it is empty, then no condition is specified and the entire table is to be selected. This may not be permitted by the configuration of the JDBC adapter for security reasons and will therefore result in an error during message processing and an appropriate error message.
    The response document contains the result of the action in XML format as follows:
    <row>
    <column1>value11</column1>
    <column2>value12</column2>
    </row>
    <row>
    <column1>valueN1</column1>
    <column2>valueN2</column2>
    </row>
    This will help you.
    regards
    Aashish Sinha
    PS : reward points if helpful

Maybe you are looking for

  • How do you apply multiple songs or audio clips to one slideshow?

    I created a large project, 200+ slides. I wanted to to use multiple songs so when one ends a new one comes on. Everytime a dragged a new audio clip from Itunes it just replaced the other song. 

  • Web gallery does not work

    Hi, Problem that I have ... is  difficult to explain so picture : As you see when I click under the web gallery  and I selected a flash galery or imported web galley (exemple here is airtight simpleviewver...) ... the screen in the middle box keeping

  • Just need some simple stats :)

    I've been using Microsoft's "Excel Lite" program for a few years. I don't even know what it's called, but its performance is more limited than Excel, which I've never used. I've never used a mathematical formula in a spreadsheet. All I do is insert d

  • What are the Includes in Function Module...? if the fuction group IS ZSJ_FC

    What are the Includes in Function Module...? if the fuction group IS ZSJ_FC..? How can I access SAP through Internet....? Moderator Message: Interview-like question(s). Thread locked. Edited by: Suhas Saha on Sep 30, 2011 11:14 AM

  • Field extensions in Privat Account and Corporate Account

    Hi, is it a bug or a feature that there is no distinction between the Overview views of Corporate and Private Accounts with regard to extension fields? Background: I try to show different extension fields for Corporate and Private Accounts. Unfortuna