Column mismatch when exporting as spreadsheet in version 4.7

Hi All,
In  transaction WE02 when downloading data using local file option as spreadsheet, entire data is coming in single column in SAP 4.7 version. At the same time in ECC 6.0 same data in coming in different columns (correct format).
please help me to find what can be the reason for the same, when procedure in both the cases is same.
Also this is true with every other transaction whether SAP standard or Z transaction.
The process i am following is Local File --> spreadsheet & downloading to my hard drive.
Normally if there are 5 columns then in excel also 5 columns should come but only 1 column is coming on the other hand in ECC 6.0 all 5 columns are coming.
Thanks & Regards,
Amit sharma.

HI
try this sample code
REPORT  Z_SELSCR_BLOCK.
PARAMETERS show_all radiobutton  group g1 USER-COMMAND flag.
PARAMETERS no_show radiobutton  group g1 default 'X'.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
PARAMETERS: p1(10) TYPE c,
            p2(10) TYPE c,
            p3(10) TYPE c.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME.
selection-screen begin of line.
SELECTION-SCREEN COMMENT 1(30) text-006 FOR FIELD insme modif id bl2.
PARAMETERS: insme AS CHECKBOX MODIF ID bl2.
            selection-screen end of line.
SELECTION-SCREEN END OF BLOCK b2.
AT SELECTION-SCREEN OUTPUT.
  LOOP AT SCREEN.
    IF show_all <> 'X' AND
       screen-group1 = 'BL2'.
       screen-active = '0'.
    ENDIF.
    MODIFY SCREEN.
  ENDLOOP.
regards
kishore

Similar Messages

  • Column headings are mismatched when export to excel (Data Only)

    Hi All,
    We have an old Crystal Web Portal designed using CE10 in VS 2003.   The crystal viewer shipped with VS 2003 exports to excel (Data only) in correct order where all the columns headers are matched with the corresponding data.
    We have re-written the entire new web portal in VS 2008 with using CE10 on windows 2003 server.  Everything works we can view the report, page navigation, export to PDF, export to MS Excel 97-2000.   However when export to MS Excel 97-2000 (Data only) option, the column headings are mismatched with the corresponding data.   I don't understand what changed between VS 2003 Crystal Viewer and VS 2008 Crystal Viewer.   I think this has to be the crystal viewer problem because I'm exporting from the viewer tool bar.
    Here is the API referencing in the code:
    In Visual Studio I'm referencing all CE10 10.0.3300 version api's.  Howerver since Crystal Viewer with VS 2008 is newer and has 10.5.3700 version I'm using CrystalDecision.Shared and CrystalDecision.Web are version 10.5.3700.   These seems to have no problem.  The entire web portal works fine. 
    More about Web Portal:
    -User is validated upon login with CE10
    -use selects the report from the list
    -Report ID is then passed to reportdocument
    -reportdocument API loads the report and
    -Viwer.reportsource= reportdocument.reportsource
    We cannot update Crystal Enterprise 10 right now.   I'm in the middle of deploying new web portal with VS 2008.   I have to resolve the Export excel (Data only) option and have the column headers matched with the data in excel.   I have tried everthing.
    Can some help here.
    thanks

    Hi, 
    The report saves the printer information and if it can connect to the exact same printer then the print options will get passed to the printer. 
    If the report is being sent to a different printer, Crystal doesn't know if this new printer will support the same settings, ie. duplex or color.  In our case we were setting the report to print duplex printing and landscape.  When our application went to print it actually crashed because some of the printers didn't support duplex. 
    What we did is disable the print button on the viewer and added the PrintDialog control to our form.  Use the ReportDocument.PrintOptions method to set the properties for the PrintDialog control. 
    var printDialog1 = new PrintDialog();
    printDialog1.UseEXDialog = true;
    printDialog1.AllowSomePages = true;
    if (myLink.Parent.SavedPrinterSettings != null)
         printDialog1.PrinterSettings = myLink.Parent.SavedPrinterSettings; //Use any saved printer settigns
         printDialog1.PrinterSettings.Copies = Convert.ToInt16(copies);
         dr = printDialog1.ShowDialog();
         if (dr == DialogResult.OK)
         myLink.Parent.SavedPrinterSettings = printDialog1.PrinterSettings;     //Save the latest printer settings
         nCopy = printDialog1.PrinterSettings.Copies;               //Get the number of Copies
         sPage = printDialog1.PrinterSettings.FromPage;               //Get the number of Start Page
         ePage = printDialog1.PrinterSettings.ToPage;                    //Get the number of End Page
         myReport.PrintOptions.PrinterName = printDialog1.PrinterSettings.PrinterName;     //Get the printer name
         myReport.PrintOptions.CustomPaperSource = printDialog1.PrinterSettings.DefaultPageSettings.PaperSource;
         if (printDialog1.PrinterSettings.Duplex == System.Drawing.Printing.Duplex.Vertical)
              myReport.PrintOptions.PrinterDuplex = PrinterDuplex.Vertical;
         else if (printDialog1.PrinterSettings.Duplex == System.Drawing.Printing.Duplex.Horizontal)
              myReport.PrintOptions.PrinterDuplex = PrinterDuplex.Horizontal;
         else if (printDialog1.PrinterSettings.Duplex == System.Drawing.Printing.Duplex.Simplex)
              myReport.PrintOptions.PrinterDuplex = PrinterDuplex.Simplex;
    Hope this helps,
    Brian

  • Setting the default format when exporting to spreadsheet

    Can I set the default format to be used when my end users export a report to a spreadsheet? I would like to set the default to Excel (in Office 2003 XML format).
    Currently the end user has 7 choices for creating spreadsheets if the selecte the "All Available Formats" option when generating a spreadsheet. Those options are:
    - Excel (in MHTML format)
    - Excel (in MHTML format for 2000/97)
    - Star Office 8
    - Excel (in Office 2003 XML format)
    - SAP internal XML format
    - SAP Standard (internal table)
    - Excel (in previous XXL format)
    I ran the report SALV_BS_ADMIN_MAINTAIN and selected the following criteria:
    1.) Action = create
    2.) General Data = ALL
    3.) ALV GUI / EXCEL VERSION = Excel (in Office 2003 XML format)
    If I examine the table SALV_BS_ADMIN there is a new entry where:
    OBJECT = GUI_ALV_XML_VER
    M_USER = *
    VALUE = 04
    When I run a report and export to a spreadsheet I do not see any change in my selection criteria.
    I read SAP note 1080608. This note tells you that by running the report SALV_BS_ADMIN_MAINTAIN you cannot set the default value. Is there a report I can run that will set the default value for alll the users on the system?

    Hi
    You execute the report SALV_BS_ADMIN_MAINTAIN and selected the following criteria:
    1.) Action = change
    2.) General Data = Detailed Selection
         a) Client = SAP client no.
         b) User All = User ID
    3.) ALV GUI / EXCEL VERSION = Excel (in Office 2003 XML format)
    Execute the report and Excel 2003 will be defaulted in export to excel.

  • How to set color profile when exporting a RAW file version as a JPEG?

    I import my raw files to Aperture and when exporting as a JPEG I want to specify a color profile of sRBG. I cannot see how to set the color profile for the export. Does anyone know how to do this?

    When you go to export versions, edit the presets, and there is a drop down box that lets you select the profile.
    I'd suggest picking up the Aperture book by Luna, Long, and Harrington. Lots of great info there.

  • Strange bug when exporting a spreadsheet to a pdf

    I am using Numbers 3.5 on a brand new Mac with Yosemite and I think that I have found a bug.  When I export a spreadsheet into either a pdf or excel file it works fine if I save it to my default location (Documents).  But if I change to a subfolder within Documents before I do the export I get an error message that says "The file name.pdf doesn't exist!"  (Where name is the filename that I have specified for the export.)  It's as if Numbers is trying to open an existing file instead of exporting to make a new one.  Any ideas on this?
    Thank you,
    Paul H.

    I will reply to my own question.  I spent some time with an Apple tech support person and at first I stumped him.  Eventually he got it to work and he thinks that the key was to get my computer to reindex my file structure.  He did that by creating another folder inside Downloads, exported to it OK, and then was able to export to my previously existing subfolders.  Thank you Apple!

  • Hide/Show columns only when exporting to .CSV

    Hi, how can i hide a particular column when exporting the report to excel

    Hi,
    You can set column conditionally by request.
    E.g. columns that you do not like export set condition PL/SQL function body returning a boolean
    RETURN NVL(:REQUEST,'EMPTY') NOT IN('CSV','XLS','PDF','XML','RTF');I have sample here
    http://apex.oracle.com/pls/otn/f?p=40323:63
    EMPNO column is not exported from report
    Br,Jari

  • Why the color mismatch when exported key to mov?

    Keynote colors are rich and bright, but get all dull when exported to a mov.
    Anyone know why this happens, or better yet have a solution?

    Hi,
    Thanks for your reply.  No, I haven't converted any color images from RGB to CYMK.  The original graphic file was made as RGB.  The colored box in PM7 is set to the Color Options of:
    Type: Spot
    Model: RGB
    (R 255, G 0, B 0)
    As said, in PM7 the two red objects look identical in colour tinting etc on the screen, and you can't tell the difference.  But when the doc is converted to PDF the difference is obvious.
    After posting to this forum last night (Australian time), I wondered if it had something to do with dot resolution.  The graphic file is 300 dpi, whereas the red PM box is filled with color that may be at a much lower DPI, causing a dullness in the color.  I assume the PM 7 default for this can't be altered. Maybe there is a setting in Distiller that could handle this, so that the colors are equalised.
    The solution I'm currently using is to remove the box (or oblong) containing PM's RGB Red, then make another graphic file which is RGB Red (either at 300 dpi or 200 dpi, either TIFF or JPG, it doesn't matter), of the same page size as the PM doc, then place it onto the page and send it to the back so that everything else sits on top of it.  When converted to PDF you now can't tell the difference between the RGB Red in both graphics.
    I'm happy with the result, but it's a workaround.
    Thanks,
    Roger3

  • REUSE_ALV_GRID_DISPLAY, columns reorder when exporting to Excel

    I have a variable column output and am using "cl_alv_table_create=>create_dynamic_table" to create the field-symbol output table with correct number of columns in the exact order of the field catalog.  The field formatting also matches from the dynamic table to the field catalog.
    I call REUSE_ALV_GRID_DISPLAY with the parameter t_outtab  = <dyn_table>.
    When I execute my program, the ALV grid displays correctly in SAP.
    When I export to Excel using &XXL icon from the toolbar, the resulting Excel table has reordered some columns.
    The first columns are highlighted in yellow as though they are key fields and other columns with no background color have been bumped to the end of the row.
    I do not have any key fields defined in the field-catalog. 
    Any suggestions?

    I have a structure in the data dictionary.
    I call REUSE_ALV_FIELDCATALOG_MERGE with that structure.
    There are 150 fields in the structure.
    I loop through the fields the user has picked to include in the report and delete those from the field catalog that are not used.
    I only keep the fields in the field catalog that are being used in the report.
    I then use the reduced field catalog to create the dynamic table so the field catalog matches the output table - field for field.
    The datatypes also match between the dynamic table and the field catalog.  (char, dats, numc)

  • Error ODI-26016 when exporting and creating a version of a package

    I'm getting the following error when trying to export or create a new version of a package:
    "ODI-26016: The requested operation cannot succeed. The object no longer exists."
    The package has many steps in it, so I suppose some of them are invalid, but the Warning button shows no errors. Is there a way to find out what's wrong? Via the repository or some other procedure?
    I'm using ODI 11g.

    I don't have a metalink account, so could you post an external link or the contents of the Note [ID 1514781.1]

  • How to increase the column width when viewing a spreadsheet created by a concurrent request

    I have created a BI Publisher template to display the output from scheduled discoverer reports. It contains sixty three columns and the heading for each one is a variable but, in order to fit these on the page, each column is about a half a centimeter wide.
    When I use the Preview Template option from the RTF file and select Excel the columns are automatically sized to accommodate the data (which is what is required). However, when I upload the template and run a concurrent request and view the output, each column is shown as half a centimetre in width so the user can see very little of the data without resizing all columns. We do not think that this will be acceptable to our users.
    We are using Excel 2010 in both cases.
    I have looked at this forum and tried a few things without success so any help will be gratefully received.

    for ebs 12.1.3 you can create excel template by bip desktop 11
    i used bip desktop 11.1.1.5 with ms office 2010 for create excel template for ebs 12.1.2 and 12.1.3
    using excel template based on what do you want to do - if report contains complex visualization or many merging of cell and etc
    for starting
    https://blogs.oracle.com/xmlpublisher/entry/real_excel_templates_i
    Creating Excel Templates - 11g Release 1 (11.1.1)

  • JAVA error when exporting to reporting schema ODDM 4.1

    When attempting to export a design to a reporting schema, we received the following error:
    ERROR ReportsHandler - error exporting to reporting schema:
    java.lang.classcastException: oracle.dbtools.crest.model.design.relational.column cannot be cast to oracle.dbtools.crest.model..design..relational.columnView
    at oracle.dbtools.crest.exports.reports.RSViewColumn.export (RSViewColumns.java:43
    at oracle.dbtools.crest.exports.reports.RSRelationalModel.export (RSRelationalModel.java:62)
    at oracle.dbtools.crest.exports.reports.ReportsHandler.export (ReportsHandler.java:135)
    at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run (ControllerApplication.java:2079)
    We downloaded and installed ODDM 4.1 (EA-1) build 4.1.0.866 to resolve an issue with column widths when exporting to the reporting schema (per SR 3-10154440761).  This is the 64 bit version with the included JAVA 1.8 JRE.

    David,
    We migrated this model from data modeler 3.3.  That Model was created from an import from Oracle Designer.  We have not yet tried to import the data model from Oracle Designer directly into v4.1 but are planning to do so shortly.   When we tried to export that design (from v3.3) to the reporting schema, it failed with object too large for column errors.  We wrote SR 3-10154440761 and were advised by Michael Wickham to use v4.1 EA as the column size issue had been resolved in this version.  It was apparent that the export to the reporting schema was making more progress before it failed on the JAVA error.
    We are trying to migrate from Oracle designer to Oracle Data Modeler

  • Format Changes when Exporting to PDF

    I'm using Crystal 12.0 and have an issue very similar to these threads listed below. 
    While viewing a report on my development machine, all is fine.  I can export to PDF and the formatting is OK. 
    However, when the report is exported to PDF on the web server, the spacing between some of the text is off.  The spacing is used for a CrossTab cell in a "Display String" that I changed using "Format Field."   All that's supposed to happen here is several spaces are used to move the text under the proper column. 
    When exporting to PDF on the web, the text moves over to the left like it's missing some of the spaces.  I wondering if the below threads apply to Crystal 12.0. 
    Thread:1220516 and
    Format Changes when Exporting to PDF
    Thanks kindly for your assistance,
    -Marty

    I'm having a very similar problem using Crystal Reports for Visual Studio 2008. Everything is perfect when running in VS 2008, it takes the report and exports it to PDF format via VB code. The PDF file is idenitcal to the report. However, when run on the server the one page report (when exported to PDF) gets chopped into ten 4x4 chunks. So the PDF file is 10 pages....its like puzzle pieces of the original.
    I've drawn a bunch of lines on the report to look like boxes - perhaps this is causing issues? The font on the report is Arial.
    The server has the 10_5 runtime installed and it is set to the same default printer as the development PC. I have been stuck on this for days and would really appreciate any advice you may have.
    Thanks!
    Edited by: WanderingEye on Sep 18, 2009 4:54 PM

  • When exporting files to web pages Aperture keeping losing files, so for instance, if I choose to export 600 images to a new web page, it might do 524 images but not the full 600. I've tried resetting Aperture, it's the latest version etc etc. Help please!

    If anyone can help me with this I would be seriously grateful.
    When exporting mutliple files to web pages Aperture keeping losing files, so for instance, if I choose to export 600 images to a new web page, it might make 524 pages but not the full 600. I've tried resetting Aperture and its persmission and am using the latest version of 3.
    I have 3600 images which I need to upload as sublfolders, each with their own URL and at the moment Aperture is dropping of anything from 1 to 90 images.
    This is critical as people need to see each and every on of these images online. So if a file has 600 photos in it, Aperture should make a URL with 600 full image pages. And this is what it's not doing. On small files, say 30 or so it seems to work well, it's when it gets to more than that the problem starts.
    I've used Aperture in the past under previous versions and not had this problem.
    Any help would be great.
    Thanks.
    Bob.

    Hi Jack,
    Thanks for responding (as it seems as though no one else has been able to provide any insight as of yet)! Not sure if you saw my recent post, but the version of Aperture on the 2008 MacBook has been upgraded to 3.1.2 (not sure how; I bought it in 2009, but only have OS X 10.5.8... which apparently can't house 3.1.2 of Aperture, but hey, like many other anomalies i'm encountering, I'm no longer surprised!). I am unable to upgrade it any further, as it warns me that my OS X does not fit the requirements. I exported the projects as libraries; however, like I posted before, apparently these are from too old of a version for the new Aperture (3.3.1) to handle and import.
    It's getting to the point where I'd almost pay to upgrade the OS X on my previous MacBook (10.5.8) to something newer in order to THEN update Aperture to a newer version; however, my previous MacBook simply cannot handle this (the specs are awful -- hence my decision to save up and upgrade to the newest MBP with Retina).
    I've spent hours upon hours transferring files, libraries as projects, previews, versions, even masters (though, apparently some of them aren't accessible?) with no luck. I've rebuilt the library and reprocessed everything. And this is all after having to return one MBP already since Aperture 3.3.1 is glitch-y as it is, and froze everything for having a "managed library". So, now that I know that I have to deal with a referenced library in Aperture... I just need to actually transfer my previous library to my new one (hopefully WITH adjustments since these are years worth of photos and work).
    Again, any help is appreciated. I've lost enough sleep, time, and vision health over this at this point.
    Also, I know Migration Assistant is an option, I was told that it wouldn't work properly anyway because of the different operating systems, and the potential for problems.

  • How to hide the file name (the bizarre number assigned by the camera) when exporting an image version in aperture from an album. Pl understand I want to keep the file name in the project library version.

    how to hide the file name (the bizarre number assigned by the camera) when exporting an image version in aperture from an album. Pl understand I want to keep the file name in the project library version.

    Within Aperture you have Images, which are constructed on-the-fly from two files (the Master and the Version).  You get an image-format file _only_ when you export an Image.  You select the file name (usually a scheme) when you create an image-format file (that is, when you export).  Look under "Aperture→Presets→File Naming" for built-in Presets.  You can, of course, create your own or customize any provided.
    The Preset is applied to only the file newly created by your "export" command.  It is not applied to the Image in Aperture (unless you rename your Versions or your Masters).

  • In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins?

    In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins. I have try reinstalling aperture three times, deleting plists a few times, reinstalling plugins, restarting my MacBook Pro many times. Everything I've tried may fix the problem for a very short while and I can export a few photos before it returns. The problem happens with topaz and photomatrix pro plugins after I edited and try to export version.

    I had the same problem with the Photomatix plug-in and this solved it for me. I realised it only happened with Photomatix and not other plug-ins so I checked where the plug-ins were installed. The Photomatix plug-in was installed in
    ~/Library/Application Support/Aperture/Plug-Ins/
    where ~ is the home location for the current user account. All the other plug-ins however were installed in
    Macintosh HD/Library/Application Support/Aperture/Plug-Ins/
    which is the location that makes them available to all user accounts on your Mac. Moving the Photomatix plug-in to this location solved the problem for me.
    Note that the Library directory under the first location is normally hidden, to get to it hold down the Option (Alt) key and select it from the Finder Go menu.

Maybe you are looking for

  • Error while creating a  Document  in CV01N

    Hi Gurus, I am trying to  create  a document through CV01N and  i wnat to attach it to material . We have created some Z- Document types and  the  origin for  the  file(source) is picked up from another system. Suddenly iam creating an error  File ex

  • I've forgot my answers for security questions. Can't you reset them or do something like this?

    I have bought a new iphone 5s a week ago. Today I wanted to purchase an app. And the security system asked me for an answer for my security questions.  But I don't remember them. What should I do?

  • What files do I need to download for NI6025E

    We have a program that uses nidaqex.h and nidaq32.lib. The program is written in Borland C++ Builder 2006. Now we need to get the program to work in a newer PC. The old Borland C++ Builder 2006 refuses to install on the newer PC so we planed to use E

  • Do you need a c.d ?

    I have got all the Linksys boxes, but it has been deleted of my laptop for some reason. Do i need the C.D to install it again?

  • Requirements on an EJB to be eligible for a fail-over

    Hi all,           I was reading the EJB developer guide for weblogic server 9.2. When talking about the fail-over feature the guide said           "EJB failover requiers that bean methods must be idempotent and configured as such in weblogic-ejb-jar.