SAP SD_POST_GROUP_MESSAGES Function Module for Sperren von Belegen
SD_POST_GROUP_MESSAGES is a standard sd post group messages SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Sperren von Belegen 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 sd post group messages FM, simply by entering the name SD_POST_GROUP_MESSAGES into the relevant SAP transaction such as SE37 or SE38.
Function Group: V53S
Program Name: SAPLV53S
Main Program: SAPLV53S
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_POST_GROUP_MESSAGES 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 'SD_POST_GROUP_MESSAGES'"Sperren von Belegen.
EXPORTING
IS_VBSK = "
* IF_COMMIT = ' ' "
* IF_MSG_NO_UPDATE_TASK = ' ' "
IMPORTING Parameters details for SD_POST_GROUP_MESSAGES
IS_VBSK -
Data type: VBSKOptional: No
Call by Reference: Yes
IF_COMMIT -
Data type: RV50A-LIPS_SELKZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IF_MSG_NO_UPDATE_TASK -
Data type: RV50A-LIPS_SELKZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_POST_GROUP_MESSAGES 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_is_vbsk | TYPE VBSK, " | |||
| lv_if_commit | TYPE RV50A-LIPS_SELKZ, " SPACE | |||
| lv_if_msg_no_update_task | TYPE RV50A-LIPS_SELKZ. " SPACE |
|   CALL FUNCTION 'SD_POST_GROUP_MESSAGES' "Sperren von Belegen |
| EXPORTING | ||
| IS_VBSK | = lv_is_vbsk | |
| IF_COMMIT | = lv_if_commit | |
| IF_MSG_NO_UPDATE_TASK | = lv_if_msg_no_update_task | |
| . " SD_POST_GROUP_MESSAGES | ||
ABAP code using 7.40 inline data declarations to call FM SD_POST_GROUP_MESSAGES
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 LIPS_SELKZ FROM RV50A INTO @DATA(ld_if_commit). | ||||
| DATA(ld_if_commit) | = ' '. | |||
| "SELECT single LIPS_SELKZ FROM RV50A INTO @DATA(ld_if_msg_no_update_task). | ||||
| DATA(ld_if_msg_no_update_task) | = ' '. | |||
Search for further information about these or an SAP related objects