Partner function should be mandatory for a perticular sales org

[satya_devaraju]

We have a requirement to make Sales representative assignment to the sold-to-party mandatory , during order creation ( for a particular sale org) . We have to generate incompletion log for all the orders where this partner function is missing in the header data . Please throw some light on how to do this.

[Former Member · Accepted solution]

Dear Satya,

First of all, create partner function and partner type (Sales Representative ) in T. Code: VOPA.

Click Tab: Partner Procedure,

Insert this partner function in your Partner Determination Procedure. if you want mandatory then check this partner funtion as Mandatory. After that assign that partner determination to your Account group (say, 0001 - Sold-to-Party)

Alternatively,

Path: SPRO --> IMG --> Sales and Distribution --> Basic Functions --> Partner Determination

Check whether the partner function is checked mandatory against "Sales Representative" which is assigned to the procedure.

Best Regards,

Amit

[Lakshmipathi]

Dear Satya

As rightly said by Mr.Murali, setting the partner function Sales Representative as mandatory sales organization wise may not be possible in standard.

If you go to IMG SD --> Basic Functions --> Partner Determination --> Set Up Partner Determination, you can see that you can configure the partner functions for

- Customer Master

- Sales Order Header

- Sales Order Item

- Delivery

- Shipment

- Billing Header

- Billing Item

If you are so particular to achieve your requirement, you can go for Partner Determination user exits like EXIT_SAPLV09A_003 or EXIT_SAPLV09A_004

thanks

G. Lakshmipathi

[Former Member]

You can use the user exit USEREXIT_SET_STATUS_VBUK in the program RV45PFZA where you can set a custom Incompletion status at the header level based on your specific requirement. Workarea FXVBUV can be used for the same.

[satya_devaraju]

Hi AriBis,

Thanks for the reply . In which workarea in exit USEREXIT_SET_STATUS_VBUK in the program RV45PFZA, can I get sales organization?

regards,

satya

[former_member204513]

Dear Satya,

I don't think it is possible sales organisation wise

But you can have this requirement sales document type wise or item category wise or Customer account group wise through maintaining the check mark for sales employee partner function in the Mandatory check box at partner functions in procedure step in the partner dtermination.

Because partner functions maintained in the prtner procedure that procedure will assigned at these levels.

Customer Master

Sales Document Header

Sales Document Item

Delivery

Shipment

Billing Header

Billing Item

You can do like this

You define different customer account group for that sales organisation

Define new Partner determination procedure through copying existing standard one

You activate mandatory check for sales employee partner function in that new prtner determination procedure.

You assign this new procedure to the account group which is sales organisation specific.

Now you create customer master data with that account group in that specific sales org now system will give the error message if don't maintain the sales employee in that customer master data>sales area data>partner functions tab.

Before going to create customer master you create Sales employee master throuh VPE1 transaction.

Still not satisfied

Try with these User Exits with help of ABAPer

User Exits for Partner Determination

Partner determination contains the following user exits for your use:

EXIT_SAPLV09A_001

You can use this user exit to control whether an address that was entered manually and has already been used in other documents (referenced), should be referenced again if it changes or whether a new address shold be created (duplicated).

EXIT_SAPLV09A_002

Call up this user exit if a customer has not been maintained in the current sales area.

EXIT_SAPLV09A_003

Use this user exit to control the origin of partners in the partner determination procedure (origin X, Y or Z). If X, Y, or Z has been entered in the Origin field, this user exit is automatically called up during partner determination.

EXIT_SAPLV09A_004

Use this user exit to integrate your own check in a program, that runs before the partner is saved in the document.

For more detailed information, see the program documentation for each ofthe user exits.

I hope this will help you,

Regards,

Murali.

Edited by: Murali Mohan.Tallapaneni on Dec 15, 2008 10:47 AM

Edited by: Murali Mohan.Tallapaneni on Dec 15, 2008 10:50 AM