cancel
Showing results for 
Search instead for 
Did you mean: 

Customer hierarchy

Former Member
0 Kudos

I am learning SAP SD.

I am facing problem in cutomer hierarchy configuration for pricing.

I have referred the answer posted on https://www.sdn.sap.com/irj/scn/forums

(i have pated below this email)

But still i need your help.

I stuck at step 2 : IMG-> SD-> Master data-> Business Partners-> Customers-> Customer Hierarchy-> Set Partner Determination for Hierarchy Categories

Now I am unable to understand how to configure further.

This may be very basic question but I am unable to understand since last two days.

Thank you very much in advance.

Regards,

Ashish

-


Customer hierarchy configuration

Following are the steps followed in exact config of customer hierarchy:

T-code: OVH1

1) DEFINE HIERARCHY TYPES:

IMG-SALES AND DISTRIBUTION-MASTER DATA-BUSINESS PARTNERSCUSTOMERS-CUSTOMER HIERARCHY---DEFINE HIERARCHY TYPES.

T-code: VOPA

2) Set partner determination for hierarchy categories:

IMG-SALES AND DISTRIBUTION-MASTER DATA--BUSINESS PARTNERS-CUSTOMERS


CUSTOMER HIERARCHY-SET UP PARTNER DETERMINATION FOR HIERARCHY CATEGORIES

T-code: OVH2

3) Assign Account groups:

IMG--SALES AND DISTRIBUTIONMASTER DATABUSINESS PARTNERSCUSTOMERSCUSTOMER HIERARCHY---ASSIGN ACCOUNT GROUPS

We assign the possible higher-level account groups to the account groups permitted for each customer hierarchy type. Therefore, both the valid account groups for each hierarchy type are defined and the higher-level account groups of the valid account groups

.

T-code: OVH3

4) Assign sales areas:

IMG--SALES AND DISTRIBUTIONMASTER DATA-BUSINESS PARTNERSCUSTOMERSCUSTOMER HIERARCHY-ASSIGN SALE AREAS

We assign sales areas to each other which allow you to determine whether a sales area uses its own customer hierarchies or shares one with another sales area.

T-code: OVH4

5) Assign hierarchy type for pricing by sales document type:

IMG--SALES AND DISTRIBUTIONMASTER DATABUSINESS PARTNERSCUSTOMERS-CUSTOMER HIERARCHY----ASSIGN SALE AREAS

Edited by: Ashish Desai on Mar 16, 2009 12:06 AM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Ashish Desai,

You can check the below points :

1st Need to define Define Hierarchy Type say standard A and assign Partner function 1A ( this as be be defined in partner fucntions)

2nd as said need to define partner functions as 1A, 1B,1C and 1D.

when u frist define 1A give partner type KU, error gruoup 07, higher level as 1B, cust hierarchy type A.

Then defien 1B give partner type KU, error gruoup 07, higher level as 1C, cust hierarchy type A.

Then defien 1C give partner type KU, error gruoup 07, higher level as 1D, cust hierarchy type A.

Then defien 1D give partner type KU, error gruoup 07, cust hierarchy type A.

3rd assign the account group and higher level accout group to customer hierarchy

customer hierarchy type A, account group 0001 and higher level account group 0001.

4th then assign the sales area you are using to customer hierarchy type.

customer hierarchy type is A, and your sales are, same sales area as hight level too.

5th assign the customer hierarchy type to the sales order.

You can change the standard and use Z for partner funtions and for customer hierarchy type

Ensure that the partner functions are assigned to sales document partner procedure too.

Regards

Former Member
0 Kudos

Dear Krishna,

Thank you very much for your reply.

I am using this hierarchy for pricing therefore I have to use the below path (pl correct me if i am wrong)

Step 2: As mentioned, I have to follow the path

IMG-> SD-> Master data-> Business Partners-> Customers-> Customer Hierarchy-> Set Partner Determination For Hierarchy Categories-> Set up Partner determination for sales document header-> Partner function

Partner fun. 1A + Partnertype KU + error gr. 7 + hiegher level partner fun. 1B + cust. hierarchy type A

1B + KU + 7 + 1C + A

1C + KU + 7 + 1D + A

1D + KU + 7 + A

1) How many hierarchy levels I should create for below scenarioes -

  • Customer 1:*

Head office is in Germany + 2 subsidiaries (1 in USA & 1 in Singapore).

All three offices are buying independently and eligile for the pricing agreement done with head office Germany.

  • Customer 2*

Head office is in France + 3 subsidiaries like 1 in China, 1 in Canada, 1 in Mexico (Mexico is again subsidiary company of Canada).

All four offices are buying independently and eligile for the pricing agreement done with head office Fracne.

2) Partner functon key : Is there any logic for defining the alpha numeric number 1A, 1B, 1C, 1D?

Thank you very very much for your help.

Regards,

Ashish

Edited by: Ashish Desai on Mar 16, 2009 12:54 PM

Edited by: Ashish Desai on Mar 16, 2009 1:01 PM

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Ashish,

All the customizing is in SD/Master Data/Bussiness Partner/Customers/Customers hierarchy

1) Define hierarchy type: just put and ID and a name to the new hierarchy.

2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this informacition, in the order, you obtain the bussiness partner for each partner function.

3) Assign acount groups: you indicate which accounts groups are allowed for being part or your hierarchy.

4) Assign sales areas: symple you indicate wich sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).

5) Assigning hierarchy type for pricing: you indicate which classes of documentos uses hierarchy in pricing determination.

It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.

Customer hierarchy setup, firstly decide the hierarchy type to be used.

The standard is type A.

You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?

Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.

You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.

You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.

All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy

You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.

Thanks,

Swamy H P