ABAP Keyword Documentation →  ABAP - Reference →  program editing →  Dynamic Program Editing →  Source Code →  INSERT REPORT 

INSERT REPORT - internal additions

Other versions: 7.31 | 7.40 | 7.54

Internal Additions

Other versions: 7.31 | 7.40 | 7.54

These additions are for internal use only. Do not use them in application programs.

Extras

1. ... EXTENSION TYPE exttype

2. ... APPENDAGE TYPE apptype

3. ... STATE state
4. ... OBJECT KEY key

Addition 1

... EXTENSION TYPE exttype

Effect

The content of positions 31 to 35 (suffix 1) of the program name in prog is checked against the content of exttype. exttype must be a constant of the type group SREXT. Positions 36 to 40 (suffix 2) of prog may only contain blank characters.

Note

The additions EXTENSION TYPE and APPENDAGE TYPE are mutually exclusive.

Addition 2

... APPENDAGE TYPE apptype

Effect

The content of positions 36 to 40 (suffix 2) of the program name in prog is checked against the content of apptype. apptype must be a constant of the type group SREXT. Positions 31 to 35 (suffix 1) of prog must also correspond to a constant of the type group SREXT.

Note

The additions EXTENSION TYPE and APPENDAGE TYPE are mutually exclusive.

Addition 3

... STATE state

Effect

Determines whether the program is stored as active or inactive in the repository. state can have the values "A" (for active) and "I" (for inactive). Inactively saved programs are only visible to the current user. All other users work with the active version of the program.

Without the STATE addition, the inactive state is implicitly used for the inactive programs of the current user, and the active state for all other programs.

Addition 4

... OBJECT KEY key

Effect

You can use this addition to specify which entry in the database table TADIR the program will be assigned to during a package check. For key, you need to specify a data object of type PAK_OBJECT_KEY_CHARONLY that refers to an entry in the TADIR. During a package check, the package of the declared object is used.

Note

Many programs generated by frameworks, such as Web Dynpro ABAP, do not have their own TADIR entry, because they are subobjects of larger entities, such as class pools for classes of Web Dynpro. If a package check is carried out for these programs, this addition needs to specified in order to refer to the package it belongs to.

Exceptions

Non-Catchable Exceptions

• Cause: state has a value other than "A" or "I".
  Runtime Error: INSERT_REPORT_ILLEGAL_STATE