COM_PME_MAP_MUST_SAVE SAP Function module

COM_PME_MAP_MUST_SAVE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name COM_PME_MAP_MUST_SAVE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: COM_PME_CRM_MAP
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM COM_PME_MAP_MUST_SAVE - COM PME MAP MUST SAVE

CALL FUNCTION 'COM_PME_MAP_MUST_SAVE' "
  IMPORTING
    must_save =                 " c
    .  "  COM_PME_MAP_MUST_SAVE

ABAP code example for Function Module COM_PME_MAP_MUST_SAVE

The ABAP code below is a full code listing to execute function module COM_PME_MAP_MUST_SAVE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_must_save  
 
 TYPE C
.

CALL FUNCTION 'COM_PME_MAP_MUST_SAVE'
  IMPORTING
    must_save =                  ld_must_save
    .  "  COM_PME_MAP_MUST_SAVE

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_must_save
 
 TYPE C .