Condition type appearing twice in Line item of Sales order

[former_member284325]

Hello All,

We have a situation where condition type for Packing is appearing twice in the Sales order. Its a manual condition and no access sequence is maintained in VK11 for the same. I am unable to replicate the same scenario in the Quality server. Checked various threads on the same but unable to arrive at solution.

Regards

Sushil

[Former Member · Accepted solution]

Dear Sushil,

Please see whether "manual" is checked in your Pricing procedure and also see whether "manual entries got priority" in your condition type, also check how the condition record is determined in the sales order from "condition origin".

[former_member284325 · Accepted solution]

"Manual" is checked in Pricing procedure. Condition type screenshot is given above.

Condition record reflects the following:

ZVPK 207 Condition has been found (without condition record)

[former_member188076 · Accepted solution]

Hi,

If this is a manual condition, user may enter it twice in the Condition tab, while creating the Sales Order. However only one (the lower one) will be active, the other one will be deactivated.

Thanks and regards,

Amitesh Anand

[former_member284325 · Accepted solution]

Thanks guys for your support. I got the solution. The Condition type was entered twice at Quotation level. However after creating the subsequent documents (till invoicing) the header was reflecting the condition type only once but line item was still showing 2 times.

[former_member187610]

Hi Sushilkumar,

Please check which access sequence is assigned to these condition types.  Next go to V/07, select that access sequence and ensure to check the box "Exclusive" button for all the tables.

Hope this will resolve your issue.

Regards,

Sharan

[former_member284325]

How to confirm if the condition type has been assigned to any access sequence? VK13 suggests

There are no access sequences for condition type ZVPK

[Lakshmipathi]

Go to V/06, select this condition type and execute.  There on top right, check any access sequence is assigned to that condition type. If not, better you delete that condition type, save with an existing transport request or with a new request, and finally, recreate that condition type.  This is assuming that you were trying in development server.

G. Lakshmipathi

[former_member284325]

In V/06, the access seq field is blank.

[former_member284325]

This being a scenario of production server where SO has already been created followed by subsequent documents. Need some solution or reason why system is behaving this way or is there any bug?

[phanikumar_v3]

Dear--Dont get confused on access sequence--from your screen shot it is clearly telling that your ZVPK condition type is a header condition.

Pl remember the following 3-thumb rules----

1.All header conditions will never have Access sequence--if assigned detoriate the systems performance--i sincerely suggest you to follow Mr.Glync  book on SD --pricing section.

2.No Access sequence--there by no condition tables required.

2. Always Condition records need to be maintained manually or through formulaes for all header conditions.

Any way, you rectified this issue on your own--that makes me happy.

Phanikumar