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>

Similar Messages

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 - 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>יונסי רותי</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

Problem with XML SQL JDBC adapter

Hello All.
I have quite strange problem with my PI.
Whole scenario is SOAP -> JDBC, asynchronous. Everything works fine on DEV server. After transporting objects (using CTS) to QA env I'm getting this error:
JDBC Message processing failed, due to Error processing request in sax parser:
No 'action' attribute found in XML document
(attribute "action" missing or wrong XML structure)
But document seems to be correct. I've compared it to DEV server documents - they are identical. What could be wrong??
Document looks like this:
<ns2:BIPMessage xmlns:ns2="http://mynamespace.com/xi/sn"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<synchSlLok>
   <STATEMENTNAME>
     <SYNCH_SL_LOK ACTION="INSERT">
        <TABLE>SYNCH_SL_LOK</TABLE>
         <ACCESS>
            <ID_TRANS>22050</ID_TRANS>
            <ID_LOK>1234</ID_LOK>
            <ID_CBK>1000050911</ID_CBK>
            <NR_LOK>1234</NR_LOK>
            <OPIS_LOK>12312312312312</OPIS_LOK>
            <TYP>D</TYP>
            <OPERACJA>U</OPERACJA>
          </ACCESS>
      </SYNCH_SL_LOK>
    </STATEMENTNAME>
</synchSlLok>
</ns2:BIPMessage>
TIA
Best Regads
Maciej

Hi,
i was also facing the same error few days back in a JDBC -RFC-JDBC Synchronous scenario. In that scenario, i was using 2 modules in JDBC sender module tab. It was working fine. later i change polling interval and then i started getting same error. it happened coz of sequence of Module got changed somehow.
So please check in Receiver JDBC adapter and SOAP sender adapter CC if anything is changed. If this scenario is working in DEV as it is then it should work after transport.
Else have a look here
Re: attribute "action" missing or wrong XML structure
JDBC - No 'action' attribute found in XML document - error
Regards
Aashish Sinha
Edited by: Aashish Sinha on Mar 15, 2011 10:42 AM

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

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

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

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.

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 :: Missing Column Headings

Hi,
I was wondering if anyone has encountered this issue with the JDBC sender adapter. After executing the following SQL select statement:
SELECT rake_yem, rake_serial_no
FROM rt_rake_ore_wt_smy
WHERE reading_datetime > SYSDATE - 2
The JDBC Sender adapter returns the following XML structure:
<?xml version="1.0" encoding="utf-8"?>
<RakeOreWeightSummaryReadings>
<row>
    <>2006</>
    <RAKE_YEM>2226A</RAKE_YEM>
</row>
<row>
    <>2006</>
    <RAKE_YEM>2226B</RAKE_YEM>
</row>
<row>
    <>2006</>
    <RAKE_YEM>2229A</RAKE_YEM>
</row>
<row>
    <>2006</>
    <RAKE_YEM>2229B</RAKE_YEM>
</row>
<row>
    <>2006</>
    <RAKE_YEM>2223B</RAKE_YEM>
</row>
</RakeOreWeightSummaryReadings>
In this case, the first column heading is blank. This leads to an XML parsing problem, and hence it cannot be processed by SAP XI.
The incidence of blank columns appears to be inconsistent. i.e. It does not matter how many columns I select, as some columns will always be blank.
Any help would be greatly appreciated.
regards,
Carl Engel.

Hi Naveen,
No luck I'm afraid. I changed the SQL statement to:
SELECT rake_yem as RAKE_YEM, rake_serial_no as RAKE_SERIAL_NO FROM rt_rake_ore_wt_smy WHERE reading_datetime > SYSDATE - 2
And the JDBC adapter returned with:
<?xml version="1.0" encoding="utf-8"?>
<RakeOreWeightSummaryReadings>
     <row>
          <>2006</>
          <RAKE_YEM>2229A</RAKE_YEM>
     </row>
     <row>
          <>2006</>
          <RAKE_YEM>2229B</RAKE_YEM>
     </row>
     <row>
          <>2006</>
          <RAKE_YEM>2223B</RAKE_YEM>
     </row>
etc.....
Though I'm beginning to suspect that this problem may be associated between Oracle versions. The integration server is running Oracle 9.2 Client, and it is accessing a database running Oracle 7.3.3.5.
Though since the data is retrieved without issues, I'm still not sure. Is there any other form of diagnostic logs that I could examine re: this issue?
thanks,
Carl.

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 !!!

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" ?>
- 
- <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

Need Help...........JDBC Adapter

Hi All,
We have installed SAP on OS/400.
My scenario is IDOC XI JDBC.
We have created a File JDBCTEST , member JDBCTEST and Field JDBCTEST.
These are created under a lib QLGP.
Then I did a message mapping between the IDOC and JDBCTEST by concatenation function.
<b>IN THE JDBC ADAPTER CONFIGURATION I am getting the error
Value missing for mandatory configuration attribute table EOColumnName Ts</b>
In the EO JDBC ADAPTER Configuration, the DATABASE parameters:
DBTABLE:JDBCTEST
KEY COLUMN NAME:JDBCTEST
Is there anything wrong I am doing?
Any help is appreciated.
Thank you.

Hi Bhavesh,
My XML structure after testing the mapping is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1><ns1:TEST_MT xmlns:ns1="http://mri.com/xi/IDOC2JDBC"><STATEMENTNAME><JDBCTEST action="INSERT"><access><JDBCTEST>567,23,2345,MRI</JDBCTEST></access></JDBCTEST></STATEMENTNAME></ns1:TEST_MT></ns0:Message1>
I have tested by giving the PERSISTENCE as LOCAL,then intially there was no error but now I am getting the Transformation error.
TransformException error in xml processor class: Error processing request in sax parser: Error when executing statement for table/stored proc. 'JDBCTEST' (structure 'STATEMENTNAME'): java.sql.SQLException: [SQL0104] Token MOTOR was not valid. Valid tokens: ) ,.
Am I doing anything wrong in the JDBC Adapter Configuration or Message Mapping?
Please help me out with this issue.
Thank you in advance.

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" ?>
- 
- <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

JDBC adapter Stored Procedure error: parameter was not supplied

I am trying to call a Stored Procedure 'SP_FUSION_DEBMS_ADRC_MANAGE_CUSTOMER_ADDRESS' in our SQL Server database.
XI 3.0 Sp13
Jdbc Url: jdbc:microsoft:sqlserver://161.241.255.91:1433;databaseName=FusionDB;SelectMethod=Cursor
I am getting following error:
beging of error-----
Exception caught by adapter framework: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SP_FUSION_DEBMS_ADRC_MANAGE_CUSTOMER_ADDRESS' (structure 'Statement1'): java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Procedure 'SP_FUSION_DEBMS_ADRC_MANAGE_CUSTOMER_ADDRESS' expects parameter '@control_no', which was not supplied.
End of error-----
I have defined the field "control_no" in the interface defenition but I am not sure what causing this error, error message is mis-leading.
Please let me know if you have any hints/comments?
thanks,
Laxman molugu

Hi Laxman,
maybe you have checked this already...from the following help link....DECIMAL might be something you might want to try out....
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/frameset.htm
<i>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. If you use the optional <table> element, the value specified here is used as the stored procedure name. This enables you, for example, to define stored procedure names containing non-XML-compatible characters or characters that prevent them from being used in interface definitions in the Integration Builder/PCK. If specified, <table> must be the first element in the block within <dbTableName>.
The elements within the stored procedure are interpreted as parameters. They can optionally have the attribute isInput=1 (input parameter) or isOutput=1 (output parameter) or both (INOUT parameter). If both attributes are missing, the element is interpreted as an input parameter. The parameter names must be identical to those of the stored procedure definition.
The attribute type=<SQL-Datatype> , which describes the valid SQL data type, is mandatory for all parameter types (IN, OUT, INOUT).
The following SQL data types are supported:
INTEGER, BIT, TINYINT, SMALLINT, BIGINT, FLOAT, REAL, DOUBLE, NUMERIC, DECIMAL, CHAR, VARCHAR, STRING, LONGVARCHAR, DATE, TIME, TIMESTAMP, BINARY, VARBINARY, LONGVARBINARY, BLOB (input and output),CLOB (input and output), CURSOR (output; only in conjunction with the Oracle JDBC driver).</i>

JDBC adapter: action attribute is missing

Similar Messages

Maybe you are looking for