Need help on avoid truncation of leading zeros while export to Excel

Hi
I am using crystal reports XI version and facing numerical format issue while exporting data from crystal report viewer to excel file, it is removing leading zeros in a alphanumeric field (String field from DB)
Thanks
Nagamani

The only thing that might do this would be to append an apostrophe (') to the beginning of the field. What I would try is:
1. Add a text object to the report where you want this string to appear.
2. Type an apostrophe in the text box.
3. Drag the field into the text box so that it's to the right of the apostrophe.
If you don't want the apostrophe to appear when viewing the report, try this:
1. Right-click on the text box and select "Format Object". Set the font color to be the same as the background color.
2. Double-click in the text box.
3. Select the field, right-click on it and select the "Format..." option. Set the font color to black or whatever other color you're using in your report.
-Dell

Similar Messages

Truncating the leading zeros which has both numbers and characters

Hello Everyone,
Can anybody pls help me to truncate the leading zeros in the incoming file structure which has both the numbers and characters.
Thanks,
Chinna

HI,
Write a UDF like this ..
public class test {
public static void main(String[] args) {
System.out.println(args[0].replaceAll("^0*",""));
Also you can use XSLT for this.
Try the XPath function number($string) in your XSLT and see if it does what you want. Since it turns any XPath object into a number, the leading zeros won't appear.
Use it ike this
<xsl:variable name="a">
<xsl:call-template name="removeLeadingZeros">
<xsl:with-param name="phone">
<xsl:value-of select="EVENT/ContactPhone"/>
</xsl:with-param>
</xsl:call-template>
</xsl:variable>
<xsl:template name="removeLeadingZeros">
<xsl:param name="phone"/>
<xsl:message>
<xsl:value-of select="$phone"/>
</xsl:message>
<xsl:choose>
<xsl:when test="starts-with($phone,'0')">
<xsl:call-template name="removeLeadingZeros">
<xsl:with-param name="phone">
<xsl:value-of
select="substring-after($phone,'0' )"/>
</xsl:with-param>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$phone"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
Regards
Aashish Sinha
PS : Reward Point if Helpful

Need to truncate extra leading zeros

Post Author: dougatrueb
CA Forum: Formula
Dear Crystal Report Gurus, I am trying to trucate the leading zeros in a feild that I am pulling from and ODBC table name {Inventory.ItemNumber}. The item number will be similiar to 0000003785768 as an example, and I need it to trancate the leading zeros so the data looks like; 3785768. Is there such a way to this easily? Thanks. Dougatrueb

Post Author: SKodidine
CA Forum: Formula
I am assuming that the itemnumber is a string. If you want it as a string but truncate the leading zeros then do this:
If NumericText({Inventory.ItemNumber}) thentotext(tonumber({Inventory.ItemNumber}),0,'','')else{Inventory.ItemNumber};

Non truncation of Leading Zero

Hi All,
I am downloading a .xls file using the function module "GUI_DOWNLOAD".
But it is truncating the leading zero's in some fileds.
For example : in the field Account group , value is "0001" but in .xls file it is coming as "1".
Can anyone please help me on how to avoid this truncation of leading zeros.
Thanks and Regards,
Nimisha Deshpande.

Just execute this porgram and check ur result .
For this u need to handle the file type as DBF .
types: begin of t_dat,
         fld1(30) type c,
         fld2(30) type c,
       end of t_dat.
data: it_dat type table of t_dat,
      wa_dat type t_dat.
wa_dat-fld1 = '12345678901234567890'.
wa_dat-fld2 = '00000000000000043210'. "->
append wa_dat to it_dat.
wa_dat-fld1 = '12345678901234567890'.
wa_dat-fld2 = '00000000000000543210'."->ur input
append wa_dat to it_dat.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>GUI_DOWNLOAD
EXPORTING
    FILENAME                  = 'C:\test.xls'
    FILETYPE                  = 'DBF'
CHANGING
    DATA_TAB                  = it_dat[]
EXCEPTIONS
    FILE_WRITE_ERROR          = 1
    NO_BATCH                  = 2
    GUI_REFUSE_FILETRANSFER   = 3
    INVALID_TYPE              = 4
    NO_AUTHORITY              = 5
    UNKNOWN_ERROR             = 6
    HEADER_NOT_ALLOWED        = 7
    SEPARATOR_NOT_ALLOWED     = 8
    FILESIZE_NOT_ALLOWED      = 9
    HEADER_TOO_LONG           = 10
    DP_ERROR_CREATE           = 11
    DP_ERROR_SEND             = 12
    DP_ERROR_WRITE            = 13
    UNKNOWN_DP_ERROR          = 14
    ACCESS_DENIED             = 15
    DP_OUT_OF_MEMORY          = 16
    DISK_FULL                 = 17
    DP_TIMEOUT                = 18
    FILE_NOT_FOUND            = 19
    DATAPROVIDER_EXCEPTION    = 20
    CONTROL_FLUSH_ERROR       = 21
    NOT_SUPPORTED_BY_GUI      = 22
    ERROR_NO_GUI              = 23
    others                    = 24.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
if sy-subrc eq 0.
write:/ 'Download completed'.
endif.
Hope this works for u .
Vijay

Truncating the leading zeros

hi,
Could anybody pls tell me how do i truncate the leading zeros in the incoming file structure.
Thanks,
Chinna

Hi,
Check this thread, i laready answered it there.
Suppressing leading zeroes during mapping
For you i pasting the solution here.
Write a UDF like this ..
public class test {
public static void main(String[] args) {
System.out.println(args[0].replaceAll("^0*",""));
Also you can use XSLT for this.
Try the XPath function number($string) in your XSLT and see if it does what you want. Since it turns any XPath object into a number, the leading zeros won't appear.
Use it ike this
<xsl:variable name="a">
<xsl:call-template name="removeLeadingZeros">
<xsl:with-param name="phone">
<xsl:value-of select="EVENT/ContactPhone"/>
</xsl:with-param>
</xsl:call-template>
</xsl:variable>
<xsl:template name="removeLeadingZeros">
<xsl:param name="phone"/>
<xsl:message>
<xsl:value-of select="$phone"/>
</xsl:message>
<xsl:choose>
<xsl:when test="starts-with($phone,'0')">
<xsl:call-template name="removeLeadingZeros">
<xsl:with-param name="phone">
<xsl:value-of
select="substring-after($phone,'0' )"/>
</xsl:with-param>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$phone"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
Regards
Aashish Sinha
PS : Reward Point if Helpful

Truncation of leading Zeros when Down Loading into Excel - OLE Objects

Hi,
Can any one help me on this.
I am using <b>OLE Objects</b> to download Data into Excel Sheet. Data with leading Zeros is getting truncated in Excel.
Ex: Report Output is showing Plant Number as 0002. But when i am downloading to Excel Plant value will become 2 .
   I would like to have it as 0002 in Excel.
I have declared Werks as CHAR of 4.I am using OLE Obects for Downloading into Excel Sheet.
I am using "OLE2_OBJECT" I can not use any other FMs to down load to Excel.As i am modifying this program not creating.
Thanks In Advance.
K.Nirmala
Message was edited by: Nirmala Reddy

Hi Nirmala,
While downloading to excel sheet, u need to change the number format of cell from General to Text, then leading zero's won't get deleted. For that u need to set the property of the cell. Please check this sample code,
INCLUDE OLE2INCL.
tables : zobrent.
data : it_kna1 type table of zobrent with header line.
handles for OLE objects
DATA: H_EXCEL TYPE OLE2_OBJECT,        " Excel object
      H_MAPL TYPE OLE2_OBJECT,         " list of workbooks
      H_MAP TYPE OLE2_OBJECT,          " workbook
      H_ZL TYPE OLE2_OBJECT,           " cell
      H_F TYPE OLE2_OBJECT.            " font
DATA H TYPE I.
DATA: cell1 TYPE ole2_object.
*&   Event START-OF-SELECTION
START-OF-SELECTION.
select * from zobrent into table it_kna1
           where zopanid = '10001'
            and zo_brent = '050'.
start Excel
CREATE OBJECT H_EXCEL 'EXCEL.APPLICATION'.
PERFORM ERR_HDL.
SET PROPERTY OF H_EXCEL 'Visible' = 1.
get list of workbooks, initially empty
CALL METHOD OF H_EXCEL 'Workbooks' = H_MAPL.
PERFORM ERR_HDL.
add a new workbook
CALL METHOD OF H_MAPL 'Add' = H_MAP.
PERFORM ERR_HDL.
output column headings to active Excel sheet
PERFORM FILL_CELL USING 1 1 1 'EDate'.
PERFORM FILL_CELL USING 1 2 1 'Brent'.
PERFORM FILL_CELL USING 1 3 1 'Zopanid'.
PERFORM FILL_CELL USING 1 4 1 'Contract Type'.
PERFORM FILL_CELL USING 1 5 1 'Price Type'.
PERFORM FILL_CELL USING 1 6 1 'Installation Type'.
PERFORM FILL_CELL USING 1 7 1 'Volume'.
PERFORM FILL_CELL USING 1 8 1 'AQ'.
PERFORM FILL_CELL USING 1 9 1 '00000123'.
LOOP AT IT_KNA1.
copy values to active EXCEL sheet
    H = SY-TABIX + 1.
    PERFORM FILL_CELL USING H 1 0 IT_KNA1-zo_effdat.
    PERFORM FILL_CELL USING H 2 0 IT_KNA1-zo_brent.
    PERFORM FILL_CELL USING H 3 0 IT_KNA1-zopanid.
ENDLOOP.
CALL METHOD OF h_excel 'Cells' = cell1
    EXPORTING
      #1 = 1
      #2 = 1.
FREE OBJECT H_EXCEL.
PERFORM ERR_HDL.
if sy-subrc eq 0.
   write : / 'year'(001).
endif.
     FORM FILL_CELL
sets cell at coordinates i,j to value val boldtype bold
FORM FILL_CELL USING I J BOLD VAL.
CALL METHOD OF H_EXCEL 'Cells' = H_ZL EXPORTING #1 = I #2 = J.
PERFORM ERR_HDL.
GET PROPERTY OF H_ZL 'Font' = H_F.
PERFORM ERR_HDL.
SET PROPERTY OF H_F 'Bold' = BOLD .
PERFORM ERR_HDL.
***Changing the format of the cell from General to Text
<b>SET PROPERTY OF H_ZL 'NumberFormat' = '@'.</b>
PERFORM ERR_HDL.
SET PROPERTY OF H_ZL 'Value' = VAL .
PERFORM ERR_HDL.
ENDFORM.
*&      Form ERR_HDL
FORM ERR_HDL.
IF SY-SUBRC <> 0.
WRITE: / 'Fehler bei OLE-Automation:'(010), SY-SUBRC.
STOP.
ENDIF.
ENDFORM.                    " ERR_HDL
U just paste this code in a sample program & see.
Please reward, if found helpful.

Truncating the leading zero's

Hi experts,
I have an ALV output, in which one of the fields is equipment number (equi-equnr).
There are some leading zero's that I need to truncate from the ALV output.
How can I achieve this? The code is as given below:
fieldcatalog-fieldname   = 'EQUIPMENT_NUMBER'.
fieldcatalog-seltext_m   = 'Equipment Number'.
fieldcatalog-col_pos     = 5.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
Thanks,
Ajay.

Hello,
Your requirement is that you need to display the equipment number in the ALV without the leading zeroes.
Ypur code is
fieldcatalog-fieldname = 'EQUIPMENT_NUMBER'.
fieldcatalog-seltext_m = 'Equipment Number'.
fieldcatalog-col_pos = 5.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
Just before append statement add the following
fieldcatalog-no_zero = 'X'.
Now try the same it should solve your problem.
Regards,
Sachin
Edited by: Sachin Dargan on Jan 19, 2010 7:34 AM

Truncation of leading zero's for a numeric field

How to truncate leading zeros for numeric key figure field. The field value shows 0.0000000000000000E+00. Why the value shows like this??? Plz explain.
Draj S

Hi,
I guess the Infoobj is FLOATING POINT. So its displaying that way.

Truncates the leading zeros even though the member is text type

We have members with data type “TEXT” in planning database. When user enters something with leading zero, it saves the same in relational but not showing the same in planning. It truncates the zero even though it is a text member.
Planning version 11.1.2
Example:
Member name : Issue code (TEXT type)
Entered value : 011_Issue (saves the same in relational)
Display value : 11_Issue (Drops the zero)
is there any workaround?
Thanks

I've opened a SR and here is the reply from MOS.
Apply a fix for Bug 12422049 - DATA TYPE TEXT MEMBER DOES NOT DISPLAY VALUE STARTING WITH ZERO CORRECTLY when its available.
The issue has been identified as a code bug and development team will fix it in future releases.
Thanks
Poorna

Need help to avoid deadlock

Hi Everyone,
I am looking for help to avoid deadlock situation in my code.
In my code, SQL loader will load a file in to temportary table.
Then i will call stored procedure, where procedure will do DML on bank_transaction and transaction_details tables.
Before processing a row in bank_transaction and transaction_details table
I want to make sure row is not locked by any other process.
if row is locked by other session then what should be my approach.
Kindly please provide your inputs.
If you have any sample code whcih is avoiding deadlock situation then please provide.
Regards,
Sandeep

Hi,
use
SELECT ... FOR UPDATE [NOWAIT]to check for locks, use NOWAIT if you want to throw an error message if the lock is detected, or omit it if you are willing to wait.
Best regards,
Nikolay

I need help with Mavericks Server: an error occurred while configuring your server. I

I need help with Mavricks Server, I get the following: an error occurred while configuring your server. I have deleted the Server.app several times along with the associated com.apple and Server folder. Any more help would be appreciated.

There are usually some log files around, related to the installation. See if Console.app (Applications > Utilities) shows anything relevant to the error, when you've done a fresh install of Server.app and tried the configuration.

Leading 0 while downloading to excel

Hi All,
I am displaying my output in ALV using REUSE_ALV_GRID_DISPLAY,but when i download the report to excel using standard download button in the tool bar(local file icon), the leading zeros are getting truncated
eg 0004 is displayed as 4
field is VBKD-ZTERM....
Whats the way out?
<REMOVED BY MODERATOR>
Regards
Gunjan
Edited by: Alvaro Tejada Galindo on Mar 4, 2008 2:52 PM

1.Introduce another field in internal table of type Numeric.
2.Before you pass the internal table to Reuse_alv_grid Display
3.Move the character field to Numeric type and use this
numeric field to display in Reuse_alv_grid_display.
Then the leading zeros will also be displayed while downloading to Excel.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Mar 4, 2008 2:53 PM

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

Need help to avoid ORA-04030 error

Oracle version : 11.1.0.6.0
OS - Solaris 64bit Sparc
Hi All,
Today we have recieved the below error messeges in the alert log.
ORA-04030: out of process memory when trying to allocate 56 bytes (callheap,kghscAllocDataElem:dataElem)
ORA-04030: out of process memory when trying to allocate 184 bytes (callheap,temporary memory)
ORA-04030: out of process memory when trying to allocate 56 bytes (callheap,temporary memory)
Trace dumping is performing id=[cdmp_20110222134605]
Tue Feb 22 13:46:52 2011
Sweep Incident[104533]: completed
Sweep Incident[104532]: completed
Sweep Incident[104531]: completed
Sweep Incident[104530]: completed
Sweep Incident[104528]: completed
Tue Feb 22 17:04:25 2011
SYS@MYDB>!oerr ora 4030
04030, 00000, "out of process memory when trying to allocate %s bytes (%s,%s)"
//*Cause: Operating system process private memory was exhausted.
//*Action:I came to know that it was due to the operating system prvate memory exhausted. Database memory configuration is as below
SYS@MYDB>show parameter sga
NAME                                 TYPE        VALUE
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     FALSE
sga_max_size                         big integer 2000M
sga_target                           big integer 0
SYS@MYDB>show parameter pga
NAME                                 TYPE        VALUE
pga_aggregate_target                 big integer 521658240
SYS@MYDB>OS Memory information
load averages: 1.58, 1.82, 2.13;                    up 196+10:43:15                                                         20:55:35
408 processes: 406 sleeping, 2 on cpu
CPU states: 80.0% idle, 15.6% user, 4.4% kernel, 0.0% iowait, 0.0% swap
Memory: 32G phys mem, 18G free mem, 43G total swap, 42G free swapThere are other 2 more databases are running on this server, one is 10g and another one is 9i and its memory configuration have given below respectivly
SQL>show parameter sga
NAME                                 TYPE        VALUE
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     FALSE
sga_max_size                         big integer 4G
sga_target                           big integer 4G
RPT>show parameter pga
NAME                                 TYPE        VALUE
pga_aggregate_target                 big integer 4G
SQL> show parameter sga
NAME                                 TYPE        VALUE
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     FALSE
sga_max_size                         big integer 1135171060
SQL> show parameter pga
NAME                                 TYPE        VALUE
pga_aggregate_target                 big integer 2147483648
SQL>Could you please suggest me how to avoid this error in future ? Looks like i need to fine tune the memory parameters, could you please suggest how can i do so ? I also noticed SGA Target is set to 0 (Automatic Memory managment is not enabled), If i set SGA target will resolve the issue ?
Kindly advise ..
Thanks in advance
Nishant

I just took the plan by setting set autotrace traceonly explain. Please check this will help, I will check and update you the table's statistics soon.
Execution Plan
Plan hash value: 1841079096
| Id | Operation                               | Name               | Rows | Bytes |TempSpc| Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                        |                    |   210M|    96G|       |    29M (1)| 99:12:47 |
|   1 | SORT ORDER BY                          |                    |   210M|    96G|       |    29M (1)| 99:12:47 |
|   2 |   HASH UNIQUE                           |                    |   210M|    96G| 1000K| 41115   (2)| 00:08:14 |
|   3 |    CONCATENATION                        |                    |       |       |       |            |          |
|   4 |     NESTED LOOPS                        |                    |       |       |       |            |          |
|   5 |      NESTED LOOPS                       |                    |   980 |   470K|       | 34365   (2)| 00:06:53 |
|   6 |       NESTED LOOPS                      |                    |   980 |   455K|       | 33384   (2)| 00:06:41 |
|   7 |        NESTED LOOPS                     |                    |   980 |   445K|       | 32893   (2)| 00:06:35 |
|* 8 |         HASH JOIN                       |                    |   980 |   434K| 7968K| 31912   (2)| 00:06:23 |
|   9 |          NESTED LOOPS                   |                    | 19606 | 7735K|       | 28804   (2)| 00:05:46 |
|* 10 |           HASH JOIN                     |                    |     1 |   306 |    11M| 27300   (2)| 00:05:28 |
| 11 |            TABLE ACCESS FULL            | VERSION_FILE_MAP   |   517K| 6064K|       | 2275   (3)| 00:00:28 |
|* 12 |            HASH JOIN                    |                    |   296K|    83M|    11M| 20121   (2)| 00:04:02 |
|* 13 |             HASH JOIN                   |                    |   296K| 8401K| 7168K| 4103   (4)| 00:00:50 |
| 14 |              INDEX FAST FULL SCAN       | ATTACHMENT_PK      |   407K| 2389K|       |   280   (3)| 00:00:04 |
|* 15 |              HASH JOIN                  |                    |   296K| 6663K| 8408K| 2966   (4)| 00:00:36 |
| 16 |               TABLE ACCESS FULL         | ATTACHMENT_MAP     |   296K| 4925K|       | 1810   (5)| 00:00:22 |
| 17 |               INDEX FAST FULL SCAN      | VERSION_PK         |   482K| 2829K|       |   317   (3)| 00:00:04 |
| 18 |             TABLE ACCESS FULL           | FILES              |   509K|   128M|       | 8744   (1)| 00:01:45 |
|* 19 |           TABLE ACCESS FULL             | ATTACHMENT         | 31967 | 3059K|       | 1504   (2)| 00:00:19 |
| 20 |          TABLE ACCESS FULL              | VERSION            |   482K|    23M|       | 1290   (2)| 00:00:16 |
|* 21 |         TABLE ACCESS BY INDEX ROWID     | VERSION            |     1 |    12 |       |     1   (0)| 00:00:01 |
|* 22 |          INDEX UNIQUE SCAN              | VERSION_PK         |     1 |       |       |     1   (0)| 00:00:01 |
|* 23 |        INDEX UNIQUE SCAN                | PAGE_THREE_PK      |     1 |    10 |       |     1   (0)| 00:00:01 |
|* 24 |       INDEX UNIQUE SCAN                 | PAGE_TWO_PK        |     1 |       |       |     1   (0)| 00:00:01 |
| 25 |      TABLE ACCESS BY INDEX ROWID        | PAGE_TWO           |     1 |    16 |       |     1   (0)| 00:00:01 |
| 26 |     NESTED LOOPS                        |                    |       |       |       |            |          |
| 27 |      NESTED LOOPS                       |                    |     1 |   492 |       | 6644   (2)| 00:01:20 |
| 28 |       NESTED LOOPS                      |                    |     1 |   227 |       | 6643   (2)| 00:01:20 |
| 29 |        NESTED LOOPS                     |                    |     1 |   215 |       | 6641   (2)| 00:01:20 |
| 30 |         NESTED LOOPS                    |                    |     1 |   209 |       | 6640   (2)| 00:01:20 |
| 31 |          MERGE JOIN CARTESIAN           |                    |     1 |   192 |       | 6639   (2)| 00:01:20 |
| 32 |           NESTED LOOPS                  |                    |       |       |       |            |          |
| 33 |            NESTED LOOPS                 |                    |     1 |   186 |       | 6359   (2)| 00:01:17 |
| 34 |             NESTED LOOPS                |                    |     1 |   170 |       | 6358   (2)| 00:01:17 |
| 35 |              NESTED LOOPS               |                    |     1 |   158 |       | 6357   (2)| 00:01:17 |
|* 36 |               HASH JOIN                 |                    |     1 |   148 |    28M| 6356   (2)| 00:01:17 |
| 37 |                TABLE ACCESS FULL        | VERSION            |   482K|    23M|       | 1290   (2)| 00:00:16 |
|* 38 |                TABLE ACCESS FULL        | ATTACHMENT         |   407K|    38M|       | 1504   (2)| 00:00:19 |
|* 39 |               INDEX UNIQUE SCAN         | PAGE_THREE_PK      |     1 |    10 |       |     1   (0)| 00:00:01 |
|* 40 |              TABLE ACCESS BY INDEX ROWID| VERSION            |     1 |    12 |       |     1   (0)| 00:00:01 |
|* 41 |               INDEX UNIQUE SCAN         | VERSION_PK         |     1 |       |       |     1   (0)| 00:00:01 |
|* 42 |             INDEX UNIQUE SCAN           | PAGE_TWO_PK        |     1 |       |       |     1   (0)| 00:00:01 |
| 43 |            TABLE ACCESS BY INDEX ROWID | PAGE_TWO           |     1 |    16 |       |     1   (0)| 00:00:01 |
| 44 |           BUFFER SORT                   |                    |   407K| 2389K|       | 6638   (2)| 00:01:20 |
| 45 |            INDEX FAST FULL SCAN         | ATTACHMENT_PK      |   407K| 2389K|       |   280   (3)| 00:00:04 |
|* 46 |          TABLE ACCESS BY INDEX ROWID    | ATTACHMENT_MAP     |     1 |    17 |       |     2   (0)| 00:00:01 |
|* 47 |           INDEX RANGE SCAN              | ATTACHMENTMAP_IDX3 |     1 |       |       |     1   (0)| 00:00:01 |
|* 48 |         INDEX UNIQUE SCAN               | VERSION_PK         |     1 |     6 |       |     1   (0)| 00:00:01 |
| 49 |        TABLE ACCESS BY INDEX ROWID      | VERSION_FILE_MAP   |     1 |    12 |       |     2   (0)| 00:00:01 |
|* 50 |         INDEX RANGE SCAN                | VERSION_FMAP_IDX2 |     1 |       |       |     1   (0)| 00:00:01 |
|* 51 |       INDEX UNIQUE SCAN                 | FILES_PK           |     1 |       |       |     1   (0)| 00:00:01 |
|* 52 |      TABLE ACCESS BY INDEX ROWID        | FILES              |     1 |   265 |       |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   8 - access("A"."ID"="VERSION"."ATTACH_ID" AND "A"."LATEST_VSN"="VERSION"."ID")
       filter("A"."LATEST_VSN">="VERSION"."ID")
10 - access("C"."ID"="D"."VERSION_ID" AND "D"."FILE_ID"="E"."ID")
12 - access("E"."ID"="A"."FILE_ID")
13 - access("A"."ATTACH_ID"="B"."ID")
15 - access("A"."LATEST_VSN"="C"."ID")
19 - filter(NVL("A"."DELETE_FLAG",0)=0 AND ("CTXSYS"."CONTAINS"("A"."DESCRIPTION",'EHS%')>0 OR
              "CTXSYS"."CONTAINS"("E"."CONTENT_URL",'EHS%')>0 AND "E"."CONTENT_URL" IS NOT NULL))
21 - filter("A"."ID"="D"."ATTACH_ID")
22 - access("A"."LATEST_VSN"="D"."ID")
23 - access("A"."ID"="C"."ID" AND "A"."CLASS"="C"."CLASS")
24 - access("A"."ID"="B"."ID" AND "A"."CLASS"="B"."CLASS")
36 - access("A"."ID"="VERSION"."ATTACH_ID" AND "A"."LATEST_VSN"="VERSION"."ID")
       filter("A"."LATEST_VSN">="VERSION"."ID")
38 - filter(NVL("A"."DELETE_FLAG",0)=0)
39 - access("A"."ID"="C"."ID" AND "A"."CLASS"="C"."CLASS")
40 - filter("A"."ID"="D"."ATTACH_ID")
41 - access("A"."LATEST_VSN"="D"."ID")
42 - access("A"."ID"="B"."ID" AND "A"."CLASS"="B"."CLASS")
46 - filter("A"."FILE_ID"=0)
47 - access("A"."ATTACH_ID"="B"."ID")
48 - access("A"."LATEST_VSN"="C"."ID")
50 - access("C"."ID"="D"."VERSION_ID")
51 - access("D"."FILE_ID"="E"."ID")
       filter(LNNVL("E"."ID"="A"."FILE_ID"))
52 - filter("CTXSYS"."CONTAINS"("A"."DESCRIPTION",'EHS%')>0 OR
              "CTXSYS"."CONTAINS"("E"."CONTENT_URL",'EHS%')>0 AND "E"."CONTENT_URL" IS NOT NULL)

Need Help Fixing Bad Color Profile (Leading to Bluish Tint)

Hi folks,
I've been experiencing problems with my late-2011 Macbook Pro for the past several months. Whenever it switches to dedicated graphics, the screen results in a bluish tint.
I believe it's a problem with the color profile on my machine. The diagnostic identifies two problems with the color profile, but the system is unable to fix the problem (see attached photo).
Does anybody know how I can fix this?
EDIT: I should note I'm running the latest version of OSX 10.8.4. I never experienced this problem with 10.7.x.

Header message digest (md5) is missing in Colorsync profiles

Need help on avoid truncation of leading zeros while export to Excel

Similar Messages

Maybe you are looking for