Difference between Reference division for customers and Reference division for conditions

[former_member193505]

Hi All,

I am looking for the difference between two fields in Reference Division table ( TVKOS) i.e. Ref division for Customer ( SPAKU) and Ref div for Condition ( SPAKO).

From F1 help, it's understood that Specifies a division where we can define conditions and share them with other divisions. Still anyone give more clarity on difference part that will be helpful. Thanks.

[pavani_mantravadi]

Hi Arindam,

The common distribution channel & division reduces the master date creation.

In situations where your sales organization contains more than one distribution channel and more than one division,
this customization setting is really helpful in reducing the master data maintenance efforts and avoiding master data
duplication within a sales organization. Using a common distribution channel customization, you can define the master
data for one distribution channel, and all other distribution channels that belong to that sales organization can use the
same master data. You don’t have to create the master data separately for all the distribution channels.

For example you have a material A having division 01 produce in plant A and you have material B having division 02 produce in plant B.
You can create a division 03 having common division with 01 and 02.

With this you can create a customer having sales area with this common division 03 instead of two different master data for these two divisions.

Always remember to define this setting irrespective of whether your business requirement setup needs a common distribution channel and common division.
You won’t be able to create master data using the sales area you just defined if this customization setting is missing.

Regards,

Pavani.

[pjcools]

Hi

There is information maintained in help.sap.com but the concept is around saving the master data maintenance effort (for customer maintenance and condition records) by combining divisions so they are grouped by a single value. For e.g. the sales area could be 1000 (Sales Org) 10 (Dist Channel) and there could be multiple divisions 10, 20, 30, 40, 50 etc. But if the customer data does not differ by division (even though you want to record individual product categories) then you would configure that these records would be maintained under the single Division - let's say the 10 Division. That way, the customer is maintained once for this sales area instead of 5 times.

The same applies to pricing records although it may be useful to define pricing with the difference divisions and so you may not want to combine the divisions for the pricing condition record maintenance. However, you could again maintain pricing records under a single Division value.

Best to try these things out in a sandpit to work out the functionality.

Thanks

Phil Cooley