SAP CALL_TRANSACTION Function Module for NOTRANSL: Transaktion starten mit Berechtigungsprüfung auf Transaktionssta
CALL_TRANSACTION is a standard call transaction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Transaktion starten mit Berechtigungsprüfung auf Transaktionssta processing and below is the pattern details for this FM, 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 call transaction FM, simply by entering the name CALL_TRANSACTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: M61R
Program Name: SAPLM61R
Main Program: SAPLM61R
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function CALL_TRANSACTION 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 'CALL_TRANSACTION'"NOTRANSL: Transaktion starten mit Berechtigungsprüfung auf Transaktionssta.
EXPORTING
* TCODE = "Transaction Code
EMDPS = "
SELKZ = "
TRGRP = "
* MATNR = ' ' "
* WERKS = ' ' "
* DISGR = ' ' "
EXCEPTIONS
T457C_UNVOLLSTAENDIG = 1 NOT_AUTHORIZED = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLM61R_001 User Exit for Evaluation PP-MRP Material Requirements Planning
IMPORTING Parameters details for CALL_TRANSACTION
TCODE - Transaction Code
Data type: SY-TCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
EMDPS -
Data type: MDPSOptional: No
Call by Reference: No ( called with pass by value option)
SELKZ -
Data type: T457C-SELKZOptional: No
Call by Reference: No ( called with pass by value option)
TRGRP -
Data type: T457C-TRGRPOptional: No
Call by Reference: No ( called with pass by value option)
MATNR -
Data type: MT61D-MATNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
WERKS -
Data type: MT61D-WERKSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DISGR -
Data type: MT61D-DISGRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
T457C_UNVOLLSTAENDIG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_AUTHORIZED - No Authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CALL_TRANSACTION 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_tcode | TYPE SY-TCODE, " | |||
lv_t457c_unvollstaendig | TYPE SY, " | |||
lv_emdps | TYPE MDPS, " | |||
lv_not_authorized | TYPE MDPS, " | |||
lv_selkz | TYPE T457C-SELKZ, " | |||
lv_trgrp | TYPE T457C-TRGRP, " | |||
lv_matnr | TYPE MT61D-MATNR, " SPACE | |||
lv_werks | TYPE MT61D-WERKS, " SPACE | |||
lv_disgr | TYPE MT61D-DISGR. " SPACE |
  CALL FUNCTION 'CALL_TRANSACTION' "NOTRANSL: Transaktion starten mit Berechtigungsprüfung auf Transaktionssta |
EXPORTING | ||
TCODE | = lv_tcode | |
EMDPS | = lv_emdps | |
SELKZ | = lv_selkz | |
TRGRP | = lv_trgrp | |
MATNR | = lv_matnr | |
WERKS | = lv_werks | |
DISGR | = lv_disgr | |
EXCEPTIONS | ||
T457C_UNVOLLSTAENDIG = 1 | ||
NOT_AUTHORIZED = 2 | ||
. " CALL_TRANSACTION |
ABAP code using 7.40 inline data declarations to call FM CALL_TRANSACTION
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 TCODE FROM SY INTO @DATA(ld_tcode). | ||||
"SELECT single SELKZ FROM T457C INTO @DATA(ld_selkz). | ||||
"SELECT single TRGRP FROM T457C INTO @DATA(ld_trgrp). | ||||
"SELECT single MATNR FROM MT61D INTO @DATA(ld_matnr). | ||||
DATA(ld_matnr) | = ' '. | |||
"SELECT single WERKS FROM MT61D INTO @DATA(ld_werks). | ||||
DATA(ld_werks) | = ' '. | |||
"SELECT single DISGR FROM MT61D INTO @DATA(ld_disgr). | ||||
DATA(ld_disgr) | = ' '. | |||
Search for further information about these or an SAP related objects