The difference between using logical columns and physical columns in derived columns calculations

When you define a calculated measure column using a logical column, OBIEE performs the aggregation for the columns used in the calculation first, before applying the calculation.

So for example, if a calculated measure (Total Revenue) is derived from the product of two LOGICAL columns (Unit Price x Number of Items), then OBIEE will create SQL such that the Unit Price and Number of Items columns are aggregated first, and then the multiplication.

However, if the calculated measure is derived from the product of two PHYSICAL columns, then the multiplication will be executed first, and then the aggregation after.

This can make a difference in some cases, so know what you want to accomplish and then carefully choose the appropriate column type for your derived column.

One thought on “The difference between using logical columns and physical columns in derived columns calculations”

  1. thank you for the post! Lets say i do not create any measures in RPD but handle the above two scenarios in answers, how do i do it? because, in answers it always behaves as the aggregation is performed on logical columns.

    Like

Leave a reply to Phani Kumar Cancel reply