ResultSet XML Conversion Error

Hi,
BPEL, SOA 11g, DB2 Stored procedure,
In a BPEL service I am getting this error while invoking a DB2 Stored procedure with Strong XSD. I am using assign to copy the input parameter to the input parameters of Stored procedure.
not able to figure out why this error message is coming.
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'JDE_DBA' failed due to: ResultSet XML Conversion Error. An error occurred while converting from a ResultSet to XML. Unable to convert a ResultSet to XML. Cause: java.lang.NullPointerException ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) 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:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:157) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283) a
---------------- BPEL Code --------
<?xml version = "1.0" encoding = "UTF-8" ?>
<!--
Oracle JDeveloper BPEL Designer
Created: Fri Dec 10 10:24:23 PST 2010
Author: chaitanyad
Purpose: Synchronous BPEL Process
-->
<process name="UPCMatchOrder"
targetNamespace="http://xmlns.oracle.com/CD_JDE_Application_jws/JDE_UPCMatchOrder/UPCMatchOrder"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:client="http://xmlns.oracle.com/CD_JDE_Application_jws/JDE_UPCMatchOrder/UPCMatchOrder"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/db/CD_JDE_Application/JDE_UPCMatchOrder/JDE_DBA"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns2="http://xmlns.oracle.com/pcbpel/adapter/db/QAMODA73/X56714P/">
<!--
PARTNERLINKS
List of services participating in this BPEL process
-->
<partnerLinks>
<!--
The 'client' role represents the requester of this service. It is
used for callback. The location and correlation information associated
with the client role are automatically set using WS-Addressing.
-->
<partnerLink name="upcmatchorder_client" partnerLinkType="client:UPCMatchOrder" myRole="UPCMatchOrderProvider"/>
<partnerLink name="JDE_DBA" partnerRole="JDE_DBA_role"
partnerLinkType="ns1:JDE_DBA_plt"/>
</partnerLinks>
<!--
VARIABLES
List of messages and XML documents used within this BPEL process
-->
<variables>
<!-- Reference to the message passed as input during initiation -->
<variable name="inputVariable" messageType="client:UPCMatchOrderRequestMessage"/>
<!-- Reference to the message that will be returned to the requester-->
<variable name="outputVariable" messageType="client:UPCMatchOrderResponseMessage"/>
<variable name="Invoke_1_InputVariable" messageType="ns1:args_in_msg"/>
<variable name="Invoke_1_OutputVariable" messageType="ns1:args_out_msg"/>
</variables>
<!--
ORCHESTRATION LOGIC
Set of activities coordinating the flow of messages across the
services integrated within this business process
-->
<sequence name="main">
<!-- Receive input from requestor. (Note: This maps to operation defined in UPCMatchOrder.wsdl) -->
<receive name="receiveInput" partnerLink="upcmatchorder_client" portType="client:UPCMatchOrder" operation="process" variable="inputVariable" createInstance="yes"/>
<!-- Generate reply to synchronous request -->
<assign name="Assign_3">
<copy>
<from variable="inputVariable" part="InputMessage"/>
<to variable="Invoke_1_InputVariable" part="InputParameters"/>
</copy>
</assign>
<invoke name="Invoke_1" inputVariable="Invoke_1_InputVariable"
outputVariable="Invoke_1_OutputVariable" partnerLink="JDE_DBA"
portType="ns1:JDE_DBA_ptt" operation="JDE_DBA"/>
<assign name="Assign_2">
<copy>
<from variable="Invoke_1_OutputVariable" part="OutputParameters"/>
<to variable="outputVariable" part="OutputMessage"/>
</copy>
</assign>
<reply name="replyOutput" partnerLink="upcmatchorder_client" portType="client:UPCMatchOrder" operation="process" variable="outputVariable"/>
</sequence>
</process>
Regards,
-CD

Hi Sanjay,
The JDBC sender adapter returns the rows selected from the database in the follwoing format.
<resultset>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
</resultset>
This error occurs , when the source datatype you have created for the JDBC adapter does not match with this format. I would suggest that you check the source format along with the occurence of your field.
Regards,
Bhavesh

Similar Messages

  • Flat Idoc to Idoc XML conversion error.

    Hi All,
    We are using PI 7.1 EHP1, Where in we would like to see the capabilty of User-Module for Conversion of IDoc Messages Between Flat and XML Formats. Gone thru the below blog and maintained the necessary NWA configurations:
    How to Use User-Module for Conversion of IDoc Messages Between Flat and XML Formats
    While testing phase, The file is not been picked by the Sender File Adapter and the below error is been displayed in RWB:
    "MP: exception caught with cause com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: Invalid character encountered in XML input data source: state=INITIAL, charPosition=0, lineNumber=1, columnNumber=1, invalidChar=U+0045, sourceSnippet=...EDI_DC40  510000000002889077846C 3012  SHPMNT05                      ZSHPMNT9                      S...                 ^"
    Any Clues?
    Thnx

    Hi Stefan,
    You are right i have maintained the mandatory parameters (SAPRelease, SourceJRA, TargetDestination) within the sender File adapter module key parameters.
    Now getting another error within Comm Channel Monitoring:
    MP: exception caught with cause java.lang.StringIndexOutOfBoundsException: String index out of range: -1
    Any Clues?
    Thnx

  • NO Ruleset for GENRAL\96A available (EDI to XML Conversion Error)

    Hi,
    My Scenario is Inbound EDI Scenario. I am facing problem during conversion of EANCOM to XML .
    Control Key Scenario Association part with the EDI Content Manager is filled in properly. we are not doing anything in the above Control Key
    Scenario Association part .Because whatever we are saving we are not able to see in the screen. Please find the below screen shot attached.
    XSD produced from B2B Integration Cockpit was being used in the ESR.
    No Acknowledgement Enabled.
    We have checked with the possible option in the below blog.But not working
    http://scn.sap.com/thread/3309007
    Regards,
    Prem

    Hi Dmitri/Ruchir,
    By mistake I have uploaded  Message Type ORDERS screen shot with Message Protocol EANCOM,but my actual one is Message Type GENRAL with Message Protocol EANCOM only
    The combination of message type and version specified in the UNH segment is not maintained in the tables?
    the above mentined EDIFACT\EANCOM seems different issue.
    Message could not be forwarded to the JCA adapter.
    Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException:
    Message cannot be dispatched: Message cannot be dispatched: Error Occured :
    Error in conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
    java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
    available.
    MP: exception caught with cause
    javax.resource.ResourceException:
    com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message
    cannot be dispatched: Message cannot be dispatched: Error Occured : Error in
    conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
    java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
    available.
    Exception caught by adapter framework:
    com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message
    cannot be dispatched: Message cannot be dispatched: Error Occured : Error in
    conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
    java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
    available.
    Transmitting the message to endpoint <local>
    using connection File_http://sap.com/xi/XI/System failed, due to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException:
    javax.resource.ResourceException:
    com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message
    cannot be dispatched: Message cannot be dispatched: Error Occured : Error in
    conversion of GENRAL/96A-Edifact-Document at character 1489 to XML:
    java.lang.UnsupportedOperationException: No ruleset for GENRAL/96A
    available.
    if you need mu input payload please let me know
    Please suggest me.
    Thanks
    Prem

  • EDI 820 EDI to XML conversion error

    Hi Experts,
    We have configure EDI 820 Inbound Scenario in our system. The incoming EDI 820 file  is not getting converted in XML from EDI. I try to convert it into XML in BIC Mapping Designer but it is displaying the below error message.
    "Error:ID=2099;LEVEL=1] InhouseDocReader doSyntaxCheck(): offset[326]: the found segment
    ENT is not in the message description.
    DESCRIPTION: InhouseDocReader Error: The Segment
    ENT is missing in the message description. Check your file."
    Please find below the EDI file.
    "ISA*00*          *00*          *12*123456789 *01*111122233  *140317*1432*U*00401*120000004*0*T*>~GS*PO*123456789*111122233*20140317*14315990*4*X*004010~ST*820*0001~BPR*I*264.9*C*CHK~REF*IA*6400900~REF*CK*7896883~DTM*097*20080811~N1*PE*COMPANY ABC~N3*21 PENN PLAZA*SUITE 909~N4*NEW YORK CITY*NY*10001~
    ENT*1~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0195112**137.33*137.33~REF*PO*008471856056~DTM*003*20080711~ENT*2~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0195040**162.38*162.38~REF*PO*008471852792~DTM*003*20080711~ENT*3~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0194903**104.8*104.8~REF*PO*008471816334~DTM*003*20080711~ENT*4~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*0195039**137.33*137.33~REF*PO*008471846520~DTM*003*20080712~ENT*5~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*RV0047997934**-224.54*-224.54~REF*RZ*0004891~DTM*003*20080807~ENT*6~NM1*PO*2*Costco*****92*1033918430000~RMR*IV*RV0084791384**-52.4*-52.4~REF*RZ*8471700434~DTM*003*20080807~SE*39*0001~GE*1*4~IEA*1*120000004~"
    Can anyone let me know what could be error is?
    Regards
    Faisal

    Dear Abdul,
    I copied the file from your posting into a text-file and tried to convert it with my 820 BIC-Mapping.
    I just had to make two modifications:
    - add some spaces so that the Sender/Receiver fields in the ISA segement were 15 fields long
    - remove a "space" before ENT*1, but this space might also just have been there because of how you posted the content into this posting.
    After I had made this small changes the file could be translated perfectly fine with the mapping
    See_E2X_ANSIX12_820_V4010
    So it looks like eitehr your settings are not correct in the channel (e.g. a wrong mapping is used) or the file has been modified manually (with some additional blanks, CRLF, etc...)
    Regards
    Stefan

  • "character conversion error" while parsing xml files

    Hello,
    I'm trying to parse MusicXML (Recordare) files, but I'm getting an exception.
    I'm using the SAX parser (javax.xml.parsers.SAXParser).
    Here is the code I use to instantiate it:
    final javax.xml.parsers.SAXParserFactory saxParserFactory = javax.xml.parsers.SAXParserFactory.newInstance();
    final javax.xml.parsers.SAXParser saxParser = saxParserFactory.newSAXParser();
    final org.xml.sax.XMLReader parser = saxParser.getXMLReader();
    I'm using my own handler, but I get the same exception even if I use org.xml.sax.helpers.DefaultHandler.
    The error I get is:
    Character conversion error: "Illegal ASCII character, 0xc2" (line number may be too low).
    The first few lines of my xml files look like this:
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <!DOCTYPE score-partwise
    PUBLIC "-//Recordare//DTD MusicXML 0.6 Partwise//EN"
    "http://www.musicxml.org/dtds/partwise.dtd">
    <score-partwise>
    [...etc...]
    If I delete the <!DOCTYPE ...> line, then I don't get the exception anymore. But the MusicXML files I get (from some other program) always contain this line, and it would be quite some work to delete them from every file manually.
    So does anyone know if there is a way to avoid deleting that line in every file, while still being able to parse the xml files without exceptions?
    Or maybe does anyone know what the exact cause of the exception is? (because I don't know what exactly causes it)
    Thank you in advance.
    Greetz,
    Jipo

    So does anyone know if there is a way to avoid
    deleting that line in every file, while still being
    able to parse the xml files without exceptions?ok this is side-stepping the real problem but I've used this code to filterout DTD references for other reasons   public static InputStream filterOutDTDRef(InputStream in) throws IOException {
          BufferedReader iniReader = new BufferedReader(new InputStreamReader(in));
          StringBuffer newXML = new StringBuffer();
          for(String line = iniReader.readLine(); line!=null; line = iniReader.readLine())
             newXML.append(line+"\n");
          in.close();
          int s = newXML.indexOf("<!DOCTYPE ");
          if(s!=-1)
             newXML.replace(s,newXML.indexOf(">",s)+1,"");
          return new ByteArrayInputStream(newXML.toString().getBytes());
       }and it actually speeds up the parsing phase too (since the DTD ref.s were on the web and the XML standard mandates that there is a fetch for each xml file parsed..)
    you can feed the above into the InputSource constructor that takes an InputStream argument.
    Now for the real problem... 0xc2 is "LATIN CAPITAL LETTER A WITH CIRCUMFLEX" according to a unicode chart - which is not an ASCII character (as the error message correctly reports). I'm not sure why the file is being parsed as ASCII though? You could try parsing in a FileReader to the inputsource and hope it picks up the default character encoding of your system, and that that character encoding matches the file. Or you could try passing in a FileReader constructed with a explicit character encoding (eg "UTF8") and see if that does the trick?
    asjf

  • XML to ABAP Conversion Error - CX_SY_CONVERSION_DATA_LOSS

    REPORT  y_rpt_test                              .
    TYPE-POOLS sscr.
    DATA: restrict TYPE sscr_restrict,
    opt_list TYPE sscr_opt_list,
    *** TYPE sscr_***.
    DATA: options TYPE STANDARD TABLE OF rfc_db_opt ,
    fields TYPE STANDARD TABLE OF rfc_db_fld ,
    meta TYPE STANDARD TABLE OF ywas_metadata ,
    xml_out TYPE string .
    data: xml_out_x type xstring.
    DATA: wa_options LIKE LINE OF options,
    wa_fields LIKE LINE OF fields ,
    wa_meta LIKE LINE OF meta .
    FIELD-SYMBOLS: <outtab> TYPE ANY TABLE,
    <l_line> TYPE ANY,
    <l_field> TYPE ANY.
    DATA: new_table TYPE REF TO data.
    DATA: new_line TYPE REF TO data.
    DATA: xslt_error TYPE REF TO cx_xslt_exception ,
    xslt_message TYPE string .
    DATA: it_fieldcat TYPE lvc_t_fcat,
    is_fieldcat LIKE LINE OF it_fieldcat.
    TYPES: BEGIN OF s_text,
             partnum(18)     TYPE c,
             LONG_DESC(3000)    TYPE c,
           END OF s_text.
    data: lt_outtab type standard table of s_text,
          is_outtab type s_text.
    data: it_temp_text(1000)  TYPE c OCCURS 0 with header line.
    data : l_file TYPE string value 'C:xmlload.xml'.
    CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
        filename                      = l_file
        FILETYPE                      = 'ASC'
      tables
        data_tab                      = it_temp_text.
    loop at it_temp_text.
        concatenate xml_out it_temp_text into xml_out.
    endloop.
        IF NOT xml_out IS INITIAL .
          TRY .
              CALL TRANSFORMATION (`ZTEST1`)
              SOURCE XML xml_out
              RESULT outtab = lt_outtab.
            CATCH cx_xslt_exception INTO xslt_error.
              xslt_message = xslt_error->get_text( ).
              WRITE:/ xslt_message .
          ENDTRY.
        ENDIF .
        break-point.
        write : / 'test'.
    ==========================================================
    I am using above code to convert input XML file into internal table I am getting conversion error. My input XML file looks is as follows. It is throwing this error in call transformation. Appreciate your help in Advance.
    <MODIFIED BY MODERATOR - RESPECT THE 2,500 CHAR LIMIT>
    Code Formatted by: Alvaro Tejada Galindo on Jan 4, 2010 3:31 PM

    Thanks for quick response.
    I think the problem is with special characters in the input XML file. If I don't have special characters in XML file then it works fine.
    Anyway here is the XSLT code. This is a generic XSLT code which I used from one of the examples
    posted on this site.
    <?xml version="1.0" encoding="iso-8859-1"?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:xa="urn:schemas-microsoft-com:xml-analysis:mddataset" xmlns:asx="http://www.sap.com/abapxml" version="1.0">
    <xsl:output method="xml" />
    <xsl:variable name="fieldNames" select="//asx:abap/asx:values/FIELDCAT" />
    <xsl:template match="/">
    <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
    <asx:values>
    <!--FIELDCAT>
    <xsl:apply-templates select="//YWAS_METADATA" />
    </FIELDCAT-->
    <OUTTAB>
    <xsl:apply-templates select="//item" />
    </OUTTAB>
    </asx:values>
    </asx:abap>
    </xsl:template>
    <xsl:template match="//YWAS_METADATA">
    <item>
    <xsl:for-each select="*">
    <!--column ><xsl:apply-templates/></column-->
    <xsl:copy>
    <xsl:apply-templates select="@*|*|text()"/>
    </xsl:copy>
    </xsl:for-each>
    </item>
    </xsl:template>
    <xsl:template match="//item">
    <item>
    <xsl:for-each select="*">
    <!--column ><xsl:apply-templates/></column-->
    <xsl:copy>
    <xsl:apply-templates select="@*|*|text()"/>
    </xsl:copy>
    </xsl:for-each>
    </item>
    </xsl:template>
    </xsl:stylesheet>

  • Mapping error in FCC to XML conversion

    hiii friends,
    im donig a simple fcc to xml conversion
    my Sender msg type is like
    TXT_mt
          records                             1.1   
                row                             1.n
                    id                             1
                    Name                       1
                    address                   1
    My receiver msg type like
    Xml_mt
          records                             1.1   
                row                             1.n
                    id                             1
                    Name                       1
                    address                   1
    msg mapping like
    records--->records
    id--->id
    Name-->Name
    address-->address
    **Im getting a mapping error like**
    <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/_pepsi_fcc_file_mm_</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/_pepsi_fcc_file_mm_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I ve checked my adapeters they r green.
    Could u tell me the problem here and how to solve it???
    Regards
    Balaji

    Hii Volker,
    I have tried to understand the trace msg,. i got one interesting error message i hope it will tell the exact problem im facing,,,
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_pepsi_fcc_file_mm_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns:xml_mt/record/row. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram
    My Sender CC  contains the following FCC parameters
    Document Name -
    > txt_mt
    Recordset Name -
    > records
    recordset Structure -
    >  row, *
    row.fieldNames -
    > id, Names,address
    row.fieldSeparator -
    > , (comma)
    row.endSeparator--- >  'nl'
    row.processConfiguration  -
    > FromConfiguration
    my TXT_in.txt contain
    100,balaji,chennai
    200,raj,orissa
    300,charakrat,bangalore
    Regards,
    Balaji
    Edited by: Balaji Pichaimuthu on Jul 1, 2009 3:44 PM

  • Seeburger EDI Text to EDI XML conversion failure should throw an error

    Hi,
    I am expecting an error message to be thrown when EDI Text to EDI XML conversion fails at Message splitter of Seeburger module. I am getting the following error in the log.
    "2012-01-19T01:46:08.032-0800 ERROR [Error:ID=2150;LEVEL=3] counter value (41) of incoming field (UNB.UNH.UNT:0074) doesnt match the calculated value (39).
    DESCRIPTION: Either the counter value is not filled in the source file or the counter field value is wrong. "
    But my expectation is that the channel should show some error in Adapter Engine monitoring itself. As shown below, it is just showing some warning that because of above error, it is not creating the attachment. Now I am expecting the the following warning to be an error rather than just warning. Please let me know if any idea on the same.
    19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Trying to establish CCI Connection to Message Splitter Adapter
    19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Creating CCI Interaction
    19.01.2012 01:46:08 Warning SEEBURGER/MESSAGESPLITTER: There is no attachment to split. So there is nothing to do.
    19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Finished splitting!
    BR,
    Aman

    Thanks you all for your inputs..
    I got the solution for the same.
    I need to set the mapping program name specifically rather than AUTO for bic mappingName parameter. This has turned my communication channel status in RWB into Red for errors.
    Closing this thread ...
    Regards,
    Aman

  • Error in Idoc to XML conversion

    Hi,
    I am doing Idoc to XML conversion using standard program RSEINB00. Can anyone plz tell me what are the pre-requisites to executing this program? I am getting an error message Port XXX segment defn YYYYY in IDoc type ZZZZZ CIM type do not exist.
    Why am i getting this error? and what is the slution for it?
    Regards,
    Mateen.

    Hi
    Delete the metadata in IDX2 for the corresponding IDOC type in PI.
    Also re-import the same in IDX2.
    Reimport the IDOC type into Integration Repository under your SWCV.
    Then check it..
    Refresh the cache also.

  • How to custom a conversion error in JSF page in JDeveloper

    According to the book "Core JavaServer Faces" p213 (fifth edition), if I add the following line to messages.properties file, and specifiy it in the faces-config.xml and .jsp file, then the displayed conversion error message should be my tailored one instead of the default. However, I still get the default error message. Besides, I didn't find "CONVERSION" variable in UIInput class. Is the book wrong? And what's the correct way?
    javax.faces.component.UIInput.CONVERSION=Please correct your input

    I didn't choose any special in JDeveloper IDE. I just selected "new" to create a file called "message.properties" and put the line there. I didn't specify converters excepts declaring the type in the Jave Beans. I guess the converting is done by the JSF framework automatically. It must be a JSF converter since I created the page as a JSF page.

  • Issue in Excel to XML Conversion

    Hi Gurus,
    I am creating a custom java module in sap nwds 7.3 for Excel to XML Conversion. But I am getting following error
    Classpath dependency validator message.
    Classpath entry  will not be exported or published. Runtime ClassNotFoundExceptions may result.
    I imported the Jars from a different PI system and i am using NWDS in local PC with creating a separate folder with all JARs and also imported them using build path option.
    This issue is occuring for all the jars imported.
    I am using following code.
    import java.io.FileInputStream;
    import java.io.FileOutputStream;
    import java.io.InputStream;
    import java.io.OutputStream;
    import java.util.Map;
    import com.sap.aii.mapping.api.StreamTransformation;
    import com.sap.aii.mapping.api.AbstractTrace;
    import java.util.HashMap;
    import jxl.Cell;
    import jxl.Workbook;
    public class JavaMappingExcelToXML implements StreamTransformation{
    private Map map = null;
    private AbstractTrace trace = null;
    public void setParameter(Map arg0) {
    map = arg0; // Store reference to the mapping parameters
    if (map == null) {
    this.map = new HashMap();
    public static void main(String args[]) { //FOR EXTERNAL STANDALONE TESTING
    try {
    FileInputStream fin = new FileInputStream ("c:/ashu.xls"); //INPUT FILE (PAYLOAD)
    FileOutputStream fout = new FileOutputStream ("C:/Users/ashutosh.a.upadhyay/My Documents/ashuXML2.xml"); //OUTPUT FILE (PAYLOAD)
    JavaMappingXLStoXML mapping = new JavaMappingXLStoXML ();
    mapping.execute(fin, fout);
    catch (Exception e1) {
    e1.printStackTrace();
    public void execute(InputStream inputstream, OutputStream outputstream) {
    String msgType = "Message Type name will come here";
    String nameSpace = "Namespace Name will come here";
    String xmldata = "";
    try {
    Workbook wb = Workbook.getWorkbook(inputstream);
    xmldata ="<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"+ "<ns0:"+msgType+" "+"xmlns:ns0=\""+nameSpace+"\n">";
    Cell[] cells ;
    Cell[] cellNames ;
    cellNames = wb.getSheet(0).getRow(0);
    for(int j=1;j<wb.getSheet(0).getRows();j++){
    xmldata = xmldata+"\n<Record>\n";
    cells = wb.getSheet(0).getRow(j);
    for(int i=0;i<wb.getSheet(0).getColumns();i++){
    xmldata = xmldata+"\t<"+cellNames[i].getContents()+">"+cells[i].getContents()+"</"+cellNames[i].getContents()+">\n";
    xmldata = xmldata+"</Record>";
    xmldata = xmldata+"\n</ns0:"+msgType+">";
    System.out.print(xmldata);
    xmldata.getBytes();
    wb.close();
    byte by[] = xmldata.getBytes();
    outputstream.write(by);
    inputstream.close();
    outputstream.close();
    System.out.println("\n"+"File processed");
    catch (Exception e) {
    e.printStackTrace();
    Request you to guide how to resolve this issue.
    Thanks  in advance

    Thanks Anand,
    PDF shared by you was extremely helpful. Now I have successfully developed and deployed the adapter. But while using it in Communication Channel I am getting following error.
    Error: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name localejbs/ExcelToXML, cannot resolve object reference. [Root exception is javax.naming.NamingException: Error occurs while the EJB Object Factory trying to resolve JNDI reference Reference Class Name: Type: clientAppName Content: sap.com/SAP_Exel_To_XMLEAR Type: interfaceType Content: local Type: ejb-link Content: Excel_To_XML Type: jndi-name Content: ExcelToXML Type: local-home Content: sap.com.excelToXML.Excel_To_XMLLocalHome Type: local Content: sap.com.excelToXML.Excel_To_XMLLocal com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/SAP_Exel_To_XMLEAR; nested exception is: java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/SAP_Exel_To_XMLEAR]. at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:398) at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:182) at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55) at com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:144) at com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:63) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:76) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:33) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:226) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:283) at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:434) at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:223) at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:242) at javax.naming.InitialContext.lookup(InitialContext.java:351) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:69) at com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:50) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.getModuleLocal(ModuleProcessorBean.java:419) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:287) at sun.reflect.GeneratedMethodAccessor946.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:74) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at com.sun.proxy.$Proxy3299.process(Unknown Source) at com.sap.aii.adapter.file.File2XI.send(File2XI.java:3605) at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1374) at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:669) at com.sap.aii.af.lib.scheduler.JobBroker$Worker.run(JobBroker.java:534) 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:182) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:280) ]
    pl
    please help

  • Sender file adapter conversion Error!!

    Hello every one....
    I am stuck with a problem...in my scenario,, there are possiblities that file may contain more than required paramters... in such case,,, paramters defined in conversion should go ahead and others should be ignored...
    for this very purpose i added the paramter:
    row.fieldSeparator                 ,
    row.fieldNames                     orderno,authcode,status
    row.endSeparator                  'nl'
    row.additionalLastFields      ignore
    the scenario works fine if the file contains thrree comma separated values but it raises an error if no of paramters increase as :
    Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting
    document line no. 1 according to structure 'row':java.lang.Exception: ERROR in configuration: more
    elements in file csv structure than field names specified!
    we are using PI 7.... does it require some more configuration in additoin to paramter row.additionalLastFields
    any help in this regard would be highly appreciated...
    thanx

    this parameter is already set, and this is the exact behavior i want from adapter engine...  but the problem
    here is different... the exception is raised at communication channel's conversion routine level,,, the retry
    interval is not the one defined in visual admin but infact the interval (polling) time defined in communication
    channel.... the system does'nt stop after 3 attempts,, but infact keep on trying to read it....
    one peice of information i  have found is in sap note:821267 , which states:
    *Q35:*
    Q: I have configured a File Sender channel with File Content
    Conversion or a custom-developed module, which may throw an
    exception. When the File Adapter encounters an invalid file, which
    triggers a conversion error or an exception in a module, the
    adapter will enter a retry interval and upon each following
    processing attempt try to process the faulty file. This basically
    prevents the File Adapter from picking up files that are located
    after the fauilty file according to the configured sort order. How
    can I change this behavior?
    o A: This is by design. When the File Adapter encounters an invalid
    file, manually remove this file from the configured source
    directory. You can configure an alerting rule to get notified each
    time this occurs.
    We are currently evaluating possible solutions that could be used
    to skip this manual interaction.
    now can there be a way around to make communication channel read the file only 3 times (value defined in adapter engine profile in visual admin)
    I have thaught of writing of module.... but the error is raised even before calling module !!
    any further clue ???

  • XML-22009: (Error) Attribute 'select' not found in 'xsl:value-of'

    Hello,
    I'm a long-time Siebel developer but novice to BIP, trying to enhance some complex rtf templates that an experienced xdo/bip developer (contractor) designed for us in the past, with a couple of new fields that have been added to the integration object.
    All templates and sub-templates receive 'no errors found' when using add-in tool selection of 'Validate Template'. Unfortunately we cannot utilize the 'preview' capability due to the way the sub-templates are called, so only way to test is to upload into server and attempt to run real-time.
    This results in UI error of SBL-OMS-00203, which when we dig into the xdo log file turns out to be:
    <Line 648, Column 88>: XML-22009: (Error) Attribute 'select' not found in 'xsl:value-of'.
    I have exported all templates and sub-templates into XSL-FO Style Sheet and looked at line 648 column 88, and none of them seem to correspond to this line/column combination (in fact most exports do not even go that high in lines).
    Googling 'XML-22009' hasn't proven to be of much help, so reaching out to the xdo experts in this forum.
    How are the line/column #'s determined in the xdo log output?
    I am pretty sure that it must be some issue with my 'Main' template, since none of the sub-templates have been changed (and the current version of the report, without the new fields incorporated, still runs fine from the UI). In the XSL-FO format export of the (modified, with new fields added) 'Main.rtf' file, line 648 places it right in the midst of a bunch of hex which corresponds to an imbedded image (which was also part of the existing template, no change there) and that line only has 65 columns (i.e. doesn't even go up to 88), so I'm questioning how valid the Line/Column information is in the xdo log error message.
    Any hints on troubleshooting this one would be greatly appreciated!
    Thanks & Regards,
    Katrina

    Hi,
    as I wrote in the inital message, we even left out the output method or used "application/pdf". The result is unfortunately always the same. And I still claim this is not a problem with the stylesheet itself, it has to do something with the mobile's environment.
    Something I didn't tell: we have 2 servlets in our application, 1 responsible for output in html and 1 in pdf. The .fo stylesheet passed to the 'html servlet' is parsed correctly (and shows the source code, because it does not know about fo and conversion to pdf), the .xsl stylesheet passed to the 'pdf servlet' raises same exception/same line. You might tell us that there is a problem with the 'pdf servlet', but once again: why in online it is working?
    Greetings and thanx very much for your precious time!

  • File Content Conversion Error

    Hello,
    I have Async. File receiver scenario in which the following is the XML message structure. This is received by the file adpater.
    <ns1:MT_Info_File xmlns:ns1="urn:http://freemanco.com/xi/info_list">
       <TYPE>
         <FileItem>
               <FileName>DD11022007</FileName>
          </FileItem>
      </TYPE>
      <DATA>
          <LineItem>   <LineEntry>234567891234567890123456789012345678901234567890</LineEntry>
          </LineItem>
       <LineItem>
    <LineEntry>95473523647586969587265245437586979798376524253586</LineEntry>
        </LineItem>
      <DATA>
    <LineItem</ns1:MT_Info_File>
    <u><b>I want to write only folowiing DATA structure to file. I do not want to wite contents of TYPE structure</u>
      <DATA>
          <LineItem>   <LineEntry>234567891234567890123456789012345678901234567890</LineEntry>
          </LineItem>
       <LineItem>
    <LineEntry>95473523647586969587265245437586979798376524253586</LineEntry>
        </LineItem>
      <DATA></b>
    In the receiver file adpater I have follwoing <u><b>File content conversion parameters</b></u>.
    RecordSetStructure: DATA,LineItem,*
    *.addHeaderLine     0
    *.fieldFixedLengths     301
    *.fixedLengthTooShortHandling     Error
    *.endSeparator     nl
    LineItem.fieldSeparator     nl
    DATA.fieldSeparator     nl
    While testing I got following error. Looks like it is expecting some values for FileItem element in the XML.
    <b>Error</b> Attempt to process file failed with java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'
    <b>Error</b> MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'
    <b>Error</b> Exception caught by adapter framework: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'
    <b>Error</b> Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'.
    How to resolve this issue? I appreciate your help.
    Thank you,
    Balaji

    Balaji,
    I would suggest to remove FileItem and LineItem in your receiver datatype. They are increasing the hierarchy of your content conversion. If you do that then you will have
    <ns1:MT_Info_File xmlns:ns1="urn:http://freemanco.com/xi/info_list">
    <TYPE>
    <FileName>DD11022007</FileName>
    </TYPE>
    <DATA><LineEntry>234567891234567890123456789012345678901234567890</LineEntry>
    <LineEntry>95473523647586969587265245437586979798376524253586</LineEntry>
    <DATA>
    </ns1:MT_Info_File>
    Then in content converstion give this parameters:
    Record structure :  TYPE,FileName,DATA,LineEntry
    TYPE.fieldfixedlengths   : 0
    FileName.fieldfixedlenghts:0
    DATA.fieldfixedlenghts:0
    LineEntry.fieldfixedlengths:301
    LineEntry.endSeparator:'nl'
    Then it should work. Also you can use FileName in your variable substituition. Also please see this weblog on how to use FileName in variable substitution:
    /people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
    If you dont want to remove FileItem and LineItem then add these also in your content conversion. Then the parameters would be:
    Recordset:  TYPE,FileItem,FileName,DATA,LineItem,LineEntry
    TYPE.fieldfixedlengths   : 0
    FileItem.fieldfixedlengths:0
    FileName.fieldfixedlenghts:0
    DATA.fieldfixedlenghts:0
    LineItem.fieldfixedlengths : 0
    LineEntry.fieldfixedlengths:301
    LineEntry.endSeparator:'nl'
    Regards,
    ---Satish

  • ** File Content Conversion Error in Receiver CC - How to solve this?

    Hi friends,
    My target structure looks like below.
    EmployeeJobDetails                                        --> Message Type
       JobCode                                                      --> Node
            EmployeeNumber            xsd:string
            Domain                           xsd:string
       JobTrack                                                     --> Node
             Department                    xsd: string
             Position                         xsd: string
    I use the FCC parameters in the receiver CC as below:
    Recordset Structure:    JobCode,JobTrack
    JobCode.fieldSeparator = |
    JobCode.endSeparator = 'nl'
    JobTrack.fieldSeparator = |
    JobTrack.endSepartor = 'nl'.
    Because, we want the output like below
    1099|Raja
    Accts|JuniorAccountant
    1100|Ram
    HR|Recruiter
    like this.
    In this scenario Source is XML and target is txt file.
    I am using XSLT Mapping. The FCC works fine, if my source input file contains some records. But, when we send empty source XML file as below
    <?xml version="1.0" encoding="UTF-8"?>
    <EMPLOYEE_DATA/>
    Mapping works fine. Message is processed successfully in SXMB_MONI. The payload in response also comes with Message Type name like below
    <EmployeeJobDetails    namespace >
    </EmployeeJobDetails>
    While convert this, the system throws below error.
    Error Message:
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)'
    Friend, how to convert this when source XML is empty.
    But, if we remove JobTrack node in target strucutre and remove the JobTrack parameters in CC, then if we send the same empty XML file FCC is working  fine and  we  get the target text file 0 KB. (Amazing !!)
    But, in the first case, how to solve the issue?
    Kind Regards,
    Jegathees P.

    Hi friends,
    If we remove JobTrack node in target strucutre and remove the JobTrack parameters in CC, then if we send the <b>same empty XML file</b> FCC is working fine and<b> we get the target text file 0 KB</b>. (Amazing !!)
    But, if we give parameters like JobCode,JobTrack then send pass the same empty file, we face the problem 'File Content Conversion' Error.
    Searching solution for this problem ...

Maybe you are looking for