Hi,
If you create the Sales order and subsequently billing document then the Pricing can not be changed and it will be displaying as 'F-Condition value fixed (billed items) . This can also be updated when you have the automatic pricing.
Let me explain further the how condition control (KSTEU) works. I will focus mainly on A, D, E and F.
The KSTEU of a condition can be changed in various places. The most
common case is that the KSTEU is changed during the copying of the
conditions from one document into another. This happens in the function
PRICING_COPY and depends on the pricing type (MODE in PRICING_COPY), the
origin of the condition KHERK and the actual value of KSTEU. For the
precise rules, please refer to the coding of PRICING_COPY itself.
Besides copying conditions there are several other occasions where KSTEU
might be changed.
The possible values are:
A Adjust for quantity variance
B Free
C Changed manually
D Fixed
E Condition value and basis fixed
F Condition value fixed (billed items)
G Condition basis fixed
H Condition value fixed (cost price)
'A': Adjust for quantity variance
************************************************************************
The condition is recalculated in a #normal# way. Its rate has been
determined automatically (e.g. via a condition record). The condition is
not fixed in any way. Especially when the item quantity is changed, the
rate might be adjusted if scales are present. All formulas (base value,
value etc) are executed the normal way. If a condition is automatically
found, #A# is the normal KSTEU value.
'D' : Fixed
************************************************************************
'D' : fixed. The rate of the condition is fixed. I.e. that if e.g. the
quantity is changed, no rate update due to scales will take place. The
The rate of the condition will not be changed during the processing of
the condition. Besides, that the condition is handled like KSTEU = 'A'
The most common place where KSTEU is set to 'D' is during the copying
of one document to another (function PRICING_COPY), But only if the
KSTEU is not 'CDEFH' (to avoid to loosen any stronger fix. Also 'C'
must not be changed to keep the information of a manual change). If
you e.g. partially bill an item and copy a condition with scales, you
do not want the scales to be re-determined. On the contrary: it is
mandatory that the condition rate stays the same with respect to the
order. KSTEU = 'D' will guarantee this. All formulas are processed as
usual. So a change of the rate in a formula is still possible. Note:
A fixed condition ('F') is often reset to 'D' during copying
(PRICING_COPY).
'E' : Condition value and basis fixed.
************************************************************************
'E' is the strongest fix of a condition in pricing. Nothing will be done
with the rate or value of this condition any longer. Especially the
condition will NOT be adjusted if e.g. the quantity of an item is
changed. Formulas are no longer processed in 'change mode'. I.e. that
the base and value formula are processed but cannot change any XKOMV
field. Technically this is realized with a RETTKOMV = XKOMV .. XKOMV =
RETTKOMV bracket in the coding. While no XKOMV field can be changed
within the formula, changes to other fields, e.g. in KOMP are still done
It is just for this reason that the formulas are still processed at all.
We cannot rule out that things are done here which are needed for the
processing of other non-fixed condition later on. One aspect of a
fixed condition is, that the rate field is grayed out afterwards,
because changing the rate would not anyhow not have any effect on the
value. In general:: not much happens in pricing with a condition with
KSTEU = 'E'.
'F' : fixed
************************************************************************
This usually happens if an item get fixed (KOMP-KAEND_TYP(1) = '*'),
e.g. if an item gets (partially) billed. The KSTEU = 'F' is only set if
you (after the invoicing) reenter the original document and access the
condition screen. It happens in LV61AA03 # FIXIEREN_KOPFKONDITION_
POSITION and only in the order for conditions with KSTEU = 'A'.
Conditions of different KSTEU are not changed because you would loose
too much information. The reason is that the KSTEU needs to be reset if
e.g. the invoice, fixing the item, is cancelled. By default it is reset
to 'A'. KSTEU is also not changed if its KHERK is 'D' or 'G'. 'F' is
much more strict than 'D'. The rate of the condition is not adjusted to
changes of the scale basis any longer. The value formula has no longer
any influence on the value (like in case of 'E') but the basis formula
is still processed in the normal way! In fact the condition value is
adjusted to changes in the basis in the following way (LV61AA55 - XKOMV_
BEWERTEN):
new_basis
new_value = * old_value
old_basis
This is necessary because you can still change the quantity (and
therefore the base) of an already billed order item. But this procedure
also causes the following problem: If the quantity or the schedule lines
of a fixed items are deleted or set to zero, the value of the condition
is set to zero, too. But as one can see from the formula, an old_value
of zero can never result in a new_value unequal to zero. So the value of
the condition remains zero for ever. This might result in pricing errors
due to inactive price conditions or zero net values. Have a look at note
140471 and 161448 which have been designed to avoid this scenario.
Another important feature of KSTEU = 'F' is, that the condition will not
participate in the distribution of (header) group condition.Nevertheless
they will be used to calculate e.g. the scale basis of the group
condition or the basis in general. But a new scale will not affect the
condition rate nor will any rounding difference be assigned to a fixed
condition.
I hope this is the information you are looking for.
Regards,
Murali
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.