SAP TABLE_MARK_SAVE Function Module for









TABLE_MARK_SAVE is a standard table mark save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 table mark save FM, simply by entering the name TABLE_MARK_SAVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SDOS
Program Name: SAPLSDOS
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TABLE_MARK_SAVE 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 'TABLE_MARK_SAVE'"
EXPORTING
* FLG_FIRST_PAGE = ' ' "
* POPUP_ACT_DIAGNOSETEXT3 = ' ' "
* POPUP_ACT_TEXTLINE1 = ' ' "
* POPUP_ACT_TEXTLINE2 = ' ' "
* POPUP_ACT_TITEL = ' ' "
* LIST_TITEL1 = ' ' "List header line 1.
* LIST_TITEL2 = ' ' "List header line 2.
* LIST_TITEL3 = ' ' "List header line 3
* LIST_TITEL4 = ' ' "List header line 4
PF_STATUS = "PF status of the check mark screen
* POPUP_ACT_DEFAULTOPTION = 'N' "
* POPUP_ACT_DIAGNOSETEXT1 = ' ' "
* POPUP_ACT_DIAGNOSETEXT2 = ' ' "

IMPORTING
ACTION = "Action on the selected list entrie

TABLES
WORKTABLE = "Table of the objects to be edited
.



IMPORTING Parameters details for TABLE_MARK_SAVE

FLG_FIRST_PAGE -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

POPUP_ACT_DIAGNOSETEXT3 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

POPUP_ACT_TEXTLINE1 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

POPUP_ACT_TEXTLINE2 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

POPUP_ACT_TITEL -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LIST_TITEL1 - List header line 1.

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LIST_TITEL2 - List header line 2.

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LIST_TITEL3 - List header line 3

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LIST_TITEL4 - List header line 4

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PF_STATUS - PF status of the check mark screen

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

POPUP_ACT_DEFAULTOPTION -

Data type:
Default: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)

POPUP_ACT_DIAGNOSETEXT1 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

POPUP_ACT_DIAGNOSETEXT2 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for TABLE_MARK_SAVE

ACTION - Action on the selected list entrie

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for TABLE_MARK_SAVE

WORKTABLE - Table of the objects to be edited

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for TABLE_MARK_SAVE 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_action  TYPE STRING, "   
lt_worktable  TYPE STANDARD TABLE OF STRING, "   
lv_flg_first_page  TYPE STRING, "   SPACE
lv_popup_act_diagnosetext3  TYPE STRING, "   SPACE
lv_popup_act_textline1  TYPE STRING, "   SPACE
lv_popup_act_textline2  TYPE STRING, "   SPACE
lv_popup_act_titel  TYPE STRING, "   SPACE
lv_list_titel1  TYPE STRING, "   SPACE
lv_list_titel2  TYPE STRING, "   SPACE
lv_list_titel3  TYPE STRING, "   SPACE
lv_list_titel4  TYPE STRING, "   SPACE
lv_pf_status  TYPE STRING, "   
lv_popup_act_defaultoption  TYPE STRING, "   'N'
lv_popup_act_diagnosetext1  TYPE STRING, "   SPACE
lv_popup_act_diagnosetext2  TYPE STRING. "   SPACE

  CALL FUNCTION 'TABLE_MARK_SAVE'  "
    EXPORTING
         FLG_FIRST_PAGE = lv_flg_first_page
         POPUP_ACT_DIAGNOSETEXT3 = lv_popup_act_diagnosetext3
         POPUP_ACT_TEXTLINE1 = lv_popup_act_textline1
         POPUP_ACT_TEXTLINE2 = lv_popup_act_textline2
         POPUP_ACT_TITEL = lv_popup_act_titel
         LIST_TITEL1 = lv_list_titel1
         LIST_TITEL2 = lv_list_titel2
         LIST_TITEL3 = lv_list_titel3
         LIST_TITEL4 = lv_list_titel4
         PF_STATUS = lv_pf_status
         POPUP_ACT_DEFAULTOPTION = lv_popup_act_defaultoption
         POPUP_ACT_DIAGNOSETEXT1 = lv_popup_act_diagnosetext1
         POPUP_ACT_DIAGNOSETEXT2 = lv_popup_act_diagnosetext2
    IMPORTING
         ACTION = lv_action
    TABLES
         WORKTABLE = lt_worktable
. " TABLE_MARK_SAVE




ABAP code using 7.40 inline data declarations to call FM TABLE_MARK_SAVE

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_flg_first_page) = ' '.
 
DATA(ld_popup_act_diagnosetext3) = ' '.
 
DATA(ld_popup_act_textline1) = ' '.
 
DATA(ld_popup_act_textline2) = ' '.
 
DATA(ld_popup_act_titel) = ' '.
 
DATA(ld_list_titel1) = ' '.
 
DATA(ld_list_titel2) = ' '.
 
DATA(ld_list_titel3) = ' '.
 
DATA(ld_list_titel4) = ' '.
 
 
DATA(ld_popup_act_defaultoption) = 'N'.
 
DATA(ld_popup_act_diagnosetext1) = ' '.
 
DATA(ld_popup_act_diagnosetext2) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!