LOG_IMPORTINFO

This user exit can be used to process the import tracking information (all executions of imports with their results). Please note: In opposite to the user exit AFTER_ADD2_TRACK, implemetations of this user exits are only processed if the import was executed via TransportManager. So if it needs complete data, including import results done w/o TransportManager (e.g. via SAP TMS), you should use an implementation of AFTER_ADD2_TRACK.

Location for activation

TM Server

Template function Module

/RTC/TM_TMPL_LOG_IMPORTINFO

Interface

Import Parameters

Internal table LT_IMPORT_INFO

Field	Description

Field	Description
TRKORR	Transport Request
SHORTTEXT	Short text of the Transport Request
R3_SID	Target System of the import
R3_CLIENT	Target Client of the import
AS4DATE	Import date
AS4TIME	Import time
AS4USER	Request Owner
TRANSUSER	<User Name>: Import executed via personal Queue of that user <SID_TM><SID_TARGET>: Import executed by system queue Others: import executed via SAP TMS
PJ_NAME	Project the imported request is assigned to
DESTI_NAME	Destination the imported request is assigned to
LEVEL_NAME	Transport Level of the target system
STEP_COUNT	Number of executed import steps (e.g. DDIC Import, DDIC Activation, etc.)
CO_RETCODE	Overall return code of all import steps
TP_RETCODE	Return code of the tp execution

Export Parameters

None

Example

All import activities should be stored in customer specific tables for further analysis

Step 1

Copy the function module /RTC/TM_TMPL_LOG_IMPORT_INFO to a new function module

Add the following code to the section “Begin of customer implementation”:

FIELD-SYMBOLS: <lw_import_info>.
LOOP AT lt_import_info  ASSIGNING <lw_import_info>.
* Copy field information, customer needs to own work area to provide cutomer own 
* table
ENDLOOP.

REALTECH Connect