Page tree
Skip to end of metadata
Go to start of metadata

Purpose

It is not clear how the contract release documentation (table EKAB) is filled when call-off POs are created for a material contract. (For service contracts please refer to this wiki article).
This article explains the logic of the contract release documentation update.

Overview

The calculation logic depends also on the customizing set in the transaction OMXX. There are two options here: „with ordered quantity” and „with delivered quantity”. This setting is stored in table TCURM- MMKON_CUS. If it is X, the EKAB is written with delivered quantity. Check this setting first. Based on this, the behavior is as follows.

If you use the "with ordered quantity":

The EKAB will hold the PO value/quantity when the PO is created and no GR is posted yet.
If the delivery completed (EKPO-ELIKZ) flag is now ticked (when there is no GR posting), the EKAB will be reduced to zero.
If partial or full GR (even with overdelivery) is posted before setting delivery completed indicator in PO manually, the EKAB will show the PO quantity and not the actual GR quantity. The same rule applies when setting the delivery completed flag after GR.
Invoice postings and the final invoice indicator have no effect on the EKAB.

If you use the "with delivered quantity":

The EKAB will hold the PO value/quantity when the PO is created and no GR is posted yet.
If the delivery completed (EKPO-ELIKZ) flag is now ticked (when there is no GR posting), the EKAB will be reduced to zero.
If partial or full GR (even with overdelivery) is posted, the EKAB will show the actual GR quantity only in case the delivery completed flag is set. (This can be automatically set by the GR posting). If the delivery completed flag is not set, the EKAB will show the PO quantity even if the OMXX is set with delivered quantity.
Invoice postings and the final invoice indicator have no effect on the EKAB.

Further information:

The value calculation is done in include MM06EF0C_CONTRACT_VALUE_CHECK. In case the target value is exceeded, the system issues the message 06 042 according your customizing setting for this message (warning/error). It is important to implement all available correction notes for this include, so the correct calculation can be ensured.

As the OMXX setting affects the update of table EKAB, system shows the Release Value in purchasing reports (ME3N, ME3L, ME3K) accordingly as well.

Related Content

Related Documents

Wiki article about the EKAB update logic for service items here.

Related SAP Notes/KBAs

SAP KBA: 1624994 - Messages 06 042 (Target value of contract & exceeded by & &) and 06 078 (Target quantity exceeded by & &) for Purchase Requsition

SAP KBA: 1998844 - Contract target value can be reduced to less than PO total values



  • No labels