The Designer installs the ABAP program in the development class shown in the Development Class field. The default development class is $TMP. The $TMP development class is temporary. You cannot transport ABAP programs from this class to another system. If you want to transport the ABAP program to a production system, create a development class within SAP for the ABAP programs. Install ABAP programs that use a namespace in a development class that is in the same namespace.
You must regenerate and install the ABAP program if there is a change in the source, Application Source Qualifier transformation, or their links.
You can install the ABAP program directly on the SAP system, or you can generate the ABAP program locally and install it using the local copy.
If the SAP system is a Unicode system, the Designer is connected to a Unicode repository, and the ABAP program contains a source filter with ISO 8859-1 or multibyte characters, generate a local copy of the ABAP program and upload the generated file into the SAP system.
Security Features for ABAP Table Reader Transports
The following transports contain security features that enforce security authorizations when you use ABAP to read data from SAP:
TBL run-time transport
TBL design-time transport
HIER_R3 run-time transport
HIER_R3 design-time transport
When you perform data integration tasks with ABAP, the PowerCenter Integration Service verifies that the following conditions are met:
The SAP user who generates and installs the ABAP program has the developer license.
The user who generates and installs the ABAP program is authorized for the following function groups:
SKEY
STR9
Users cannot generate and install ABAP programs from the Designer tool if the SAP client is locked down for changes.
A new workbench request is created to track object changes in SAP when users install or delete ABAP programs.
The ABAP program can be installed only on development systems and not on production systems.
If any of these conditions are not met, the ABAP program installation fails.