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

Issue:

You have a service contract but the release values (table EKAB) are not clear or correct.

Solution: 

The release order documentation provides information on the current status of the release orders issued against a contract. Here we have to distunguish between two scenario's: the planned scenario and the unplanned scenario.

In the planned scenario you enter the contract reference at item level AND adopt the service lines from the contract in ME21N. In this case the release values of the contract are updated with the PO's value, the PO itself is the release document.

The service line of the PO is updated:

  • the linkage is built at service level (ESLL-KNT_PACKNO and -KNT_INTROW filled with the package details of the adopted service line of the contract) 

The service line of the contract is updated by the PO:

  • the quantities of the release orders (ESLL-KNT_MENGE)
  • the value of the release orders (ESLL-KNT_WERT)

In the unplanned scenario you do NOT enter the contract reference at PO item level, you only enter the contract item in the contract limit tab. In this scenario the release documentation of the contract is not yet updated as the PO is NOT a call-off document. The release document will be the SES created with reference to the PO and selecting the service line(s) from the contract. So table EKAB (release documentation) is updated with the PO but with the SES value(s).

The service line of the SES is updated:

  • the linkage is built at service level (ESLL-KNT_PACKNO and -KNT_INTROW filled with the package details of the adopted service line of the contract) 

The service line of the contract is updated by the SES:

  • the quantities of the release orders (ESLL-KNT_MENGE)
  • the value of the release orders (ESLL-KNT_WERT)

Important remarks:

  • clubbing, mixing the two scenario's will lead to incorrect release values!
  • if you do NOT specify the contract at item level but select and adopt the service line(s) from the contract, the PO is NOT a contract release order. In this case this is considered only as an input aid and there's no linkage at service line level (ESLL-KNT* values remain empty).

Related notes / content:

 1993192 OMXX customizing transaction has no effect in case of Service contract releases

1546346 MM-SRV : General issues with contract