SAP Note 19116 - Incomplete/erroneous order master data

Symptom:

Description:
You cannot change or create master data of internal orders because certain table entries or partial objects are missing.
Transactions:
KO01, KO02, KO03, KKF1, KKF2, KKF3, KOM1, KOM2, KOM3
Error message:
The following error messages are most likely:

• BS 001 'No status object is available for AUF xxxx'

• Update termination because of SAPSQL_ARRAY_INSERT_DUPREC
  in program SAPLBSVU during insert in table JSTO or
  in program SAPLKOBR during insert in table COBRA
  or in function module CLVF_VB_INSERT_CLASSIFICATION
  during insert in table KSSK (Program SAPLCLVF).
  

Reason and Prerequisites

The inconsistent master data can result from:

• an error during the client copy

• manual deletion of AUFK records (or other table entries)

• incomplete transports
  

Solution

As of Release 3.0A, report RKOCHK02 is available which determines inconsistencies and deletes incorrect orders or completes missing table entries, if required.
You must correct the report using the correction instructions from Note 160841 (up to and including Release 6.00) before you use it!
If you have a release prior to 3.0A, you can get report RKOCHK02 from SAPSERV3 as described below.
When you start the report, you can use the UPDATE or 'Execute database changes' parameter to determine whether you want to have a list of all inconsistent objects or whether the required database changes are to be made at the same time. If you have a large number of orders (more than 1000), we recommend running the report in the background.
C A U T I O N: if you run report RKOCHK02 with database update, you should not create any new orders while the report is running: otherwise the report may create inconsistent data itself.
The report displays a list of order numbers for which inconsistencies have been determined and displays for each order the tables in which entries were found. An order is only complete if tables AUFK, ONR00, ONROR, JSTO and JEST each contain (at least) one entry. If the AUFK entry is missing, all dependent records will be deleted (column DELETE or 'Delete' has been selected). Otherwise, the system tries to reconstruct the missing entries.
Important: You must add the changes to the report that are specified in
the attachments under "Corrections" in all releases prior
to Release 4.0C, since otherwise inconsistencies may
occur with the change documents of the status management.

To get report RKOCHK02 from SAPSERV3
----------------------------------------
If report RKOCHK02 does not yet exist in your system (Release <>

• Change to a suitable UNIX directory and log on to sapserv3 via ftp:
  > ftp sapserv3
  Name : ftp
  Password: ftp

• Enter the following command sequence:
  ftp> cd dist/permanent/Note.0019116
  ftp> get rkochk02.k11
  ftp> quit
  This will copy the ASCII file rkochk02.k11 into your current UNIX directory.

• Create report RKOCHK02 (type '1') in your system with transaction SE38 and upload file rkochk02.k11 with the upload function in the program editor.

After saving, you can execute the report immediately.