Accounts group assignment in partner determination

[Former Member]

Hi SAP experts...

In our scenario our clients customer has different partners like sold to party, ship to party, bill to parpty and payer. so as to configure in partner determination procedure shall we need to go for different account groups for each partner??. What happen if we choose one account group?. Account group has number range assignment, if we go for different account groups then diff.number ranges will be there for each partner of the customer...right...

Can any one clarify and tell the procedure if we go for different account groups.

Points assured for helpful answer.

Sunanda.P

[Former Member · Accepted solution]

Sunanda,

In VOPA transaction code, you create a partner determination procedure. Here you specify the partner functions to be used & also mark the mandatory partner functions.

This partner determination procedure is then assigned to the account group. Basically the standard account group for "sold to party - 0001" has all partner functions "SP", "SH", "BP" & "PY". Your requirement demands separate partne functions for SP, SH, BP & PY.

So you will have to create 4 different partner determination procedures in VOPA.

ZSOL - SP

ZSHI - SH

ZBIL - BP

ZPAY - PY

Create similar acount groups ZSOL, ZSHI, ZBIL & ZPAY in transaction code OBD2 & do the appropriate field selection for them.

Now assign the partner determination procedures to the account groups in VOPA.

ZSOL = ZSOL

ZSHI = ZSHI

ZBIL = ZBIL

ZPAY = ZPAY

Also assign the individual partner functions as mentioned below:

ZSOL = SP, SH, BP, PY

ZSHI = SH

ZBIL = BP

ZPAY = PY

For ZSOL we assigned all partner functions because, when you will create a sold to party customer, you also have to specify who will the ship to party, bill to party & payer customers for the sold to party.

Now if you want you can assign the same number range to all account groups (assign a single person to create the customer master. So whenever a new customer is created, the partners will be created in line which will be very helpful)

Assume the number range is "0000010000 to 0000099999"

Create SP for 10000

Create SH for 10001

Create BP for 10002

Create PY for 10003

Go to XD02 - select the customer 10000 - go to sales area data - partner functions.

Here in the "PF" column enter SH & in number enter 10001

Here in the "PF" column enter BP & in number enter 10002

Here in the "PF" column enter PY & in number enter 10003

So you have assigned the relevant partners to the sold to party.

Hope this clarifies your doubt.

With best regards,

Allabaqsh G. Patil.

[Former Member · Accepted solution]

Hi Allab.patil.,

Thanks a lot for your decent explanation. Your way of explain is also very impressive and cleared my doubts.

Awarded points.

Sunanda.P

[Former Member]

Hi Sunanda,

Usually we have the std partners called SP,SH,BP,PY. We know that one Sold to party can have any no .of ship to parties,Bill to parties,Payers.We can do this through Partner determination procedure in std sap. For each and every partner we will define seperate acc group and maintain different no.range.This account group decides

1.Which fields and screens are to be displayed during the creation of CMR.

2.Wheather we can or we must make an entry in those fields or not.

3.How customer master numbers are to be generated either by the system automatically or by the user.

4.Which partner functions are valid for that particular customer master.

So Basing on our requirement we will go for different acccount group.

We can use one account group to any no.of partner functions.If we do so same no ranges will be applied to the remaining partner functions also.

If we want to maintain different no ranges for different partner functions we need to maintain different account groups respectively.

Steps need to follow in partner determination

1.Define account group (FI people can do this)

2.Define partner functions

3.Assing partner functions to respective account groups

4.Define partner determination procedure

5.Place partner functions in the procedure

6.Assign partner determination procedure to the account group.

Basing on these settings partner are to be determined in the sold to parties master data.

But we have to assign partner determination procedure to the account group of sold to party,If we maintain different account groups for different partner functions.

Award me points if this answer is useful to u.

With Regards,

Revan.

Edited by: REVAN on Aug 8, 2008 8:53 AM

[Former Member]

Hi Revan...,

Thank u very much for your elobarate and useful answer. It would be better if you differentiate the procedure in img screen partner determination for one acc.group all partner functions assignment and for diff. account groups diff.partner functions. I am getting little confusion how to differentiate these two procedures. In case of diff.acc.groups diff.partner functions shall we create master data for bill to party, ship to party, and payer also? Please clarify this.

Thanks in advance.

Sunanda.P

[Former Member]

Hello,

If you want to create different partners like Ship-to, Bill-to, Payer seperately, you should have different account groups for the same and number ranges.

Prase

[former_member184555]

Hi

The Sold To Party (SP) account group will have all the partner functions like SH,BP,PY also. But if you want to maintain exclusive SH master records - that will not have all the partner functions.

When creating the order the SP may ask to despatch different line items to different SH parties. In such cases those SH parties should have their own Customer master records (as maintained for the SP) and those SH customer numbers should be assigned in the customer master record of this SP. To create a customer master record of SH you need to use the Account group of SH and this will have its own number range.

Thanks,

Ravi

[Former Member]

Hi,

Help take help from:

http://help.sap.com/erp2005_ehp_03/helpdata/EN/dd/55f534545a11d1a7020000e829fd11/frameset.htm

http://help.sap.com/erp2005_ehp_03/helpdata/EN/dd/55f4ba545a11d1a7020000e829fd11/content.htm

Best regards,

Amit