SAP Note 152571 Composite SAP note: Missing or incorrect commitmentsNote Language: English Version: 15 Validity: Valid Since 29.11.2005 Summary Symptom Commitment values are recorded incorrectly in cost centers, orders, WBS elements or network activities. Examples: Commitments arising from purchase orders, purchase requisitions, or funds reservations are missing, contain the wrong amounts, or are not reduced. This means the data shown in reports is incorrect. As commitments also increase the assigned amounts in budgeting, further symptoms may include incorrect assigned amounts and seemingly unjustified messages from availability control. Other terms ME21, ME22, ME51, ME52, MB01, ME21N, ME51N, commitment, purchase requisition, PReq, purchase order, budget check, invoice verification, commitment carried forward, CJCF, KOCF, KSCF, VACF Reason and Prerequisites Customizing, program error Solution This note gives advice on analyzing the errors and also lists notes and correction programs. It is not exhaustive. Pay attention to the release validity of the notes mentioned below. However, some notes do contain correction programs that can be applied generally outside the note validity. Settings in Customizing o If commitments are missing, first check the customizing as described in Note 47992. You should also check the settings that control how the commitment is reduced ('Goods receipt', 'Unvalued goods receipt' and 'Invoice receipt' indicators in the purchase order or purchase requisition), and whether the commitment is to be reduced by quantity or by value (up to and including Release 3.1I, Transaction OMSC; as of Release 4.0A, Transaction CUNI). Correction of Missing or Incorrect Commitments o Firstly, ascertain which level the incorrect values are being displayed on; if the commitment line items are correct and only the totals record is incorrect, then the problem is generally not a commitment problem. Inconsistent data between line items (Table COOI) and the totals record (COSP) can be corrected using the RKACOR04 program(->Note 21649). For assessment, use the RKACSHOW technical inspection program, view the database directly with Transaction SE16(N), or start the program first without updating. 25.01.2011 Page 1 of 4 The system responds in a similar way if. In every case where commitments are missing or incorrect. implement the correction from Note 216255. ten units are ordered at 100 Euro each. was solved using Note 158892. after commitment data has been corrected. To do this. o o o o o o o Problems with the Availability Control due to Budget Overruns o When you enter invoices. for example. but the invoice records each unit at 1000 Euro each.01. you can then delete these kinds of commitments from the database using the ZKAOIDE2 program (Note 334851).6. and Transaction K031 for orders. Continuing on. refer to Note 88850. Some problems with currency translation are solved in Notes 73333. If you run Enterprise Release or higher and expect the response Page 2 of 4 25. This problem occurs if you want to post an invoice and the unit price is higher than the purchase order value. in this case.SAP Note 152571 Composite SAP note: Missing or incorrect commitments o o For negative commitments on the totals level. When it does this invoice values are seen as more current than purchase order values. 97615. This is often due to the fact that the system is tries to calculate commitment values on the most current basis. If commitment line items are missing after a commitment carryforward. commitments for orders that were created before the upgrade are not reduced after a goods receipt or an invoice receipt: see Note 125266. apply Note 165154. 90153. In some cases. you also need to update the assigned values for the relevant account assignment objects. the program is of no use. 202465 and 742611. you can draw on an alternative version of this program (the RKOBLM01 program. refer to Note 78398. If only the commitment for the first item is reduced correctly in the invoice receipt for a purchase order with several purchase order items. that is a case of commitments on incorrect account assignment objects but with existing purchase orders. After a release upgrade to Release 4.If the program terminates (for example. sometimes there is a budget overrun because a commitment was not reduced. If this system response is not in your interests. try to correct the data using the RKANBU01 program (see also Note 534993). Using the ZKAOIDE0 program from Note 100409. you can set to zero any commitments that originate from purchase requisitions or purchase orders that do not exist or are already archived. transport request: U40K900002).2011 . because account assignment objects are missing after a migration). see R/2 Note 61642) using SAPSERV3 (directory/specific/mig_R2_R3/note61642. A similar problem. use Transactions CJEN and CJBN (in that order) for projects. Note that when you delete a purchase order item. the purchase order still exists on the database.5/4. 22. o Header Data Release Status: Released on: Master Language: Priority: Category: Primary Component: Released for Customer 29.11. you need to set up an example which can be reproduced so that the cause of the problem can be analyzed.2011 Page 3 of 4 . One such example would be if an incorrect value existed even though you used the RKANBU01 program. Provide us with all the input data required for the transaction and use SAPNet to send a problem message to us. For instructions on how to use this check report.01. Use the technical check report RKACSHOW to analyze the table contents. invoice receipt) leads to the incorrect commitment. 24). If the problems with incorrect commitment values recur.SAP Note 152571 Composite SAP note: Missing or incorrect commitments described above. implement Note 490624. Prepare an example and tell us which transaction (for example. Notes on Error Analysis o Commitments are recorded in the COSPA totals records table (view: COSPA) and the line item table COOI (WRTTP 21. All values that can be corrected using the program require a very detailed description of how the incorrect commitment can be created. see Note 28145.2005 11:22:59 German Recommendations/additional info Help for error analysis CO-OM-OPA-D Commitments The Note is release-independent Related Notes Number 1128464 551506 534993 520717 411541 397799 397239 352584 Short Text FAQ: Commitments FAQ note Overhead Cost Controlling Short instructions RKANBU01 Budget check in EBP Statistics update:Incorrect commitments from purchase orders INFORMATION: CO-OM-OPA (Order & Project Accounting) INFO:CO-OM Interface/actual postings/commitment/down payment Composite note 'Applicatn-specifc special features' 25. SG104 during GR or IR PUCHIS-commtnts f. or dely csts & invoce Missing open cmmt ln itms after cmmt bal.01.car.mltple sel.2011 Page 4 of 4 .forwrd Error message SG111 or SG119 No commitment is displayed in reporting Posting open purchase order requisitions Using technical inspection report RKACSHOW 25.5 or higher Commitment line items differ from totals records Commitment without purchase order or purchase requisition FAQ: Posting commitments Incorrect currency translation for the commitment Commitment is completely phased out BCD_FIELD_OVERFLOW.SAP Note 152571 Composite SAP note: Missing or incorrect commitments Number 212114 165154 158892 137936 125266 113423 100409 100406 97615 93951 90153 88850 78398 73333 47992 41511 28145 Short Text Deleted network component and purchase requisition Negative commitments Commitment for purchase order without account assignment Performance for RKANBU01 Commitment incorrect after upgrade to Release 4.
Report "Sapnote_0000152571 Missing or Incorrect Commitments"