Customer Relation

[former_member301027]

Dear Gurus,

At my client side we have five customers, basically customer companies are same, but due to diffrent location of customer we created multiple customer, payer of all the customer is same.

Is there any standard function so that i can identify each customer, to whom it basically belong, or can find the tree of all five customer.

Looking forward for the gurus feedback.

Regards,

[former_member301027]

Nearest solution, will assign marks once configure and match the result with requirement and answer giving by my gurus.

Regards,

[Former Member]

Hi,

You can use the customer heirarchy concept.

You have standard reports also for the same.

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.

Configuration Steps:

Follow the steps for customer hierarchy:

spro -> s&d -> master data -> business partner -> customer -> customer hierarchy.

(1) define hierarchy types (OVH1) (optional) (you can use the standard type A)

(2) set up partner determination for cust hierarchy

a) Partner functions

1a ku 1b A (see the step 1)

1b ku 1c A

1c ku 1d A

1d ku -- A

b) A/C group functions assignment

sold to a/c gr 1A, 1b, 1c, 1d

bill to -do- 1A

ship to -do- 1A

payer -do- 1A

3) Assign a/c groups OVH2

standard a/c gr your a/c gr( as example)

0012 sold to

sold to ship to

ship to bill to

(do it as per your requirement)

4) Assign sales areas. OVH3

New entries

higher level to lower level

(what ever the discounts you maintain for the higher level it will be passed to lower level)

5) Assign hierarchy types for pricing by sales document types OVH4

6) Create nodes V-12 (condition record)

use the standard account group 0012(see the 3rd step)

7) Condition record for maintaining customers in hierarchy levels.

VDH1N. use the standard type A and use the node number that you have created in above step.

click on create

Heir level customer node number

lower level customer XXXXXXXXXX ( from the sales area and a/c groups used above steps for assignments)

**First time using the node in the higher level is must

see the chart 0012-----

-

---

XXXXXXX

-

---

YYYYYYY

-

---

ZZZZZZZ

-

---

kkkkkkk

All the X Y and Z customers are assigned to node directly but customer k is assigned to cust Z meaning : the discount given to node 0012 will be passed on to all But cust k will only get the discount that assigned to cust z.

• Maintain hierarchy discount types HI01 or HI02 in pricing procedure.

• Maintain discount on the above condition types in VK11 by node or customer

Regards,

Saju.S