Reg: FVU file conversion error

Dear All,
While i try to validate the txt file generated from SAP by FVU utility, I'm getting the error that
'T-FV-1000 Invalid File Header Record Length'
The file header line of my file is below for reference
1^FH^NS1^R^11032011^123456789^D^ABCD12345F^1^^^^^^^
Also, I went through these threads too, but no gain.
[Re: Generate Quarterly e-TDS File. prob|Re: Generate Quarterly e-TDS File. prob]
[Re: REGARDING TDS|Re: REGARDING TDS]
Regards,
Bala

Hi,
Issue resolved. Problem is TAN no, MOBILE no of TDS deductor, and BSR code not been updated in text file that we generate thrugh J1INQEFILE.
I have done manually by putting these things in text file and uploaded. I got the FUV file.
For TAN updating, SAP told us to apply some note.
SO, issue is NO MORE now.
Thanks

Similar Messages

  • FVU file conversion process related issues

    Hi,
    I am in process of conversion of text file into FVU file for TDS purpose.
    When I get text file through J1INQEFILE, its not conatining TAN of deductor.
    I checked in configuration.....like section code place, business place and even in SM30 J_1I_SECCODE....TAN is there at all three places...
    I have three requirements now
    1. How to update TAN in text file
    2. I want to get mobile no of TDS deductor in text file
    3. Where to update BSR code and even i want it to be updated in text file.
    I expect some of the experts to reply who had done already for their requirements. Its urgent please...

    Hi,
    Issue resolved. Problem is TAN no, MOBILE no of TDS deductor, and BSR code not been updated in text file that we generate thrugh J1INQEFILE.
    I have done manually by putting these things in text file and uploaded. I got the FUV file.
    For TAN updating, SAP told us to apply some note.
    SO, issue is NO MORE now.
    Thanks

  • File Conversion error in Receiver File Adapter

    Hi ,
    I am facing the below error in  receiver file adapter .
    Conversion initialization failed: java.lang.Exception: java.lang.NumberFormatException: For input string: "4|8|10|2|10|4|10|4|40|40|40|1|20|2|20|8|40|0|12|12|12|1|12|4|4|8|40|8|8|8|8|12|40|8|10|10|10|10|10|1|10"
    Kindly suggest !
    Regards,
    Hemanthika

    Hi,
    Check it - File adapter is active ? try to Re-activate the same.
    Also do CPACache Refresh.
    Still problem, tyr out by restarting the Adapter Engine.
      I guess you're just trying to send all the data in your file record to a <data> element as a whole. If so, this blog will help you:
    Configuring Generic Sender File CC Adapter
    Under certain operating system platforms, such as Solaris, the APIs used by the Java Runtime (JRE) are not Unicode-aware. Consequently, the JRE needs to be configured to correctly interpret the character set it receives from the operating system.
    This is configured through the "file.encoding" system property as well as the "LANG" environment variable.
    Make sure you set "file.encoding" to a character set (such as ISO-8859-1) that supports the special characters you would like to process. This system property can be configured by appending "-Dfile.encoding=<encoding>" to the Java VM parameters section of the SAP J2EE Config Tool.
    Additionally, you need to set the "LANG" environment variable to a locale that supports more than 7 bits, such as "de.ISO8859-1". The encoding you specify in the LANG environment variable needs to match the encoding set via "file.encoding".
    You can persistently configure the environment variable by setting it in the profile $HOME/.sapenv_$HOSTNAME.csh of the <sid>adm user: setenv LANG de.ISO8859-1
    Refer this article
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10dd67dd-a42b-2a10-2785-91c40ee56c0b
    See below link
    http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    Please refer this thread .
    File Adapter Not Initialized Error
    Cheers,
    Regards,
    Suryanarayana

  • File conversion error when combining files

    Hello,
    I am using Adobe Create to combine several files (both word and pdf) into a single pdf document.  I have done this several times in the past with no problems.  However today it won't allow me to combine any documents which are already in pdf format.  The system generates an error for each of these documents as: "Conversion Failed".  I am clearly not trying to convert them, but rather to combine them...  Any ideas?

    Hi gina_hall_7848,
    If you're combining both Word and PDF files into PDF, there is some conversion happening (with the Word docs, as they're converted into the combined PDF file). If you're getting the error when combining only PDF files--that's another story. It could be that one or more of the files that you're combining isn't in a supported format, or that Adobe PDF Pack is timing out before it can complete the conversion.
    Does the error occur regardless of what files you try to combine?
    Best,
    Sara

  • Word doc file conversion error - virus or OS?

    I have word documents made on the Mac and have only existed on the Mac. When double clicked, some of them will not open anymore. Office prompts to convert the file but no matter what format chosen, the converted file is no good.
    This issue doesn't seem to effect all word docs. Seems like there was an Mac OS update or something that may have caused issue. The system has Parallels running XP and it was thought that might have allowed a virus or caused some corruption. (The virtual PC never had e-mail setup or Office installed.)  Moving the files to another Mac provides the same results. So the files themselves seemed to have changed or it's something in the OS.
    Only difference I have noticed between the two files are, the files that don't open have a file extension and the files that do open have none. The ones with no file extension I think are a legacy from an older OS version that was not as strict on having them. Adding and then removing a file extension does nothing, the OS still sees those files as Word docs.
    Removing the file extension on a file that has one, does not change convert file prompt. In fact it just makes the file loose it application type so the OS doesn't know what type of file it is.
    All of this was happening using Office 2008 (Word 12.3.6) so today I bought Office 2011 today to see if the issue could be resolve and got the same results.
    I have read many threads on Word conversion issues but none like this one or that doesn't involve a PC. Anybody have thought or seem this? Maybe there is a work around I'm missing?
    Thanks for your time.

    Thank you about your XP answer. That makes sense. I would think that would be a major flaw in the Parallels product.
    That leaves OS versions possibly. All these word docs were created in Office 2008 after the company got the Macs and made the switch. The only things that really changed over that time was OS upgrades and MS Office updates.
    The issue only came to known last year. Inital research and current have found nothing to act on.  Other issues I've read involve going between platforms and that's just not the case here. We threw the PCs out after the move.
    This issue effects many files throughout our client file folders, the only differences being as I noted. Attach two JPEGs showing a good (no extension) and bad (has file extension) file info.

  • Flat File Conversion Error: Unable to initialize communication channel

    Dear experts.
    I have a file to flat file scenario. I just wanted to test this first because it's the first time. I followed this blog: /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    I get this message: Channel has not been correctly initialized and cannot process messages. I looked around on the forum and in other blogs, and it seems something is wrong with my Content Conversion Parameters. Could you please advise?
    The message is a small customer test message:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_TEST xmlns:ns0="urn://xi/csr/customer">
      <Customer_File>
        <Customer>
          <Name>xxx</Name>
          <Last>xxxxxxxx</Last>
        </Customer>
      </Customer_File>
    </ns0:MT_TEST>
    The parameters I am using are:
    Recordset structure: Customer_File,Customer
    Customer.addHeaderLine: 0
    Customer.fieldSeparator: #
    Customer_File.fieldSeparator: 'nl'
    Customer.endSeparator: 'nl'
    The mapping I am using is one-to-one.
    This is not working for me...
    Furthermore, I would like to set the Name and Last tag to set field lengths. Is this possible for these tags??
    Thanks in advance.
    *Will reward points for helpful answers

    hi
    PLz try with the following steps:
    chk the occurence of customer.
    if the customer occurence is (0-------unbounded) then
    ur recordset structure is  Customerfile,Customer*
    may helful.
    THanks
    MANas

  • FVU file Validation Error

    Hi Experts,
    We did Quarterly TDS Return through T. code J1INQEFILE and then validating same in our software Skroydov but we are facing some validation errors because of some cases as under:
    Case 1
    Document No.1700000040 Down Payment amount is Rs.22060/-and TDS @11.33% is Rs.2499/-.
    1900000308 is Invoice Base amt. 20000+service tax @10% 2000 + Ecess @2% 40 + HS Cess @1% 20.
    Total invoice amt. Is Rs.22060/- Now TDS system deducted TDS on Rs.20000/- i.e. Rs.2266/- Not on Service Tax?
    1700000096 down payment converted special to normal Gl. Here we converted exact invoice amount Rs.22060/- TSD Rs.2499/-
    The  TDS Difference in vendor A/c i.e. Rs.233/- (2499-2266=233)
    This difference is because of Service Tax.
    Case 2
    1700000053 Down payment is Rs.169167/- and TDS @ 11.33% is Rs.19167/-
    1900000729 is invoice base amt 80866+ service tax 8086.60 + EC 161.73 + HS Cess 80.87 =89195.20 system TDS deducted on Base amt. i.e. Rs.80866/-tds is Rs.9162/- . Not on Service tax.
    1700000274 down payment converted special to normal Gl. Here we converted exact invoice amount Rs.89195/- TDS Rs.10106/-
    Now TDS Difference lying in vendor A/c i.e. Rs.944/- (10106-9162=944)
    This difference is also due to Service Tax.
    Case 3
    1700000030 Down Payment of Rs.10000/- TDS is Rs.1030/-
    1700000129 Down payment converted special to normal Rs.10000/- TDS is Rs.1030/-
    Please suggest how to rectify these processes and in future how to handle these cases.
    Thanks and Regards,
    Jiyalal Pandey

    Hi,
    Please refer to these explanations as under that will helpful to you:
    If Down payment amount is more then invoice amount then at the time of converting into normal through T. code F-54 we have to consider only invoice amount rest remaining amount of down payment must be converted with the other invoice references accordingly.
    In other case if at the time of converting into normal through T. code F-54 we have balance of amount from down payment in the vendoru2019s account then that remaining amount must be converted later on with the other invoice references accordingly

  • PDF file Conversion

    Hello Friends,
    In SAP, SOST Transaction, we can see the pdf document of delivery, but when send to the customers by email, the pdf file doesn't open at customer end.SOST sends this
    It gives the file conversion error.
    What we can do from developer's perspective to solve this ?
    Is this a ABAP issue?
    Regards
    Prashant

    MOVE p_spoolno TO lv_spoolno.
    * CONVERT THE SPOOL TO PDF
      CALL FUNCTION 'CONVERT_OTFSPOOLJOB_2_PDF'
        EXPORTING
          src_spoolid                    = lv_spoolno
          no_dialog                      = lc_no_dialog
    *     DST_DEVICE                     =
    *     PDF_DESTINATION                =
       IMPORTING
         pdf_bytecount                  = lv_bytecount
    *     PDF_SPOOLID                    =
    *     OTF_PAGECOUNT                  =
    *     BTC_JOBNAME                    =
    *     BTC_JOBCOUNT                   =
       TABLES
         pdf                            = gt_pdf_output
       EXCEPTIONS
         err_no_otf_spooljob            = 1
         err_no_spooljob                = 2
         err_no_permission              = 3
         err_conv_not_possible          = 4
         err_bad_dstdevice              = 5
         user_cancelled                 = 6
         err_spoolerror                 = 7
         err_temseerror                 = 8
         err_btcjob_open_failed         = 9
         err_btcjob_submit_failed       = 10
         err_btcjob_close_failed        = 11
         OTHERS                         = 12
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ELSE.
    * Transfer the 132-long strings to 255-long strings
        LOOP AT gt_pdf_output INTO wa_pdf_output.
          TRANSLATE wa_pdf_output USING ' ~'.
          CONCATENATE v_buffer wa_pdf_output INTO v_buffer.
          MODIFY gt_pdf_output FROM wa_pdf_output.
          CLEAR wa_pdf_output.
        ENDLOOP.
    TO CONVERT THE DATA INTO PDF FORMAT ELSE THE PDF FILE*
    WON'T OPEN & REPORT WOULD GIVE A MESSAGE THAT*
    THE FILE IS DAMAGED & COULD NOT BE OPENED*
    TRANSLATE v_buffer USING '~ '.
        CLEAR : wa_messg_att,
                gt_messg_att.
        DO.
          wa_messg_att = v_buffer.
          APPEND wa_messg_att TO gt_messg_att.
          SHIFT v_buffer LEFT BY 255 PLACES.
          IF v_buffer IS INITIAL.
            EXIT.
          ENDIF.
          CLEAR wa_messg_att.
        ENDDO.
      ENDIF.

  • What does the "conversion error" I get when converting a pdf file to Microsoft word?

    What is the "conversion error" I get when converfting a pdf file to aMicrosoft word?

    Adobe reader with export to PDF
    Sent from my iPhone 5
    Marty Kennedy

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

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

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

  • Premature end of file Error in the File conversion

    Hi Experts
    Working on File to Proxy scenario and file is picking up by the XI server and in the message mapping I am receiving the following error
    Can anyone let me know what is Premature end of file, Do I need to specify any parameter in the Content Conversion additional than normal parameters
    Thanks
    PR
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <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_ISO_to_ECC_FROI_SROI_TA_TE_TR_T~</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException:</SAP:P2>
      <SAP:P3>Premature end of file.</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ISO_to_ECC_FROI_SROI_TA_TE_TR_T~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Premature end of file.</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    check out this link. it might help you..
    File Content Conversion Error in PI 7.1 (file to Proxy)

  • SCOT error "File format conversion error"

    Dear All,
    When a PDF file is sent as a FAX, the SCOT throws the following error with message XS 812:
    No delivery to <fax_number>
    Message no. XS812
    Diagnosis
    The message could not be delivered to recipient <fax_number>. The node gave the following reason (in the language of the node):
    File format conversion error
    Can anybody suggest what could be the problem?
    Note that the normal PCL and RAW data are being sent to the same FAX number without any problem.
    Thanks
    Sagar

    Hello,
    You need to specify the correct formats:
    Check this link:
    http://help.sap.com/saphelp_nw70/helpdata/EN/b0/f8ef3aabdfb20de10000000a11402f/frameset.htm
    Regards,
    Siddhesh

  • I have paid for a year subscription, but all the PDF's I attempt to export to Word give me a "Conversion Error" message, citing that the "file's security settings do not allow export." I want a refund. Adobe, please advise. Thank you.

    I have paid for a year subscription, but all the PDF's I attempt to export to Word give me a "Conversion Error" message, citing that the "file's security settings do not allow export." I want a refund. Adobe, please advise. Thank you.

    Hi la recruiter,
    There are a few types of files that Acrobat can't convert--and PDF files with security applied is one on them. I'm happy to cancel your subscription, if you decide that it's not going to work out for you. Please confirm that you'd like me to proceed with the cancelation, and I'll take care of it right away.
    Best,
    Sara

Maybe you are looking for