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

Similar Messages

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

Jdbc reciever error

hi,
My scenario is rfc to jdbc.Reciever shows the follwing error.
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'TBLTSEMPLOYEES_INTRA' (structure 'StatementName'): java.sql.SQLException: FATAL ERROR document format in structure 'StatementName': expected 'access' tag(s) not found.
Pls help me.

Hi,
This is your structure.
<?xml version="1.0" encoding="UTF-8"?>
<ns1:mes_emp_info xmlns:ns1="http://saphrandhrmas.com">
<StatementName>
<TBLTSEMPLOYEES_INTRA action="INSERT">
<access>
<EMPID>
</EMPID>
<REASON>
</REASON>
<CATEGORY>
</CATEGORY>
</EMP</access>
</TBLTSEMPLOYEES_INTRA>
</StatementName>
</ns1:mes_emp_info>
<?xml version="1.0" encoding="UTF-8"?>
<ns1:mes_emp_info xmlns:ns1="http://saphrandhrmas.com">
<StatementName>
<TBLTSEMPLOYEES_INTRA action="INSERT">
<access>
<EMPID></EMPID>
<REASON></REASON>
<CATEGORY></CATEGORY>
<EMP></EMP>
</access>
</TBLTSEMPLOYEES_INTRA>
</StatementName>
</ns1:mes_emp_info>
you are missing the tag <EMP> .
Also put some values in the parameters,
like,
<?xml version="1.0" encoding="UTF-8"?>
<ns1:mes_emp_info xmlns:ns1="http://saphrandhrmas.com">
<StatementName>
<TBLTSEMPLOYEES_INTRA action="INSERT">
<access>
<EMPID>001</EMPID>
<REASON>xyz</REASON>
<CATEGORY>abc</CATEGORY>
<EMP>abcdef</EMP>
</access>
</TBLTSEMPLOYEES_INTRA>
</StatementName>
</ns1:mes_emp_info>
The resultant query will be,
insert into TBLTSEMPLOYEES_INTRA values('001','xyz','abc','abcdef')
Assuming all the fields are String type.
Urs,
Soorya.

ERROR IN ORACLE STORED PROCEDURE in JDBC RECIEVER

Hi all
i have an FILE2JDBC2FILE sync scenario.have configured this w/o BPM.i need to call an stored procedure which will return me the output in the outpur parameters.input out put parametrs of the stored procedure are.
     p_api_version               IN NUMBER
    ,p_init_msg_list             IN NUMBER DEFAULT EBS_ECOM_UTILS_PUB.G_TRUE
    ,p_ebs_place_in_t     IN p_ebs_place_in_t(sql TABLE TYPE )
    ,p_ebs_std_call_o     IN ebs_std_call_oty(sql TABLE TYPE )
    ,x_return_status            OUT VARCHAR2
    ,x_msg_count                OUT NUMBER
    ,x_msg_data                 OUT ebs_message_tty
    ,x_row_count                OUT NUMBER
    ,x_ebs_place_out_t      OUT ebs_place_out_toty(sql TABLE TYPE );
where
p_ebs_place_in_t is of type p_ebs_place_in_t which has 2 fields MDM_SYSTEM_REF,EMAIL_ADDR and START_DATE
p_ebs_std_call_o is of table type ebs_std_call_oty which has 2 fields WORK_GRP_ID and DEBUG_MODE
In XI i am passing the arguments in the following fashion to ORACLE (JDBC reciever adapter)
<p_api_version isInput="true" type="integer">1</p_api_version>
<p_init_msg_list isInput="true" type="integer">1</p_init_msg_list>
<p_ebs_place_in_t isInput="true" type="CHAR">
<MDM_SYSTEM_REF isInput="true" type="CHAR">MDM-237</MDM_SYSTEM_REF>( this is a field in p_ebs_place_in_t )
<EMAIL_ADDR isInput="true" type="CHAR"></EMAIL_ADDR>>(this is a field in p_ebs_place_in_t )
<START_DATE isInput="true" type="date"/>06-OCT-2009 00:00:00</START_DATE>>(this is a field in p_ebs_place_in_t )
</p_ebs_place_in_t>
<p_ebs_std_call_o isInput="true" type="CHAR">
<WORK_GRP_ID isInput="true" type="integer">95714</WORK_GRP_ID>
<DEBUG_MODE isInput="true" type="integer">5</DEBUG_MODE>
</p_ebs_std_call_o>
<x_return_status isOutput="true" type="CHAR"></x_return_status>
<x_msg_count isOutput="true" type="integer"></x_msg_count>
<x_msg_data isOutput="true" type="CHAR"></x_msg_data>
<x_row_count isOutput="true" type="integer"></x_row_count>
<x_ebs_place_out_t isOutput="true" type="CHAR">
</x_ebs_place_out_t>
i am gettng the below error when i am trying to post th message from RWB
Error when executing statement for table/stored proc. 'APPS.EBS_CUSTOMER_SERVICE_PUB.MAINTAIN_PLACE' (structure 'StatementName1'): java.sql.SQLException: ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to 'MAINTAIN_PLACE' ORA-06550: line 1, column 7: PL/SQL: Statement ignored .
please suggest..
Edited by: Rohan Patil on Jun 13, 2010 12:55 AM

HI Praveen,
thanks for your reply.
my stored procedure has input and output parameters both.
and in XI i have created the data type for both isInput(passedwith all the required values) and isOutput(passed the null values)
is this correct..?or should i take only isInput parameters in the data type?
do i need to take the isOutput also in the datatype?my stored procedure will return the output in the output parametrs.
can i take only 1 or 2 output paraetrs as there are 4 to 5 output parameters for my sotred procedure.?
and how will my response data type to send the output of the stored procedure to the FILE sustem.should it be also in the statement form?
and also would like to know..some of my isInput parameters to the stored procedure has the table type structure as the input parameters.now my question is i should i declare them in my data type?
can you please elaborate.

Insert query in JDBC Reciever adapter!!!

Hi All,
We have an interface in which we are inserting data in Oracle server using JDBC Reciever Adapter.
The interface ends up in error on adapter engine level whenever the we are sending long data in one of the field of target structure. The error which we get in communication channel monitoring is that "String too long", on googling i found that in oracle they solve such problem by making the field data type as CLOB.
Thus can we define target structure field of CLOB type so that while inserting the data in Oracle server we never face the issue of this long string.
Thanks

>
Arpit Seth wrote:
> Hi All,
>
> We have an interface in which we are inserting data in Oracle server using JDBC Reciever Adapter.
> The interface ends up in error on adapter engine level whenever the we are sending long data in one of the field of target structure. The error which we get in communication channel monitoring is that "String too long", on googling i found that in oracle they solve such problem by making the field data type as CLOB.
>
> Thus can we define target structure field of CLOB type so that while inserting the data in Oracle server we never face the issue of this long string.
>
> Thanks
if the field contains very large data then yes, defining the target field in Oracle as a CLOB will solve your issue.
http://www.herongyang.com/jdbc/MySQL-CLOB-Overview.html

JComboBox Unable to recieve key events

Hello,
I have a Table which contains multiple editors and multiple renderers for different items that may or may not be added in the table. I have added a KeySelectionManager to the ComboBox class that I have defined. When I add this Combo box to a Frame/Panel listener recieves key board events, but when I add the combox box to a table which has other components and listeners, the combo box listener is not getting any events.
How do I tell table to send the event to combo box?
Praveen

I didnot write the code. I am trying to add some enhancements to it. Basically I want the Combo box to scroll as I enter the text.
Coming to your question...All the data I have is in another class and I am using the table.setModel(obj) where obj is the Object in which I have data. After setting the model, I am registering the editors and renderers for table.
Please point to me any good tutorial on how the setModel works. I can see that while initializing the editors, there is a call made to the ComboBox class. May be this is where the ComboBox is getting created.
Does this reply makes some sense?
Thanks for your reply,
Praveen

JPanel cannot recieve Key Events?

Hi. I'm trying to make a simple game, which recieves input from the arrow keys and spacebar. The drawing is done inside a paintComponent() method in a JPanel. Therefore, the key events should also be handled in the same JPanel. I can call the addKeyListener() method on the JPanel, but it does not recieve key events. I've tried calling setFocusable(true) but it doesn't seem to do anything. If JPanel can't recieve key events (it can recieve mouse events fine), I have to handle the events in the JFrame, which I'm hesitant to do. My book does it in an applet and applets can recieve key events fine, but I want to make an application.
No working source code here, try to figure out what I'm saying.
Thanks.

Please help me. I did help you. I gave you a link to the tutorial that shows that proper way to do this.
All Swing components use Key Bindings so you might as well take the time to understand how they work.
Anyway, based on your vague description of the problem we can't help you because we don't know the details of your code.

HT4972 how to back up all the key element of my ipad touch?

how to back up all the key element of my ipad touch?

What exactly do you mean by all key elements? You can check this page on how to back up your iPod touch.
http://support.apple.com/kb/HT1766

JDBC RECIEVER ADAPTER Configuration

Hi,
i'm doing one scenario.I'm sending sap data to Oracle 9i database.Pls give reciever jdbc structure.which structure i follws for oracle 9i.Pls this is urgent.Pls help me.
Thanks
Ravi

Hi Ravi ,
Please show us the input file format which you are trying to store in the Oracle DB.
The format should look like any of these statement formats,
<root>
<StatementName1>
<dbTableName action=u201DUPDATEu201D | u201CUPDATE_INSERTu201D>
    <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>
<StatementName2>
<dbTableName action=u201DINSERTu201D>
<table>realDbTableName</table>
<access>
<col1>val1</col1>
<col2>val2</col2>
</access>
<access>
<col1>val11</col1>
</access>
</dbTableName>
</StatementName2>
<StatementName3>
<dbTableName action=u201DDELETEu201D>
<key1>
<col2>val2old</col2>
<col4>val4</col4>
</key1>
<key2>
<col2>val2old2</col2>
</key2>
</dbTableName>
</StatementName3>
<StatementName4>
<dbTableName action=u201DSELECTu201D>
    <table>realDbTableName</table>
<access>
<col1/>
<col2/>
<col3/>
</access>
<key1>
<col2>val2old</col2>
<col4>val4</col4>
</key1>
<key2>
<col2>val2old2</col2>
</key2>
</dbTableName>
</StatementName4>
<StatementName5>
<storedProcedureName action=u201D EXECUTEu201D>
    <table>realStoredProcedureeName</table>
<param1 [isInput=u201Dtrueu201D] [isOutput=true] type=SQLDatatype>val1</param1>
</storedProcedureName >
</StatementName5>
<StatementName6>
<anyName action=u201D SQL_QUERYu201D | u201CSQL_DMLu201D>
<access>SQL-String with optional placeholder(s)</access>
<key>
<placeholder1>value1</placeholder1>
<placeholder2>value2<placeholder2>
</key>
</anyName >
</StatementName6>
</root>
Check this once and correct yourself.
Or please give us the sample format which you are configuring.
Urs,
Soorya

JDBC Reciever issue with Place Holders

Hi,
I am working with Idoc to JDBC scenario.
Where the table field names contains $ value in it.
Example: T$value1, T$value2,T$valuse3 and ... so on.
The special characters would not be accepted in datatype elements in XI.
I found some details working on this, Which require the SQL statements. Can any of you let me know the SQL statements for the below contest given in help.sap.com for JDBC receiver.
block can be omitted or left empty. In both cases, you must not select the Key Tags Mandatory field in the configuration, as this will cause runtime errors.

Hey Manoj,
I was working with a scenario where a single quot was converted to &apos during mapping as this was a special character in xml string. But when i completed the scenario with jdbc receiver it worked successfully.
So in your case, can you please try and finish of the scenario and see if there is an error or not??
Also i saw this in the SAP docuumentation. This mite of of help 2 u...
Column Name Delimiter
Depending on the database being used, column names can be enclosed by a special delimiter character, for example, if the names can contain special characters (such as ). This character can be specified at this point. The default setting is no delimiter character. If a character occurs that is invalid for the database being used, the adapter triggers an error message (an SQL exception) concerning the SQL syntax that is generated by the database.

JDBC reciever for SQL??

Hi everyone,
I have configured a scenario RFC-> XI -> JDBC to update the SQL database.
Everything is fine, channels r working good. But am not able to update SQL database.
When i thorougly checked the communication channel, the status for JDBC adapter is green but there is no LOG.. (No data).
Can anyone help me in this???
regards,
Vijay Vikram

Dear Vijay,
please share the xml after technical routing .
Are you using correct key combination for update records.......?
Is it update or update/insert...?
thanks and regards,
Anup Banerjee

How to recieve key events

Hi guys,
in the javax.microedition-package i can't find something like the KeyListener in java.awt.event-package. How can I recieve the Key-char when the user is pressing a key?

you will find this lisetener in canvas package not in form package

ADF Faces - type of key element!

Does anybody know What type of element that can be get by
Set rowSet = selectionEvent.getSelectedKeys().getKeySet();
or
Set rowSet = treeTableEventType.getSelectionState().getKeySet();
Iterator rowSetIterator = rowSet.iterator();
in SelectionListener method

Dear John,
I think so
but I get exception
SEVERE: java.lang.ClassCastException: java.util.Collections$UnmodifiableRandomAccessList
javax.faces.el.EvaluationException: java.lang.ClassCastException: java.util.Collections$UnmodifiableRandomAccessList
     at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:130)
     at oracle.adf.view.faces.component.UIXComponentBase.__broadcast(UIXComponentBase.java:1079)
     at oracle.adf.view.faces.component.UIXTreeTable.broadcast(UIXTreeTable.java:318)
When when Itry to cast Set element to Key type:
Key k=(Key)rowSetIterator.next()

JDBC Reciever Encoding

Hi
my scenario is FILE -> XI -> JDBC
Im using content conversion to convert the file from flat to xml
the encoding is UTF-8 , I want to change it to ISO-8859-8
because the hebrew letters is changed to question marks
any ideas?
thx,Shai

Hey
have a look at the following.
Urgent : Change Encoding type?
Re: Change encoding from utf-8 to iso-8859-1 in JMS receiver!
u have to use XSLT mapping to change the encoding
Or if u just want to read the Hebrew characters then i guess the better idea would be use Text as File Type and ISO-8859-1 as encoding in sender communication channel
thanx
ahmad
Message was edited by:
Ahmad

Persistence under Exactly-Once Handling in JDBC Reciever Adapter

Hi,
Can any one explain me significance of persistance (Local or Database) in JDBC Receiver Adapter.
Please provide me document if anyone has?
Thanks,
ABDUR

hi,
both types are described here with many details:
http://help.sap.com/saphelp_nwpi71/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
under : Defining Exactly-Once Handling
do you need anything more ?
Regards,
michal Krawczyk

JDBC Reciever key element

Similar Messages

Maybe you are looking for