Skip to Content

What is job CODE_INSPECTOR_DELETION?

Hi all.

I use Code Inspector for searching several things in programs.

I see that every night it is run a job called CODE_INSPECTOR_DELETION. I didn't deliberately launch this job.

Does anybody knows what does this job, and how to avoid to launch every night?

Thanks in advance.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Mar 25, 2008 at 02:50 PM

    Hi!

    When you use the code inspector (in transaction SCI; to check objects in the Workbench; and, as of SAP_BASIS Release 6.40, to release transports), a "CODE_INSPECTOR_DELETION" job is scheduled automatically with a daily execution - provided that you create and execute an inspection while using the inspector. The job executes the "RS_CI_DELETE" program that deletes, for example, object sets and inspections whose deletion date has expired. This avoids that too many data is collected in the code inspector.

    Best!

    Jim

    Add comment
    10|10000 characters needed characters exceeded

    • See SAP Help Code Inspector

      [SAP Help - Code Inspector|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm]

      Also, here is the documentation for Tran SCI - Code Inpector

      CODE INSPECTOR

      The Code Inspector tests single objects or object sets (programs, function groups, classes, interfaces, Dictionary objects) for performance, security, serviceability, error proneness, and statistical information.

      You can call the Code Inspector for the relevant single objects directly from the ABAP Editor (SE38), the Function Builder (SE37), or the Class Builder (SE24) (Object->Check->Code Inspector). The system then checks using a default check variant.

      Object sets, check variants, and inspections are created using transaction SCI.

      Object Sets and Check Variants (that is, combinations of single checks to which you can assign parameters) are managed independently of one another. An Inspection connects one check variant with an object set. Inspections, object sets, and check variants are created by one user locally | | or visible to all users globally | |.

      An inspection returns a Check Result, from which you can derive another object set.

      For more information, see extended help Code Inspector