SAP TRINT_MODIFY_DEVCLASS Function Module for
TRINT_MODIFY_DEVCLASS is a standard trint modify devclass 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 modify devclass FM, simply by entering the name TRINT_MODIFY_DEVCLASS into the relevant SAP transaction such as SE37 or SE38.
Function Group: TRDVC
Program Name: SAPLTRDVC
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function TRINT_MODIFY_DEVCLASS 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_MODIFY_DEVCLASS'".
EXPORTING
* IV_ACTION = 'SHOW' "
* IV_DIALOG = 'X' "
* IS_DEVCLASS = "
* IS_FIELDS_FOR_CHANGE = "
* IV_REQUEST = "
IMPORTING
ES_DEVCLASS = "
EV_SOMETHING_CHANGED = "
EV_REQUEST = "
EXCEPTIONS
NO_AUTHORIZATION = 1 INVALID_DEVCLASS = 2 INVALID_ACTION = 3 ENQUEUE_FAILED = 4 DB_ACCESS_ERROR = 5 SYSTEM_NOT_CONFIGURED = 6
IMPORTING Parameters details for TRINT_MODIFY_DEVCLASS
IV_ACTION -
Data type: SY-UCOMMDefault: 'SHOW'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_DIALOG -
Data type: TRPARI-FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_DEVCLASS -
Data type: TRDEVCLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_FIELDS_FOR_CHANGE -
Data type: TRDEV_FIELDS_FOR_CHANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_REQUEST -
Data type: E070-TRKORROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TRINT_MODIFY_DEVCLASS
ES_DEVCLASS -
Data type: TRDEVCLASSOptional: No
Call by Reference: No ( called with pass by value option)
EV_SOMETHING_CHANGED -
Data type: TRPARI-FLAGOptional: No
Call by Reference: No ( called with pass by value option)
EV_REQUEST -
Data type: E070-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_DEVCLASS - INvalid development class
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_ACTION - Invalid action
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENQUEUE_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DB_ACCESS_ERROR - Database access error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_NOT_CONFIGURED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TRINT_MODIFY_DEVCLASS 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_iv_action | TYPE SY-UCOMM, " 'SHOW' | |||
lv_es_devclass | TYPE TRDEVCLASS, " | |||
lv_no_authorization | TYPE TRDEVCLASS, " | |||
lv_iv_dialog | TYPE TRPARI-FLAG, " 'X' | |||
lv_invalid_devclass | TYPE TRPARI, " | |||
lv_ev_something_changed | TYPE TRPARI-FLAG, " | |||
lv_ev_request | TYPE E070-TRKORR, " | |||
lv_is_devclass | TYPE TRDEVCLASS, " | |||
lv_invalid_action | TYPE TRDEVCLASS, " | |||
lv_enqueue_failed | TYPE TRDEVCLASS, " | |||
lv_is_fields_for_change | TYPE TRDEV_FIELDS_FOR_CHANGE, " | |||
lv_iv_request | TYPE E070-TRKORR, " | |||
lv_db_access_error | TYPE E070, " | |||
lv_system_not_configured | TYPE E070. " |
  CALL FUNCTION 'TRINT_MODIFY_DEVCLASS' " |
EXPORTING | ||
IV_ACTION | = lv_iv_action | |
IV_DIALOG | = lv_iv_dialog | |
IS_DEVCLASS | = lv_is_devclass | |
IS_FIELDS_FOR_CHANGE | = lv_is_fields_for_change | |
IV_REQUEST | = lv_iv_request | |
IMPORTING | ||
ES_DEVCLASS | = lv_es_devclass | |
EV_SOMETHING_CHANGED | = lv_ev_something_changed | |
EV_REQUEST | = lv_ev_request | |
EXCEPTIONS | ||
NO_AUTHORIZATION = 1 | ||
INVALID_DEVCLASS = 2 | ||
INVALID_ACTION = 3 | ||
ENQUEUE_FAILED = 4 | ||
DB_ACCESS_ERROR = 5 | ||
SYSTEM_NOT_CONFIGURED = 6 | ||
. " TRINT_MODIFY_DEVCLASS |
ABAP code using 7.40 inline data declarations to call FM TRINT_MODIFY_DEVCLASS
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 UCOMM FROM SY INTO @DATA(ld_iv_action). | ||||
DATA(ld_iv_action) | = 'SHOW'. | |||
"SELECT single FLAG FROM TRPARI INTO @DATA(ld_iv_dialog). | ||||
DATA(ld_iv_dialog) | = 'X'. | |||
"SELECT single FLAG FROM TRPARI INTO @DATA(ld_ev_something_changed). | ||||
"SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_request). | ||||
"SELECT single TRKORR FROM E070 INTO @DATA(ld_iv_request). | ||||
Search for further information about these or an SAP related objects