cancel
Showing results for 
Search instead for 
Did you mean: 

Query in HIER Info Object

former_member197527
Active Participant
0 Kudos

Hi,

We have hierarchy as attached:

For each node value, The last value is Customer (eg 02564), and the first value being distribution channel (00/02) and DR01/DR02 is salesorg.

But, the Hierarchy data is in KNVH and hence using zcustsales as Hierarchy Info object which is a template of 0cust_sales, to load in BW.

For zcustsales, salesorg and distribution channel are compounding attr.

  • Because the end values are on customer, should I use 0customer as the Hierarchy object? But no applicable hierarchy for it. Is it fine if I use zcustsales in reports directly?
  • Haven't added any external char to the zcustsales in hierarchies. Is it fine because there are compounding attr? I studied and got to know that if I add distribution channel and salesorg are added there, they come as folders (not posted). What does this exactly mean?
  • Because I need to use node level restriction, while creating analysis object, is it fine if we use ONLY 0TCTAUTHH and zcustsales, or should we also add the other 3 special chars? Any specific standard roles to be added in this when compared to value authorizations?

Please help me with these 3 queries.

Tried to search forum but not one document covers these in detail, most of them are value ones

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member186399
Active Contributor
0 Kudos

Dear Aditya

1) & 2)      If your reporting requirement is to bring the customer as per the Division / sales org then you have to go with Custsales infoobject and the hierarchy has to be on custsales.

Now the issue when you use a compounded info object is that you can only evaluate the customer in conjunction with a division and sales org.

3) In the analysis object you need to only relevant authorisation object. if the division and sales org are  authorisation relevant you will have to add them also.

Regards

Gajesh

former_member197527
Active Participant
0 Kudos

Hi Gajesh,

One confirmation from a process aspect. Say we have 2 different hierarchies for 2 different plants.

Both of these are in KNVH table, which is customer hierarchy

Please confirm the below?

  • Loaded data into a single infoobject YCUSTSALES for both the hierarchies. Salesorg and Division are the compounding attr of YCUSTSALES. Can I add these both in same infoobject or different ones?
  • Each Node in BW displayed as Eg: 00/DR01/02580 - No Folder Structure as such, as haven't added any external CHAR to YCUSTSALES. Is it fine?
  • For all the reports, restrict this by the authorization variable and nothing else to ensure security implementation
former_member186399
Active Contributor
0 Kudos

Dear Aditya

Please check whether Division and sales org are ticked as authorisation relevant infoobjects.  If so then you have to add both in the Authorisation Analysis.External characters may not be required.

Regards

Gajesh

former_member197527
Active Participant
0 Kudos

Dear Gajesh,

Salesorg is already authorization relevant as its being used as value authorization for other plants.

For these 2 new plants, we need this on hierarchy based which are in KNVH table.

So, used ZCUSTSAL, which is a template of 0cust_sales.

This has 3 compounding ones salesorg, division and dist channel. Should I mark the division and channel as relevant as well?

Currently am not sure of the basis of these compounding attr to be authorization relevant.

Should these be also authorization relevant?

former_member186399
Active Contributor
0 Kudos

Dear Aditya,

Please check functionaly whether the division & dist channel needs to be authorisation relevant.

If the user can see any division data for a sale order then Division neednot be a authorisation relevant field.

Regards

Gajesh

former_member197527
Active Participant
0 Kudos

Please update on this, thanks in advance