Multiple Levels in Hierarchy using MDX in SSAS

Hi All,
I am Hiren Parikh from India.
I have a requirement in which I want multiple levels in a single hierarchy.
But this levels should not depend on each other.
For eg -
+ Country
-India
- China
- Japan
+ State
- X
- Y
- Z
+ City
- Mumbai
- Beijing
- Tokyo etc
I will not select Country, State & City at the same time. If I select the Country then Country will become my filter.
If I select the State then State will become my filter.
If I select the City then City will become my filter. This means all the 3 levels are independent should work.
Thanks in advance...
Regards,
Hiren Parikh
Hiren Parikh

Hi Hiren,
According to your description, you will not select Country, State & City at the same time, right?
So as per my understanding, you needn't to create the hierarchy, just create three attributes Country, State and City. Then when you select one of the attributes in the PowerPivot table, the attribute can be the filter which you can see on the screenshot
below.
Regards,
Charlie Liao
TechNet Community Support

Similar Messages

Except function with parent child hierarchy using mdx query

HI,
I need to remove some items using mdx query in parent child hierarchy.
I tried with below query,it is not removeing ,could you please help me.
SELECT
{[Measures].[Amount]} ON
COLUMNS
NonEmpty([Account].[Accounts].[Account Level 01],[Measures].[Amount])
ON ROWS
FROM (SELECT
-Descendants({[Account].[Accounts].&[47]},,Leaves)
} ON COLUMNS
FROM [Adventure Works])
indu

Hi Indu,
Why do you remove some itmes using
Descendants function? Generally, we use FILTER function to achieve the requirement.
WITH SET [CustomAccounts] AS
FILTER ([Account].[Accounts].[Account Level 01].Members , [Account].[Accounts].CurrentMember.Name<>'Net Income')
SELECT {[Measures].[Internet Sales Amount]} ON 0
[CustomAccounts] ON 1
FROM [Adventure Works]
WITH SET [CustomAccounts] AS
FILTER ([Account].[Accounts].[Account Level 01].Members , [Account].[Accounts].CurrentMember.Name='Net Income')
SET [RemainingAccount] AS
[Account].[Accounts].[Account Level 01]- [CustomAccounts]
SELECT {[Measures].[Reseller Sales Amount]} ON 0
[RemainingAccount] ON 1
FROM [Adventure Works]
Results.
References.
http://www.databasejournal.com/features/mssql/article.php/3306101/MDX-Essentials-Basic-Set-Functions-The-Filter-Function.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c0149678-97f2-4066-903f-7f9e9ff09b56/filtering-out-dimension-members-with-mdx?forum=sqlanalysisservices
Regards,
Charlie Liao
If you have any feedback on our support,
please click here.
Charlie Liao
TechNet Community Support

How can i create Level Based Hierarchy using multiple logical table.

Hi All,
in my use case i have two master logical table.
Division_Mst(divncd,DivnName)
Department_Mst(deptcd,DeptName)
and one logical table which contain both column Header (divncd,deptcd)
and fact table detail where one measure column(empcd) using aggregation count on it.
so i want to create levelbased hierarchy like this.
DivnName
|------DeptName
which are come from(Division_Mst,Department_Mst) .
so user can see no of employees division wise and drill down to Department wise.
How can i achieved this?
thanks
Manish

Check out Shay's blog https://blogs.oracle.com/shay/entry/adf_faces_dynamic_tags_-fora
Timo

Extract Data in Power Pivot from MDX with diffrentnt different Level of Hierarchy in MDX

Hi All,
My requirement is to extract the data form tabular model and put in power pivot,as all the measures calculation is present in model just extracting the aggregated data.
Issue is appearing on Rolling up the data, so is there any way to extract the data so that it will display the right data on different level. As per the below example on level 2 data is getting summed up which is not correct.
Ex:-
Level1
A
10%
B
20%
Level2
30%
Thanks Chandan

Hi Chandan,
According to your description, you create a SQL Server Analysis Services Tabular model and extract Data in Power Pivot from MDX, the problem is that the hierarchy data rolling up base on the hierarchy level, right?
I have tested it on my local environment, we cannot reproduce this issue. So as per my understanding, the issue can be cause by the hierarchy setting in your tabular model. Here are some links about how to create and manage hierarchies in a tabular model,
please refer to the links and check if the settings are correct.
http://msdn.microsoft.com/en-in/library/hh213003.aspx
http://www.youtube.com/watch?v=qKKNY1Vj_2c
If the issue persists, please provide us more information about you hierarchy creation steps, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Display two members of same dimension hierarchy using mdx on 2 diff columns

Hi,
Is it possible to print the parent of a member that belongs to a certain level in the hierarchy. For this example, the Dimension hierarchy is a Variable hierarchy based on a Row Source, - BOM - Bill of Materials.
Let say there is a BOM hierarchy with 4 levels.
Finished Good - Comp1 - Comp2 - Comp3.
Then we want to display in the IOP report as follows.
Finished Good Supply Chain--These are the column headers
Finished Good1 Finished Good1
Comp1
Comp2
Finished Good2 Finished Good2
Comp3
Comp4
Comp3
Edited by: user596497 on Mar 16, 2011 1:39 PM

The question is wrong ...
MDX helps you to construct cross-product of indices for the underlying cube and then it tells the system to find whether there is any cell with that index, and if so, returns a value for that combination.
If you put two dimensions next to each other, what does it mean? There is no such combination in the underlying cube as each dimension is uniquely represented. We will throw an error as follows:
You cannot mix-up display semantics with the syntax/semantics of MDX.
"Can only cross join sets with different dimensions Statement"
An internal error occurred during the query execution phase. Please contact your administrator.
Query Definition
WITH SET [AnotherGeography] AS '{[Geography].DefaultMember}' SELECT {Fiscal.DefaultMember} ON COLUMNS, { CrossJoin( {[Geography].DefaultMember}, {[Customers].DefaultMember}, {[AnotherGeography]}, {Hierarchize(Descendants([Product].DefaultMember, [Product].[Product Family], SELF_AND_BEFORE), POST) }, { [Measures].[Target Revenue], [Measures].[Demand Plan Revenue], [Measures].[Market Share], [Measures].[Adjusted Demand Plan Quantity] }) } ON ROWS FROM [Demand]
Can only cross join sets with different dimensions Statement: WITH SET [AnotherGeography] AS '{[Geography].DefaultMember}' SELECT {Fiscal.DefaultMember} ON COLUMNS, { CrossJoin( {[Geography].DefaultMember}, {[Customers].DefaultMember}, {[AnotherGeography]}, {Hierarchize(Descendants([Product].DefaultMember, [Product].[Product Family], SELF_AND_BEFORE), POST) }, { [Measures].[Target Revenue], [Measures].[Demand Plan Revenue], [Measures].[Market Share], [Measures].[Adjusted Demand Plan Quantity] }) } ON ROWS FROM [Demand]

Multiple levels in hierarchy is not showing data properly in AWM

I may have to create a hierarchy like this :
Cluster name -> Trunk Type -> Trunk name.
A cluster can have many trunk types, say T1, T2 etc and each trunk can have many names.
For example, this is my data :
C1, T1, c1T1_1
C1, T1, c1T1_2
C1, T2, c1T2_1
C2, T1, c2T1_1
C2, T1, c2T1_2
But I see that all the data to be shown for c2 and T1 is shown in C1, T1 itself.
I see that the issue, is that as T1 is not distinct, it is causing this issue.
How can i fix this ?

This sounds like the same problem that has been recently posted.
hierarchy problem in awm
You cannot have the single member, T1, report into both C1 and C2. You need to make the member name unique in some way. Here is a simple example following the pattern you have already set.
C1, c1T1, c1T1_1
C1, c1T1, c1T1_2
C1, c1T2, c1T2_1
C2, c2T1, c2T1_1
C2, c2T1, c2T1_2

Unable to create cross tab report with multiple level dynamic columns

Hi Gurus,
We are trying to develope group above cross tab report with BI Publisher.
i am unable to achieve multiple level columns dynamically.Using cross tab wizard i can achieve single level measure column ,but not the second level column.
Output should look like this:
Country1
Region1 Region2 Region3 --(level1 column)
d1 d2 d3 d1 d2 d3 d1 d2 d3 -- (level2 column)
Row1 10 20 30 70 80 90 40 70 90 --data
Row2 21 24 54 65 23 64 64 76 87
Here regions and d1 d2 d3 may vary based on xml data.Also we have page break on country.
Thanks,
Mahesh

Hi kavipriya,
Any update on this.I have set the rtf and xml to ur gmail id.
Thanks,
mahesh

Setting default member of attribute hierarchy in MDX script. Default member not taken into account while using user defined hierarchy

Hi all
I have a date dimension that (type time) with attributes
- [FiscalYear] (type years)
- [FiscalMonth] (type months)
- [FiscalWeek] (type weeks)
In addition to the attributes used in the natural hierarchy, I have an attribute [PerType] containing one member comming from the relational table 'WTD' which corresponds to 'Current Date'. All other members of this attribute hierarchy are calculated members (defined in the MDX script). Examples:
--Last year
CREATE MEMBER CURRENTCUBE.[Date].[PerType].[LY] AS NULL,
VISIBLE = 1;
SCOPE([Date].[PerType].[LY]);
SCOPE(DESCENDANTS([Date].[Fiscal].[All], [Date].[Fiscal].[Year], SELF_AND_AFTER));
THIS = ([Measures].CurrentMember, [Date].[PerType].[WTD], ParallelPeriod([Date].[Fiscal].[Year], 1));
END SCOPE;
END SCOPE;
--Month to date
CREATE MEMBER CURRENTCUBE.[Date].[PerType].[MTD] AS NULL,
VISIBLE = 1;
SCOPE([Date].[PerType].[MTD]);
SCOPE(DESCENDANTS([Date].[Fiscal].[All], [Date].[Fiscal].[Week], SELF_AND_AFTER));
THIS = Aggregate(CrossJoin({[Date].[PerType].[WTD]}, MTD([Date].[Fiscal].CurrentMember)));
END SCOPE;
END SCOPE;
--Year to date
CREATE MEMBER CURRENTCUBE.[Date].[PerType].[YTD] AS NULL,
VISIBLE = 1;
SCOPE([Date].[PerType].[YTD]);
SCOPE(DESCENDANTS([Date].[Fiscal].[All], [Date].[Fiscal].[Period], SELF_AND_AFTER));
THIS = Aggregate(CrossJoin({[Date].[PerType].[WTD]}, YTD([Date].[Fiscal].CurrentMember)));
END SCOPE;
END SCOPE;
The defalut member of FiscalWeek attribute hierarchy is set dynamically in the MDX script:
ALTER CUBE CURRENTCUBE UPDATE DIMENSION [Date].[FiscalWeek], DEFAULT_MEMBER =
Filter(
[Date].[FiscalWeek].Members,
[Date].[FiscalWeek].Properties( "FiscalWeekStartDate", TYPED) <= DateAdd("d", -2, CDate(CStr(Month(Now())) + "/" + CStr(Day(Now())) + "/" + CStr(Year(Now()))))
AND
[Date].[FiscalWeek].Properties( "FiscalWeekEndDate", TYPED) >= DateAdd("d", -2, CDate(CStr(Month(Now())) + "/" + CStr(Day(Now())) + "/" + CStr(Year(Now()))))
)(0).PrevMember;
If I run the following query:
with member
measures.x as [Date].[Fiscal].DefaultMember.Name
measures.y as [Date].[FiscalWeek].DefaultMember.Name
select
measures.x,
measures.y
} on axis(0)
from [GLWeekly]
it gives me back correctly the default member set over the MDX script.
I order the statements in the MDX Script so that the default period (week) is set at the beginning of the script (just after the calculate).
I do not understand why creating the following calculated member I am obliged to specify [Date].[Fiscal].CurrentMember in the tuple to have correct results:
MEMBER [Account].[CoA].[Standard Engagement Revenue (MTD)] AS ([Account].[CoA].[Standard Engagement Revenue], [Date].[PerType].[MTD], [Date].[Fiscal].CurrentMember)
I would expect that:
([Account].[CoA].[Standard Engagement Revenue], [Date].[PerType].[MTD])
is sufficient.
If the default week is specified in the slicer using a member of the natural hierachy (=> [Date].[Fiscal].x) it works.
Why can't SSAS use the default member if it is must defined in the MDX script?
Can someone explains me this. Thanks a lot in advance.

Hi Ina,
have you thought about adding a dynamic statement inside the MDX script? You could define the default member like this:
... DEFAULT_MEMBER = iif( Day( Now() ) = 3, <expression for previous month>, <expression for current month> );
This way you don't need to change it everytime by running a script.
By the way, what do you mean it doesn't update the default member? When you execute this MDX what does it says?
with member measures.x as [Dimension].[HierarchyName].DefaultMember.Name
select { measures.x } on 0 from Cubename
If this returns the correct name, then the problem is somewhere else. I believe it should return you the correct name. Look here, test this on Adventure Works, statement by statement and see what happens.
ALTER
CUBE [Adventure Works]
UPDATE
DIMENSION [Product].[Product Categories],
DEFAULT_MEMBER = [Product].[Product Categories].[Category].&[1]
with
member measures.x
as [Product].[Product Categories].DefaultMember.Name
select measures.x on 0
from [Adventure Works]
ALTER
CUBE [Adventure Works]
UPDATE
DIMENSION [Product].[Product Categories],
DEFAULT_MEMBER = [Product].[Product Categories].[All Products]
with
member measures.x
as [Product].[Product Categories].DefaultMember.Name
select measures.x on 0
from [Adventure Works]
I think you can see which members are default (on related hierarchies) using
MDX Studio. This should help you detect which attributes have not moved accordingly and hence cause problems in your report. The usual suspects are those attributes used in your last month reports. If that's too much for you, just copy paste the definition
of the measure x and use .CurrentMember instead .DefaultMember. And so for all related hierarchies of your dimension. You can run it as one query, just put enough measures (x1, x2, ...), one for each hierarchy, ok?
Here's a test for Day():
with
member measures.y
as
iif( Day(Now()) = 28, 'Yes', 'No' )
select
measures.y on 0
from [Adventure Works]
Today this returns Yes, tomorrow it will be No.
Ups, I just checked one more thing. When you run the script, it sets the default member only for that session. If you execute the first two of the four statements that I've sent you, it will set the default member on Bikes and show you that.
But, if you open another query windows and execute that select statement (only), you'll see All member instead. So, it has set it to Bikes only for the currect session. Consequence? You reports are not aware of it. So, better use dynamic statement in
your MDX script.
Regards,
Tomislav Piasevoli
Business Intelligence Specialist
www.softpro.hr

Multiple levels in ALV Hierarchy

Hi All
How to display Multiple levels in ALV Hierarchy.
I have header and Item Tables but Under Header Expansions I have to display one more Expansion.
Means Multiple levels.

Hi,
I think you can check standard program BCALV_TEST_HIERSEQ_LIST
Regards,
Himanshu

Using SUM BY or MAX BY for multiple levels

I was wondering if anyone knows if you can use the SUM BY for multiple levels e.g.
I am using the following at the moment: SUM("Fact.Value" BY Dimension.Level1), but I also want to sum the value by a different level, so adding a second 'BY' level.
I can't seem to figure if its possible. Any help would be appreciated.

Hi,
If I understood you correctly, yes, you can use for example: SUM(saw_4 by saw_1, saw_2, saw_3)
I hope this helps.

Problem in Aggregate with Multiple level of dimension

Hi,
I have a BI repository with a snowflake schema. I have also designed the business model with snowflake, It works with drilling and all but I am facing problem when I am
creating a logical column aggregating with a higher level of dimentation. Let me illustrate that :
I have the Following Hierarchy :
Tournament(id, Name) ---- > Round (id, name, tournament_id) -------> Match (id, Name, RoundId ) | Match is fact table and other 2 dimension.
I also created a logical dimension called tournament with 3 levels.
Now say I want to create a logical column Total Number of Matches , aggregating to the dimension level of Tournament. The result gives counts a 0 for every tournament. However
it is working perfectly when the dimension level is Round (which is the immediate next level after fact).
The Logical request generated (in case of Tournament level) :
   MatchId:[DAggr(Measure1.MATCHID by [ Matches$.TournamentId] SB Tournament)] as c1 GB.
    There is no such column as TournamentId in Matches$ table. How does the BI server got this ?
   The execution plan evaluate this:
     cast(NULL as INTEGER ) as c1 GB [for database 0:0,1]
   Can someone please explain why is this happening, is it because of the snowflake schema, but I guess if BI server can handle a snowflake schema it should work the Aggregate
   properly in multiple levels of dimensions, or it is something I am doing wrong.
   Execution Environment:
     Windows XP , OBI 10g on OC4J. Data source : MS Excel (ODBC 3.5)
Regards,
Ru

Hi,
With reference to your question.
Can any operator perform this task..I don't think any single operator will help you.
I suggest using an intermediate (staging) table by using a PL SQL procedure with output port to store the values of account number provided the number of accounts are limited. Else use an array variable for account of an employee.
In short no simple solution because of the bad source design else the pivot/unpivot operator would have helped you.
Cheers
- Mohammed

HANA level based Hierarchy is not displaying in AOLAP

Hi all,
I have created a level based Hierarchy in HANA which I have been able to display in Excel using a HANA MDX Provider connection:
However when I try to use the Hierarchy in Analysis for OLAP I am unable to see it, instead the dimensions are flat:
I have used an OLAP connection to HANA which otherwise appears to be working correctly.
We are on SAP BusinessObjects BI Platform 4.1 Support Pack 1 Version: 14.1.1.1036. and HANA 1.00.69.01.386065.
If anyone can help it would be greatly appreciated.
Regards,
Steve Willis.

Hi Stephen,
This should be possible. In my environment, I'm able to access both the flat and hierarchical presentations for a dimension, if I expand the dimension in the tree (see screenshot). I have noticed that the flat presentation is the default. However, if I expand and drag the appropriate hierarchy, I am seeing the hierarchy in the crosstab.
Are you able to expand the dimension and access the hierarchy?
Best regards,
Philip

Level Base Hierarchy???

Hi,
I have two dimension tables which have join relation in physical layer, and now on top of this 2 tables i need to create Level Base Hierarchy in BMM Layer.
By Maintaining single Logical table with all the required columns from 2 tables (using Multiple LTS) and creating hierarchy on it.
I want to know Is this is the right way to create Level Based Hierarchy????
or is there any alternative way to do,
Please need your suggestions.
Thanks.

Since you got 2 tables follow as below:
Assume DimA and DimB are 2 tables and you want to create Level Base Hierarchy for DimB. In this case other table DimA treat as fact, and create alias for that dim as FactDimA.
Joins in Physical layer
FactDimA->DimA
FactDimA->DimB
BMM: Pull these 3 tables and create level based hierarchy as needed and for other dim just create default hierarchy
Use metrics in FactDimA and descriptive or char type columns from DimA
If you have any issues; I assume you are not following as I said.
Finally mark as correct ;)

OBIEE BI Answers: Wrong Aggregation Measures on top level of hierarchy

Hi to all,
I have following problem. I hope to be clear in my English because it's a bit complicated to explain.
I have following fact table:
Drug Id Ordered Quantity
1 9
2 4
1 3
2 2
and following Drug Table:
Drug Brand Id Brand Description Drug Active Ingredient Id Drug Active Ingredient Description
1 Aulin 1 Nimesulide
2 Asprina 2 Acetilsalicilico
In AWM i've defined a Drug Dimension based on following hierarchy: Drug Active Ingredient (parent) - Drug Brand Description (leaf) mapped as:
Drug Active Ingredient = Drug Active Ingredient Id of my Drug Table (LONG DESCRIPTION Attribute=Drug Active Ingredient Description)
Drug Brand Description = Drug Brand Id of my Drug Table (LONG DESCRIPTION Attribute = Drug Brand Description)
Indeed in my cube I've mapped leaf level Drug Brand Description = Drug Id of my fact table. In AWM Drug Dimension is mapped as Sum Aggregation Operator
If I select on Answers Drug Active Ingredient (parent of my hierarchy) and Ordered Quantity I see following result
Drug Active Ingredient Description Ordered Quantity
Acetilsalicilico 24
Nimesulide 12
indeed of correct values
Drug Active Ingredient Description Ordered Quantity
Acetilsalicilico 12
Nimesulide 6
EXACTLY the double!!!!!!! But if I drill down Drug Active Ingredient Description Acetilsalicilico I see correctly:
Drug Active Ingredient Description Drug Brand Description Ordered Quantity
Acetilsalicilico
- Aspirina 12
Total 12
Wrong Aggregation is only on top level of hierarchy. Aggregation on lower level of hierarchy is correct. Maybe Answers sum also Total Row????? Why?????
I'm frustrated. I beg your help, please!!!!!!!!
Giancarlo

Hi,
in NQSConfig.ini I can't find Cache Section. I post all file. Tell me what I must change. I know your patient is quite at limit!!!!!!! But I'm a new user of OBIEE.
# NQSConfig.INI
# Copyright (c) 1997-2006 Oracle Corporation, All rights reserved
# INI file parser rules are:
# If values are in literals, digits or _, they can be
# given as such. If values contain characters other than
# literals, digits or _, values must be given in quotes.
# Repository Section
# Repositories are defined as logical repository name - file name
# pairs. ODBC drivers use logical repository name defined in this
# section.
# All repositories must reside in OracleBI\server\Repository
# directory, where OracleBI is the directory in which the Oracle BI
# Server software is installed.
[ REPOSITORY ]
#Star     =     samplesales.rpd, DEFAULT;
Star = Step3.rpd, DEFAULT;
# Query Result Cache Section
[ CACHE ]
ENABLE     =     YES;
// A comma separated list of <directory maxSize> pair(s)
// e.g. DATA_STORAGE_PATHS = "d:\OracleBIData\nQSCache" 500 MB;
DATA_STORAGE_PATHS     =     "C:\OracleBIData\cache" 500 MB;
MAX_ROWS_PER_CACHE_ENTRY = 100000; // 0 is unlimited size
MAX_CACHE_ENTRY_SIZE = 1 MB;
MAX_CACHE_ENTRIES = 1000;
POPULATE_AGGREGATE_ROLLUP_HITS = NO;
USE_ADVANCED_HIT_DETECTION = NO;
MAX_SUBEXPR_SEARCH_DEPTH = 7;
// Cluster-aware cache
// GLOBAL_CACHE_STORAGE_PATH = "<directory name>" SIZE;
// MAX_GLOBAL_CACHE_ENTRIES = 1000;
// CACHE_POLL_SECONDS = 300;
// CLUSTER_AWARE_CACHE_LOGGING = NO;
# General Section
# Contains general server default parameters, including localization
# and internationalization, temporary space and memory allocation,
# and other default parameters used to determine how data is returned
# from the server to a client.
[ GENERAL ]
// Localization/Internationalization parameters.
LOCALE     =     "Italian";
SORT_ORDER_LOCALE     =     "Italian";
SORT_TYPE = "binary";
// Case sensitivity should be set to match the remote
// target database.
CASE_SENSITIVE_CHARACTER_COMPARISON = OFF ;
// SQLServer65 sorts nulls first, whereas Oracle sorts
// nulls last. This ini file property should conform to
// that of the remote target database, if there is a
// single remote database. Otherwise, choose the order
// that matches the predominant database (i.e. on the
// basis of data volume, frequency of access, sort
// performance, network bandwidth).
NULL_VALUES_SORT_FIRST = OFF;
DATE_TIME_DISPLAY_FORMAT = "yyyy/mm/dd hh:mi:ss" ;
DATE_DISPLAY_FORMAT = "yyyy/mm/dd" ;
TIME_DISPLAY_FORMAT = "hh:mi:ss" ;
// Temporary space, memory, and resource allocation
// parameters.
// You may use KB, MB for memory size.
WORK_DIRECTORY_PATHS     =     "C:\OracleBIData\tmp";
SORT_MEMORY_SIZE = 4 MB ;
SORT_BUFFER_INCREMENT_SIZE = 256 KB ;
VIRTUAL_TABLE_PAGE_SIZE = 128 KB ;
// Analytics Server will return all month and day names as three
// letter abbreviations (e.g., "Jan", "Feb", "Sat", "Sun").
// To use complete names, set the following values to YES.
USE_LONG_MONTH_NAMES = NO;
USE_LONG_DAY_NAMES = NO;
UPPERCASE_USERNAME_FOR_INITBLOCK = NO ; // default is no
// Aggregate Persistence defaults
// The prefix must be between 1 and 8 characters long
// and should not have any special characters ('_' is allowed).
AGGREGATE_PREFIX = "SA_" ;
# Security Section
# Legal value for DEFAULT_PRIVILEGES are:
# NONE READ
[ SECURITY ]
DEFAULT_PRIVILEGES = READ;
PROJECT_INACCESSIBLE_COLUMN_AS_NULL     =     NO;
MINIMUM_PASSWORD_LENGTH     =     0;
#IGNORE_LDAP_PWD_EXPIRY_WARNING = NO; // default is no.
#SSL=NO;
#SSL_CERTIFICATE_FILE="servercert.pem";
#SSL_PRIVATE_KEY_FILE="serverkey.pem";
#SSL_PK_PASSPHRASE_FILE="serverpwd.txt";
#SSL_PK_PASSPHRASE_PROGRAM="sitepwd.exe";
#SSL_VERIFY_PEER=NO;
#SSL_CA_CERTIFICATE_DIR="CACertDIR";
#SSL_CA_CERTIFICATE_FILE="CACertFile";
#SSL_TRUSTED_PEER_DNS="";
#SSL_CERT_VERIFICATION_DEPTH=9;
#SSL_CIPHER_LIST="";
# There are 3 types of authentication. The default is NQS
# You can select only one of them
#----- 1 -----
#AUTHENTICATION_TYPE = NQS; // optional and default
#----- 2 -----
#AUTHENTICATION_TYPE = DATABASE;
# [ DATABASE ]
# DATABASE = "some_data_base";
#----- 3 -----
#AUTHENTICATION_TYPE = BYPASS_NQS;
# Server Section
[ SERVER ]
SERVER_NAME = Oracle_BI_Server ;
READ_ONLY_MODE = NO;     // default is "NO". That is, repositories can be edited online.
MAX_SESSION_LIMIT = 2000 ;
MAX_REQUEST_PER_SESSION_LIMIT = 500 ;
SERVER_THREAD_RANGE = 40-100;
SERVER_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
DB_GATEWAY_THREAD_RANGE = 40-200;
DB_GATEWAY_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
MAX_EXPANDED_SUBQUERY_PREDICATES = 8192; // default is 8192
MAX_QUERY_PLAN_CACHE_ENTRIES = 1024; // default is 1024
MAX_DRILLDOWN_INFO_CACHE_ENTRIES = 1024; // default is 1024
MAX_DRILLDOWN_QUERY_CACHE_ENTRIES = 1024; // default is 1024
INIT_BLOCK_CACHE_ENTRIES = 20; // default is 20
CLIENT_MGMT_THREADS_MAX = 5; // default is 5
# The port number specified with RPC_SERVICE_OR_PORT will NOT be considered if
# a port number is specified in SERVER_HOSTNAME_OR_IP_ADDRESSES.
RPC_SERVICE_OR_PORT = 9703; // default is 9703
# If port is not specified with a host name or IP in the following option, the port
# number specified at RPC_SERVICE_OR_PORT will be considered.
# When port number is specified, it will override the one specified with
# RPC_SERVICE_OR_PORT.
SERVER_HOSTNAME_OR_IP_ADDRESSES = "ALLNICS"; # Example: "hostname" or "hostname":port
# or "IP1","IP2":port or
# "hostname":port,"IP":port2.
# Note: When this option is active,
# CLUSTER_PARTICIPANT should be set to NO.
ENABLE_DB_HINTS = YES; // default is yes
PREVENT_DIVIDE_BY_ZERO = YES;
CLUSTER_PARTICIPANT = NO; # If this is set to "YES", comment out
# SERVER_HOSTNAME_OR_IP_ADDRESSES. No specific NIC support
# for the cluster participant yet.
// Following required if CLUSTER_PARTICIPANT = YES
#REPOSITORY_PUBLISHING_DIRECTORY = "<dirname>";
#REQUIRE_PUBLISHING_DIRECTORY = YES; // Don't join cluster if directory not accessible
DISCONNECTED = NO;
AUTOMATIC_RESTART = YES;
# Dynamic Library Section
# The dynamic libraries specified in this section
# are categorized by the CLI they support.
[ DB_DYNAMIC_LIBRARY ]
ODBC200 = nqsdbgatewayodbc;
ODBC350 = nqsdbgatewayodbc35;
OCI7 = nqsdbgatewayoci7;
OCI8 = nqsdbgatewayoci8;
OCI8i = nqsdbgatewayoci8i;
OCI10g = nqsdbgatewayoci10g;
DB2CLI = nqsdbgatewaydb2cli;
DB2CLI35 = nqsdbgatewaydb2cli35;
NQSXML = nqsdbgatewayxml;
XMLA = nqsdbgatewayxmla;
ESSBASE = nqsdbgatewayessbasecapi;
# User Log Section
# The user log NQQuery.log is kept in the server\log directory. It logs
# activity about queries when enabled for a user. Entries can be
# viewed using a text editor or the nQLogViewer executable.
[ USER_LOG ]
USER_LOG_FILE_SIZE = 10 MB; // default size
CODE_PAGE = "UTF8"; // ANSI, UTF8, 1252, etc.
# Usage Tracking Section
# Collect usage statistics on each logical query submitted to the
# server.
[ USAGE_TRACKING ]
ENABLE = NO;
//==============================================================================
// Parameters used for writing data to a flat file (i.e. DIRECT_INSERT = NO).
STORAGE_DIRECTORY = "<full directory path>";
CHECKPOINT_INTERVAL_MINUTES = 5;
FILE_ROLLOVER_INTERVAL_MINUTES = 30;
CODE_PAGE = "ANSI"; // ANSI, UTF8, 1252, etc.
//==============================================================================
DIRECT_INSERT = YES;
//==============================================================================
// Parameters used for inserting data into a table (i.e. DIRECT_INSERT = YES).
PHYSICAL_TABLE_NAME = "<Database>"."<Catalog>"."<Schema>"."<Table>" ; // Or "<Database>"."<Schema>"."<Table>" ;
CONNECTION_POOL = "<Database>"."<Connection Pool>" ;
BUFFER_SIZE = 10 MB ;
BUFFER_TIME_LIMIT_SECONDS = 5 ;
NUM_INSERT_THREADS = 5 ;
MAX_INSERTS_PER_TRANSACTION = 1 ;
//==============================================================================
# Query Optimization Flags
[ OPTIMIZATION_FLAGS ]
STRONG_DATETIME_TYPE_CHECKING = ON ;
# CubeViews Section
[ CUBE_VIEWS ]
DISTINCT_COUNT_SUPPORTED = NO ;
STATISTICAL_FUNCTIONS_SUPPORTED = NO ;
USE_SCHEMA_NAME = YES ;
USE_SCHEMA_NAME_FROM_RPD = YES ;
DEFAULT_SCHEMA_NAME = "ORACLE";
CUBE_VIEWS_SCHEMA_NAME = "ORACLE";
LOG_FAILURES = YES ;
LOG_SUCCESS = NO ;
LOG_FILE_NAME     =     "C:\OracleBI\server\Log\CubeViews.Log";
# MDX Member Name Cache Section
# Cache subsystem for mapping between unique name and caption of
# members for all SAP/BW cubes in the repository.
[ MDX_MEMBER_CACHE ]
// The entry to indicate if the feature is enabled or not, by default it is NO since this only applies to SAP/BW cubes
ENABLE = NO ;
// The path to the location where cache will be persisted, only applied to a single location,
// the number at the end indicates the capacity of the storage. When the feature is enabled,
// administrator needs to replace the "<full directory path>" with a valid path,
// e.g. DATA_STORAGE_PATH = "C:\OracleBI\server\Data\Temp\Cache" 500 MB ;
DATA_STORAGE_PATH     =     "C:\OracleBIData\cache" 500 MB;
// Maximum disk space allowed for each user;
MAX_SIZE_PER_USER = 100 MB ;
// Maximum number of members in a level will be able to be persisted to disk
MAX_MEMBER_PER_LEVEL = 1000 ;
// Maximum size for each individual cache entry size
MAX_CACHE_SIZE = 100 MB ;
# Oracle Dimension Export Section
[ ORA_DIM_EXPORT ]
USE_SCHEMA_NAME_FROM_RPD = YES ; # NO
DEFAULT_SCHEMA_NAME = "ORACLE";
ORA_DIM_SCHEMA_NAME = "ORACLE";
LOGGING = ON ; # OFF, DEBUG
LOG_FILE_NAME     =     "C:\OracleBI\server\Log\OraDimExp.Log";

CL_SALV_HIERSEQ_TABLE - Multiple level heirachial sequential list

Class CL_SALV_HIERSEQ_TABLE - Can this class be used for multiple level heirarchial sequential list ?
It works perfect for 2 level heirarchial list u2013 Thanks to Rich Heilman. Say for Eg, SCARR and SFLIGHT.
My requirement has more levels. I looked into all the methods of the class, but none of them seems to help to append more levels.
Here is my requirement.
Selection screen had date range, partner functions etc ..
-->Select all Inquiries for given date range or (TABLE u2013 VBAK) given sold to party/ship to party etcu2026
-->Get all statuses (system status /user status etc (TABLE u2013 JCDS and TJ30T ).
-->Select all Quotations for given inquiry, if any
-->Select all Orders for the selected quotations, if any
-->Select all deliveries for selected orders, if any and read status, whether shipped or not (VBFA/LIKP/ VBUK )
And list these in a multilevel heirarchial mode
Inquiry1/created by/created on/ sold to party/ Application engineer/inside sales Rep
     Status1 / description/ active / changed by / date
     Status2/ description/ active / changed by / date
     u2026..
     u2026..
     Status 5u2026..
          Quotation1 / Created on /created by/quantityu2026
               Order1/created on/created by/
                    Delivery1 /created on / created by/ not shipped
                    Delivery2/ created on / created by / partially shipped
               Order2/created on/created by
Inquiry2/created by/created on/ sold to party/ Application engineer/inside sales Rep
     Status1 / description/ active / changed by / date
     Status2/ description/ active / changed by / date
     u2026..
     u2026..
     Status 5u2026..
          Quotation1 / Created on /created by/quantityu2026
I need atleast 3 internal tables, 1 for Inquiry, another for status data, another for Quotation/order/delivery.
Anyone has any clue, how to achieve this ? cl_salv_tree also doesnu2019t seems to helpu2026
As per my understanding, we could pass only 1 single structure to a tree output.
For eg, all lines of the tree output should be of the same structure. (please correct me if I am wrong )..
But In my case, the fields on each level are different, and I need to pass different structures to the tree.
Please let me know, if anyone have a clue..
Thanks much

Sujamol (or anyone),
did you ever manage to do this? I would like to do the same.
Report SALV_DEMO_HIERSEQ_COLUMN does it for two levels. What about 3, 4.....?
Thanks.

Multiple Levels in Hierarchy using MDX in SSAS

Similar Messages

Maybe you are looking for