ABAP/4 Consistency Checkconsistency checking so that a system which has beeninconsistently installed can be started in order toanalyze the problem.
Repairing installation problems.
Who is allowed
Limitation for os
Limitation for db
Accepts the following values0: Full check. Use this value for R/3 Systems thatare in production use. Under no circumstances shoulda production system run with any other value.
After the transaction SICK is used to analyze theproblem, the system can be used in spite of database inconsistencies.
No check for correct NAMETAB information when ABAP/4programs are loaded.