Hi Martin,
Thanks for these inputs. There are 2 hierarchies. And am loading them to same infoobject which is a template of 0cust_sales.
ROOT - Node 1
- 00/DR01/02564 - Node 2 (Level 1)
- 00/DR01/02566 - Node 3 (Level 2)
- 00/DR02/02570 - Node 4 (Level 3)
- 00/DR02/02572
- 00/DR02/02580 - Node 5 (Level 4)
- 00/FG01/02568 - Node 6 (Level 2)
- 00/FG02/02574 - Node 7 (Level 3)
-----------------------------------------------------------------
There are further more such groups at corresponding levels.
Say the users need access only after the Level 3. Will it be one object with type of auth "1" and selected node 4? Can there be more node selections in single object?
For each level, is it a new object of auth or how? Please help me understand
Client needs such restriction in queries. Is it that we drag and drop the custom info object which has both hierarchies loaded into the query and nothing else?