SAP MESSAGE_TYPES_READ_OUTBOUND Function Module for Get possible outbound message types for object
MESSAGE_TYPES_READ_OUTBOUND is a standard message types read outbound SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get possible outbound message types for object 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 message types read outbound FM, simply by entering the name MESSAGE_TYPES_READ_OUTBOUND into the relevant SAP transaction such as SE37 or SE38.
Function Group: BD15
Program Name: SAPLBD15
Main Program: SAPLBD15
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MESSAGE_TYPES_READ_OUTBOUND 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_TYPES_READ_OUTBOUND'"Get possible outbound message types for object.
EXPORTING
OBJECT_TYPE = "Object type read when IDOC arrives
TABLES
MESSAGE_TYPES = "Possible message types for object type
IMPORTING Parameters details for MESSAGE_TYPES_READ_OUTBOUND
OBJECT_TYPE - Object type read when IDOC arrives
Data type: SWOTBASDAT-OBJTYPEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MESSAGE_TYPES_READ_OUTBOUND
MESSAGE_TYPES - Possible message types for object type
Data type: MESTYPESIFOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MESSAGE_TYPES_READ_OUTBOUND 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_object_type | TYPE SWOTBASDAT-OBJTYPE, " | |||
| lt_message_types | TYPE STANDARD TABLE OF MESTYPESIF. " |
|   CALL FUNCTION 'MESSAGE_TYPES_READ_OUTBOUND' "Get possible outbound message types for object |
| EXPORTING | ||
| OBJECT_TYPE | = lv_object_type | |
| TABLES | ||
| MESSAGE_TYPES | = lt_message_types | |
| . " MESSAGE_TYPES_READ_OUTBOUND | ||
ABAP code using 7.40 inline data declarations to call FM MESSAGE_TYPES_READ_OUTBOUND
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 OBJTYPE FROM SWOTBASDAT INTO @DATA(ld_object_type). | ||||
Search for further information about these or an SAP related objects