SAP IDOC_GET_MESSAGE_ATTRIBUTE Function Module for Get short of message of current IDoc status record
IDOC_GET_MESSAGE_ATTRIBUTE is a standard idoc get message attribute 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 short of message of current IDoc status record 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 idoc get message attribute FM, simply by entering the name IDOC_GET_MESSAGE_ATTRIBUTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BDID
Program Name: SAPLBDID
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IDOC_GET_MESSAGE_ATTRIBUTE 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 'IDOC_GET_MESSAGE_ATTRIBUTE'"Get short of message of current IDoc status record.
EXPORTING
IDOC_NUMBER = "
IMPORTING
IDOC_MESSAGE = "Message text
IMPORTING Parameters details for IDOC_GET_MESSAGE_ATTRIBUTE
IDOC_NUMBER -
Data type: EDIDC-DOCNUMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for IDOC_GET_MESSAGE_ATTRIBUTE
IDOC_MESSAGE - Message text
Data type: BDIDOCATTR-MESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IDOC_GET_MESSAGE_ATTRIBUTE 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_idoc_number | TYPE EDIDC-DOCNUM, " | |||
| lv_idoc_message | TYPE BDIDOCATTR-MESSAGE. " |
|   CALL FUNCTION 'IDOC_GET_MESSAGE_ATTRIBUTE' "Get short of message of current IDoc status record |
| EXPORTING | ||
| IDOC_NUMBER | = lv_idoc_number | |
| IMPORTING | ||
| IDOC_MESSAGE | = lv_idoc_message | |
| . " IDOC_GET_MESSAGE_ATTRIBUTE | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_GET_MESSAGE_ATTRIBUTE
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 DOCNUM FROM EDIDC INTO @DATA(ld_idoc_number). | ||||
| "SELECT single MESSAGE FROM BDIDOCATTR INTO @DATA(ld_idoc_message). | ||||
Search for further information about these or an SAP related objects