SAP NetWeaver AS ABAP Release 740, ©Copyright 2014 SAP AG. All rights reserved.
ABAP Keyword Documentation → ABAP − Reference → program editing → Dynamic Program Editing → Source Code → INSERT REPORT →INSERT REPORT - Internal Additions
Internal Additions
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
... 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.
... 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.
... 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), which is checked statically if specified as Literal. 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.
... 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.
Non-Catchable Exceptions