Terminating Decimal places in Appraisal Scales

Hi All,
When I am using numerical scale in appraisals, it gives the values with three decimal places.. Ex: 5 is displayed as 5,000.
Can anybody tell me how to terminate the decimal places in scales..
Thank you in advance
Regards
Syed

Syed,
How did you resolved this ?
Aneez

Similar Messages

Print Scale Percentage - Can the percentage go more than 2 decimal places??

Hello All,
Illustrator CS6
I want to know if it is possible to get more than 2 decimal places in the Print Scale Percentage option box (as shown below)?
It seems to round to 2 and I would like to get at least 3 for better accuracy.
Any thoughts?
Thanks
Geoff

Not that I know of. If you need it to be more exact, resize the artboard and scale the content. It's an arguable point, anyway, given how your printer will translate/ rasterize the stuff. Even if there were more digits, the result after the halfftoning might not at all be any different...
Mylenium

OSA - Weightage Column Percentage decimal place

Hello
I have set up FWGT column for weightage in the Appraisal Template as percentage and it is giving 1.000 as default value, can the decimal place be changed to 1.0?
Could you please help me with the following issue?
Regards
Vibha

Hi,
as mentioned, it was a guess ;o)
I fiddled around a bit but if you create a new quantity scale with interval 0,1 (instead of 0,001 which is assigned to the standaard 100 point scale), you'll see only one decimal.
Or at least it does so in the SAP backend.
Wilfred.

U261B An Issue due to 3 Decimal Places in Percentage - Help Required

I've an Issue in BEX report output, which is like when I try to create a 'Percentage' computation on a Key Figure Value, I'm getting 3 decimal places as 'default' output.
The 'Calculations' settings I made for this KF is
> Calculate Result as ... Nothing Defined
> Calculate Single Values as .... Normalize According to Next Group Level Result
> [✔] Apply to results
> Calculation Direction - Along Rows
☹ I ran SAP_RSADMIN_MAINTAIN and set object 'IGNORE_T006_ANDEC' to the value 'X' - Not woking! Should I choose Update/Insert/Delete??
☹ T006-ANDEC & T006-DECAN for '%' has 0 decimal places only. Am I checking the correct stuff?
☹ OSS note 866505 not helpful for my issue. BW 7.0 Stack
I'm getting my output as expected, but the only worrying factor is 3 decimal places due to the 'Calculations'. I'm unable to resolve using existing methods. Should I raise an OSS Note for this?
Please help...

Hi, I posted a message to SAP on this topic and got an explanation - it is a behaviour that cannot be changed in certain cases:
it is the known design that it is always displayed with three decimal
places for normalized values and the setting in Query Designer for
decimal place doesn't take effect. This is because that normalization
changes the number dimension of this structure element.
You may refer to below notes about more details.
> 869135 Decimal places and scaling for "Calculate Single Values As"
You cannot set the number of decimal places or the scaling for some
columns or structural components.
For 2: Some "Calculate As" functions change the number dimension of a
KID. In this case, the scaling and the number of decimal places set for
the KID are no longer relevant. In this case, the system ignores the
original setting and selects a setting that corresponds to the new
number dimension. This cannot be overwritten. The following functions
are affected:
Calculate Single Values as Scale to Result, Overall Result or Query
Result: Scaling 1 and three decimal places.
> 501930 Number of decimal places setting is not applied
As a result, normalized values resulting from the list calculation are
displayed with three decimal places and without scaling by default.
best regards, thom

Decimal Places in Pivot table

Hi Gurus,
When I create a pivot table with a measure and I choose "Show Data as ...
percent of something (for example section) I get the result with 1 Decimal Place.
How to modify it for 2 or more Decimal Places?
Thanks
Laszlo

Hi Laszlo!
We have found and discussed the answer already, but to more people can see it I write it.
When You have the results already, You can use the 'Advanced' page to see the XML source. There you can modify the code carefully. Change the section:
<saw:dataFormat xsi:type="saw:percent" minDigits="2" maxDigits="2" scale="2"/>
Change maxDigits to the number of decimal digits You wanted.
Although we found the answer on the course, I found later this page - also could help:
http://blog.trivadis.com/blogs/andreasnobbmann/archive/2008/07/15/quot-percent-of-quot-in-obiee-s-pivot-tables.aspx
Best regards,
Tamas

Select amount field of a table with decimal place of 3rd value grater than 0.

Select all the reord in a table with amount decimal place of 3rd value grater than 0.

Can you show the sample data + desired result?
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

How to validate for 2 decimal places

How can I put a check while inserting into a number(5,2) field that user has entered only 2 decimal places. Right now if the user inserts records like 23.5456 it gets inserted as 23.56 . I want these type of records to error out. Is there an easy way to do this kind of a validation while inserting.?
Thank You,
SK

Sorry, I don't see how you're going to accomplish this. The value has already been implicitly rounded before check constraints or triggers fire. I guess if they were inserting true literals you could check the SQL statement itself and it's possible to get at bind variable values but that's going to be a real nightmare to implement properly. I think you're going to have to have the column as a number with no scale and check constrain it if this is really required. You could probably do this with a view and instead of triggers but that's going to be ugly.

Yielding the desired number of decimal places using the AVG function in t-sql

Hello again. Confused retired hobby coder having trouble setting up a scalar-valued function to return the desired number of decimal places from a AVG query.
Whenever I run the following script I get the number of decimals I desire:
Using the above I created a scalar-valued function as follows:
Running this function as: SELECT [dbo].[TestHCIPartial] (1,3) my return is -7.
Can you help me with the function causing it to yield the answer to 6 decimal places?
Thanks and regards, Minuend.

You've not specified precision and scale in UDF return type. So you're leaving it to server to interpret it based on default settings
If you want exactly up to four decimal places tweak udf as below
ALTER FUNCTION..
RETURNS decimal(20,4)
AS
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Some urgent chart issues : Lost labels & erroneous decimal places

Hello everybody,
we have some new and really urgent problems with some charts.
Lost labels
Like you can see in the figure below, our charts sometimes loose some lables on the graphs.There are some different scenarios for the problem.
1) Two neighbouring bars have similar values and similar height. So the labels would overlap. In that cases, the charts loose one of the two labels. (see the yellow markers on the bars in the figure below)
2) A chart´s graph tends to the maximum scale of its surrounding container div. The chart components then often "decide", that they do not have enough space for a label and so do not display these labels (line in figure below).
Is there any possibility to fix these problems? Manipulating the charts via css doesn´t work, because the missing elements are not created at all. So there isn´t any element in the DOM that could be adressed.
Erroneous decimal places
In addition to the problems above, we have another one that causes ugly headaches. The values in some charts have 14 decimal places. Settings in the query (we use BW queries as DataSrc) or in the initial view are completely effectless. First we supposed that the problem correlates with some chart types, but in the meanwhile we get the problem with almost all types.
Is anybody out there with similar problems or any ideas to fix the problem?
Thanks so far & kind regars,
Sebastian

Hi Tammy,
thank you for your very quick response. I´m working with IE 10.0.9200 and Design Studio 1.2 SP1. The Application runs normally on a BOE-Server. but the problems occur even when i run the application locally.
But first of all i will check the thread you recommended.
Thanks for your help!

11g Client - Inconsistencies at the 16th decimal place

In TOAD, SQLPlus, & ODBC clients numbers returned from a query are correct (max 3 decimal places)
In Discoverer & from a report, the numbers are off at the 16th decimal place...
EG:
7.081 becomes 7.0810000000000004
7.090 becomes 7.0999999999999994 (which is exceptionally weird because the rounding doesn't work)
7.200 becomes 7.2000000000000002
Any idea what would cause this?
How can I query from SQLPlus (or TOAD) to confirm whether or not those extended decimal places actually exist in the table?

Alan3 wrote:
Maybe I should have added this little tidbit...Please be as verbose as possible (feasible). Show queries etc. - use copy and paste.
The particular table in question is an interface table that has been in place for 4+ years.
The columns in question are of data type NUMBER.
We just switched the PC that runs this interface to Win7 with an 11g client.Describe the interface. E.g. In what program language is it written?
Now we see the extended decimals with Discoverer (on any PC) and the interface report (an old report built from developer 6) as well, but not from SQL, etc...How is changing one pc client related to the Discoverer and Reports reports? Has the database server been upgraded also? (full version from select * from v$version; )
Do you see the same change for "old" data (from before the switch).
I want to know if there is a setting in SQLPlus or the DB client that limits the display of the decimal places that I can alter to determine if the extended decimals actually show up... (they shouldn't be there at all)Both sqlplus and db may affect the outcome, e.g.
SQL> desc test
Name                                      Null?    Type
A                                                  NUMBER
B                                                  NUMBER(38,5)
SQL> show numw
numwidth 10
SQL>
SQL> select * from test;
         A          B
     12345      12345
123456789 123456789
    123,45     123,45
123,456789 123,45679
     1,234      1,234
1,23456789    1,23457
6 rows selected.The same values was inserted to both columns of test. With scale = 5 for its datatype, B values are rounded (4th and 6th row).
SQL> set numw 5
SQL> select * from test;
    A     B
12345 12345
123,5 123,5
123,5 123,5
1,234 1,234
1,235 1,235
6 rows selected.The numwidth setting affects sqlplus formatting.
Edited by: orafad on Jan 5, 2011 9:44 PM

Rounding to 2 decimal places in Derived column transform editor

I want to replace the contents of a value column with itself but rounded to 2 decimal places.
The current column is a double and I have tried to perform this using the following expression but it fails to work.
Code Snippet
Round(cc_vl,2)
How should I achieve this?

I’ll take a guess here but you started with this –
123.45678
Got this –
123.45000
Wanted this –
123.45
So the 123.45000 is absolutely correct, the value has been rounded to 2 digits. A double however has a scale greater than 2, and you only wanted two digits after the point because you were concerned about how the value looked rather than the actual value. This is certainly not a bug. It is how you format the data for display.
Your solution is the way to do this, either on the Derived Column or Data Conversion Transformation. You got it in the end, the replace versus new, because you cannot change the type of a column. You may convert the value, but the storage type of the column means it will implicitly revert to the base column type when you put it back, albeit with a value that has been rounded.
Does that explain it?

Displaying Decimal Places

I wonder if anyone can help.
I am trying to set oracle up to always display the decimal numbers according to the scale. So if the number was set up as 8,2 and 150 was held in a field, 150.00 would be displayed.
Is the a setting for this, how would I set it?
Thanks
Kev

The problem is neatly illustrated by your example. You want to set the default format for "all number types with a decimal place". But your example shows a rendering of 150 as 150.00.
All numbers have an implicit decimal point. With integers the default to suppress the decimal point, because the zeroes are not significant. Of course, the zeroes are significant when, for example, the figure represents a monetary sum.
So the nub of the problem is, when do you want to render 150 as 150.00 and when do you want to render it as 150? That is a business rule and the Oracle database cannot implement it.
Regards, APC

Price per unit is getting round off to two decimal places.

Hi Gurus,
In the Billing output, the Price per unit is getting round off to two decimal places.
How can we avoid this or allow 4 decimal places for such cases.
In the same pricing procedure, we have two pricing condition types PR02 and ZR01.
When PR02 is being used,it doesnt rounds off Price per unit.e.g .578888 = .578888
But when ZR01 is being used the system rounds off price per unit.e.g.578888 = .58
Please suggest where is the setting for it.
Thanks
Montee

Hi,
Which currency you are using? If its INR, then it will do only for 2 decimal places.
The solution for ur problem can be ractified by changing the scales :
Also check OSS 80183
Thanks,
Raja

Rounding off a float to two decimal places

I want to make a function where I shall pass a float and and integer.
The float shall have to be rounded off to a value in the integer.
Can anyone please suggest how to round off a float.
E.g.: if the float is 12.56890 and I want to round it off to 2 decimal places, then it should be 12.57.
Regards
Hawker

I didn't mention any datatypes like float, double.True, but that is what the question is about, so you weren't answering the question. For a change.
As I mentioned, that was just a mathematical steps to round of the floating point value. (Not in any programming languages point of view).False. You didn't mention that at all.
This is the code for that in java.So here you are mentioning datatypes and floats for the same piece of mathematics that you have already been told, with reasons, doesn't work in floating point.
which seems to be working fine
Seems to. What evidence do you have that the float actually got rounded? As opposed to got displayed as rounded? Which is not what the OP asked for.
And of course all that code seems to do is round 0.01 to two decimal places, which again is not what the OP asked for.
For any remaining fans of this 'technique', please explain the behaviour of the following code:
     public static void     main(String[] args)
          int     count = 0, errors = 0;
          for (double x = 0.0; x < 1; x += 0.0001)
               count++;
               double     d = x;
               int     scale = 2;
               double     factor = Math.pow(10, scale);
               d = Math.round(d*factor)/factor;
               if ((d % 0.01) != 0.0) // if 'd' really has been rounded this should be zero
                    System.out.println(d % 0.01);
                    errors++;
          System.out.println(count+" trials "+errors+" errors");
     }

Printing two decimal places from BigDecimal values

I am using BigDecimal to represent money values. My output needs to line up so that (with a non-proportional font) the decimal point and the two decimal places are in the same columns for each line. But when the dollar value has zero cents, or has a number of cents that is divisible by ten, it drops the trailing zeroes, and drops the decimal point if the decimal places are both zeroes. For example, I want to see "25.00" instead of "25" and "25.50" instead of "25.5". It doesn't seem to make any difference if I set the scale to 2. (I have resorted to getting the toString() of the BigDecimal and hacking the string before I display it, but surely there must be an easier way?)
      BigDecimal aaa = new BigDecimal("25");
      BigDecimal bbb = new BigDecimal("25.0");
      BigDecimal ccc = new BigDecimal("25.00");
      BigDecimal ddd = new BigDecimal("25.5");
      BigDecimal eee = new BigDecimal("25.50");
      BigDecimal fff = new BigDecimal("25.75");
      aaa.setScale(2);
      bbb.setScale(2);
      ccc.setScale(2);
      ddd.setScale(2);
      eee.setScale(2);
      fff.setScale(2);
      System.out.println("SCALE SET TO 2: ");
      System.out.println("aaa = " + aaa);
      System.out.println("bbb = " + bbb);
      System.out.println("ccc = " + ccc);
      System.out.println("ddd = " + ddd);
      System.out.println("eee = " + eee);
      System.out.println("fff = " + fff);produces this output:
SCALE SET TO 2:
aaa = 25
bbb = 25.0
ccc = 25.00
ddd = 25.5
eee = 25.50
fff = 25.75Thanks,
Martin

Thankyou Dr. Clap. This solved my problem - I added an LHS to the setScale statements:
      aaa = aaa.setScale(2);
      bbb = bbb.setScale(2);
      ccc = ccc.setScale(2);
      ddd = ddd.setScale(2);
      eee = eee.setScale(2);
      System.out.println("SCALE SET TO 2: ");
      System.out.println("aaa = " + aaa);
      System.out.println("bbb = " + bbb);
      System.out.println("ccc = " + ccc);
      System.out.println("ddd = " + ddd);
      System.out.println("eee = " + eee);produced:
SCALE SET TO 2:
aaa = 25.00
bbb = 25.00
ccc = 25.00
ddd = 25.50
eee = 25.50

Terminating Decimal places in Appraisal Scales

Similar Messages

Maybe you are looking for