4 Replies Latest reply: Aug 21, 2012 9:26 AM by Shankar S.-Oracle RSS

    Different Languge/Description Based on Dimension Level

    938723
      Is it possible at all to have either short or long description be chosen through a function depending on a condition e.g. different level in cube?

      Example. If Condition A is met than Long Description is used, Condition B is met than Short Description is used.

      Edited by: user7853353 on Aug 14, 2012 2:36 PM
        • 1. Re: Different Languge/Description Based on Dimension Level
          Shankar S.-Oracle
          Not through Oracle OLAP alone. This is more of a Reporting issue and can be done via db view or using reporting tool features:

          a) Mapping is restricted to a single column. So Long and Short Descriptions need to be mapped to a specific column in source table/view. If your condition is static or related to backend dimension attribute value conditions then you can define the logic in a source view and map both desc attributes to the special column.

          define column green_ldesc_else_sdesc in dimension view....
          case when product_alias.color = 'GREEN' then product_alias.long_desc else product_alias.short_desc end as green_ldesc_else_sdesc

          Use this column to map to short_description/long_description attributes in olap aw dimension mapping.


          b) In OBIEE Answers, you can expose the relevant fields in the reporting layer or Presentation layer of rpd and use it in a case statement to implement your logic.

          E.g:
          CASE WHEN "OLAP Presentation Layer Name"."Product"."Level Name" = 'CLASS' THEN "OLAP Presentation Layer Name"."Product"."Long Description" ELSE "OLAP Presentation Layer Name"."Product"."Short Description" END
          • 2. Re: Different Languge/Description Based on Dimension Level
            Shankar S.-Oracle
            Looking at your subject line, if what you're looking for is support for Multi-Language, then yes, multiple languages (descriptions) are supported for Oracle OLAP. You need to refer to the OLAP Users Guide for more details.

            Check out:
            Oracle® OLAP User's Guide
            11g Release 2 (11.2)

            3 Creating Dimensions and Cubes

            •Supporting Multiple Languages


            HTH
            Shankar
            • 3. Re: Different Languge/Description Based on Dimension Level
              938723
              How will tools such as Simba OLAP connector handle custom views?
              • 4. Re: Different Languge/Description Based on Dimension Level
                Shankar S.-Oracle
                which custom view?

                if custom view=source view used to load cube/dimension then simba connector will not need to use that. It will use the default cube/dimension view which already contains the logic loaded in aw object.

                if custom view=custom view defined over cube/dimension (i did not suggest this in either a) or b) of my post), then simba connector will not be able to use that. It will the default views.