SAP TRINT_CALL_AFTER_IMP_METHOD Function Module for









TRINT_CALL_AFTER_IMP_METHOD is a standard trint call after imp method SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for trint call after imp method FM, simply by entering the name TRINT_CALL_AFTER_IMP_METHOD into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCTS_EXE_EXP
Program Name: SAPLSCTS_EXE_EXP
Main Program: SAPLSCTS_EXE_EXP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TRINT_CALL_AFTER_IMP_METHOD pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'TRINT_CALL_AFTER_IMP_METHOD'"
  EXPORTING
   IV_TRKORR =  "Imported Request
*  IV_NO_COMMIT_WORK = ' ' "
   IS_E070 =  "
   IT_E071 =  "
   IT_E071K =  "
*  IV_DATNAME = ' ' "
*  IV_UPDATE_LOCKFLAG = 'X' "
*  IV_CTC = ' ' "
*  IV_SFW_CALL = ' ' "
*  IV_STATLOG_FILE = ' ' "

CHANGING
   IT_CLIENT =  "
.



IMPORTING Parameters details for TRINT_CALL_AFTER_IMP_METHOD

IV_TRKORR - Imported Request

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

IV_NO_COMMIT_WORK -

Data type: TRPARI-W_VALID
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_E070 -

Data type: TRWBO_S_E070
Optional: No
Call by Reference: No ( called with pass by value option)

IT_E071 -

Data type: TRWBO_T_E071
Optional: No
Call by Reference: Yes

IT_E071K -

Data type: TRWBO_T_E071K
Optional: No
Call by Reference: Yes

IV_DATNAME -

Data type: TRBAT-DATNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_UPDATE_LOCKFLAG -

Data type: TRPARI-W_VALID
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CTC -

Data type: TRPARI-FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SFW_CALL -

Data type: TRPARI-FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_STATLOG_FILE -

Data type: TSTRF01-FILE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for TRINT_CALL_AFTER_IMP_METHOD

IT_CLIENT -

Data type: SCTS_CL_RESULTS
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TRINT_CALL_AFTER_IMP_METHOD Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_it_client  TYPE SCTS_CL_RESULTS, "   
lv_iv_trkorr  TYPE E070-TRKORR, "   
lv_iv_no_commit_work  TYPE TRPARI-W_VALID, "   ' '
lv_is_e070  TYPE TRWBO_S_E070, "   
lv_it_e071  TYPE TRWBO_T_E071, "   
lv_it_e071k  TYPE TRWBO_T_E071K, "   
lv_iv_datname  TYPE TRBAT-DATNAME, "   SPACE
lv_iv_update_lockflag  TYPE TRPARI-W_VALID, "   'X'
lv_iv_ctc  TYPE TRPARI-FLAG, "   SPACE
lv_iv_sfw_call  TYPE TRPARI-FLAG, "   SPACE
lv_iv_statlog_file  TYPE TSTRF01-FILE. "   SPACE

  CALL FUNCTION 'TRINT_CALL_AFTER_IMP_METHOD'  "
    EXPORTING
         IV_TRKORR = lv_iv_trkorr
         IV_NO_COMMIT_WORK = lv_iv_no_commit_work
         IS_E070 = lv_is_e070
         IT_E071 = lv_it_e071
         IT_E071K = lv_it_e071k
         IV_DATNAME = lv_iv_datname
         IV_UPDATE_LOCKFLAG = lv_iv_update_lockflag
         IV_CTC = lv_iv_ctc
         IV_SFW_CALL = lv_iv_sfw_call
         IV_STATLOG_FILE = lv_iv_statlog_file
    CHANGING
         IT_CLIENT = lv_it_client
. " TRINT_CALL_AFTER_IMP_METHOD




ABAP code using 7.40 inline data declarations to call FM TRINT_CALL_AFTER_IMP_METHOD

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_iv_trkorr).
 
"SELECT single W_VALID FROM TRPARI INTO @DATA(ld_iv_no_commit_work).
DATA(ld_iv_no_commit_work) = ' '.
 
 
 
 
"SELECT single DATNAME FROM TRBAT INTO @DATA(ld_iv_datname).
DATA(ld_iv_datname) = ' '.
 
"SELECT single W_VALID FROM TRPARI INTO @DATA(ld_iv_update_lockflag).
DATA(ld_iv_update_lockflag) = 'X'.
 
"SELECT single FLAG FROM TRPARI INTO @DATA(ld_iv_ctc).
DATA(ld_iv_ctc) = ' '.
 
"SELECT single FLAG FROM TRPARI INTO @DATA(ld_iv_sfw_call).
DATA(ld_iv_sfw_call) = ' '.
 
"SELECT single FILE FROM TSTRF01 INTO @DATA(ld_iv_statlog_file).
DATA(ld_iv_statlog_file) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!