JDBC to JDBC

Hi all,
I am doing jdbc to jdbc scenario, my scenario is like this:
I got two databases, i need to read the table from first database and send it to XI, after that i need to check the record is exist in one of the table in second database, if that record exist i need to write it to another table in second database.
In reciiver jdbc adapter configuration is it possible to validate one table and write it to another table?
Answer will be rewarded
Prasad

Hi Prasad,
2 options.
1. Use a SP and do the validation there and insert it in the correct table.
2. Use a BPM.
Steps in BPM.
1. Receive (Asynch) - Msg from DB1.
2. Send (Synch) - Do a select on table1 in DB2.
3. Switch (Do a check on the response from DB2) - 2 branches
4. Send (Asynch) in each branch to send it to the desired table.
Regards,
Jai Shankar

Similar Messages

  • Problem in JDBC to JDBC scenario

    Hello all,
    I am working on a JDBC 2 JDBC Scenario.
    Everything gone fine, data is picked from source, but it is not updated in the destination.
    I could not see any message related to this in SXMB_MONI it shows only messages related to IDOC, on search I fould, we need to add trace level,etc in SXMB_ADM but still couldnot found any message (I restarted the system, cleared cache also).
    In RWB(communication channel monitoring) I could find that sender is sucessful, but no message for receiver.
    In RWB (message monitoring) I checked my business system, i could see sender entries but no receiver entries, there is only one error message as :
    <b> transmitting the message to endpoint http://xisystem:50100/sap/xi/engine?type=entry using connectio</b>
    For which I found we need to change XI businesssystem's pipeline port no from some 54+++ to 4+++ (but I could see only 50100 in the pipeline so i did'nt)
    we are using R/3, was7.0 sp11,XI3.0,
    Can any body help me in this regard
    Thanks,
    Sai.k.k

    Hi,
    Error in SXMB_MONI :
    com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_JDBC2JDBC_MM_: RuntimeException in Message-Mapping transformatio~
    Error in Integration repository when I test with the payload :
    <pre>
    13:01:52 Start of test
    Document start
    Start tag [ns0:Receiver_JDBC_MT]
    Add raw attribute [ xmlns:ns0="http://xyz.com/JDBC2JDBC_NMSP"]
    Start tag [Statement]
    Start tag [dbTable]
    Add attribute: [action]=[INSERT]
    Start tag [table]
    Put value [Example]
    Close tag [table]
    Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)com.sap.aii.utilxi.misc.api.
    BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:XML Declaration not allowed here.(:main:, row:1, col:8)
    at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157)
    at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
    at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException:Fatal
    Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) ->
    com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126)
    at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
    at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
    at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155)
    at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
    at java.lang.Thread.run(Thread.java:534) -
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
    at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155)
    at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
    at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126)
    at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
    at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    13:01:52 End of test
    </pre>
    Query : Select * from Employee fetches all the fields
    Payload :
    <pre>   <?xml version="1.0" encoding="utf-8" ?>
    - <resultset>
    - <row>
      <PerNer>t</PerNer>
      <Initials>t</Initials>
      <Name>t</Name>
      <DOB>t</DOB>
      <State>t</State>
      <Country>t</Country>
      </row>
      </resultset>
    </pre>
    Regards,
    Sai.k.k

  • Help on RFC to JDBC and JDBC to RFC

    Help on RFC to JDBC and JDBC to RFC
    Hi Gurus
    I have the scenario where an RFC will be triggered in SAP , to write to a DB2 database and insert new records in a table
    and vice versa the JDBC has to read som data from a table based on a primary key, mark them as read for not be read next time and send the data to an RFC where a table in SAP will be updated.
    I have never worked with JDBC before , pls advice.
    is there any new issue to consider in PI 7.0 regarding JDBC
    Thanks.

    The requirement looks standard,
    SEARCH IN SDN FOR JDBC scenarios,you will find many docs for sender as well as Receiver.
    >
    > is there any new issue to consider in PI 7.0 regarding JDBC
    >
    no issue with PI7.0.
    Regards,
    Raj

  • IDoc to JDBC  and JDBC to IDoc Scenario

    Dear All,
    I am working on IDoc to JDBC and JDBC to IDoc Scenario.
    I have to send Idoc from SAP to Non SAP system(.NET application) i almost configured in XI but still i don't know when my INTEGRATION will INVOKE how my data will proceed from IDOC to Oracle database(Through JDBC) and in case of revese how and when Data flow will start.
    Does anyone have completed STEP by STEP scenario document for this?
    How my Idoc will sent to XI?
    How XI will pick up data from IDoc?
    How XI will Convert data to JDBC and UPDATE in Oracle Database?
    And i reverse case(JDBC to IDoc) when my INTEGRATION will INVOKE?
    Where and When i can watch my process and data?
    How can i test the whole integration?
    I AM GETTING ERROR WHILE TESTING CONFIGURATION IN Integration Directory "Error while refreshing the XI runtime cache" and when i check this in SXI_CACHE  it gives me error
    "Unable to refresh cache "NO_BUSINESS_SYSTEM"
    "Error during last refresh to cache"LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM"
    Please solve all the above problems i will reward u points
    thanks,
    RP

    Hi,
    While we working on IDOC to JDBC interface..
    We have to deploy JDBC Drivers?
    Go through this links,
    /people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
    http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
    To install JDBC driver follow the how to guide.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
    Configuration of JDBC Adapter for SQL Server
    JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
    Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
    UserID and Password.
    If the connection is not working find the correct port number.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
    JDBC- X I -  R/3 Scenario
    /people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    Please check the driver path as mentioned below.
    JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
    Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
    No JDBC driver required.
    Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
    follow this thread
    Re: Problem when connecting to MS Access through JDBC Adapter.
    SAP Note 850116 has details
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    Configuring the Sender JDBC Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/756b3c0d592c7fe10000000a11405a/content.htm
    Configuring the Receiver JDBC Adapter
    http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm
    Idoc Reveiver adapter..
    http://help.sap.com/saphelp_erp2004/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
    Thanks,
    Satya Kumar
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    Edited by: SATYA KUMAR AKKARABOYANA on May 8, 2008 5:51 PM

  • Jdbc -rfc -jdbc

    hi all,
    i have jdbc - rfc - jdbc scenario,should i go with bpm or without bpm approach?

    i have jdbc - rfc - jdbc scenario,should i go with bpm or without bpm approach?
    we have 3 Approaches :
    1. using bpm synchasynchbridge
    2.RFC LooKUP it is standard function of the "CONVERSION" Function Group in pi 7.1
    Defining RFC Lookups Graphically
    http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/8661
    note: if you are using pi 7.1 below version, then you need to wite one udf for RFC Lookup.
    3.Standard Adapter Module BEans RequestResponseBean
    http://wiki.sdn.sap.com/wiki/display/XI/Sync-AsyncwithoutccBPM
    http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/7032

  • JDBC-RFC-JDBC  without  BPM

    Hi
    I have JDBC-RFC-JDBC Scenario.Now i have complated JDBC-RFC part but for the RFC response i dont want to use BPM . We are on PI 7.0 SP 11 . What changes needs to be done in module level to achieve this .
    Regards
    Vijay

    Hi bhavesh,
    But In your one of the thread File-RFC-File scenario
    These steps are mentioned ,  is it required in my JDBC-RFC-JDBC Scenario???
    4. We need to add a few modules in the Sender File Adapter.
    Go to the Modules Tab of the Sender File Adater, and add the following modules in the same sequence,
    Number - ModuleName - Type - ModuleKey
    1- AF_Modules/RequestResponseBean - Local Enterprise Bean - 1
    2- CallSapAdapter-Local Enterprise Bean - 2
    3-AF_Modules/ResponseOnewayBean-3
    Parameters
    ModuleKey - ParameterName - ParameterValue
    1 - passThrough - true
    3-receiverChannel - Receiver File Adapter Name
    3-receiverService - Receiver Business Service/ System
    Regards Vijay

  • OC4J에서 DEFAULT로 제공하는 JDBC CLASSES를 원하는 JDBC CLASSES FILE로 변경하는 방법

    제품 : JDBC
    작성날짜 :
    OC4J에서 DEFAULT로 제공하는 JDBC CLASSES를 원하는 JDBC CLASSES FILE로 변경하는 방법
    =================================================================
    PURPOSE
    9iAS에서 JDBC thin driver인 classes file을 새로운 version으로 변경하기 위한
    여러가지 방법을 정리한다.
    Explanation
    9iAS R2에 포함된 JDBC THIN driver는 기본적으로 <J2EE_HOME>/jdbc/lib directory에
    포함된 classes12dms.jar 화일이다. 이 classes12dml.jar는 경우에 따라서 새로운
    version의 classes12.jar file로 변경되어져야 할 필요가 있는데 그러한 경우
    먼저 현재 화일 backup을 받아두고 지우거나 옮긴 후 아래 정리된 방법 중
    한가지를 이용하여 조치한다.
    단 아래와 같이 아래의 certify된 jdbc driver version에 한하여
    필요한 경우 같은 version을 대치, 혹은 upgrade하도록 한다.
    Application Server release Certified Oracle JDBC Supported Database
    release releases
    ================================================================================
    ===
    Oracle9iAS Release 1 (1.0.2.2) 8.1.7 8.1.7
    Oracle9iAS Release 2 (9.0.2 and 9.0.3) 9.0.1.4 9.2.0*, 9.0.1, 8.1.7
    Oracle9iAS Release 2 (9.0.3.1) 9.0.1.4, 10.1.0 (thin), 10.1.0, 9.2.0, 9.0.1, 8
    .1.7
    + one off patch 9.2.0 (thin)
    Oracle Application Server 10g (9.0.4) 9.0.1.4 9.2.0*, 9.0.1, 8.1.7
    Oracle Application Server 10g (9.0.4.1) 9.0.1.5, 10.1.0 (thin), 10.1.0*, 9.2.0*,
    9.0.1, 8.1.7
    - patched core 9.2.0 (thin)
    ================================================================================
    ===
    현재 화일이 인식되지 못하도록 하기 위한 가장 간단한 방법은 다음과 같이
    화일이 .jar나 .zip으로 인식되지 않도록 rename하는 것이다.
    os>cd $ORACLE_HOME (or top level directory where oc4j was unpacked)
    os>cd jdbc/lib
    os>mv classes12dms.jar classes12dms.raj
    (1) 방법1
    OC4J가 실행되는 JSDK환경에서 global하게 access되도록 하려면 다음 directory에
    classes12.jar 와 nls_charset12.jar를 copy한다.
    <JDK_HOME>/jre/lib/ext
    [주의] 이 위치에 .jar file을 위치시키게 되면, 이것은 OC4J뿐 아니라
    command line에서 실행되는 java application 등 이 JDK환경의 어떤
    java class에서도 인식이 된다.
    이 extention directory는 jdk boot classpath보다는 이후 인식되지만,
    사용자가 지정하는 CLASSPATH환경 변수 등보다는 더 상위에서 인식되기
    때문이다.
    그러므로 이 extention directory에 .jar를 위치시키는 것이 경우에 따라
    원하지 않는 결과를 발생시킬 수 있음을 유의하여야 한다.
    (2) 방법2
    새로 사용하고자 하는 library file을 OC4J가 기본적으로 인식하는
    <J2EE_HOME>/jdbc/lib directory로 다음과 같이 위치시킨다.
    단 이때 새로운 version의 jdbc에 classes12dms.jar가 없다면 classes12.jar를 classe
    s12dms.jar로 이름을 변경시켜 두도록 한다.
    그 이유는 9iAS의 경우 default로 dms가 붙은 jdbc를 이용하기 때문이다.
    os>cp classes12.jar <J2EE_HOME>/jdbc/lib/classes12dms.jar
    os>cp nls_charset12.jar <J2EE_HOME>/jdbc/lib/nls_charset12.jar
    (3) 방법3
    $OC4J_HOME/j2ee/home/config/application.xml 에 아래와 같이 library path로
    새로운 jdbc driver를 지정한다.
    이때 다른 library path tag보다 앞 부분에 지정하도록 한다.
    <library path="jdbc_classfile이_위치한_상대경로\classes12.jar"/>
    <library path="jdbc_classfile이_위치한_상대경로\nls_charset12.jar"/>
    NOTE: OPTIONS 1 through 3 update the JDBC classes used by all
    applications running in the OC4J container.
    (4) 방법4
    위의 세가지 방법이 해당 OC4J의 모든 application에 영향을 미친게 된다.
    원하는 application에서만 변경된 jdbc driver를 사용하고자 한다면
    해당 application의 META-INF/application.xml화일에 다음 내용을 다른 libarary
    path tag보다 앞 부분에 지정하도록 한다.
    <library path="jdbc_classfile이_위치한_상대경로\classes12.jar"/>
    <library path="jdbc_classfile이_위치한_상대경로\nls_charset12.jar"/>
    Reference Documents
    <Note:236947.1> How to override the default JDBC DRIVER classes with the
    selected JDBC classes in OC4J

  • JDBC to JDBC Scenario - Communications Channel Error

    I am following the published JDBC to JDBC Scenario:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/step-by-step+guides
    I am a 3rd Party Vendor, and I'm using NX7: SAP Exchange Infrastructure. My goal is to have a JDBC Sender that sends MS Access data from my PC to NX7, and have a JDBC Receiver that receives MS Access data, and map the data from one database to the other via XI per the scenario, with both databases on my PC.
    I set up the NX7 SAP XI per the scenario, but I'm getting an error on the NX7 Communications Channel:
    Error during database connection to the database URL 'jdbc:odbc:Driver={Microsoft Access Driver(.mdb)};DBQ=//204.245.44.232/C:/Documents and Settings/All Users/Documents/XI_FILES/SENDER/STUDENT_Database.mdb' using the JDBC driver 'sun.jdbc.odbc.JdbcOdbcDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver(.mdb)};DBQ=//204.245.44.232/C:/Documents and Settings/All Users/Documents/XI_FILES/SENDER/STUDENT_Database.mdb': SQLException: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified'
    The data source is in
    C:/Documents and Settings/All Users/Documents/XI_FILES/SENDER/STUDENT_Database.mdb on my PC and it is a shared folder. My PC IP 204.245.44.232 is a public IP address. It should be using the JDBC-ODBC bridge driver in the JDK.
    Why am I getting the error?
    Thanks,
    Ed Culnane

    Hi
    Connection Parameters are of given below check
    Transport Protocol: JDBC 2.0
    Message Protocol: XML SQL Format
    Adapter Engine: Integration Server
    JDBC Driver: jdbc.odbc.JdbcOdbcDriver
    Connection: jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//xiserver/xitemp/db/TestDB.mdb
    5) In my case there is no userid and password required, but if you have userid and password, then the parameter for Connection becomes,
    jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//xiserver/xitemp/db/TestDB.mdb;Uid=yourid;Pwd=yourpwd;
    Well ms access file should be in the XI Server path or it should be able to accessed by the XI
    Try this above option of keeping u r file in the XI Server path instead of the local
    rgd
    srini

  • JDBC OCI和JDBC Thin有什么区别?

    JDBC OCI和JDBC Thin有什么区别?
    效果有什么区别?(都是通过weblogic连db的)

    一般来说
    OCI效率应该高一些
    不过使用的时候一般使用jdbc直接连接
    因为OCI不是纯java实现

  • JDBC TO JDBC  adapter

    Hi ,
             i am using JDBC to JDBC adapter.in my scenario sender comunication channel is in error.
    Error during database connection to the database URL 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)}  ;DBQ=C:\xifile\Student_Database.mdb' using the JDBC driver 'sun.jdbc.odbc.JdbcOdbcDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)}  ;DBQ=C:\xifile\Student_Database.mdb': java.lang.NullPointerException'
    please help.

    Can you change your string from:
    jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)} ;DBQ=C:\xifile\Student_Database.mdb
    to:
    jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=C:/xifile/Student_Database.mdb
    I think you have checked this blog:
    /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
    but if you note try to check it.
    Edited by: Arman Eker on Jun 11, 2010 11:07 AM

  • JDBC to JDBC scenario error

    Hi techies,
    I am trying out  the scenario JDBC to JDBC.
    I have mapped the
    CC_JDBC_SENDER          
    Data Base Connection          
    JDBC Driver          oracle.jdbc.driver.OracleDriver
    Connection          jdbc:oracle:thin:@<<ip>>:<<port>>:<<hostname>>
    User Name          kiran
    Passowrd          *****
    Processing parameters          
    Query SQL Statement          SELECT * FROM STUDENT WHERE FLAG = 'TRUE'
    Document                               DBExtract
    Update SQL statement          UPDATE STUDENT SET FLAG = 'FALSE' WHERE FLAG ='TRUE'
    CC_JDBC_RECIVER          
              Standard configuration
    Mapping           
    Sender
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://jdbc_2_jdbc" targetNamespace="http://jdbc_2_jdbc">
    <xsd:element name="mt_sender" type="dt_sender" />
    <xsd:complexType name="dt_sender">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    0b0fdc6840c211e09d490000004d9c8e
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:element name="row">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    7eca0f413fcb11e08a2800270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="NAME" type="xsd:string" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    7eca6d3e3fcb11e0b9da00270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ID" type="xsd:string" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    7eca6d3f3fcb11e0c34f00270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ADDRESS" type="xsd:string" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    7eca6d403fcb11e0a4fa00270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="FLAG" type="xsd:string" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    7eca6d413fcb11e0a72300270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    Reciver
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://jdbc_2_jdbc" targetNamespace="http://jdbc_2_jdbc">
    <xsd:element name="mt_reciver" type="dt_reciver" />
    <xsd:complexType name="dt_reciver">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    0b1e084240c211e08a7f0000004d9c8e
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:element name="STATEMENT">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    81fd5e1d3fdb11e0980b00270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ROW">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    81fd5e1e3fdb11e0c89000270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="action" type="xsd:string" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    81fd5e1f3fdb11e0bcea00270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="TABLE" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    81fd5e203fdb11e0b15c00270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="access" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    81fd5e213fdb11e0980000270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="LIBID" type="xsd:string" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    81fd5e223fdb11e0c80500270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="LIBNAME" type="xsd:string" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    81fd5e233fdb11e0baf800270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="LIBADDRESS" type="xsd:string" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    81fd5e243fdb11e0838400270e0eb886
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    Sender communication channel is working fine and I am able to access data from Oracle. And also I am able to change the flag status to false.
    At receiver end I am having this error
    com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_mm_mapping_: RuntimeException in Message-Mapping transformatio~
    Exception of class CX_XMS_SYSERR_MAPPING.

    Hi prabhat,
    Thanks alot for your reply,
    While testing the xml message copied from paylod screen, this error iam getting
    Cannot produce target element /ns0:Messages. Queue does not have enougth values in context. Target xsd requires a value for this element but target field mapping does not produce one. XML instance is not invalid for source xsd, or the target field mapping does not fulfill the requirement of the target xsd.
    Payload xml details
    <?xml version="1.0" encoding="utf-8"?>
    <DBExtract>
         <row>
              <NAME>MSCKIRAN</NAME>
              <ID>1895400</ID>
              <ADDRESS>BHEL</ADDRESS>
              <FLAG>TRUE</FLAG>
         </row>
         <row>
              <NAME>DVKMOHAN</NAME>
              <ID>1883682</ID>
              <ADDRESS>BHEL</ADDRESS>
              <FLAG>TRUE</FLAG>
         </row>
    </DBExtract>
    Message Mapping XML details which is working fine while testing
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
       <ns0:Message1>
          <ns1:mt_sender xmlns:ns1="http://jdbc_2_jdbc">
             <row>
                <NAME>MSCKIRAN</NAME>
              <ID>1895400</ID>
              <ADDRESS>BHEL</ADDRESS>
              <FLAG>TRUE</FLAG>
             </row>
          </ns1:mt_sender>
       </ns0:Message1>
    </ns0:Messages>

  • JDBC to JDBC in PI 7.1

    Hi
    I  need to work on JDBC to JDBC adapter scenario, Can anyone send me the Blog which explains with screen to develop,
    Thanks
    PR

    Hi
    Pls check the following link
    https://wiki.sdn.sap.com/wiki/display/XI/JDBCTOJDBC
    Though it is not for PI 7.1, but it will give a step wise jdbc to jdbc scenario.
    Regards
    Abhijit

  • JDBC - JavaProxy - JDBC (Synchronous) Interface without BPM  ?

    Hi,
    I was reading the following Blog
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/file-rfc-file%28without+bpm%29&
    I want to know that, is it possible to develop an interface like below without using BPM :
    JDBC - JavaProxy - JDBC
    Can we use the same approach as mentioned in above Wiki post for this scenario also.
    Regards
    Kulwinder

    Hello Everyone,
    JDBC - JavaProxy - JDBC Sync scenario works using modules similar to File or Jms adapter.
    Thanks.

  • Can I get information on JDBC to JDBC Using BPM

    Hi @SAPXI
    Can I get information on JDBC to JDBC Using BPM
    Thanks
    Rao

    hi
    look into this u ll get the answer
    JDBC to JDBC Scenerio
    regards
    kish
    reward if found useful

  • JDBC to JDBC Scenerio

    Dear All,
    i want to do one JDBC to JDBC scenario in which I want to update one table in MSAccess by taking data from the other table stored in MSAccess. Plz tell me the parameters which I have to maintain for this scenerio in Integration Directory & Repository. Also plz tell shuld I have to write any SQL Query for that & if yes then where I have to give that query. Also, plz tell me the good weblog for this scenario.
    Waiting for ur valuable replies,
    reg,
    nishu

    Hi,
    In your sender JDBC adapter , you can give a JOIN select query.
    Like,
    select table1.col1,table1.col2,table2.col3 from table1,table2 where table1.col1=table2.col1 and table2.col4 = '1'
    <i> Also there is something called Document Namespace, so what we have to specify there.</i>
    You will create your Sender JDBC Datattype under a Namespace. GIve the DocumentNamespace value as this Namespace and Document Name as the Datatype Name.
    <i>Also, what will be the structure for the Sender JDBC Data Type.</i>
    For query above,
    <i><DT_SORUCEDATATYPE>
    <row>  <b>0 to UB</b>
    <col1>  </col1>
    <col2> </col2>
    <col3> </col3>
    </row>
    </DT_SOURCEDATATYPE></i>
    All this info is available on http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
    Please read the same for all info you need.
    Regards,
    Bhavesh

Maybe you are looking for