SAP MODEL_ADD_MESSAGE_TYPE_LINK Function Module for Include message type in distribution model
MODEL_ADD_MESSAGE_TYPE_LINK is a standard model add message type link SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Include message type in distribution model 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 model add message type link FM, simply by entering the name MODEL_ADD_MESSAGE_TYPE_LINK into the relevant SAP transaction such as SE37 or SE38.
Function Group: BD22
Program Name: SAPLBD22
Main Program: SAPLBD22
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MODEL_ADD_MESSAGE_TYPE_LINK 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 'MODEL_ADD_MESSAGE_TYPE_LINK'"Include message type in distribution model.
EXPORTING
MLINK = "
TABLES
FILTER = "
EXCEPTIONS
VIEW_NAME_NOT_SPECIFIED = 1 SENDING_SYSTEM_NOT_VALID = 2 RECEIVING_SYSTEM_NOT_VALID = 3 MESSAGE_TYPE_NOT_VALID = 4 MODEL_FOREIGN_LOCK = 5 LINK_ALREADY_EXISTS = 6 VIEW_MAINTENANCE_NOT_ALLOWED = 7 FILTER_DATA_ERROR = 8
IMPORTING Parameters details for MODEL_ADD_MESSAGE_TYPE_LINK
MLINK -
Data type: BDI_MLINKOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MODEL_ADD_MESSAGE_TYPE_LINK
FILTER -
Data type: BDI_MSFLTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
VIEW_NAME_NOT_SPECIFIED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SENDING_SYSTEM_NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RECEIVING_SYSTEM_NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MESSAGE_TYPE_NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MODEL_FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LINK_ALREADY_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
VIEW_MAINTENANCE_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FILTER_DATA_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MODEL_ADD_MESSAGE_TYPE_LINK 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_mlink | TYPE BDI_MLINK, " | |||
| lt_filter | TYPE STANDARD TABLE OF BDI_MSFLT, " | |||
| lv_view_name_not_specified | TYPE BDI_MSFLT, " | |||
| lv_sending_system_not_valid | TYPE BDI_MSFLT, " | |||
| lv_receiving_system_not_valid | TYPE BDI_MSFLT, " | |||
| lv_message_type_not_valid | TYPE BDI_MSFLT, " | |||
| lv_model_foreign_lock | TYPE BDI_MSFLT, " | |||
| lv_link_already_exists | TYPE BDI_MSFLT, " | |||
| lv_view_maintenance_not_allowed | TYPE BDI_MSFLT, " | |||
| lv_filter_data_error | TYPE BDI_MSFLT. " |
|   CALL FUNCTION 'MODEL_ADD_MESSAGE_TYPE_LINK' "Include message type in distribution model |
| EXPORTING | ||
| MLINK | = lv_mlink | |
| TABLES | ||
| FILTER | = lt_filter | |
| EXCEPTIONS | ||
| VIEW_NAME_NOT_SPECIFIED = 1 | ||
| SENDING_SYSTEM_NOT_VALID = 2 | ||
| RECEIVING_SYSTEM_NOT_VALID = 3 | ||
| MESSAGE_TYPE_NOT_VALID = 4 | ||
| MODEL_FOREIGN_LOCK = 5 | ||
| LINK_ALREADY_EXISTS = 6 | ||
| VIEW_MAINTENANCE_NOT_ALLOWED = 7 | ||
| FILTER_DATA_ERROR = 8 | ||
| . " MODEL_ADD_MESSAGE_TYPE_LINK | ||
ABAP code using 7.40 inline data declarations to call FM MODEL_ADD_MESSAGE_TYPE_LINK
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.Search for further information about these or an SAP related objects