SAP RM_DOCUMENT_LOG_ALV Function Module for NOTRANSL: Anzeige des Belegprotokolls / Stornierung
RM_DOCUMENT_LOG_ALV is a standard rm document log alv SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Anzeige des Belegprotokolls / Stornierung 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 rm document log alv FM, simply by entering the name RM_DOCUMENT_LOG_ALV into the relevant SAP transaction such as SE37 or SE38.
Function Group: BARM
Program Name: SAPLBARM
Main Program: SAPLBARM
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_DOCUMENT_LOG_ALV 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 'RM_DOCUMENT_LOG_ALV'"NOTRANSL: Anzeige des Belegprotokolls / Stornierung.
EXPORTING
* BY_MF41 = ' ' "
* STORNODATUM = SY-DATLO "
* MAX_RECORDS = 800 "
* IV_NO_ALV = "New Input Values
IMPORTING
ET_BLPK = "
ET_BLPP = "
TABLES
* T_SO_WERKS = "Plant
* T_SO_STORN = "Cancellation ID
* T_SO_UNAME = "User Name
* T_SO_VORNE = "RP Number
* T_SO_OBNUM = "
* T_SO_WAKZH = "GI in Background
* T_SO_FLKZH = "
* T_SO_KAPKZH = "
* T_SO_PRTNR = "Document log number
* T_SO_REPTP = "Production Type
* T_SO_VAART = "
* T_SO_MATNR = "Material Number
* T_SO_VERID = "Production Version
* T_SO_BUDAT = "Posting Date
* T_SO_DATUM = "Entry Date
* T_SO_KDAUF = "Sales Order Number
* T_SO_KDPOS = "Sales order item
* T_SO_PKNUM = "Control Cycle Number
* T_SO_PKPOS = "Kanban
EXCEPTIONS
NO_ENTRIES = 1 TOO_MANY_ENTRIES = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLBARM_001 Customer Exit: RM_BACKFLUSH_CHECK
EXIT_SAPLBARM_002 Customer Exit: RM_BACKFLUSH_GO
EXIT_SAPLBARM_003 Customer Exit: RM_CANCEL_BACKFLUSH_CHECK
EXIT_SAPLBARM_004 Customer Exit: RM_CANCEL_BACKFLUSH_GO
IMPORTING Parameters details for RM_DOCUMENT_LOG_ALV
BY_MF41 -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
STORNODATUM -
Data type: BLPK-BUDATDefault: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)
MAX_RECORDS -
Data type: IDefault: 800
Optional: Yes
Call by Reference: Yes
IV_NO_ALV - New Input Values
Data type: XFLAGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RM_DOCUMENT_LOG_ALV
ET_BLPK -
Data type: BFALV_BLPKOptional: No
Call by Reference: Yes
ET_BLPP -
Data type: BFALV_BLPPOptional: No
Call by Reference: Yes
TABLES Parameters details for RM_DOCUMENT_LOG_ALV
T_SO_WERKS - Plant
Data type: RMPO_TYPE_TAB_WERKSOptional: Yes
Call by Reference: Yes
T_SO_STORN - Cancellation ID
Data type: RMPO_TYPE_TAB_STORNOptional: Yes
Call by Reference: Yes
T_SO_UNAME - User Name
Data type: RMPO_TYPE_TAB_UNAMEOptional: Yes
Call by Reference: Yes
T_SO_VORNE - RP Number
Data type: RMPO_TYPE_TAB_VORNEOptional: Yes
Call by Reference: Yes
T_SO_OBNUM -
Data type: RMPO_TYPE_TAB_OBNUMOptional: Yes
Call by Reference: Yes
T_SO_WAKZH - GI in Background
Data type: RMPO_TYPE_TAB_WAKZHOptional: Yes
Call by Reference: Yes
T_SO_FLKZH -
Data type: RMPO_TYPE_TAB_FLKZHOptional: Yes
Call by Reference: Yes
T_SO_KAPKZH -
Data type: RMPO_TYPE_TAB_KAPKZHOptional: Yes
Call by Reference: Yes
T_SO_PRTNR - Document log number
Data type: RMPO_TYPE_TAB_PRTNROptional: Yes
Call by Reference: Yes
T_SO_REPTP - Production Type
Data type: RMPO_TYPE_TAB_REPTPOptional: Yes
Call by Reference: Yes
T_SO_VAART -
Data type: RMPO_TYPE_TAB_VAARTOptional: Yes
Call by Reference: No ( called with pass by value option)
T_SO_MATNR - Material Number
Data type: RMPO_TYPE_TAB_MATNROptional: Yes
Call by Reference: Yes
T_SO_VERID - Production Version
Data type: RMPO_TYPE_TAB_VERIDOptional: Yes
Call by Reference: Yes
T_SO_BUDAT - Posting Date
Data type: RMPO_TYPE_TAB_BUDATOptional: Yes
Call by Reference: Yes
T_SO_DATUM - Entry Date
Data type: RMPO_TYPE_TAB_DATUMOptional: Yes
Call by Reference: Yes
T_SO_KDAUF - Sales Order Number
Data type: RMPO_TYPE_TAB_KDAUFOptional: Yes
Call by Reference: Yes
T_SO_KDPOS - Sales order item
Data type: RMPO_TYPE_TAB_KDPOSOptional: Yes
Call by Reference: Yes
T_SO_PKNUM - Control Cycle Number
Data type: RMPO_TYPE_TAB_PKNUMOptional: Yes
Call by Reference: Yes
T_SO_PKPOS - Kanban
Data type: RMPO_TYPE_TAB_PKPOSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRIES -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TOO_MANY_ENTRIES -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RM_DOCUMENT_LOG_ALV 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_by_mf41 | TYPE C, " SPACE | |||
| lv_et_blpk | TYPE BFALV_BLPK, " | |||
| lv_no_entries | TYPE BFALV_BLPK, " | |||
| lt_t_so_werks | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_WERKS, " | |||
| lt_t_so_storn | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_STORN, " | |||
| lt_t_so_uname | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_UNAME, " | |||
| lt_t_so_vorne | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_VORNE, " | |||
| lt_t_so_obnum | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_OBNUM, " | |||
| lt_t_so_wakzh | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_WAKZH, " | |||
| lt_t_so_flkzh | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_FLKZH, " | |||
| lt_t_so_kapkzh | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_KAPKZH, " | |||
| lt_t_so_prtnr | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_PRTNR, " | |||
| lt_t_so_reptp | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_REPTP, " | |||
| lt_t_so_vaart | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_VAART, " | |||
| lv_et_blpp | TYPE BFALV_BLPP, " | |||
| lt_t_so_matnr | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_MATNR, " | |||
| lv_stornodatum | TYPE BLPK-BUDAT, " SY-DATLO | |||
| lv_too_many_entries | TYPE BLPK, " | |||
| lt_t_so_verid | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_VERID, " | |||
| lv_max_records | TYPE I, " 800 | |||
| lv_iv_no_alv | TYPE XFLAG, " | |||
| lt_t_so_budat | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_BUDAT, " | |||
| lt_t_so_datum | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_DATUM, " | |||
| lt_t_so_kdauf | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_KDAUF, " | |||
| lt_t_so_kdpos | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_KDPOS, " | |||
| lt_t_so_pknum | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_PKNUM, " | |||
| lt_t_so_pkpos | TYPE STANDARD TABLE OF RMPO_TYPE_TAB_PKPOS. " |
|   CALL FUNCTION 'RM_DOCUMENT_LOG_ALV' "NOTRANSL: Anzeige des Belegprotokolls / Stornierung |
| EXPORTING | ||
| BY_MF41 | = lv_by_mf41 | |
| STORNODATUM | = lv_stornodatum | |
| MAX_RECORDS | = lv_max_records | |
| IV_NO_ALV | = lv_iv_no_alv | |
| IMPORTING | ||
| ET_BLPK | = lv_et_blpk | |
| ET_BLPP | = lv_et_blpp | |
| TABLES | ||
| T_SO_WERKS | = lt_t_so_werks | |
| T_SO_STORN | = lt_t_so_storn | |
| T_SO_UNAME | = lt_t_so_uname | |
| T_SO_VORNE | = lt_t_so_vorne | |
| T_SO_OBNUM | = lt_t_so_obnum | |
| T_SO_WAKZH | = lt_t_so_wakzh | |
| T_SO_FLKZH | = lt_t_so_flkzh | |
| T_SO_KAPKZH | = lt_t_so_kapkzh | |
| T_SO_PRTNR | = lt_t_so_prtnr | |
| T_SO_REPTP | = lt_t_so_reptp | |
| T_SO_VAART | = lt_t_so_vaart | |
| T_SO_MATNR | = lt_t_so_matnr | |
| T_SO_VERID | = lt_t_so_verid | |
| T_SO_BUDAT | = lt_t_so_budat | |
| T_SO_DATUM | = lt_t_so_datum | |
| T_SO_KDAUF | = lt_t_so_kdauf | |
| T_SO_KDPOS | = lt_t_so_kdpos | |
| T_SO_PKNUM | = lt_t_so_pknum | |
| T_SO_PKPOS | = lt_t_so_pkpos | |
| EXCEPTIONS | ||
| NO_ENTRIES = 1 | ||
| TOO_MANY_ENTRIES = 2 | ||
| . " RM_DOCUMENT_LOG_ALV | ||
ABAP code using 7.40 inline data declarations to call FM RM_DOCUMENT_LOG_ALV
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.| DATA(ld_by_mf41) | = ' '. | |||
| "SELECT single BUDAT FROM BLPK INTO @DATA(ld_stornodatum). | ||||
| DATA(ld_stornodatum) | = SY-DATLO. | |||
| DATA(ld_max_records) | = 800. | |||
Search for further information about these or an SAP related objects