Oracle DBConnect fetches less records when increasing decimal places

Hi All,
In our project we are extracting data from Oracle table into BW using DBConnect. One of the fields is an amount field which is stored as a DEC datatype in Oracle. When we try to bring in the value as it is by increasing the decimal places in the datasource "Proposal" tab, we see that the number of records transferred gets reduced. If we specify the decimal place as 2 or 3, we get all the records, but if we specify 4 or more, the records get reduced. Any idea what could be the problem? We are in BI 7.0 SP 13.
Thanks
Sundar

Hi Kishore,
Thank you for quick reply.
Yes, I've already played around with different call interface types - no result.
It is funny, but in View Data I see the column values are shown as integers! Of course, datatype is set to DOUBLE in OBIEE.
May be it has something to do with the fact underlying db object is not a table, but a view? In the db view datatype is shown as NUMBER.
I also noticed the same issue with other physical tables which are defined as opaque views (Select). If I change type to Physical Table and underlying db object is a table indeed, values are displayed as decimals, but no issues with extra digits. Still I have the issues with queries over this physical table.

Similar Messages

How we can increase decimal places in Sales Order for Qty

Hi,
In Sales Order qty field now its 3 decimal places for MON unit of measure but we want 4. how we can increase decimal places.
Thanks in advance
Thanks & Regards,
PM

To elaborate better.
Again, use Tcode CUNI - Unit of measurement : Initial Screen.
At initial screen, choose TIME from the list (where by default AAAADL- no dimensions is there).
And click on UNIT OF MEASUREMENT button.
In that you will find MON - Month.
There go for details by selecting MON or select MON and press F5 from Key board.
For MON unit maintain following parameter as per your requirement:
-Number of decimal places for number display
Use - This parameter determines the number of decimal places with which this measurement unit is displayed.
-Base ten exponent for floating-point display
Use - This exponent determines how the values for this measurement unit are formatted as floating point numbers.
Examples - If the exponent is 3, the floating point numbers have the format xxx.xxxxE3.
And deselect commercial meas. unit in application parameters section.
I would suggest instead of changing standard settings of MON, you create ZMON in TIME dimension.
Thanks & Regards
JP

Increase decimal places in Gross Unit of Measure

Hello Everyone,
I had an issue regarding Decimal places for a specific Unit of measure.
My Base unit of measure is maintained in Ea. For this the material is maintained with a gross maintained in Kg's. Now to record 2.5 grams i have to menition .0025 Kg but system does not accept up to 4 decimal places. system only accepts up to 3 decimal places. Even increasing the decimal places in CUNI does not make the system to accept 4 Decimal places.
So what is the solution to this.
Any help is highly appreciated.
Sincerely,
Aji

HI
I dont think that we can increase the length of the decimal places filed in all cases. Refer note 95869.
Regards
Abhijit Gautam

Increasing decimal places in System Prefs

Hello all. I was wondering if there was a way to increase the decimal places for a currency when you go to System Preferences > International > Formats Tab.
I'm not sure if there are other countries that have 3 decimal places for their currency, but I'm currently in Jordan, and the local currency (Jordanian Dinar) has 3 decimal places. If I change the currency in the formats tab of the international pref to Jordanian Dinar, it shows 2 digits. Is there a way to customize or change this to increase the decimal places from 2 to 3?
Any help would be appreciated.
OKS
Dual 2.7 GHz PowerPC G5 Mac OS X (10.4.6) Macbook Pro 2.16GHz Intel Core Duo

Looks like Apple updated the Jordanian Dinars currency to 3 digits!
Thxs Apple.

Error message when updating decimal places in general settings

Hello together,
I got a big problem with the settings of decimal places.
I know that I am only be able to incerase these but it's a virgin database for a customer with no data imported.
Everytime I want to increase the prices decimal places I get the following error message:
"cannot update while another user is connected to the company"
But I checked all sessions connected to this database. I am the only person that is logged in.
I closed the db more that one time but it doesn't work.
Can you help me please?

Hello Meike,
I have had this problem a while ago and it was caused by the RPD-connection i had made with the customer server.
I had to change the values directly on the client machine.
Hope this also your solution.
Kind regards.

Increase decimal Places in SAP B1

Dear Experts,
(Using SAP B1 PL 49)
I am trying to change the Decimal places in the General Settings->Display (Decimal Places), from 2 to 6 to in all the fields.
When i try to update it gives me the following error:-
"Cannot update while another user is connected to the company"
Any help will be appreciated.
Regards,
Feroz

Dear Asif,
Thank you for the information.
I logged all the users out from the SAP server and i stopped the SQL services and then re-started the SQL services again.
I logged into SAP b1, but was getting the same error message.
I removed the network cable of the server and I restarted the SAP server and then logged into SAP and tried to change the decimal places, but was still getting the same error message.
I'm all out of ideas, this has never happened before to me.
regards,
Feroz.

Increase decimal places in the PO quantity and Price

Hi All,
Can the decimal places in the PO( ME21N) creation be increased more than 3 decimal places in quantity and price?
I did changes in UOM's in CUNI, I increased the decimal places upto 14 but still it does not take more than three i-e., 0.001 maximum.
Is there any other way to handle this?
Request inputs on this.
Note 569326 - ME9F: Customized decimal places are not taken into account........ found this OSS but this correction instruction is not for our pack level ECC 6.0
Best regards,
Sridhar

hi
In case if you are already working in production remember that decimal places should not change. It will affect all previous data.
For your problem best solution is make order unit as 1000. So that your problem will solve
e.g. instead of 2.009 inr for 1 Unit use 2009 inr for 1000 unit.

Increase decimal place for price

Dear All,
We are having a requirement to increase the decimal place to 6 for price.
Any suggestions how we can do that in SNC.
thanks,
mahesh.

Dear Mahesh
You cannot have 6 decimal for standard currencies.
What you can do is, create a dummy currency and maintain it as 6 decimal and maintain exchange rate of conversion for this dummy currency and original currecy.
If you try to maintain for standard currency, it will lead to inconsistencies
Lets say AUD is standard currency
now create AUD6 as dummy currency and maintain decimal as 6, and create rate (direct/indirect) between AUD & AUD6
Regards
Vinod

VO fetches 25 records, when there are 150 in the iterator.

Hi All,
I'm using View Objects as part of my AD form. In the bean associatd with the form, in one fo my methods, I loop through the Iterator associated with this VO.
I notice that only 25 records are being fetched, even though the number of rows is clearly more than that. I've looped through usinga for loop and printed each and every record within the VO and it only prints 25.
How can I tune this VO to bring back all my records at once?Will it always only bring back 25 at a time?
JDev-11g used.
The code I use to bring back the rows is :
int numRows = vo.getRowCount();
System.out.println("*Number of rows*" + numRows); // This returns 150
for (int i = 0; i < numRows; i++) {
System.out.println("Role data" + roledata);
I'm trying to print out each line's role data : I notice only 25 printed lines in the logs.
//some code
What am I doing incorrect here?
Thanks
Preethi.
Edited by: 859810 on 08-Aug-2011 02:38

On the page go to bindings - executables - select the iterator and set its range size to -1.
setting -1 will fetch all the records
Edited by: in the line of fire on Aug 8, 2011 1:41 PM

Fetching many records all at once is no faster than fetching one at a time

Hello,
I am having a problem getting NI-Scope to perform adequately for my application. I am sorry for the long post, but I have been going around and around with an NI engineer through email and I need some other input.
I have the following software and equipment:
LabView 8.5
NI-Scope 3.4
PXI-1033 chassis
PXI-5105 digitizer card
DELL Latitude D830 notebook computer with 4 GB RAM.
I tested the transfer speed of my connection to the PXI-1033 chassis using the niScope Stream to Memory Maximum Transfer Rate.vi found here:
http://zone.ni.com/devzone/cda/epd/p/id/5273. The result was 101 MB/s.
I am trying to set up a system whereby I can press the start button and acquire short waveforms which are individually triggered. I wish to acquire these individually triggered waveforms indefinitely. Furthermore, I wish to maximize the rate at which the triggers occur. In the limiting case where I acquire records of one sample, the record size in memory is 512 bytes (Using the formula to calculate 'Allocated Onboard Memory per Record' found in the NI PXI/PCI-5105 Specifications under the heading 'Waveform Specifications' pg. 16.). The PXI-5105 trigger re-arms in about 2 microseconds (500kHz), so to trigger at that rate indefinetely I would need a transfer speed of at least 256 Mb/s. So clearly, in this case the limiting factor for increasing the rate I trigger at and still be able to acquire indefinetely is the rate at which I transfer records from memory to my PC.
To maximize my record transfer rate, I should transfer many records at once using the Multi Fetch VI, as opposed to the theoretically slower method of transferring one at a time. To compare the rate that I can transfer records using a transfer all at once or one at a time method, I modified the niScope EX Timestamps.vi to allow me to choose between these transfer methods by changing the constant wired to the Fetch Number of Records property node to either -1 or 1 repectively. I also added a loop that ensures that all records are acquired before I begin the transfer, so that acquisition and trigger rates do not interfere with measuring the record transfer rate. This modified VI is attached to this post.
I have the following results for acquiring 10k records. My measurements are done using the Profile Performance and Memory Tool.
I am using a 250kHz analog pulse source.
Fetching 10000 records 1 record at a time the niScope Multi Fetch
Cluster takes a total time of 1546.9 milliseconds or 155 microseconds
per record.
Fetching 10000 records at once the niScope Multi Fetch Cluster takes a
total time of 1703.1 milliseconds or 170 microseconds per record.
I have tried this for larger and smaller total number of records, and the transfer time per is always around 170 microseconds per record regardless if I transfer one at a time or all at once. But with a 100MB/s link and 512 byte record size, the Fetch speed should approach 5 microseconds per record as you increase the number of records fetched at once.
With this my application will be limited to a trigger rate of 5kHz for running indefinetely, and it should be capable of closer to a 200kHz trigger rate for extended periods of time. I have a feeling that I am missing something simple or am just confused about how the Fetch functions should work. Please enlighten me.
Attachments:
Timestamps.vi ‏73 KB

Hi ESD
Your numbers for testing the PXI bandwidth look good. A value of
approximately 100MB/s is reasonable when pulling data accross the PXI
bus continuously in larger chunks. This may decrease a little when
working with MXI in comparison to using an embedded PXI controller. I
expect you were using the streaming example "niScope Stream to Memory
Maximum Transfer Rate.vi" found here: http://zone.ni.com/devzone/cda/epd/p/id/5273.
Acquiring multiple triggered records is a little different. There are
a few techniques that will help to make sure that you are able to fetch
your data fast enough to be able to keep up with the acquired data or
desired reference trigger rate. You are certainly correct that it is
more efficient to transfer larger amounts of data at once, instead of
small amounts of data more frequently as the overhead due to DMA
transfers becomes significant.
The trend you saw that fetching less records was more efficient sounded odd. So I ran your example and tracked down what was causing that trend. I believe it is actually the for loop that you had in your acquisition loop. I made a few modifications to the application to display the total fetch time to acquire 10000 records. The best fetch time is when all records are pulled in at once. I left your code in the application but temporarily disabled the for loop to show the fetch performance. I also added a loop to ramp the fetch number up and graph the fetch times. I will attach the modified application as well as the fetch results I saw on my system for reference. When the for loop is enabled the performance was worst at 1 record fetches, The fetch time dipped around the 500 records/fetch and began to ramp up again as the records/fetch increases to 10000.
Note I am using the 2D I16 fetch as it is more efficient to keep the data unscaled. I have also added an option to use immediate triggering - this is just because I was not near my hardware to physically connect a signal so I used the trigger holdoff property to simulate a given trigger rate.
Hope this helps. I was working in LabVIEW 8.5, if you are working with an earlier version let me know.
Message Edited by Jennifer O on 04-12-2008 09:30 PM
Attachments:
RecordFetchingTest.vi ‏143 KB
FetchTrend.JPG ‏37 KB

Increase Decimal Points

Hi All ,
my req is to increase decimal places.
I have variable Lv_qty type EKPO-MENGE
its has only 2 decimal places .
but i want 10 decimal places in calculation
PO item Value is
= (net price )1400 * (Conversion factor ) 0.0133333333 * (ord qty)252
= 18.66666662
=4703.99998824 =4704 usd
According to my report ,the conversion factor comes to 0.013 ( i.e. field length = 5 instead of std field length for numeric field which equals to 12 )
PO item Value = 1400 *0.013 *252
=4586.40 usd
here I want to print PO item Val = 4703.99998824 =4704 usd

Hi gs p,
for any calculations put result to a field TYPE f. This will use as many digits as possible. The result may be stored afterwards to a TYPE field with number of digits you want.
Regards,
Clemens

Decimal Places in BOM

Dear All
How can i increase decimal places of components in BOM as it is taking only three decimal but i want to add upto 6 decimal. I mean i want to add component qty as 8.785642 in BOM. so how can i enter it

Dear Ahmad,
Go to transaction CUNI, Click on unit of measurement, select ur unit of measure(ex: M/L/KG etc) for which u want to maintain 6 decimals, In decimal places field maintain 6. come back and create BOM.
test and come back
sree

How to decrease decimal places in invoices

Good day,
How do i drecrease decimal places in invoices. For example , i have set the decimal places to 4 for costing purposes but i want the final invoice to be 2 decimal places for display purposes. i have tried decreasing the decimals using the decrease decimals icon but the decimals are still 4.
Thanks

Hi Wendy,
This is System Standard that If you increased Decimal Place then you can not decrease those decimal Place again.
If you want this then you can do this in (Print of Document) Document Layout through Crystal Report.
Hope this help
Regards::::
Atul Chakraborty

XL REPORTER DECIMAL PLACES

Although may be selected for a Company 6 decimal places (e.g. prices, rates, amounts) XL returns only 2 decimal (in Report Builder and Report Composer). Is there a possibility to increase decimal places in XL? Rounding makes serious differences in results.

Please refer SAP note no. 896207
The following is the content of the note.
You have to edit the registry to change this. Do the following:
1. Go to Start->Run in Windows and enter "Regedit".
2. Go to HKEY_Local_Machine\Software\iLytix\XLReporter\Settings and add new string value (Right-click and choose New->String Value) and enter "FloatDecimals".
3. Press Enter and double-click to enter the decired number of decimals.
Note: This will only affect figures in the Report Designer, and not Report Composer.
Incorrectly editing the registry may damage your system. System registry changes should therefore only be performed by an advanced user who is prepared to both edit and restore the registry. For details about the system registry, please refer to Microsoft Registry Editors help system.
Kindly provide Points if this has resolved your query.
Regards:
Vivek

I need to get 2 decimal places when using a formula for a quotient and Numbers will only give me whole integers which is useless since most items will be less than 1. How can I change this?

How do I get 2 decimal places when using a formula for a quotient? It only gives me whole integers. Most of the results will be less than 1 so I need 2 decimal places

the quotient function returns only whole number portion of the dividing two numbers. If you want the actual decimal value use the divide operator. you enter this as:
A/B
if the numerator is in A1 and the denominator is in B1 you can enter the formula like this:
=A1/B1

Oracle DBConnect fetches less records when increasing decimal places

Similar Messages

Maybe you are looking for