Register Login

Why Expected value mandatory in service POs with limits

Updated May 18, 2018

The expected value has to be mandatory in case only limits are maintained in a purchasing document. The former system design was not correct, because it allowed to create purchasing documents with a total net value of zero, in case only unplanned materials / services had been maintained (and no service lines or materials). This resulted in problems with the release strategie, commitment figure and service entries.

The expected value is added to the total value of planned services of the purchasing document.
For example, a PO with ONLY unplanned services /materials (only limits maintained), the expected value builds the net value.
In such a case Controlling derives the purchase commitment figure only from this value.

Concerning the variability of actual cost of a purchase order, expected value means that the unplanned services (or materials) covered by this item are not EXPECTED to exceed.
It is not mandatory that it has the same value like total limit value. Expected value can exceed, it is used for comparison with total limit
value in cost control.
Expected value can also be combined with unlimited total limit in a purchasing document.


×