turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

Find a Community

- Home
- /
- BI
- /
- Enterprise Guide
- /
- Ratio

Topic Options

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content

10-27-2010 12:13 AM

Hi,

Would like to know how EG generates the resulting values if the expected output is undefined value?

In our scenario, we are computing for ratio with the following given values:

numerator = 15,123,021,740.41

denominator = 0

generated ratio = 1741640597964550%

Although, the data should not have a 0 denominator, just want to ask how EG was able to get the value 1741640597964550%? Moreover, the client tried re-generating the report using same data but the ratio output displayed a different value, 34102446547241500%. Howcome the values are inconsistent?

Thanks!

Would like to know how EG generates the resulting values if the expected output is undefined value?

In our scenario, we are computing for ratio with the following given values:

numerator = 15,123,021,740.41

denominator = 0

generated ratio = 1741640597964550%

Although, the data should not have a 0 denominator, just want to ask how EG was able to get the value 1741640597964550%? Moreover, the client tried re-generating the report using same data but the ratio output displayed a different value, 34102446547241500%. Howcome the values are inconsistent?

Thanks!

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content

10-27-2010 01:40 PM

We'll need more details for how this calculation was done. Using Query Builder? A program with DATA step? A log/output example would help.

EG doesn't perform calculations itself, usually. All of the computations are done within SAS and driven by SAS programs, either written by users or generated in a UI like the Query Builder.

Chris

EG doesn't perform calculations itself, usually. All of the computations are done within SAS and driven by SAS programs, either written by users or generated in a UI like the Query Builder.

Chris

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content

10-28-2010 04:38 AM

Thank you, Chris. I sent you a separate email. I think it's possible that it's a format issue? I tried summarizing the amounts manually in Excel using the values of the tables used as source by the OLAP cube. It appears that there are two items that did not match because of the decimal values, although when rounded off to two decimals they get the same value. The wierd thing though is that none of them matched the RAW VALUE produced in the EG subtotal.

__Excel Manual Summation:__

* The optimized value when the Consolidated amount is summarized will equal to**0.00000**.

* The original value when the Consolidated amount is summarized will equal to**0.00055**.

__Query using SAS Base:__

* The optimized value when the Consolidated amount is summarized will equal to**0**.

* The original value when the Consolidated amount is summarized will equal to**0.0008544922**.

__EG Subtotal Raw Value:__

* The optimized value when the Consolidated amount is summarized will equal to**4.43458557128906E-05**.

* The original value when the Consolidated amount is summarized will equal to**0.000868320465087891**.

* The optimized value when the Consolidated amount is summarized will equal to

* The original value when the Consolidated amount is summarized will equal to

* The optimized value when the Consolidated amount is summarized will equal to

* The original value when the Consolidated amount is summarized will equal to

* The optimized value when the Consolidated amount is summarized will equal to

* The original value when the Consolidated amount is summarized will equal to

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content

10-27-2010 10:10 PM

Louise,

I'd suggest that you read this article and see if it answers your question

http://support.sas.com/documentation/cdl/en/lrcon/62955/HTML/default/viewer.htm#a000695157.htm

At the heart of the problem is that you are thinking in base-10 and computers work in base-2, so most things are approximations. Integers can be represented exactly, but decimal numbers cannot. Therefore

X=0;

is not the same as

X=0.0;

I'd suggest that you read this article and see if it answers your question

http://support.sas.com/documentation/cdl/en/lrcon/62955/HTML/default/viewer.htm#a000695157.htm

At the heart of the problem is that you are thinking in base-10 and computers work in base-2, so most things are approximations. Integers can be represented exactly, but decimal numbers cannot. Therefore

X=0;

is not the same as

X=0.0;

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content

10-28-2010 04:40 AM

Thank you, Doc. I'll check on the link you provided and see if that explains the issue.

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content

10-28-2010 09:42 AM

Just FYI for the group...

In follow-up e-mail, it turns out this scenario is related to OLAP from within EG. We're following up within the development group with a more detailed analysis.

Chris

In follow-up e-mail, it turns out this scenario is related to OLAP from within EG. We're following up within the development group with a more detailed analysis.

Chris