Only valid partner allowed in VA02

[Former Member]

Hi friends,

In the VA02 we have the option of changing partner functions. E.g. in Customer master SP is 101, SH is 101, BP is 101 and PY is also 101. No other SH is maintained.

In Sales Order, customer 101 will be coming by default for all the partner functions. Now SH is changed from 101 to 102, system will allow (because it is std functionality) even if 102 is not maintained in the customer master of 101.

But we want that system should allow only those partners which are maintained in the Customer Master of Sold-to party. How can we achieve it? Pl suggests.

Thanks.

[Lakshmipathi]

In VOPA itself, there would be one field "Not Modifiable".  You can check this field against SH so that, I think, in sale order, it will be greyed out.

G. Lakshmipathi

[former_member182378]

R Sgr,

Based on my tests, I think functionality "Not Modifiable" (as suggested by G. Lakshmipathi) could satisfy this business requirement.

Added: If you have setup partner function (SH) in the partner procedure assigned to the item category, then for that partner function also (in the partner procedure), activate Not Modifiable.

Message was edited by: T W - added comment in blue color font

[former_member184080]

Hi TW,

I have not tested and i am not able to recollect how system behaves. But, trying to through some light here, when we check not modifiable at partner procedure may have another problem. What If the customer has more than one SH and while creating SO if user wants to select other than the defaulted one. In more practical scenario, the user has selected say:SH -2 instead of selecting SH-5.Now, after entering few line items user realised and wants to change from SH-2 to SH-3. In this case, system will not allow him.. Correct ?

Regards, Sai Krishna.

[former_member182378]

Sai,

Thank you for this "refreshing" post!

Presenting / Thinking about (in advance) practical issues that the users could face, while doing their daily work, adds a lot of value (benefit to the client).

Yes, I have tested G Lakshmipathi's (both) suggestions (Source, Not Modifiable functionalities).

Your example is correct!

Once a customer is entered as SH, (with Non modifiable), it can not be changed.

The OP would have to "analyze / compare" whether to go with a standard solution or to for a solution which involves coding (my previous suggestion).

Both suggestions have their own pros and cons!

For your other question / point -

What If the customer has more than one SH and while creating SO if user wants to select other than the defaulted one. 

If there are multiple options of a partner function (e.g. many SH assigned to a SP), the system shall give a popup window, and the user can select the one he/she wishes (to populate in the sales order).

Modifiable / Not Modifiable does not impact the above step (done by the system).

In other words, with Not Modifiable, the user can select the default or any other customer. No problem!

[Former Member]

Let me add a bit more info about this topic:  see the answer from Indranil Ain in:

http://scn.sap.com/message/9600287#9600287

If the standard does not work (and it seems so): you can use table of origin with 'X', 'Y' or 'Z' and control it your way via user exit EXIT_SAPLV09A_003.

[Lakshmipathi]

Try with the following:-

Execute VOPA, select Sales Document Header and click on Partner procedures.  Again select the required procedure and maintain SP under the tab "Source" against the function SH. 

G. Lakshmipathi

[former_member182378]

G Lakshmipathi,

In the partner pricing procedure assigned to the sales document type, if one tries to enter value "SP" in field Source, the field becomes blank.

In other words, we can not maintain SP in field Source.

Probably this is because blank means SP (as source).

Even if source is blank (default or SP) still other values (any value satisfying the partner function, the sales area) can be entered in the Sales order.

In other words, source gives the initial option (choice) but it does not restrict the user, the choice of customer number in the sales order.

It would be interesting to know your comments and test results.

Thank you!

[Lakshmipathi]

 if one tries to enter value "SP" in field Source, the field becomes blank.

Thanks for sharing the information.  To be honest, while giving suggestion, just with some rough assumption, I gave that and in fact, I had not even checked SAP and never come across such a requirement.  Will have to explore some alternate way.

G. Lakshmipathi

[former_member182378]

R Sgr,

I think that this requirement can not be met with standard SAP; you would have to go for enhancement (i.e. coding).

My understanding of the requirement is as follows -

For a particular Sales Area,

there is a CMR 101.

In XD03, Sales Area Data, Tab Partner Functions: SP = 101, SH = 101, 299 BP = 101, PY = 101

In VA01 /2, if the SP = 101, then the SH can only be either 101 or 299.

ABAPer has to incorporate the code in program MV45AFZZ, userexit USEREXIT_SAVE_DOCUMENT_PREPARE

The ABAPer would have to write the code based on the below specifications -

1. Fetch VBPA-KUNNR, input VBPA-VBELN, VBPA = SH (for Ship To)

(if SH customer needed to be fetched for the line item level, then give VBPA-POSNR too)

2. Fetch KNVP-KUNN2, input KNVP-KUNNR (Sold to party), KNVP-VKORG, KNVP-VTWEG, KNVP-SPART, KNVP-PARVW = SH

If SH customers got from step 1 do not exist in the entries fetched in step 2, then do not save the sales order and populate an error message.

[Former Member]

HI,

Please try with following customizing.

when you assign the "Partner Functions in Procedure" for Sales order like  TA and SH /SP/PY/BP assignment there is a column called " Origin"  where you can maintain from where  you need to access the partner function. If you choose "C" then it will pick only form customer master partner function.

Hope it will help you .

Regards

Pitabash

[Former Member]

Hi Pitabash

Are you sure Origin 'C' will work for Partner function SH?

[Former Member]

Hi Pronojit,

I have never checked  this one. I hope it ll worked. But it won't work . I have just checked.

Sorry for inconvenience..

[Former Member]

Do you want the Ship-to to be same as Sold-to?

If thats what you want. go to IMG - S&D-Basic Function-Partner determination-Set Up Partner Determination for Sales Document Header. In that screen -- in Dialog Structure - click on PDP and create a separate PDP and assign it to the SO. (This was you can regulate which documents u want to control).  Then click on Partner Function and select SH and copy and rename (as eg. S1) and save. Then assign this S1 new Ship to party to new PDP in Partner Functions in Procedures and select Non-modifiable and Mandatory checkboxes as required.

Check and revert.

[former_member184080]

Hi Pronojit,

Have you ever suggested or implemented this in any of your projects. As far as i know its not best practice to rename the original parner functions.

What if this requirement comes after some years of Go-Live?

Regards, Sai Krishna.

[Former Member]

Hi Sai

That is the reason why I suggested creating a separate PDP and copying SH and renaming and then attaching it to custom PDP instead of TA so it may be used for an exclusive document type.