Mapping Issue in JDBC-- XI-- RFC

Hi All,
I have developed a scenario, where data flow is as follows...
sql->JDBC sender-> XI->RFC Reciever---> SAP.
Now, the data is retrieved from SQL and queued in Message monitoring.
I am unable to pass it to RFC reciever and then to SAP.
I hope it may be problem with the message mapping.
In this scenario, what should be the message mapping...???
Can anyone explain me how many mappings needed...????
Regards
Pavan

I am not using any BPM or context objects.
Business systems are properly associated with the communication channels.
Doubt about the configuration.....
sql>sender jdbc-> Xi Reciever RFC---->Sap
Integration Repository:
data types:
sender_dt, reciver_dt
Message types:
sender_mt, reciever_mt
Imported RFC:
ZBAPI_pavan
(Reciver_dt will be having same structure as ZBAPI_pavan)
Message Interfaces:
jdbc_ob_mi (o/b, Async. sender_mt)
rfc_ib_mi (I/B, Async, reciever_mt)
Message Mapping:
sender_mm
(Mapped sender and reciever message types)
Interface Mapping:
jdbc_rfc_im
(Source Interface: jdbc_ob_mi and Target Interface: rfc_ib_mi)
(Source message: sender_mt, mapping pgm: sender_mm and Target mesg: reciever_mt)
Integration Directory:
Sender (sql to XI)
Business Sys: JDBC_SENDER_BS
Comm Channel: JDBC_SENDER_CC
Reciever (XI to SAP)
Business Sys: RFC_RECIEVER_BS
Comm Channel: RFC_RECIEVER_CC
Reciever Det:
In this Buss Sys wil be sender business sys.
Interface wil be jdbc_ob_mi... (sender Outbound)
Configured Recievers--->service = RFC_RECIEVER_BS (Reciever Buss sys)Configuration Overview->RFC_RECIEVER_BS->RFC_IB_MI, jdbc_rfc_im,  rfc_reciever_cc
Interface Determination:
Sender---> Buss Sys: JDBC-SENDER_BS, Interface: jdbc_ob_mi,
Reciever--->Buss Sys: RFC_RECiever_BS
Configured inbound interfaces:
I/b interface: rfc_ib_mi, interface mapping: jdbc_rfc_im
Sender Agreement:
Sender--> Buss Sys: jdbc_sender_BS, interface: jdbc_ob_mi,
sender comm channel: JDBC_SENDER_CC
Reciever Agreement:
Sender-->service: jdbc_sender_bsReciever:
service: rfc_reciever_bs,
Interface: rfc_ib_mi
With the above configuration, messages are qued up in the SXMB_MONI.
They are not passing into SAP.
When i tested in Configuraion->Tools-->Test Configuration,
error is displayed as follows.... Error is at Interface Determination and Mapping.
Interface Mapping
... (109 lines)
can any one Help me out.....?
Mappings are perfectly alright..
I have created interface det, rec/sender agreements again anad again.....
Restarted server...cleared cache...
Kindly go through above configurations and help m ein solving this problem....Any help...????
Message was edited by:
        Pavan Sanganal

Similar Messages

  • Graphical message mapping examples for JDBC and RFC lookup

    hi, can any body provide me graphical message mapping examples for the "JDBC Lookup" function and "RFC Lookup" function?
    I'm now studying the graphical message mapping and want to try those 2 functions. thank you.
    I expect the examples to be simple enoung, not need to set up much.

    >
    Madhu_1980 wrote:
    > can u check this link:
    >
    > PI 7.0 & 7.1 Mapping - Blogs,Articles,Wiki,Code Samples and Videos Collections https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=79955426  
    >
    > it contains a link : SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups /people/jin.shin/blog/2008/02/15/sap-pi-71-mapping-enhancements-series-graphical-support-for-jdbc-and-rfc-lookups
    May be I'm too foolish to follow those links, I got issues of each links.
    What I really want is an example from step0
    Swarup:
    Refer the Lookup document - Easy Lookup in Process Integration 7.1
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20befc9a-aa72-2b10-ae9b-b0988791d457
    The first step is "Create an RFC Enabled Function Module for look up", but where can I create the function module? Should I use ESB, IB? or use transaction 'SE11' ?
    Kulkarni:
    Very good links for RFC lookup with 7.0/3.0
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70d90a91-3cf4-2a10-d189-bfd37d9c3231&overridelayout=true
    At page6 "PI Development/Configuration", it saies "You are on the design maintenance screen in the Integration Builder.Expand the subnodes for the software component version for which you want to import interfaces".
    What is "design maintenance screen" ? My IB version is: Service Pack:08 Release:NW07_08_REL.
    When I open IB, it display a screen titled with "Configuration: Intergation Builder", I did not find "software component version" node on the left tree.
    Madhu_1980 :
    it contains a link : SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups /people/jin.shin/blog/2008/02/15/sap-pi-71-mapping-enhancements-series-graphical-support-for-jdbc-and-rfc-lookups
    The Prerequisites state:
    The JDBC channel to be used for the lookup must be configured and activated in the Integration Directory.
    The definition of the table used for the lookup must already be imported into the ES Repository as an external definition
    But I don't know how to create a JDBC channel and define the table.

  • Mapping issue in jdbc to idoc scenario

    Hi
    we have a  jdbc to idoc scenario , we need to repeat the segment given below which has only two fields FLDGRP  and FLDVAL,
    both filed_Group and fieldgroup1 is coming simultaneously . when field group =BATCH, batch=FLDVAL and fieldgroup1=CUST cust_code=FLDVAL
    mapping is as follows :
    E1WXX01 (segment name) occurance 0:9999999999                                     
    fieldgroup----
    > FLDGRP
    batch----
    >FLDVAL
    fieldgroup1----
    >FLDGRP(same filed as above )
    cust_code----
    >FLDVAL(same filed as above)
    pl sugggest how to map using graphical mapping
    rgds
    arun

    I see the problem here... hmmm.. It is simple
    You need to just duplicate the E1WXX01 segment by right clicking and pressing Duplicate Subtree.
    Once you do duplication of segment then you will have two segments of E1WXX01.
    In first segment map
    > fieldgroup----
    > FLDGRP
    > batch----
    >FLDVAL
    and in second segment of E1WXX0, map
    > fieldgroup1----
    >FLDGRP
    > cust_code----
    >FLDVAL
    Regards,
    sarvesh

  • Mapping Issue(UDF) in HTTP-RFC scenario with URL parameters - Urgent

    Hi All,
    I am working out an HTTP-RFC scenarion wherein there is no xml data to be pushed.
    The data will be coming in the url parameters.
    Also we'll exposing our url(created by SAP PI) to 3rd party system to push data in terms of url parameters.
    So how do I do mapping? Also what UDF code will contain?
    Since I'm working on this kind of scenario for the first time, I need every help from you guys.
    Thanks & Regards,
    Amit Patil

    Hi All,
    I have worked on RFC to HTTP scenario wherein URL have to be passed. I used UDF in d same.
    But now the case is reverse, how shall I move ahead with what source message type(in the mapping) and how to do mapping.
    What kind of UDF will be useful here?
    I am completely blank in this kind of scenario where 3rd party system is going to pass four parameters on URL link craeted by us since its an HTTP to RFC scenario.
    Please guys help me! Give me some inputs.
    Thanks,
    Amit Patil

  • Mapping problem in message response  RFC -- xi -- JDBC

    Hi all,
    I'm using the follow scenario:
    RFC <-> xi <-> JDBC
    It's a synchronous interface.
    In JDBC the message do a SELECT in database and returns selected rows in message response.
    The message response transfers selected rows to RFC.response in the mapping.
    It seems working right but no data are transfered to RFC.
    In SXMB_MONI I can see the selected rows from database.
    There is no error in JDBC and RFC adapter. Bellow is the message response in the SXMB_MONI:
      <ns1:MT_jbdc_select_response xmlns:ns1="http://braskem.com.br/xi/sapxi03">
      <t7_productionorder_response>
      <row>
      <PRODUCT>Nafta Media</PRODUCT>
      </row>
      <row>
      <PRODUCT>Nafta Media</PRODUCT>
      </row>
      </t7_productionorder_response>
      </ns1:MT_jbdc_select_response>
    I think that there is an error in message mapping between RFC.response <-- message_response, because I'm just mapping the fields <row> and <product>, because if I make a link beteween <t7_productionorder_response> and return table of RFC, a Short DUMP happens.
    Bellow the structure of MESSAGE RESPONSE:
       <t7_productionorder_response>
          <row>
             <PRODUCT/>
          </row>
       </t7_productionorder_response>
    Bellow the structure of RFC RESPONSE:
    <RFC.response>
      <t_return>
         <item>
             <product/>
         </item>
      </return>
    </RFC.response>
    When I make a link in the mapping between
    <t7_productionorder_response> -> <t_return>
    a short DUMP happens in RFC call in R/3.
    Anyone could help me about this problem ?
    Thanks in advance
    Regis Ferrato

    Hi,
      <i>because if I make a link beteween <t7_productionorder_response> and return table of RFC, a Short DUMP happens.</i>
    After doing this mapping, did you test it in the IR mapping editor? was it successful?
    Do specify the occurence of all the headers so we can help you better.
    Regards,
    Smitha.

  • Mapping issue in idoc to JDBC scenario

    mapping issue in idoc to JDBC scenario
    source structure
    E1KNB1M
      BUKRS = 1000
    E1KNB1M
      BUKRS=  9000
    E1KNB1M
      BUKRS=  2000
    THE NODE E1KNB1M is repeated many times and the field BUKRS is also repeated with E1KNB1M as above
    TARGET field : ISFRANCHISE
    if any where value of BUKRS =9000 we have to pass Y to the target filed, else N
    if BUKRS = 9000   THEN ISFRANCHISE= Y
                   ELSE
                ISFRANCHISE=N
    I've done the mapping as below
    BUKRS = 9000--> IF THEN Y ELSE N--
    > ISFRANCHISE
    BUT everry time the target value is N only
    pl suggest
    rgds
    mojib

    mapped like this
    BUKRS--->SORT---->
                                                 EQUALS --------IF---THEN    Y
    9000------------------------>                                               ----------------->ISFRANCHISE
                                                                  ELSE   N
    context of BUKRS set to parent node
    its worked
    thanks to all for valuable suggestions
    rgds
    mojib

  • Mapping Issue

    Hi Gurus,
    I have a JDBC-XI-RFC scenario (EOIO), where in I had to use Enhanced receiver determination to split the calls to RFC's (Regular Vs Emergency). Emergency call was directed using the filter queue to change the priority. We have tested in many env (d,q, pre prod) & now when I moved to Prod I get a strange error. When it first come to the integration engine & if it requires a split it fails showing a mapping error. But if I re-trigger it flow succesfully. Please fing the log from "moni" below(1) & a sussesful log (2).
    Please see the below bolded log which I am getting confused
    In case of error I get
    <SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>
    Else I get
    <SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION</SAP:Interface>
    **(1)**
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Request Message Mapping
      -->
    <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>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>4A6DF427-B0EE-7444-E100-00000AAA0C0C</SAP:MessageId>
      <SAP:TimeSent>2009-07-28T13:37:05Z</SAP:TimeSent>
    <SAP:Sender>
      <SAP:Service>CIS_PROD_STORMS</SAP:Service>
    <SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface> *
      </SAP:Sender>
    <SAP:Receiver>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
      <SAP:Service>BS_ENVISION_SAP_EMERG</SAP:Service>
      <SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION_EMERG</SAP:Interface>
    <SAP:Mapping notRequired="M">
      <SAP:ObjectId>RNPgv18MOBmjhpr+oO1mNw==</SAP:ObjectId>
      <SAP:SWCV>oZGAQNmpEdym2dnSCqoHjQ==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
      <SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>
      </SAP:Main>
    <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
      <SAP:QueueId>XI_ENV_SERIALIZE</SAP:QueueId>
      </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>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_ENVISION_WO_TO_SAP_NOTIF_EMERG_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
    (2)
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Response
      -->
    <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>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>4A6DDA42-B138-7443-E100-00000AAA0C0C</SAP:MessageId>
      <SAP:TimeSent>2009-07-27T22:01:00Z</SAP:TimeSent>
    <SAP:Sender>
      <SAP:Service>CIS_PROD_STORMS</SAP:Service>
      <SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>
      </SAP:Sender>
    <SAP:Receiver>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
      <SAP:Service>BS_ENVISION_SAP_REGULAR</SAP:Service>
      <SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION</SAP:Interface>
    <SAP:Mapping notRequired="M">
      <SAP:ObjectId>oPLLbgxJOWimAK6rdZb/MA==</SAP:ObjectId>
      <SAP:SWCV>oZGAQNmpEdym2dnSCqoHjQ==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
    <SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION</SAP:Interface> *
      </SAP:Main>
    <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
      <SAP:QueueId>XI_ENV_SERIALIZE</SAP:QueueId>
      </SAP:ReliableMessaging>
    Regards
    UK

    Hi,
    Sorry, My text help was not working due to some IE setting & I can understand the message got cluttered.
    Anyways let me repost the actual thread,
    I have a JDBC-XI-RFC scenario which requires an Enhanced receiver determination and requires calling two different RFC programs(emergency, regular) based on that. I use a queue filter to direct to XBQA* for emergency. As I indicated, it seems working fine with d,q,preprod. When I move it to prod, it show me some maping issue. However when I retrigger the same from my moni, they execute succesfully. Please see the log below for a message that goes error & the log when it is succesful (retrigger).  Let me know if you need more details.
    When there is error Please see the last tag
    MI_TBL_WMS_SOURCE_STAGING_SDW_EGD is the sender
    <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>ApplicationMessage</SAP:MessageClass>
    <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
    <SAP:MessageId>4A6DF427-B0EE-7444-E100-00000AAA0C0C</SAP:MessageId>
    <SAP:TimeSent>2009-07-28T13:37:05Z</SAP:TimeSent>
    <SAP:Sender>
    <SAP:Service>CIS_PROD_STORMS</SAP:Service>
    <SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>
    </SAP:Sender>
    <SAP:Receiver>
    <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
    <SAP:Service>BS_ENVISION_SAP_EMERG</SAP:Service>
    <SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION_EMERG</SAP:Interface>
    <SAP:Mapping notRequired="M">
    <SAP:ObjectId>RNPgv18MOBmjhpr+oO1mNw==</SAP:ObjectId>
    <SAP:SWCV>oZGAQNmpEdym2dnSCqoHjQ==</SAP:SWCV>
    <SAP:SP>-1</SAP:SP>
    </SAP:Mapping>
    </SAP:Receiver>
    *<SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>
    </SAP:Main>*
    Blelow is when its succesful
    <SAP:Interface namespace="urn:sap
    -com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION_EMERG</SAP:Interface>.
    Regards
    Unni
    Edited by: Unni Krishnan on Jul 28, 2009 5:06 PM

  • JDBC TO RFC SCENARIO

    Hi,
    I am tryiing JDBC TO RFC SCEANRIO.
    XI is picking data from MS SEQUEL SERVER but
    the same data is not getting mapped into RFC
      I am not getting any error as such.
    Following are the details.
    made a datatype
    resultset
         row
         EmployeeID
         LastName
         FirstName
    message mappping
                                    RFCFORJDBC
         resultset                      outab
                row                        item
                  EmployeeID----
    Empno
                  FirstName
                               concatenate--- Empname
                  Lastname
        But for some odd reason
        the OUTTAB FOR RFC
         is coming like this in message
          <?xml version="1.0" encoding="UTF-8" ?>
    - <p3:ZZTESTXIJDBC xmlns:p3="urn:sap-com:document:sap:rfc:functions">
      <OUTAB />
      </p3:ZZTESTXIJDBC>
    while payload is getting picked correctly
    <?xml version="1.0" encoding="utf-8" ?>
    - <resultset>
    - <row>
      <EmployeeID>9</EmployeeID>
      <FirstName>Anne</FirstName>
      <LastName>Dodsworth</LastName>
      </row>
      </resultset>
    Kindl help with the same

    Hi,
    t' was namespace.
    It solved issue.
    Besides
    the sql statement
    select EmployeeID , FirstName ,LastName from Employees where EmployeeID > 7
    and the output is
    <?xml version="1.0" encoding="UTF-8" ?>
    - <p3:ZZTESTXIJDBC xmlns:p3="urn:sap-com:document:sap:rfc:functions">
    - <OUTAB>
    - <item>
      <EMPNO>8</EMPNO>
      <EMPNAME>Laura Callahan</EMPNAME>
      </item>
    - <item>
      <EMPNO>9</EMPNO>
      <EMPNAME>Anne Dodsworth</EMPNAME>
      </item>
      </OUTAB>
      </p3:ZZTESTXIJDBC>
    but I see only one record is getting updated
    <EMPNO>9</EMPNO>
      <EMPNAME>Anne Dodsworth</EMPNAME>
    what could be the reason for that

  • Step by step cofig for jdbc-- xi-- rfc adapter.

    hi,
    all
    can any one post any doc.. for the scenario
       jdbc--> xi -->rfc
    thanx
    all sdn's

    Hi ! Dantuluri
    U couldnt find the direct weblog
    JDBC receiver
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    JDBC sender
    /people/yining.mao/blog/2006/09/13/tips-and-tutorial-for-sender-jdbc-adapter
    IDoc sender
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    Refer the below links also for this scenario
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
    For any issues check this blog:
    /people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi
    also refer these .....
    /people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
    /people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
    idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
    Try this also .....
    /people/laxman.molugu/blog/2006/08/13/integration-with-databases-made-easy-150-part-1
    Re: Idoc triggering from a transaction
    Message Mapping - JDBC to IDoc
    Re: JDBC - System/Application Acknowledgement
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    Process Integration (PI) & SOA Middleware
    Pls reward if useful

  • 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

  • Sync. Scenario JDBC - XI - RFC

    Hi everybody,
    we are polling a JDBC-table MYTABLE. The result of the JDBC-poll is mapped into a RFC. The RFC itself gives a response. The RFC-response is now mapped to a JDBC-Update statement on table MYTABLE.
    We don not want to use BPM.
    How do we have to configure the objects the RFC-response to the JDBC-Update in directory?
    Is this possibe?
    Thanks
    regards Mario

    Hi,
    we folled the instructions of your thread and encounter a null pointer exception during execution of module
    reponseonewaybean in audit log
    (we entered receiver service and receiver channel in module configuration)
    FYI: We are on PI 7.1
    any suggestions?

  • Mapping problem on CSV to RFC scenerio

    Hi all,
    I am implementing an CSV to RFC scenerio on SAP XI 3.0, but stuck on a mapping issue. Please find the message, below;
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:357) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at ...
    I do not face any kind of error on mapping test and see the source and result documents, below;
    Source;
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_Csv xmlns:ns0="http://com.sap.astron/tekkasa">
       <mydoc>
          <itemList>
             <items>
                <fld1>1</fld1>
                <fld2>2</fld2>
                <fld3>3</fld3>
             </items>
             <items>
                <fld1>4</fld1>
                <fld2>5</fld2>
                <fld3>6</fld3>
             </items>
          </itemList>
       </mydoc>
    </ns0:MT_Csv>
    Result:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:Z_READ_CSV xmlns:ns1="urn:sap-com:document:sap:rfc:functions"><ITAB_ZCSV><item><FLD1>1</FLD1><FLD2>2</FLD2><FLD3>3</FLD3></item><item><FLD1>4</FLD1><FLD2>5</FLD2><FLD3>6</FLD3></item></ITAB_ZCSV></ns1:Z_READ_CSV>
    It is interesting that I see the message in payload, below;
    <?xml version="1.0" encoding="utf-8"?>
    <mydoc>
    <itemList>
         <items>
              <fld1>1</fld1>
              <fld2>2</fld2>
              <fld3>3</fld3>
         </items>
         <items>
              <fld1>4</fld1>
              <fld2>5</fld2>
              <fld3>6</fld3>
         </items>
    </itemList>
    </mydoc>
    Anyone has a suggestion about the problem? Thank you very much.

    Hi Shabarish;
    I pasted  complete output, below. I would be very appreciated, if you could suggest a solution. Thank you.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Request Message Mapping --> <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>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>asynchronous</SAP:ProcessingMode><SAP:MessageId>977D6A50-91B1-11DC-A122-00145E6896FD</SAP:MessageId><SAP:TimeSent>2007-11-13T06:28:05Z</SAP:TimeSent><SAP:Sender><SAP:Service>GarantiTekKasaFtp</SAP:Service><SAP:Interface namespace="http://com.sap.astron/tekkasa">MI_Outbound_Async</SAP:Interface></SAP:Sender><SAP:Receiver><SAP:Party agency="" scheme=""/><SAP:Service>B3T003</SAP:Service><SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">Z_READ_CSV</SAP:Interface><SAP:Mapping notRequired="M"><SAP:ObjectId>5bz79NusOaWn/LbMSmdpTA==</SAP:ObjectId><SAP:SWCV>rsCz8ZEJEdycocVZCkEBQg==</SAP:SWCV><SAP:SP>-1</SAP:SP></SAP:Mapping></SAP:Receiver><SAP:Interface namespace="http://com.sap.astron/tekkasa">MI_Outbound_Async</SAP:Interface></SAP:Main><SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>ExactlyOnce</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=""><SAP:Category>Application</SAP:Category><SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code><SAP:P1>com/sap/xi/tf/_MM_CSV_</SAP:P1><SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2><SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>During the application mapping com/sap/xi/tf/_MM_CSV_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~
    </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="2007-11-13T06:28:05Z" wasRead="false"><SAP:Engine type="AE">af.yxi.yxint01</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>977D6A50-91B1-11DC-A122-00145E6896FD</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2007-11-13T06:28:05Z" wasRead="false"><SAP:Engine type="IS">is.00.yxint01</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>977D6A50-91B1-11DC-A122-00145E6896FD</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList><SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Date>20071113</SAP:Date><SAP:Time>082805</SAP:Time><SAP:Host>yxint01</SAP:Host><SAP:SystemId>YXI</SAP:SystemId><SAP:SystemNr>00</SAP:SystemNr><SAP:OS>Windows NT</SAP:OS><SAP:DB>ORACLE</SAP:DB><SAP:Language/><SAP:ProcStatus>014</SAP:ProcStatus><SAP:AdapterStatus>000</SAP:AdapterStatus><SAP:User>XIAFUSER</SAP:User><SAP:TraceLevel>1</SAP:TraceLevel><SAP:Logging>1</SAP:Logging><SAP:LogSeqNbr>006</SAP:LogSeqNbr><SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr><SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal><SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal><SAP:PipelineElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId><SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId><SAP:PipelineService>PLSRV_MAPPING_REQUEST</SAP:PipelineService><SAP:QIdInternal>XBTO6___0002</SAP:QIdInternal><SAP:CommitActor>X</SAP:CommitActor><SAP:SplitNumber>0</SAP:SplitNumber><SAP:NumberOfRetries>0</SAP:NumberOfRetries><SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries><SAP:TypeOfEngine client="294">CENTRAL</SAP:TypeOfEngine><SAP:PlsrvExceptionCode/><SAP:EOReferenceRuntime type="TID">0A4101420318473943F5015F</SAP:EOReferenceRuntime><SAP:EOReferenceInbound type="TID"/><SAP:EOReferenceOutbound type="TID"/><SAP:MessageSizePayload>234</SAP:MessageSizePayload><SAP:MessageSizeTotal>2690</SAP:MessageSizeTotal><SAP:PayloadSizeRequest>234</SAP:PayloadSizeRequest><SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap><SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse><SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap><SAP:Reorganization>INI</SAP:Reorganization><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound><SAP:InterfaceAction>DEL</SAP:InterfaceAction><SAP:RandomNumber>06</SAP:RandomNumber><SAP:AckStatus>000</SAP:AckStatus><SAP:SkipReceiverDetermination/><SAP:Sender_Agreement_GUID>E8E1DEF39D603F158F70394833EF0ADE</SAP:Sender_Agreement_GUID><SAP:Serialize_Children>X</SAP:Serialize_Children></SAP:RunTime><SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.39</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.406</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.406</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.406</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.406</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.515</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.515</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.531</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.531</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.531</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.546</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.546</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.546</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.64</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.64</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:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
    <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
    <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
    <Trace level="1" type="T">Sender party external = </Trace>
    <Trace level="1" type="T">Sender party normalized = </Trace>
    <Trace level="1" type="T">Party normalization: receiver </Trace>
    <Trace level="1" type="T">Receiver scheme external = </Trace>
    <Trace level="1" type="T">Receiver agency external = </Trace>
    <Trace level="1" type="T">Receiver party external = </Trace>
    <Trace level="1" type="T">Receiver party normalized = </Trace>
    <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
    <Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
    </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="1" type="T">system-ID = YXI</Trace>
    <Trace level="1" type="T">client = 294</Trace>
    <Trace level="1" type="T">language = E</Trace>
    <Trace level="1" type="T">user = XIAFUSER</Trace>
    <Trace level="1" type="Timestamp">2007-11-13T06:28:05Z 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><!-- ************************************ -->
    <Trace level="1" type="T">Message-GUID = 977D6A5091B111DCA12200145E6896FD</Trace>
    <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
    <Trace level="1" type="T">QOS = EO</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC"></Trace><!-- ************************************ -->
    <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>
    <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
    <Trace level="1" type="T">Queue name : XBTI0002</Trace>
    <Trace level="1" type="T">Generated prefixed queue name = XBTI0002</Trace>
    <Trace level="1" type="T">Schedule message in qRFC environment </Trace>
    <Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Going to persist message </Trace>
    <Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
    <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
    <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
    <Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
    </Trace>
    <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
    <Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
    <Trace level="1" type="T">system-ID = YXI</Trace>
    <Trace level="1" type="T">client = 294</Trace>
    <Trace level="1" type="T">language = E</Trace>
    <Trace level="1" type="T">user = XIAFUSER</Trace>
    <Trace level="1" type="Timestamp">2007-11-13T06:28:05Z CET  </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
    <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>
    <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <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>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    </Trace>
    <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <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 E R M I N A T I O N </Trace>
    <Trace level="1" type="T"> Cache Content is up to date </Trace>
    </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    </Trace>
    <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">number of receivers: 1 </Trace>
    <Trace level="1" type="T">Single-receiver split case </Trace>
    <Trace level="1" type="T">Post-split internal queue name = XBTO6___0002</Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Persisting single message for post-split handling </Trace>
    <Trace level="1" type="T"> </Trace>
    <Trace level="1" type="T">Going to persist message + call qRFC now... </Trace>
    <Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
    <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
    <Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
    </Trace>
    <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
    <Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
    <Trace level="1" type="T">system-ID = YXI</Trace>
    <Trace level="1" type="T">client = 294</Trace>
    <Trace level="1" type="T">language = E</Trace>
    <Trace level="1" type="T">user = XIAFUSER</Trace>
    <Trace level="1" type="Timestamp">2007-11-13T06:28:05Z CET  </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
    <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>
    <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Interface Mapping http://com.sap.astron/tekkasa IM_CSV </Trace>
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_CSV_ </Trace>
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
         at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:357)
         at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105)
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91)
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy186.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100)
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
         at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Root Cause:
    com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
         at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:212)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:352)
         at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105)
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91)
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy186.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100)
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
         at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    </Trace>
    <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_CSV_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd </Trace>
    <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_CSV_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73)
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91)
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy186.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100)
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
         at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Root Cause:
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
         at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:357)
         at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105)
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91)
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy186.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100)
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
         at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Root Cause:
    com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
         at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:212)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:352)
         at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105)
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91)
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy186.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100)
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
         at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    </Trace>
    <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    </Trace>
    <Trace level="1" type="System_Error">Error exception return from pipeline processing! </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></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"><SAP:Payload xlink:href="cid:[email protected]"><SAP:Name>MainDocument</SAP:Name><SAP:Description/><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>

  • JDBC to RFC  Scenario large data

    Hi,
    I have jdbc to rfc scenario. I have no problem with the small size data (about 10 mb ). if resultset is very large ( about 80 -120 mb ) , i received resultset and proceess it  but when PI try to send these data to RFC it stucks status Scheduled in sxmb_moni , and in rwb is  to be delivered and doesn't send to rfc.
    What can i do ?

    Since you are using JDBC as sender, I would think you query from the sender and resultset is mapped to RFC for the target system. PI  gives optimum performance upto 5 mb message size. YOur message size is pretty big.
    Suggestion:
    A) Make a minor change and do the query to result less records.
    Example: Select Fields from tablename where rownum < 500    and
                   in update statement set flag = true for the read records so that next time you will not reread those old records again and every time you query only for 500 or  300 or your desired number records and keep the  mesg size always constant irrespective of data available.
    Hope that helps.

  • Question regarding JDBC - XI -RFC

    Hi all,
    I have a scenario which XI will get data from database (using jdbc adpater) then send data to execute in RFC. This is an asynchronous call. My question is that.
    1. If XI can get many records from database in 1 select, will it send many records to RFC at once? Is there any way i could tell XI to split input data into many message (1 message for each record) without using BPM? or Is it possible or better to set import parameter of RFC into table to get many record from XI at once?
    2. If i manage to make 1 message for each record, Could i use queue for sending data to RFC? I want the first record to be completed before sending second record. Since this is an asynchronous call, I'm not sure that XI could be able to know when to send the second record or Do I have to make it synchronous call to get return response from RFC after RFC finish execution and use BPM to get return response before sending next data to RFC.
    Any suggestion from expert?
    Thanks,
    Pavin

    Hi
    1. If XI can get many records from database in 1 select, will it send many records to RFC at once? Is there any way i could tell XI to split input data into many message (1 message for each record) without using BPM? or Is it possible or better to set import parameter of RFC into table to get many record from XI at once?
    Yes you can do multi mapping 1:N without BPM
    Message Splitting Using the Graphical Mapping Tool
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    2. If i manage to make 1 message for each record, Could i use queue for sending data to RFC? I want the first record to be completed before sending second record. Since this is an asynchronous call, I'm not sure that XI could be able to know when to send the second record or Do I have to make it synchronous call to get return response from RFC after RFC finish execution and use BPM to get return response before sending next data to RFC.
    You can queue to process one by one. Response can be obtained with or without BPM
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/file-rfc-file(Without%2bBPM)
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/jdbcTOJDBC
    JDBC to RFC Mapping Problem.
    Thanks
    Gaurav

  • JDBC- XI- RFC(V.V.Urgent)

    Hi ,
    JDBC->XI->RFC
    I am Integrating Oracle database with SAP(RFC).
    How should adapter knows some thing updated in Oracle.
    How Should the Triggers in Oracle.How we have to write Query in XI..
    Points Will be awarded for the Solution..
    Regards,
    Jayasimha

    Hi
    Refer the below links ...
    check the below blogs
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    /people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
    /people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter
    See the below links also ..
    /people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response - XI: How-to on JDBC receiver response
    JDBC Response /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
    Receiver JDBC scenario - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
    /people/ajay.kumar/blog/2005/03/24/writing-bsp-for-sap-r3-version-46
    /people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
    /people/prasad.illapani/blog/2006/10/25/how-to-check-jdbc-sql-query-syntax-and-verify-the-query-results-inside-a-user-defined-function-of-the-lookup-api
    /people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
    /people/community.user/blog/2006/09/21/xi-rfcadapter-reconnect-issue
    /people/sap.user72/blog/2005/12/22/new-to-xi
    Rewards point if useful

Maybe you are looking for

  • ITunes constantly freezes when opening, no error message

    Please help! ITunes has been working fine. One day I opened it and it got stuck on the default of opening up the music store. The only way I can get out of it is CtlAltDel. There is no error message. I have installed & re-installed it numerous times

  • Please help this: JNLP association extensions confict with arguments

    Hello, Please help this: I use <argument> tag to transfer some parameters to JWS application. I also use <associatio> tag to associate a specila file(such as .zzz) to JNLP. But when I doulbe click .zzz file, my application only get "-open" and file p

  • How to hide or lock toolbar fileds by using script

    Hi experts, Could you please let me know how to lock or hide toolbar fields by using script. Thanks, Pavan

  • How to backup EP 6.0

    Hi,      How can I take backup of EP6.0 server, show that if I Install EP 6.0 in another system I can get all contents exartly similar to what are there currently. thank & regards Ashutosh

  • StateManager / storing views bug?

    A web application which shows two windows in same session has problems on restoring the correct view. Assuming both windows are displaying the same view (same .jsp file but different contents) then the StateManagerImpl.java (jsf version 1.0 and 1.1)