Dp scenerio

Hi gurus
i have my project scenerio , could u plz help me out,
How to Generate CVC in DP as soon as New IPC get created in ECC. I would like to know what all option are available and what all parameter you need system must have.

Hello,
one solution could be to use the APO CIF Inbound Exit for Products to generate CVCs. This is what we did to avoid maintenance of CVCs in DP. You can use standard functions in APO to generate CVCs in your DP PLOB. One prerequisite of this approach is that you CIF the new products from ECC to APO.
Regards
Thomas
Here is a bit of where and how:
Ext.: APOCF005
Exit: EXIT_/SAPAPO/SAPLCIF_PROD_001
Include: ZXCIFUSERU08
  call function '/SAPAPO/TS_PLOB_CREATE'
       exporting
            iv_bas_plobid      = <your_plob_id>
       importing
            ev_new_records     = lv_new_records
            ev_exit_change     = lv_exit_change
       changing
            ct_plob_values_tab = lt_plob_values_tab
       exceptions
            no_bas_plobid      = 1
            inherited_error    = 2
            others             = 3.
    call function '/SAPAPO/TS_LCM_PLOB_DELTA_SYNC'
         exporting
              iv_bas_plobid  = <your_plob_id>
         exceptions
              plobid_invalid = 1
              others         = 2.
    if sy-subrc <> 0.
      raise failed.
    endif.

Similar Messages

  • Not getting attribute values in IPC routines Scenerio R/3 B2B using AP 7.0

    Hi,
    Our Scenerio is using ISA R/3 B2B using AP 7.0. I have developed IPC routines but when i debug my routines in SM53 I notice that I'm not getting any attribute value except for VKORG.
    I'm pasting the code below. Please help me if I have to implement some BADI or do something more to get the attribute values.
    I have defined the attributes properly in Routine assignment in tcode /n/sapcnd/ueass
    userexitlogger.writeLogDebug("*requirment 901*" + "Plant = "plant"||ANZ_MONATE ="+ item.getAttributeValue(ANZ_MONATE_STR).toString()"||ANZ_JAHRE="item.getAttributeValue(ANZ_JAHRE_STR).toString()"||MATKL="item.getAttributeValue(MATKL_STR).toString()"||PSTYV="item.getAttributeValue(PSTYV_STR).toString()"||VKORG="item.getAttributeValue(VKORG_STR)"||PRSFD="item.getAttributeValue(PRSFD_STR)"||MVGR2="item.getAttributeValue(MVGR2_STR).toString()"||PRSDT="item.getAttributeValue(PRSDT_STR).toString()"||AUDAT="item.getAttributeValue(AUDAT_STR).toString());
    I would reward points for help
    Many Thanks n regards,
    Dipender

    I would like to go through each Value of the xml file and give each Value a name
    e.g. from the xml file <VentCount Value=1> Retreive the value above and giving it the name VentCount. Then I would beable to use the name vent count as follows:
    setVentCount() //My own method can use as follows: setVentCount(VentCount); I would like to do his for ever value, each value with a specific name

  • Complex mapping scenerio.

    Hi Experts,
                            in my scenerio, in the Interface mapping, data from source reaches target through 3 stages. 2 XSL mapping, and then a graphical mapping.
    In my scenerio, file is picked from FTP and posted to SAP through RFC .
       In the sender File Adapter, I have to go for the FILE CONTENT Conversion. But In the interface mapping,  data first enters the two  XSL mappimgs and then the graphical mapping.
      Now I dont understand hw to maintain the CONTENT CONVERSION mandatory parameters, becasue if I do so on the basis of the Graphical mapping source fields, that wont be correct, as data firsts passes through the 2 XSLT mappings, and then reaches the Graphical mapping.
    I got the following errors in the communication channel.
    Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'ROOT.fieldFixedLengths' or 'ROOT.fieldSeparator' is missing Mandatory parameter 'ROOT.fieldNames': no value found.
    I donno hw to handle this.
    Also , mine is a .DAT file, I dont understand how can i send it for drytesting and see hw is the load reacting to the FIRST XSL mapping, I mean is there any way i can check this??
    Pls comment.
    Regards,
    Arnab.

    Hi, did as u instructed, used the standard templete : GMTLogSenderFileChannelTemplate. The Interface Mappig used here is: GMTLog2POSDM.
    Now I am getting the following error:
    15:33:27 Start of test
    Call XSLT processor with stylsheet GMTLog2IXRetailPOSLog.xsl.
    TransfromerException during XSLT processing:
    javax.xml.transform.TransformerException: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1429 at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:255) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingTransformer.transform(RepMappingTransformer.java:150) at com.sap.aii.ibrep.server.mapping.ibrun.RepXSLTMapping.execute(RepXSLTMapping.java:81) at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0.transform(MapServiceRemoteObjectImpl0_0.java:167) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0p4_Skel.dispatch(MapServiceRemoteObjectImpl0_0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:215) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Caused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1429 at com.sap.engine.lib.xsl.xpath.DTM.getAttributeAndNSNodes(DTM.java:406) at com.sap.engine.lib.xsl.xslt.XSLCopyOf.copyElementNode(XSLCopyOf.java:70) at com.sap.engine.lib.xsl.xslt.XSLCopyOf.copyNode(XSLCopyOf.java:151) at com.sap.engine.lib.xsl.xslt.XSLCopyOf.process(XSLCopyOf.java:214) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLForEach.process(XSLForEach.java:116) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLForEach.process(XSLForEach.java:116) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:281) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.callTemplate(XSLStylesheet.java:1355) at com.sap.engine.lib.xsl.xslt.XSLCallTemplate.process(XSLCallTemplate.java:111) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:281) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.callTemplate(XSLStylesheet.java:1355) at com.sap.engine.lib.xsl.xslt.XSLCallTemplate.process(XSLCallTemplate.java:111) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLIf.process(XSLIf.java:32) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:281) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:469) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:437) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:394) at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:412) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:244) ... 19 more
    15:33:28 End of test
    Pls comment.
    Regards,
    Arnab.

  • How to send status message in SOAP to IDOC scenerio without BPM

    Hi,
    I have a SOAP to IDOC scenerio in which we require to send the status message back to user from XI that " IDOC has been sent successfully to SAP system"
    We do not want to use BPM bacause of performance issues.
    Can you please help me how to achieve this synchronous response without BPM.
    Note: We require the status message from XI that the IDOC has been successfully posted to WESAP system

    Idoc only support async behaviour. U can't get the Idoc response as per ur requirement without BPM.
    Better to go for abap proxy or RFC.
    Or u may get the ack till XI.
    Regards,
    Prateek

  • XI and R/3 System connection settings for IDOC to File scenerio.

    Hi SAP champs,
                               I am working on a IDOC to File XI scenerio. But I am confused while configuring connection settings at XI system and R/3 system. I am finding problem in transaction IDX2 to maintain the IDOC metadata. Please let me know the complete step by step system cofigurations in XI and R/3 systems for the scenerio. Thanks in advance..
    Regards
    Sanjeev.

    Hi Sanjeev,
    We upload Medata in IDX2 to just reduce runtime effort and hence to improve the performance. However it is not a mandetory step to be performed for R/3 TO XI scenario.
    You are confused just because here you dont find any F4 help to select the metadata and the PORT.
    Thanks
    Sunil Singh

  • Complete file not displayed in File server(Idoc - XI File scenerio)

    Hi,
    Am working on Idoc-XI-File scenerio.
    The target file is getting generated properly and complete xml n Adapter Monitoring in RWB.
    But in the file server(in the directory)only part of the xml is displayed.The size of the file is 82KB.
    Is there any configuration need to see the complete file in File Server.

    Hi Amit,
    This could be due to Network. How far is the file server from XI server?
    I suggest putting the file in to local machine or in the same network and check whether it is OK.
    - Pinkle

  • Billing in Third Party Scenerio

    Hi All,
    I completed the complete cycle for third party process.While i am trying to do billing for Third Party Scenerio, i getting a warning message "No Billing quantity has been determined".If i ignore it, i am able to create the billing.But the issue is that we are using a user-exit in billing.Because of the above message, User-exit fails.I want to aviod the error. Please guide me.
    With Regards
    Vinu.N

    This error occur b'coz of two possibilities:
    1) Check your billing relevance in Item Cat (VOV7) in your THIRD PARTY process or sales order. It should be F.
    2) IR - Invoice receipt (MIRO) should have been completed before you raise a sales invoice.
    +If you don't want IR to happen before raising sales invoice, select a relevant Billing relevance for your process Item Cat. +
    Hope this can assist you.
    Thanks & Regards
    JP

  • Problem in FILE to RFC scenerio

    Hi,
    I am working on File to RFC Scenerio
    I am getting a problime in Communication channel (Sender).
    The problem is coming in File COntent Conversion
    Parameters are like
    Documenet name : MT_ROXY ( ->Header -> EMPNO
                                                                 -> EMPNAME
                                                                 -> DEPTNAME)
    Recordset Name: Details
    Recordset str     : HEADER,*
    Recordset Seq   : Variable
    " per message   :*
    Conersion Params:
    ignoreRecordsetName  : True
    HEADER.addHeaderLine : 0
    HEADER.fieldSeperator: ,
    HEADER.endSeperator: 'nl'
    HEADER.fieldFixedLengths : 12,40,40
    HEADER.fieldNames          :EMPNO,EMPNAME,DEPARTMENTNAME
    HEADER.lastFieldsOptional : YES
    Problem:The message content i am getting is like
    <ns:MT_ABAPPROXY>
    &#8722;
         <HEADER>
    <EMPNO>IT,Munish,22</EMPNO>
    </HEADER>
    &#8722;
         <HEADER>
    <EMPNO>IP,Munish1,2</EMPNO>
    </HEADER>
    &#8722;
         <HEADER>
    <EMPNO>IS,Munish2,2</EMPNO>
    </HEADER>
    &#8722;
         <HEADER>
    <EMPNO>IQ,Munish3,2</EMPNO>
    </HEADER>
    &#8722;
         <HEADER>
    <EMPNO>IR,Munish4,2</EMPNO>
    </HEADER>
    </ns:MT_ABAPPROXY>
    as  it does not dividing the Fields by ,
    as it shud come like
    <EMPNO>IR,2</EMPNO>
    <EMPNAME>Munish5</EMPNAME>?
    <DEPARTMENTNAME>2</DEPARTMENTNAME>
    but its not taking the other 2 filds and not separating by , sepreator,
    Kindly guide me in solving this problem on urgent basis
    Thanks in Advance
    Munish SIngh

    HI,
    Then use only fieldSeparator see the spelling it should be in proper case.
    refer the below weblog for more information:
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    Also refer the file FCC parameters.
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
    Thnx
    Chirag

  • Problem in Picking the file in  FTP to RFC Scenerio

    Hi,
    I am using FTP to RFC scenerio, i have a CSV file and need to use file Content COnversion at the sender Communication Channel. But its not picking up the file from my  FTP..
    My data is like
    11    Munish     IT
    My Message Type is like :
    MT_ABAPPROXY ->
                 HEADER    ->>
                                    Empno
                                    Empname
                                    Departmentname
    My Communication channel is like this..
    Transport Protocol:FTP
    Message Protocol:FIle COntent COnversion
    SOurce Directory : /
    File name:            file.csv
    then Server name and port is corrwctly configured
    My messe Content COnversion is like this
    Doc Name:MT_ABAPPROXY
    Namespace:http://www.munnamespace.com
    Recordsetname:Details
    Rec Str :            HEADER,*
    HEADER.fieldSeperator     ','
    HEADER.fieldNames    Empno,Empname,Departmenname
    HEADER.lastFieldsOptional   YES
    HEADER.fieldFixedLengths    12,24,24
    ignoreRecordsetName         true
    HEADER.endSeperator     'nl'
    But it is unable to pick the file , but if i wont use file conten conversion , it picks but it has no use as the date is not in XML
    SO kindly help me in solving this as the problem is mostly in File COnetent Conversion
    Thanks
    Munish SIngh

    Hi arvind,
    thankd for the reply,
    i have done the same what u said but i am getting this error in communcation channel monitoring (RWB)
         Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting document line no. 1 according to structure 'HEADER':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this

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

  • File to RFC Scenerio in PI 7.1

    Hi Experts,
    Please provide any documents for File to RFC Scenerio in PI 7.1

    The procedure is the same as it was in SAP PI7.0 or lower versions.....no major change on this front.
    Search SDN for documents related to your protocol.
    Regards,
    Abhishek.

  • BPM scenerio

    Hello All,
    I have scenerio SAP(IDOC) --- > PI -
    > Webservice (SOAP)
    Here we are using BPM AsyncSync Call because we need to send response back to SAP system.It is working perfectly , but now in Production system we found frequently it is giving error.
    Mostly in MONI it dont show any error it always shows error in smq2 inbound q with error message exception in BPE.
    When i analyse this error i found that while sending a response from webservice there was some connection problem, but i didnot understood why it  got stuck in Inbound q.
    Can anyone let us know why we have got this error or is there anyone we can rectify this.Can it be a cause of interface design issue,This is very frequent problem so we want to rectify this .
    Regards,
    Vikrant

    Using an Exception Handling in such a case is always helpful.
    Include the SyncSend step inside a block and include an Exception Branch for this Block.
    So now if any error is faced while getting back the response (like connection issue) it will be caught by the exception branch.
    In there you can apply the relevant exception logic (send alert email) or even a simple Cancel Process step will also do (depending on your business logic)
    This will fix the issue forever and prevent the BPM getting stucked. Ask your TL/ PM to follow this approach and let us know what they think on it.
    Even I am implementing the same logic in my project for every sync call with a WS.
    Regards,
    Abhishek.

  • Isssue in File To RFC Scenerio

    Hi Experts,
       I am sending a .DAT  file to R/3 using PI.
       File gets successfully picked up from FTP into PI. But sxmb_moni is not showing any error messeges, nothing. In fact I know this is a perfectly OK file as few days ago it was successfully processing the same file, without errorrs.
      I hav checked in messege monitering and got the following error.
    Error Category XI_J2EE_ADAPTER_XI_HANDLER
    Error Code GENERAL_ERROR
    Received XI system error.error Code:SLD_NO_OWN_BS Error Text:Error Stack:error while reading ID of own business system from the SLd for system RXT and client 001 Internal error in Landscape Directory.                
    I hav checked the LOG in SLD and got the fllowing error.
    #1470 03/10/2009 15:00:49.918 [SAPEngine_Application_Thread[impl:3]_18] WARNING com.sap.lcr.cimsrv.ChangePasswordServlet: Password change required for automated client. Please ensure that service client users don't have initial passwords. Alternatively, logon to the SLD user interface with the corresponding user and assign a new password. After the password has been changed, client settings must be updated accordingly.
    I hav done no changes in any where,, no password change or no craetion of new client. This scenerio was working ok, but all of a sudden it started giving this strage issue. Only hint I can giv is,, the file size is some where around 2.5mb,, and i believe this is NOT a constraint..but may be I can be wrong.
    Please comment experts.
    Regards,
    Arnab .

    Hi! Arnab,
    com.sap.lcr.cimsrv.ChangePasswordServlet: Password change required for automated client. Please ensure that service client users don't have initial passwords. Alternatively, logon to the SLD user interface with the corresponding user and assign a new password. After the password has been changed, client settings must be updated accordingly
    According to my knowledge the issue is not related to development side. Please check with your basis guys to check all the conenctions like SLD conenctions and J2EE engine status and also regardign ABAP stack.
    1. Got to ABAP stack and enter T code SLDCHECK.
    2. Also goto T code SMICM and there restart j2ee engine by selecting options J2EE soft Restart in the top menu.
    3. If still issues s there then if possible ask them to do entirre XI server restart once..
    Also go through this SAP note and ask your basis guys if any patches are to be implemented.
    [Note 1225611- com.sap.lcr.cimsrv.ChangePasswordServlet:|
    [1225611|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1225611]
    Regards::
    Amar Srinivas Eli

  • FILE TO PROXY SCENERIO DEBUGGING

    Hi All,
       I am using a file_to_proxy scenerio(SAP SYSTEM), it processed sucessfully in quality but is throwing the error in development though we have the same code all around.
    Any idea on this will be a great help.
    Also i need to debug the code to check out the exect cause of the error but even i am giving the break-point it is skipping out.
    Please let me know the steps required to debug the same.
    Many thanks,
    JGD.

    Hi All,
      Let me make the things clear,
    I have a FILE-->XI-->R/3(PROXY) scenerio,
    The file processed sucessfully in XI-->MONI
    The file also processed sucessfully in R/3---->MONI,
    <b>Now it need to update into the table and here exactly it showing error in validation.
    Now i need to know how can i debug in this part. ( FORM R/3 till to the TABLE )
    Each time i cant process the file and debug, so is there any option where i can debug it by using the payload.
    </b>
    Many Thanks,
    JGD
    Edited by: JGD on May 6, 2008 7:42 AM

  • Scenerio mapping For a CAN Industry

    HI
    The scenerio is the raw material is fed in at inlet to a automatic machine.It undergoes 4 operations
    Folding , Checking(quality),Printing ,labeling the output is the CAN.At the output the cans are packed in to a pallet which has 50 cans for a pallet and a packing material.
    The cans are stored in a pallet in a ware house.they recognise it with pallets.
    Say they manufacture in can ,Sell in cans in storage through Palets
    So how to map this scenerio.How to fix the material type.
    Regards
    Jayshankar.A

    Hi,
    First thing is material type like
    Material                                                                Material type
    R01(Raw material is fed)                                         ROH
    Palates                                                                  ROH                       
    Packing material                                                    Packing
    CAN                                                                      FERT.
    Create BOM for CAN material, Create routing.
    Regards
    Vijay
    Edited by: vijay pawadi on Jan 30, 2009 10:05 AM

  • File 2 RFC scenerio

    Mine is a File toXI to  RFC scenerio.
    File in DAT format  is picked up fro FTP and send to XI. XI further sends it to BI server through RFC adapter. The thing is due to some reasons I hav deliberately entered wrong data  uid and password]  for XI to BI connection in sm59 and in the RFC adapter. Initially just wished to see wether the data movement between File aServer to XI takes place properly.
    Activated the components and carried out the Tools - Test Configuration.
    It is giving following error:
    Receiver Agreement
    More over when ever I place the file in the specified soure path ....I don see any RESULTS IN sxmb_moni or messege monitoring .
    But Communication channel monitoring shows GREEN for file adapter.
    My query is if sender  File adapter is green and polling, why do i not see the same in messee monitoring and sxmb_moni.
    Pls comment.
    Pls revert back if anything is not clear.

    Hi,
    just for check - in ID in sender file comm channel, set mode to delete and see if your test file in source directory is getting deleted.........if it is deleted, then in comm chnnel monitoring, you will get yur msg and also in SXMB_MONI...........if the file is not deleted, then check for file permissions to pick the file..
    Regarding your No receiver agreement found error, in ID just create the reciver agreement for your sneder system, reciver sytem, receiver interface namespace data.............activate it and restart your msg in SXMB_MONI.
    Regards,
    Rajeev Gupta

Maybe you are looking for

  • IPhone 5S GPRS/E slow / unusable

    Hi, A month ago I upgraded from an iPhone 4 to the iPhone 5S. Ever since I had the 5S I have noticed the GPRS / E data is extremely slow and most of the time it is unusable as pages time out or you end up giving up. I am on Tesco mobile in the UK (O2

  • 2008 MacBook Pro won't boot from Leopard DVD or Target Disk

    Yesterday I was working on my MacBook Pro. I use FontExplorer to manage fonts. I ran the conflicts diagnostic looking for missing font files, which returned about 200 results (I was expecting this). I've moved the fonts installed by Adobe/Microsoft o

  • Help needed to do port forwarding in ipfw...

    For the last weeks I have been working to get the new open-source content management system Alfresco working. It is a pure Java web application that runs under Tomcat. There is official support for Mac OS X but only Windows and Linux gets true instal

  • Which data base tables contain SCM customer code

    Friends, I am writing an user exit for VA01/VA02/VA3/VA32. I am getting the customer number from VBAK-KUNNR when I execute any of the above transactions. According to functional sepecification, we can find SCM code in the data base table ADRC. (we ca

  • Secure wireless and generic ldap

    Hi All, I'm looking into setting up a secure wireless network and can't seem to find a good fit with environment we have. Environment: WLC's ACS 4.1 Generic ldap 95% of laptops use built in Windows XP(SP3) configuration tool. I can get everything wor