SAP MESSAGE_CHECK_TECHNICAL_DATA Function Module for
MESSAGE_CHECK_TECHNICAL_DATA is a standard message check technical data 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 message check technical data FM, simply by entering the name MESSAGE_CHECK_TECHNICAL_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: BDCH
Program Name: SAPLBDCH
Main Program: SAPLBDCH
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function MESSAGE_CHECK_TECHNICAL_DATA 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 'MESSAGE_CHECK_TECHNICAL_DATA'".
EXPORTING
MESSAGE_TYPE = "
MESSAGE_CODE = "
MESSAGE_FUNCTION = "
RECEIVING_SYSTEM = "
* MODEL_VALID_DATE = SY-DATUM "
* CROSS_SYSTEM_CHECK = ' ' "
TABLES
T_CHECK_LOG = "
T_SYNCH = "
EXCEPTIONS
CHECK_STOP = 1
IMPORTING Parameters details for MESSAGE_CHECK_TECHNICAL_DATA
MESSAGE_TYPE -
Data type: EDIDC-MESTYPOptional: No
Call by Reference: No ( called with pass by value option)
MESSAGE_CODE -
Data type: EDIDC-MESCODOptional: No
Call by Reference: No ( called with pass by value option)
MESSAGE_FUNCTION -
Data type: EDIDC-MESFCTOptional: No
Call by Reference: No ( called with pass by value option)
RECEIVING_SYSTEM -
Data type: TBDLS-LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
MODEL_VALID_DATE -
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
CROSS_SYSTEM_CHECK -
Data type: TBDA1-ACTIVEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MESSAGE_CHECK_TECHNICAL_DATA
T_CHECK_LOG -
Data type: BDI_LOGOptional: No
Call by Reference: No ( called with pass by value option)
T_SYNCH -
Data type: BDI_SYNCHOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CHECK_STOP -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MESSAGE_CHECK_TECHNICAL_DATA 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_check_stop | TYPE STRING, " | |||
lt_t_check_log | TYPE STANDARD TABLE OF BDI_LOG, " | |||
lv_message_type | TYPE EDIDC-MESTYP, " | |||
lt_t_synch | TYPE STANDARD TABLE OF BDI_SYNCH, " | |||
lv_message_code | TYPE EDIDC-MESCOD, " | |||
lv_message_function | TYPE EDIDC-MESFCT, " | |||
lv_receiving_system | TYPE TBDLS-LOGSYS, " | |||
lv_model_valid_date | TYPE SY-DATUM, " SY-DATUM | |||
lv_cross_system_check | TYPE TBDA1-ACTIVE. " SPACE |
  CALL FUNCTION 'MESSAGE_CHECK_TECHNICAL_DATA' " |
EXPORTING | ||
MESSAGE_TYPE | = lv_message_type | |
MESSAGE_CODE | = lv_message_code | |
MESSAGE_FUNCTION | = lv_message_function | |
RECEIVING_SYSTEM | = lv_receiving_system | |
MODEL_VALID_DATE | = lv_model_valid_date | |
CROSS_SYSTEM_CHECK | = lv_cross_system_check | |
TABLES | ||
T_CHECK_LOG | = lt_t_check_log | |
T_SYNCH | = lt_t_synch | |
EXCEPTIONS | ||
CHECK_STOP = 1 | ||
. " MESSAGE_CHECK_TECHNICAL_DATA |
ABAP code using 7.40 inline data declarations to call FM MESSAGE_CHECK_TECHNICAL_DATA
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 MESTYP FROM EDIDC INTO @DATA(ld_message_type). | ||||
"SELECT single MESCOD FROM EDIDC INTO @DATA(ld_message_code). | ||||
"SELECT single MESFCT FROM EDIDC INTO @DATA(ld_message_function). | ||||
"SELECT single LOGSYS FROM TBDLS INTO @DATA(ld_receiving_system). | ||||
"SELECT single DATUM FROM SY INTO @DATA(ld_model_valid_date). | ||||
DATA(ld_model_valid_date) | = SY-DATUM. | |||
"SELECT single ACTIVE FROM TBDA1 INTO @DATA(ld_cross_system_check). | ||||
DATA(ld_cross_system_check) | = ' '. | |||
Search for further information about these or an SAP related objects