Problems Exporting to Excel in Acrobat XI

I have some problems exporting a PDF to excel in Acrobat Std or Pro XI but not in Acrobat Std or Pro X.  When exporting in X all the columns and rows are created as they should be, but in XI everything is slammed to the left in one column.  Has anyone experienced anything like this and is there maybe a setting that I am missing in the conversion process that was automatic in X but is not in XI?
Thanks in advance for the help.

I am having a similar problem.  I used the 30 trial acrobat XI and it exports pdf to excel perfectly.  However, after buying and installing the program, the export is all messed up with data not in correct columns...etc.
Acrobat tech controlled my computer and experimented a bit.  He said that my pdf was created by a 3rd party application called crystal reports and that acrobat doesn't work on about 50% of these 3rd party creations.  I said, then why does the trial work so well.  He said there is nothing different between the trial version and the actual purchased version.  This cannot be true or something else is up.  I told him I wanted to uninstall my purchased program and reinstall the trial version just to prove it to him.  He said it would not allow me to reinstall the Trial.
After my phone call was over, I did it anyways.  It did let me reinstall the trial version.  I took 7 pdf sent to me from work from each server (wanted to make sure one of my servers was not sending different types of pdfs).  Each pdf did not convert successfully when I used my purchased version.  Then I uninstalled and reinstalled the trial version.  The trial version successfully exporting my pdf to excell (all 7 of them).  Something weird is going on.
Any insight would be appreciated.

Similar Messages

  • Problem Export to Excel it takes long time and Takes more space.

    Hello All,
    when we export to Excel in portal(reports), it takes long time and it takes more space.
    how to overcome this problem please any one knows provide the proper solution for this issues
    Regards,
    Ch.

    Hi Chetans,
    I have had the same problem, and I had to create a OSS message to SAP in order to solve this issue, until now I don't have an answer. They made me to change a lot of configuration in Java and BW without luck. To tell you more, when we try to export to excel the java instance restarts aumotatically.
    But we have this problem, when we try to export a huge quantity of data, so I found a note which says the limitation of exporting to excel. Take a special attention to the Performance section.
    Note 1178857
    [https://service.sap.com/sap/support/notes/1178857|https://service.sap.com/sap/support/notes/1178857]
    I recomend you that you create a message to SAP. If you find a solution, please let me know.
    Regards, Federico

  • Problem exporting to excel when using embedded web templates through WAD

    Using web templates designed with WAD, we are experiencing an issue when trying to export excel when using embedded web templates. 
    We have set up tabstrips within our templates that load other templates (embedded into the global template). 
    Upon right clicking on any query and choosing "Export to Excel", any query that is in one of the tabs using the embedded web template item does not show up.  Any queries in natively in the global web template will export and show up fine.
    Any thoughts on how to enable something like this, or workarounds to make this work?  We decided to split up these templates for performance reasons and can't go back from that decision.  Also let me know if you need a better explanation of what we're trying to do.
    Thanks in advance!
    Jonathan

    Hi SDBI,
    Is this in place of loading a new template per tab?  We are using container layouts in all of our templates so we can link things into tabstrips as well, we have just split up some templates to be embedded into tabs for performance reasons and data locking.
    Also when exporting, we are looking for all of the items displayed at that time to be exported, however only the items from the global template show up, not all of the displayed queries.  For example, anything outside of the tabstrip will export perfectly, but since the query embedded into the template the tabstrip is loading is not part of the native web template, it does not show up.
    Seems like a tool limitation to me when embedding templates?
    Thanks,
    Jon

  • Webi reports - Problem exporting to excel

    HI,
    I have exported a webi report as an excel file. The report contains a column with numeric values preceded by a dollar sign. After exporting to excel, i want to calculate the sum of the values in that column. However some cells show a numeric value, while some others show string value (i.e. text) because of which I am not being able to calculate the sum. Please help.

    Hi there, 
    Is the object that you are exporting with the dollar sign a string?  If so then this is normal because it is not numeric.  I tried the workflow in Excel and wen I try to apply a sum, it seems to change one of the values from string to numeric but this is within excel.  Maybe this is happening to you too.  In order to be able to add a calculation correctly, you need to change the object to a numeric.  You can do this by creating a new variable in webi, removing the $ and converting it to a numeric. For Ex:  "=ToNumber(Substr([dollar string object];2;10))".  Note, if you still want the $ to appear, you can use the format number feature.
    Hope this helps!

  • Crystal 11.5 truncating column headers on export to excel

    Hi,
    We are currently (or finally as the case may be) upgrading our reports from Crystal 8.5 to Crystal 11.5 (which I know is a few versions behind but unfortunately the software that we integrate with is only compatible to 11.5).
    However, I've been having a problem exporting to excel.
    The column headers (which can be in a range of report header/page header/group header) are truncating to the the length that they display on the screen before the export.  When I view them in crystal viewer I can see that the entire text field is available.  However this does not flow through to export to excel.
    I have utilised the "Can grow" formatting option however this then creates a merged field up 3 rows high in excel and the report then has problems using excel functions like sort etc. 
    I also attempted to use the data only option which does export the full text in the column names but then I lose the rest of my formatting.
    There were no issues exporting from v8.5
    I have snapped to grid.
    The actual data exports without issue it is only the column headers (text) which pose a problem.
    I am unable to reduce the amount of data that we include in our report to free up space to display the entire text.
    I would prefer to not reduce to a 4pt text size to ensure that it exports correctly as this will have significant impacts for those people who actually export the reports.
    Is anyone able to shed some light on how to resolve this issue?   I've googled and searched these forums extensively but can't quite find a resolution to the issue and would really appreciate any assistance that anyone can offer me. 
    Kind regards
    Janne

    Ian
    It works for me whether my headers are text fields or field headers. Once I export them I expand the columns and set the cells to wrap, and I get the complete contents. Ditto for the fields themselved, and text fields containing data fields.
    I always export excel(97-2003)data only with Column width based on objects in the details & checking   Export object formating, Maintain relative object position, Maintain column alignment, export page header and page footer, Simplify page headers.
    Allow fields to grow is off on everything during exports.
    Note: nearly all my reports are designed in Crystal 2008 without any SQL commands and all exports are done manually. Perhaps it is a XI.5 issue?
    Edited by: Debi Herbert on Oct 5, 2011 10:07 AM

  • Problem exporting a Financial Report to excel

    Hello Everyone,
    Of several users who have tested this functionality, I only have 1 user who is experiencing this problem, however we can't figure out what's wrong... Here is what is happening:
    1. Run a financial report from the web-portal using HTML preview
    2. Once the report is displayed in HTML, he goes to File | export | fully formated excel file (he also tried with the query ready report and had the same problem)
    3. he is prompted to either save or open this xml file
    4. he selects open, he gets an excel window and is prompted with the following: "Please select how you would like to open this file:" and the radio button options are: "as an xml list", "As a read-only workbook", "use the xml source task pane".
    5. he selects "as an xml list" he then is prompted with the following: "The specified source does not refer to a schema. Excel will create a schema based on the xml source data."
    6. he clicks on "ok" and the result is what looks like an excel pivot table except is says "error" in one of the cells and then an adjacent cell says: Logon Failed. User Name must not be empty.
    No matter which combination of the options he chooses, he sees the same result.
    In addition, I know it is not a problem with his ID b/c he can run the report AND export to excel just fine when he does it from my computer!
    Has anyone seen this problem before? Is this maybe a setting that needs to be changed? etc...?
    FYI - we are in the final stages of migrating to system 9 so our current configuration is as follows: Financial Reports / Workspace version 9.3.1 however his run time client on is version 7.1.2 and the essbase cube is version 9.3.1. I have several other people who have run the same report, against the same essbase cube, also using the ver 7 RTC and it works fine.
    Any ideas???
    Thanks in advance for any help!
    Alina

    Hello Everyone,
    Of several users who have tested this functionality, I only have 1 user who is experiencing this problem, however we can't figure out what's wrong... Here is what is happening:
    1. Run a financial report from the web-portal using HTML preview
    2. Once the report is displayed in HTML, he goes to File | export | fully formated excel file (he also tried with the query ready report and had the same problem)
    3. he is prompted to either save or open this xml file
    4. he selects open, he gets an excel window and is prompted with the following: "Please select how you would like to open this file:" and the radio button options are: "as an xml list", "As a read-only workbook", "use the xml source task pane".
    5. he selects "as an xml list" he then is prompted with the following: "The specified source does not refer to a schema. Excel will create a schema based on the xml source data."
    6. he clicks on "ok" and the result is what looks like an excel pivot table except is says "error" in one of the cells and then an adjacent cell says: Logon Failed. User Name must not be empty.
    No matter which combination of the options he chooses, he sees the same result.
    In addition, I know it is not a problem with his ID b/c he can run the report AND export to excel just fine when he does it from my computer!
    Has anyone seen this problem before? Is this maybe a setting that needs to be changed? etc...?
    FYI - we are in the final stages of migrating to system 9 so our current configuration is as follows: Financial Reports / Workspace version 9.3.1 however his run time client on is version 7.1.2 and the essbase cube is version 9.3.1. I have several other people who have run the same report, against the same essbase cube, also using the ver 7 RTC and it works fine.
    Any ideas???
    Thanks in advance for any help!
    Alina

  • Export to Excel problem in Signal Express 2012

    Equipment used: PXIE-8102 CELERON T3100 1.9GHZ Controller Windows 7, PXIE-1071 4 Slot Chassis, PXIE-4140 4-Channel SMU 1.7.5 version.
    I am using Signal Express 2012 and the SMU to plot the I/V characteristics of FET and other active devices. I am able to obtain the anticipated curve traced results but I am not able to Export the data to Excel directly from the Data View using the Microsoft Excel option. The error message is: Data could not be sent to Microsoft Excel. Please ensure you have a properly licensed version of Microsoft Excel. See attachment.
    We have checked our version of Microsoft Office, it is Professional Plus and has the correct volume license so it does not revert to a home or student version.
    I have been able to use the Export to Excel function directly from the Dataview when I was using one of the waveform tutorials supplied with Signal Express so I suspect it is a function of the SMU.
    In conversations with an NI support engineer he felt it may be a problem with "an active x call is just not seeing the license for some reason", his suggestion is to drag the data into Excel rather than use the Data view tab. Because the SMU is being used in a production environment it is not really appropriate to have the operator work at this level so I would rather figure a way to have the data exported using the Data View tab.
    Anyway please can you let me know if there are any known work around for this issue.
    Thank you

    Calvin1957,
    I am not seeing any attachments in the first post or this latest post. The images should be added using the attachments section when creating the post. You should also be able to insert an image using the insert image button in the toolbar. Let me know if you have any questions. Thanks!
    Robert B
    Applications Engineer
    National Instruments

  • ALV TO EXCEL PROBLEM? ( 90 COLUMNS ALV CAN'T EXPORT TO EXCEL NORMALLY)

    HI ABAPERS,
    anyone have a alv that have over 90 columns and want to export to excel have experienced abnormal formating (like the header row show only up to 60 column and the rest show up in next row) and the data show in separate line.
    anyway can have a better format?
    also after 90 columns show up on alv, it can't show anymore except modify the layout in run time.
    can we do something before that?
    thanks & regards,
    HOWARD

    Hi HOWARD,
    My Report ouput having more than 90 columns in ALV, while downloading data from ALV to Excel sheet am facing alignment problem. (ie) the output column > 66 are appearing in next line of the excel sheet leads to improper alignment.
    Pls give me a solution as u had already come across this issue..
    Thank & Regards,
    Paramesh.

  • Problem in ALV export to Excel (Local File)

    Hi guys,
    I'm using the option export data do local file, option excel, but some strange behave is happening...
    Some columns are exported without the last digit...
    Ideas?
    Regards,
    LMS

    Hi LMS,
    Use this link.
    Export to excel in ALV
    Problem with Export to Excel from ALV Grid
    Hope this will help you to resolve your problem.
    Regards,
    Vijay

  • Problem in Export to Excel in WAD

    Hi,
    We are facing problems while using the "export to excel" feature in WAD.
    While displaying the report in WEB or even RRMX, the display is fine for all fields of the report. However, when i use the export to excel feature from WAD, the fields with length of 24 characters are not displayed correctly.
    It is displayed as "1.4E+23" (this feild displays numbers), whereas the number should be "140000000000000001232007".
    Please can someone tell me what the possible problem could be.
    Thanks in advance
    Regds
    Priyya

    Hi,
    Take a copy of template 0ANALYZER, it will have all the components which have the web analyzer.
    Check the below link for the same:
    http://help.sap.com/saphelp_nw04/helpdata/en/0d/af12403dbedd5fe10000000a155106/frameset.htm
    Hope this helps........
    Rgs,
    Ravikanth

  • Problem in Exporting to Excel 2007 using CRServer 2008

    Can anyone please help me know the difference between Crystal Reports Server 2008 and Business Objects XI R2? Both the support guides says that it supports Office 2007. I have a problem in exporting the reports to Excel 2007 .I have downloaded the trial version of Crystal Reports Server 2008 but still unable to view my complete reports in Excel 2007 through infoview because few of my report's colums are truncated and it still exports in Excel 2003.I have LiveOfficeXIR2_SP4 and Office 2007 installed. Is it so that i have to switch over to Business Objects XI R2 or any other to solve my problem instead of using Crystal Reports Server 2008 or is it the problem with the version of my Live office.Pls help me regarding this..
    Babita.

    Hi Ani,
       First Thank you for your reply..I have already tried exporting it in Excel 2003 but since the limit is upto 256 columns and that my report's content exceeds this limit, few of the columns are truncated. Thats why i thought that it would be better to export it in Excel 2007. But i could'nt find any way to do it so..Pls help me if there is any other way..
    Babita.

  • Problems Exporting rpts to Excel!

    Post Author: miguelitobh
    CA Forum: Exporting
    Hello Everybody! I´m new in the forum, and i have a question that is killing me... I´ve an application that runs asp and COM+ using Visual Basic... I made another litlle module for Crystal Reports rpts imports... I wrote the code using the Business Objects Samples like example (rtpserver.asp, etc) ands works fine. The problem that i´ve found is: In the export all the options are working, except the 2 excel´s types. When a try do export a report to Excel, i put the file name and try to save, but the application hangs my IIS server... Anyone can help me? I´m using Windows XP SP2, Office 2003 and Crystal Reports XI R2...
    Tahnk´s

    Wannetta,
    When the user filters the data and then exports it to excel; all of the original data is exported rather than the filtered data.
    Can you describe the exact workflow in a bit more detail.  Here is one "gotcha" to consider, which sounds suspicous to your case.  If the user is using InfoView (not WebI), and he or she uses Export to Excel with CSV, then there is no consideration to what has been done in the report, the contents of what you see in the "Results Object" panel from the Edit Query view is what is sent over to the CSV file.  Also, the order of the columns of data is according to what is specified in the "Results Object" panel.  So, just a heads-up to consider if this is happening or not.  Otherwise, please give us the workflow and the version of XI and client's versioin of Java on the workstation...
    Thanks,
    John

  • ALV Export to Excel problem

    Hi All
    I have a problem with exporting a ALV Grid to Excel. If I add the quantity field to my Grid output the excel spreadsheet does not bring through the quantity field and it puts all the other columns one place out. I tried changing field attributes from QUAN to CHAR field and it made no difference.
    I am using the standard sap functionality:
    List > Save > Local File > Spreadsheet
    It works fine as long as I do not include my quantity column? I have tried many other custom FM's with no luck because all of them require you to put in a internal table inside the function but I do not want to send whole internal table to spreadsheet only the ones selected in the ALV Grid. So please do not suggest function modules as I have had no luck with these!
    I need to know how to use the standard sap alv export to excel function with my quantity field? The only issue I can think of that would cause a error would be that I have 50+ columns on the grid and internal table. Even If I put quantity field by itself in the grid then export to excel it brings through the Qty header but no data.

    Hi Atish
    Quantity is below: (RMNGE)
    Data type is QUAN, Length 10, Decimal places 0.
    DATA: BEGIN OF I_DATA OCCURS 0.
             INCLUDE STRUCTURE ZWRNTHDR.
    DATA:   POSNR LIKE ZWRNTITM-POSNR,      "Sales Document Item
             MATNR LIKE ZWRNTITM-MATNR,      "Material Number
             CLRFL LIKE ZWRNTITM-CLRFL,      "Claim Reference Line ID
             PCBPN LIKE ZWRNTITM-PCBPN,      "PCB Part Number
             PCBPX LIKE MAKT-MAKTX,          "PCB Part Number Description
             RMNGE LIKE ZWRNTITM-RMNGE,      "Quantity
             MEINS LIKE ZWRNTITM-MEINS,      "Base Unit of Measure
             WRNTC LIKE ZWRNTITM-WRNTC,      "Warranty Claimed
             WRNTG(3) TYPE C,                "Warranty Given
             FLTCD LIKE ZWRNTITM-FLTCD,      "Fault Code
             MFATE LIKE ZWRNTITM-MFATE,      "Module Fate
             CMNTS LIKE ZWRNTITM-CMNTS,      "Comments
             SRIAL LIKE ZWRNTITM-SRIAL,      "Serial Number
             PFREX LIKE ZWRNTITM-PFREX,      "PFR External
             PFINT LIKE ZWRNTITM-PFINT,      "PFR Internal
             RLCRQ LIKE ZWRNTITM-RLCRQ,      "Replacement Requested
             TCHID LIKE ZWRNTITM-TCHID,      "Technician ID
             PMATN LIKE ZWRNTITM-PMATN,      "Parent Material
             PMATX LIKE MAKT-MAKTX,          "Parent Material Description
             MDLNO LIKE ZWRNTITM-MDLNO,      "Module Number
             MDLNT LIKE MAKT-MAKTX,          "Module Description
             CLVFX LIKE ZWRNTITM-CLVFX,      "Claim Value FX
             CRVFX LIKE ZWRNTITM-CRVFX,      "Credit Value FX
             CRVLC LIKE ZWRNTITM-CRVLC,      "Credit Value Local
             XRATE LIKE ZWRNTITM-XRATE,      "FX Rate
             NAME1 LIKE KNA1-NAME1,          "Customer Name
             MAKTX LIKE MAKT-MAKTX,          "Material Description
             CTYPT LIKE DD07T-DDTEXT,        "Customer Type Text
             BUNTT LIKE DD07T-DDTEXT,        "Business Unit Text
             FRCRT LIKE DD07T-DDTEXT,        "Freight Carrier Text
             FLTCT LIKE ZFLTCODES-FDESC,     "Fault Code Text
             ISRES LIKE ZWRNTITM-ISRES,      "Issue Resolved
             DCODE LIKE ZWRNTITM-DCODE,      "Date Code
             ISTAT LIKE ZWRNTITM-ISTAT,      "Ignore Stats
             LABCL LIKE ZWRNTITM-LABCL,      "Labour Claimed
             MATCL LIKE ZWRNTITM-MATCL,      "Material Claimed
           END OF I_DATA.
    Field Catalog:
    FORM          BUILD_ALV_COLUMNS
    Build Main Page ALV Fieldcat
    FORM BUILD_ALV_COLUMNS.
       CLEAR FIELDCAT_LN.
       ADD 1 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'KUNNR'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-KEY = 'X'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 2 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'CLMID'.
       FIELDCAT_LN-KEY = 'X'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 3 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Claim Type'.
       FIELDCAT_LN-FIELDNAME = 'CTYPT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 4 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'CLREF'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 5 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Business Unit'.
       FIELDCAT_LN-FIELDNAME = 'BUNTT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 6 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'CURCY'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-EMPHASIZE = 'C500'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 7 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'CHKID'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 8 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'RECVD'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 9 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'APVDT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 10 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'CRDRF'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 11 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'RORDR'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 12 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'RORDD'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 13 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'ARVDT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 14 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'TSTDT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 15 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'TEDDT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 16 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'FSTDT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 17 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'FEDDT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 19 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Freight Carrier'.
       FIELDCAT_LN-FIELDNAME = 'FRCRT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 20 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'FRTRF'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 21 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'FRINV'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 22 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'UNAMECR'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 23 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'DATUMCR'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 24 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'UNAMECH'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 25 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'DATUMCH'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 26 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'UNAMEDE'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 27 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTHDR'.
       FIELDCAT_LN-FIELDNAME = 'DATUMDE'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 28 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'POSNR'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-KEY = 'X'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 29 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'MATNR'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-EMPHASIZE = 'C700'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 30 TO COL_POS.
       FIELDCAT_LN-TABNAME   = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'RMNGE'.
       FIELDCAT_LN-SELTEXT_L = 'Qty'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 31 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'CLRFL'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 32 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'PCB Part No'.
       FIELDCAT_LN-FIELDNAME = 'PCBPN'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-EMPHASIZE = 'C700'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 33 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'MEINS'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 34 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'WRNTC'.
       FIELDCAT_LN-DO_SUM = SPACE.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 35 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Warranty Given'.
       FIELDCAT_LN-FIELDNAME = 'WRNTG'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 36 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'FLTCD'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 37 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'MFATE'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 38 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'CMNTS'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 39 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'SRIAL'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 40 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'PFREX'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 41 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'PFINT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 42 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'RLCRQ'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 43 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'TCHID'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 44 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'PMATN'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-EMPHASIZE = 'C700'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 45 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'MDLNO'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-EMPHASIZE = 'C700'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 46 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Customer Name'.
       FIELDCAT_LN-FIELDNAME = 'NAME1'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-KEY = 'X'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 47 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'MAKT'.
       FIELDCAT_LN-FIELDNAME = 'MAKTX'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-EMPHASIZE = 'C700'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 48 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Parent Matl Description'.
       FIELDCAT_LN-FIELDNAME = 'PMATX'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-EMPHASIZE = 'C700'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 49 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'PCB Matl Description'.
       FIELDCAT_LN-FIELDNAME = 'PCBPX'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-EMPHASIZE = 'C700'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 50 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Fault Code Description'.
       FIELDCAT_LN-FIELDNAME = 'FLTCT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 51 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'CLVFX'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-EMPHASIZE = 'C500'.
       FIELDCAT_LN-NO_ZERO = 'X'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 52 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'CRVFX'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-NO_ZERO = 'X'.
       FIELDCAT_LN-EMPHASIZE = 'C500'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 53 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'XRATE'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-NO_ZERO = 'X'.
       FIELDCAT_LN-EMPHASIZE = 'C500'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 54 TO COL_POS.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'CRVLC'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-NO_ZERO = 'X'.
       FIELDCAT_LN-EMPHASIZE = 'C500'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 55 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Module Description'.
       FIELDCAT_LN-FIELDNAME = 'MDLNT'.
       FIELDCAT_LN-COL_POS = COL_POS.
       FIELDCAT_LN-EMPHASIZE = 'C700'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 56 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Iss Resvld'.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'ISRES'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 57 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Date Code'.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'DCODE'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 58 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Ignore Stats'.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'ISTAT'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 59 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Labr Claimed'.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'LABCL'.
       APPEND FIELDCAT_LN TO FIELDCAT.
       CLEAR FIELDCAT_LN.
       ADD 60 TO COL_POS.
       FIELDCAT_LN-SELTEXT_L = 'Matl Claimed'.
       FIELDCAT_LN-REF_TABNAME = 'ZWRNTITM'.
       FIELDCAT_LN-FIELDNAME = 'MATCL'.
       APPEND FIELDCAT_LN TO FIELDCAT.
    ENDFORM.                    " BUILD_ALV_COLUMNS

  • Export to Excel Problem - Page server Error

    Post Author: Preethig
    CA Forum: Exporting
    Crystal Reports were designed using the Seagate Crystal Reports Developer Version 8.5.3.975.The reports does designed are published in the Seagate Crystal Enterprise 8.0.2.6725  across the web.
    When we try to the export these reports to excel from the Crystal report viewer of the Crystal Enterprise it throws up an error" The export format 'U2FXLS:5' is not supported. &#91;on Page Server : <webserver>.pageserver&#93;."
    The webserver as the Following ConfigurationWindows Terminal Edition - Windows 2000Service Pack 4.Seagate Crystal Enterprise 8.0.2.6725
    The Client system on which the "Export to Excel" is performed has the following Configuration.Windows XP Professional Operating SystemService Pack - SP2.Excel 2002 (10.2614.2625).
    We have tried uninstalling the Crystal Enterprise 8.0.We have also checked for the u2fxls.dll and Crxf_xls.dll in the C:/ <% system Root%> /Crystal.
    Kindly help us to figure out the problem. It has been working fine for quite long and flawed only recently.
    Thank You in advance.
    Thanks and regards,
    Preethi

    Post Author: Preethig
    CA Forum: Exporting
    Cyril,
         Thank You For your tip. But the problem of export To excel could be solved after I renamed the Crxf_xls.dll in the  <%System root%> /Crystal folder which allowed the dll U2fxls.dll to Excel export work just as fine as explained in the Knowledge Base of Bussiness Object.
    Thank you
    With Regards,
    Preethi

  • Export to Excel - Macro problems

    I have moved this to the Discoverer forum. Exporting to Excel - Macro Problems
    Message was edited by:
    user385142

    Hello Denes.
    Excuse me for send you a message in this way , but I dont find other way to contact with you.
    Im using the export_excel_pkg, and really it work good.
    I have only one problem, I tell you.
    When, in one item, data is very long and numeric, by example a EAN code, without any class of format, by default it give me the value ###, Im studing the package and trying to resolve this, but if you can send me any idea it can help me a lot.
    Thanks in advanced.
    You are doing a great work for us.

Maybe you are looking for