Classic file types are no longer available for use as of January 2021. You can transition your classic files or download a PDF. Learn More

SAP BW MDX Query

Beantwoord
0

Opmerkingen

1 opmerking

  • Officiële opmerking
    Brett Harper

    I'm not sure exactly what is wrong from what you show, but some general information that might help:

    Given a standard MDX query defining your axes (rows, columns) and measures (used to compute value of the cell at the intersection of the coordinates of these dimension members.

    In a Flattened output each row is a unique permutation of the dimensions specified for the columns, so it is expected that repeated values might come out if those values don't depend on the member values.  For example, AC_CATEG=ACTUAL, CONSUNIT=1000 calculates the same as AC_CATEG=ACTUAL, CONSUNIT=""

    Key vs. Text: By default, most MDX implementations return the key of a dimension member. To get the descriptive text, you'll usually need to explicitly request it. This often involves functions like MEMBER_CAPTION, MEMBER_NAME, or properties like [Dimension].[Hierarchy].[Member].Properties("Caption"). The exact syntax depends on your BW version and the specific dimension.

    SELECT 
        {[Measures].[Sales Amount]} ON COLUMNS,
        {
            MEMBER_CAPTION([Customers].[Customer].[Customer1]), // Get text for Customer1
            [Customers].[Customer].[Customer2].Properties("Caption") // Another way to get text
        } ON ROWS
    FROM [Your Cube]

    Mapping: When the processing of the output of RSR_MDX_GET_FLAT_DATA happens, it should use the information from RSR_MDX_GET_AXIS_INFO to correctly interpret the data. If an axis element was defined in your MDX to return text (using MEMBER_CAPTION or similar), the corresponding data in RSR_MDX_GET_FLAT_DATA will contain that text. Otherwise, it will be the key.

U moet u aanmelden om een opmerking te plaatsen.