Skip to content

ABAP Keyword Documentation →  ABAP − Reference →  program editing →  Dynamic Program Editing →  ABAP 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 the positions 31 to 35 (suffix 1) of the program name in prog checks the content of exttype. exttype must be a constant from the type group SREXT. Positions 36 to 40 (suffix 2) of prog can 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. The 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

This addition determines whether the statement uses the active version or an inactive version of the repository object. state can have the values "A" (for active) and "I" (for inactive), which is checked statically if specified as a literal.

  • If the addition state is not specified, the statement accesses either
  • the active version of the repository object or
  • the inactive version of the repository object in the worklist of the current user. If there are no inactive versions in the worklist of the current user, the statement accesses the active version of the repository object.
Before the statement can evaluate the worklist of the current user, it must be prepared accordingly. This can be done using, for example, the function module RS_WORKING_AREA_PREPARE. If the worklist is not prepared, the statement accesses the active version of the repository object.
  • If the addition state is specified, the statement accesses
  • the active version of the repository object if "A" is specified,
  • the inactive version of the repository object if "I" is specified. The user to which the inactive version is assigned is not important here or whether the version is part of a worklist. If there are no inactive versions, the object is not accessed and sy-subrc is set to 4.

Addition 4

... OBJECT KEY key

Effect

This addition can be used to specify to which entry in database table TADIR the program is assigned during a package check. key expects a data object of type PAK_OBJECT_KEY_CHARONLY that refers to an entry in TADIR. During a package check, the package of the specified object is used.


Note

Many programs generated by frameworks, such as Web Dynpro ABAP, do not have their own TADIR entry, as they are subobjects of larger entities, such as class pools for classes of Web Dynpro. If a package check is performed for these programs, this addition needs to be specified so that it refers to the package it belongs to.

Exceptions

Non-Handleable Exceptions

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