Export to excel truncates trailing zeros

When we try to export to excel trailing zeros are truncated like this:
In report on BIEE dashboar:
Product----Amount
Product A 327,876
Product B 4,000
Product C 1,278
In the exported excel spreadsheet:
Product A 327,876
Product B 4
Product C 1,278
Any ideas for a solution?

well it is because excel thinks the the comma is a decimal seperator in stead of a thousands seperator.
So check your operating system properties and your excel properties.

Similar Messages

Answers report-download as Excel loose trailing zeroes

Hi!
When I download Answers report to Excle (Word) I loose trailing zeroes.
1.2500 -> 1.25Trailing zeroes are important and I'd like that format remain as it is in OBI in all downloading types (Excel, Word etc).
When I export to PDF (run through Oracle BI publisher) trailing zeroes are correct.
Any help please.
My config, OBI on Windows 2003 32 bit:
Product Information
Oracle Business Intelligence Product Version     10.1.3.4 (Build 080726.1900)
Physical Presentation Catalog Path     \\?\C:\OracleBIData\web\catalog\teb\root
Oracle BI Server Data Source     AnalyticsWeb
Available Paging Memory (MB)     5176
Available Virtual Address Space (MB)     1833

Hi,
here are mine data as requested ...
The only three formating columns are Cash up KN, Cash up EUR i Cash up EUR/KN.
Column that has problem has no "mso" like formating at all, only two decimal number format, defined in classic way in OBI.
Generated Excel file from OBI:http://sites.google.com/site/vadasovi/icon_holders-1/BAZA.xls
How it is opened in Excel 2003:http://sites.google.com/site/vadasovi/_/rsrc/1318338523563/Home/temp/2007.PNG , look column in red.
Same file in Excel 2010 (other mashine then 2003:http://sites.google.com/site/vadasovi/_/rsrc/1318338543353/Home/temp/2010.png
Both client are Win XP SP3 with Croatian locale (same one in detail).
Rg,
Damir

Export to EXCEL truncates character field to 255?

Exporting a report to excel containing fairly long memo text, the text is truncated to apparently 255 characters. Is this a hard limitation or are there settings that will allow more?
InfoView 6.1.021.2263
WebIntelligence Reporter 6.1b
WebIntelligence Explorer 6.1b
WebIntelligence OLAP 6.1b
Excel (on desktop) 2003 SP3

Hi Susan,
This is a known issue in Infoview 6.1 and has been fixed in E6.5.1 Infoview.
Hope this helps you!
Regards,
Anindita

Grid Download to Excel truncates leading zeros

We are on tools 8.51. The download feature for a Grid now removes the leading zeros when the grid is downloaded to excel. Has anyone found a way to fix this issue ? Thanks in advance

When you download from PS query, the output is created as a true binary xls file, but when you download from a grid in PT 8.51 the output file is html, even though the filename is ps.xls. You can open this file in a text editor.
If you have all numeric data in a column, it will be stored as <td>nnnnnn</td> in the html file. if the column has mixed numeric and text data, it will be stored as <td>=&quot;nnnnnn&quot;</td>. The leading zeroes are still there in both cases, but when excel imports the first form it will convert the result to numeric, the second it will treat as text.
Other than logging a case with Oracle, the only workaround I could think of would be to save the file to disk and run the macro directly against the html. Of course, this would likely be a major redesign.
Regards,
Bob

Export to Excel dropping leading zeroes

Hi,
I have used the 'Export' feature of the form and is working well except it drops the leading zeroes on some columns.
I have defined them as string so it should retain them. How can I keep the zeroes?
Thank you.

When you say that is dropping the zeros only for a few columns, is it working fine for other columns having leading zeros? If yes, check the type of data defined for the placeholder bean and the data type of the corresponding VO column.
--Shiv

Download to EXCEL - Problem with truncating leading zeros

Hello Experts
I have Reqs-
When i download data into EXCEL some of the fields like PERNR lets say if the valus of the PERNR is 01000032 then in the excel it is displaying it as 1000032 or esle if a DATE field with value 02/03/2007 (obtained by concatenating MM / DD / YYYY) it is displaying in the excel as 2/3/2007.
I dont want the truncating of zeros to happen.
Any INPUT will be rewarded with points.
Thanks
Vj

Hi,
Try to use this FM.
There are two very important functional modules ,which are used to add zeroes(0) & Remove zeroes(0) from numeric string input respectively.
The functional module CONVERSION_EXIT_ALPHA_INPUT comes handy in this situation.
Another functional module CONVERSION_EXIT_ALPHA_OUTPUT is used to reverse the Operations performed by the above FM.
Let us look up the first case.
Function Module: CONVERSION_EXIT_ALPHA_INPUT
PARAMETER:
Importing Parameter: Input   of type C
Exporting Parameter: Output of type C.
This function module is use to add zeroes (0), to the left of the numeric string input ,after making the input numeric string right justified .
If the input string is non-numeric (including alphanumeric) , string is stored as left justified ,with blanks towards the right.
If the string is numeric say vehicle number , vlcvehicle-vhcle( 10 char)
INPUT : 123456
OUTPUT : 0000123456
Whereas if string is non-numeric
INPUT :    ABCD
OUTPUT: ABCD.
Hope this will solve your problem.
Regards
Balaji

Export to Excel, VARCHAR2 DB Type and leading zeros issue

Oracle JHeadstart Release 11.1.1.2.29
We are using the Export to excel option, but when we have leading zeros it doesn't export it as text so the data is incorrect.
Can any one please tell how doe we configure ADF to have the leading zeros and export it as text rather than as number.
<af:commandMenuItem partialSubmit="true"
textAndAccessKey="#{nls['EXPORT']}"
icon="/jheadstart/images/excel.png"
immediate="true" id="cmi0">
<af:exportCollectionActionListener exportedId="IdLookupTab"
type="excelHTML"/>
</af:commandMenuItem>
Regards
Ram

you could add an apostrophe ' in front of all fields that you want exported as a text.
this will ensure no truncating is done.
it's excel that does the shifting, so you can't really interfere from the SAP side

JHS: Export to Excel doesn't work when having leading zeros

Oracle JHeadstart Release 11.1.1.2.29
We are using the Export to excel option, but when we have leading zeros it doesn't export it as text so the data is incorrect.
Can any one please tell how doe we configure JHeadstart/ADF to have the leading zeros and export it as text rather than as number.
Regards
Ram

Ram,
Export to excel is native ADF feature,not related to JHeadstart. Please post your question on the JDeveloper forum.
Steven davelaar,
JHeadstart team.

ALV truncates last digit of field when exported to Excel.

Hello SAPients!
I have an ALV grid that truncates the last digit of one of the fields (VBELN) when it is exported to Excel. The field is defined with reference to the standard field VBRK-VBELN.
I'm working on SAP 4.6C.
Any idea?
Thank you for your help

That's funny. Make sure the the outputlen is big enough.
REgards,
RIch Heilman

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

Character drops zeros when exported to Excel

I have a template that when exported to Excel from E-Business Suite, drops the leading zeros. We want those zeros to be there.
For example, Project Number 000400 is SEGMENT1 of PA_PROJECTS_ALL so when viewed in Word, it shows the full text string. When the user exports to Excel, it drops the three leading zeros and just displays 400.
Is there a way around this?
Thanks,
Rob

Use a special character called a non-breaking-space and that should resolve your issue. Put it before or after your xml field
Insert->Symbol->Special Characters Tab->Nonbreaking Space
or
Ctrl+Shift+SpaceIf this works, don't forget to give me some points. :-)
Ike Wiggins
http://bipublisher.blogspot.com

Export to Excel - data with leading zeros

Does anyone have any tips or tricks for running a query then exporting to Excel without dropping leading zeros from the data?
Examples: numeric Item codes with leading zeros, telephone numbers that have been entered with no spaces.
Regards,
Douglas McDove

< Font Color="RED" Size = 3 Face=Verdana>
I liked the challenge and therefore.......I got this for you
</Font>
SELECT CHAR(28) + T0.CardCode [BP Code\] FROM [dbo\].[OCRD\] T0
SELECT CHAR(29) + T0.CardCode [BP Code\] FROM [dbo\].[OCRD\] T0
SELECT CHAR(30) + T0.CardCode [BP Code\] FROM [dbo\].[OCRD\] T0
SELECT CHAR(31) + T0.CardCode [BP Code\] FROM [dbo\].[OCRD\] T0
Any of the above 4 should work. T0.CardCode is the database field I tested, you can substitute this with any database field and it should work.
Regards
Suda

Using excel vi's loses trailing zeroes

I've been given to write a program that saves columns of numbers to a txt
file that is in the format of spreadsheet. All the numbers in this file are
3 places format even if there are trailing zeroes. I am using the excel
vi's that I downloaded from NI. When I save the file all the numbers lose
their trailing zeroes. So when the user opens the file using notepad the
columns tend to not line up anymore. I can format the numbers I am writing
into strings, but still all the rest of the spreadsheet loses its trailing
zeroes. I wrote a quick fix that reads all 32 columns and reformats them as
strings with 3 places, but that is kind of a kludge. Is there a better way?

"Greg McKaskle" wrote in message
news:[email protected]..
> > I've been given to write a program that saves columns of numbers to a
txt
> > file that is in the format of spreadsheet. All the numbers in this file
are
> > 3 places format even if there are trailing zeroes. I am using the excel
> > vi's that I downloaded from NI. When I save the file all the numbers
lose
> > their trailing zeroes. So when the user opens the file using notepad
the
> > columns tend to not line up anymore. I can format the numbers I am
writing
> > into strings, but still all the rest of the spreadsheet loses its
trailing
> > zeroes. I wrote a quick fix that reads all 32 columns and reformats
them as
> > strings with 3 places, but that is
kind of a kludge. Is there a better
way?
>
> I'm not positive that I understand what is going on, but if you have
access
> to the diagrams, you should look for where the numbers are formatted. To
> format a number as a string and pad with zeroes, you can change the format
> to %0f, or %08.3f for eight chars with three decimal chars and filled with
> zeroes.
In excel ObjectRepository.vi (from excel get data to modify.vi from excel
save.vi) the diagram can't be viewed without a password. I think that is
where the data is prepared for saving. I never even knew diagrams could be
protected like that.

Exporting report values with preceeding zeroes in excel

Hi,
i'm trying to export a report to excel but the report has values like '0000250000' and excel strips it down to '250000'.
How do i fix this?
Thanks
Deepak

Hi Jayvee,
Without using Mid() function you can do this.
Please follow the steps given below.
(1). Select the properties of Item Description text box.
(2). Change CanShrink to True and CanGrow to False.
(3). Adjust report width so that it will fit in A4 paper.
(4) . Save and Deploy the report.
After exporting to excel, now you can see the full item description.
Hope this will solve your issue.
Please click the 'Mark as Answer' button, if this post solves your issue.
Best Regards,
Dhanisha

Formatting an Export to Excel

Can anyone tell me how to force a column being exported to Excel to be interpreted by Excel as a text field? The column contains only digits, but has values such as '0000' where all four zeroes are to be considered significant.

Thanks for your replies. Unfortunately, enclosing values in quotes won't work. To give you a simple example, imagine the source for an interactive report is:
select '0180' account_code, 145.23 amount from dual;
When the user views the interactive report, they should see 0180 for the account code and 145.23 for the amount...and they do. So far so good.
Now, they click the tool widget and select to download the report to Excel. Here's where the wheels come off. I need the account code to be interpreted by Excel as text and amount to be interpreted as numeric. Anything I apply at the download-level, like enclosing the columns with single quotes will apply to both account_code and amount. I need a granular way to specify formatting on a field-by-field basis, only to be used when downloading the data.

Export to excel truncates trailing zeros

Similar Messages

Maybe you are looking for