cancel
Showing results for 
Search instead for 
Did you mean: 

Condition record

Former Member
0 Kudos

Hi,

For condition type MWST, two different access sequences (records) have been picked up in sales and billing doc having same pricing procedure .

Access seq. for sales order is

S. Org./Destination country/customer tax/material tax.

Access seq. for billing doc is-

S.Org./Sales doc type/Shipping pt./Destination country

For same pricing procesdure, same access seq. should get determined irrespective of doc. type i.e. sales & billing doc.

What could be the reason for such system behavoiur.

Pls. guide

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

.

former_member183879
Active Contributor
0 Kudos

Hi Mrunal,

It can be possible in the following scenarios.

You have the redetermination of taxes in the invoice document.

and

The first condition record had a valid date when the sales order was created, but while the invoice was created the validity of the record expired or it was deleted. As a result during invoicing, during the condition access, value was taken from the second condition table.

Please check whether the condition record for the first condition table is valid or not. If not existing try to find out the change history of the condition record and rectify the inconsistency.

If your specific document is landing into problems, just because of this, you can cancel that invoice document and recreate another invoice document with reference to the sales order. This has to be done after making your masterdata settings perfect.

Hope this helps you

Pls reward if it helps you

Former Member
0 Kudos

Hello Mrunal,

According to your description, it seems that a custom access sequence is associated with the condition type MWST.

I guess that requirements (formula), which were assigned to lines of the access sequence, caused the problem. Please check the access sequence.

Please reward points if helpful!

Best regards!

Gordon