cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot delete item-level partner function on sales order. VPD005

Former Member
0 Kudos

Hello Experts -

In ECC 5.0. In the sales order, a user inadvertantly changed the partner at item level instead of header level. The item-level indicator was activated and cannot be deactivated. So to fix we tried activating at item-level for all items with identical partner data (identical to header partner data, also). Didn't work. Then we changed configuration to make the item-level partner not mandatory, but despite this, it will not allow itself to be deleted: Message no. VPD005 - You cannot delete partner function Carrier (mandatory function in Standard item-procedN). Order has no subsequent docs. All items must be on a singel delivery - cannot have split delivery. Searched SAP OSS notes w/out luck.

Please advise! Thanks,

Anke

Edited by: Anke Snow on Jun 29, 2010 8:08 PM

Addt'l info: Item-level partner function can be deleted if it was activated AFTER configuration change. But order entered prior to making item-level partner not mandatory will not allow deletion of item-level partners.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Anke

I am not getting it why you should delete the partner at item level or any level. You should just change. Since you have no subsequent documents, you should be able to change. Also there should be no need to change the config.

Let me talk out the scenario with you: for an order with 2 items.

Originally (Order creation time)

Header Partner CR (assume) : A

Table VBPA will have only one entry for header ( Item Number 000000)

Erroneous change of item 10: In stead of changing Header Partner to B, user changed item partner for Item 10 to B.

Header Partner CR (assume) : A

Item 10 : B

Table VBPA will have 2 entries: one for header ( Item number 000000) and one for header ( Item number 000000) and another for Item 10 (000010).

To fix, change header and item 20 also to B.

Table VBPA will have 2 entries

one for header ( Item number 000000), another for Item 10 and one more for item 20.

Now if you create a Delivery, both the items will be on one delivery. I tested this for SH party which is mandatory in our system and it works.

Am I missing something? Let me know.

Former Member
0 Kudos

Yes, I did this - changed partner on header and all items to partner B, but delivery is still split. This is how my VBPA entries look now. Partner function in question is ZZ:

Sales document Item Part.funct. Customer Address Adress ind.

0000619902 000000 AG 0000001438 0600007635 D

0000619902 000000 RE 0000001438 0600007635 D

0000619902 000000 RG 0000001438 0600007635 D

0000619902 000000 WE 0000001438 0600007635 D

0000619902 000000 ZR 0000500049 0600012957 D

0000619902 000000 ZZ 0000002851 9000036842 E

0000619902 000010 ZZ 0000002851 9000036828 E

0000619902 000020 ZZ 0000002851 9000037138 E

0000619902 000030 ZZ 0000002851 9000037139 E

0000619902 000040 ZZ 0000002851 9000037140 E

And this is my log of collective run after trying to create the delivery in VL10A:

Error Log for coll. run 0000100194

4 0000619902 000000 The customer has requested complete delivery

4 0000619902 000020 Item 000020: delivery split because the partners are different

4 0000619902 000030 Item 000030: delivery split because the partners are different

4 0000619902 000040 Item 000040: delivery split because the partners are different

Is the issue possibly with the address? Actual data is the same, but maybe it's because it was changed and now the address number is different? If so, how would I remedy this?

Thanks much!

Anke

Former Member
0 Kudos

Yes, Address number is the issue. However it is not happening in our system. I will try and get the reason for you. Try to attack that angle working with an ABAPer and see what can be done to ensure that address number is same

Meanwhile consider this Knowledge Base article (Euphemism for unreleased OSS note):

SAP Knowledge Base Article: 1461604 - Delivery Split Occurs

As per the note, You need to change the partner procedure for Delivery. Did you do that way or have you changed the Sales Order Partner procedure? Check that.

Even if you do that, like you have already seen, it might not help for an order existing before config change.

Keep me posted.

Former Member
0 Kudos

Problem solved! I changed the ZZ partner on header and all line items to a different partner, then changed all back to the partner I wanted. This caused the address number to be the same on the header and all items, and we could create the delivery without split.

I had changed the config at sales order item level, not delivery level. I looked at delivery, but it does not differentiate between header and item so I didn't try it there. I will take a closer look at this, though. It may be useful in future.

Thank you so much for the feedback and confirming my findings. It made me look more closely and find the answer. I will also look at the unreleased note to which you refer. I am still frustrated that I could not delete the item level partner on the existing order after I changed the configuration.

Thanks again! The dialogue was very helpful!

Anke

Former Member
0 Kudos

Glad to hear!

In fact even I changed the partners the way you did, that is changed to another partner first and to the correct one later. I made a mistake while changing and so I had to do that, but did not pay attention to it.

For future, take a look at OSS note below which also throws some insights.

448919 - Delivery split concerning partner data works incorrectly

Also check your Delivery type config for the field: Delivery Split for Additional Partners, for any use i future.

Take care!

Answers (0)