SAP COM_PME_SESSION_SAVE Function Module for
COM_PME_SESSION_SAVE is a standard com pme session 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 com pme session save FM, simply by entering the name COM_PME_SESSION_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_PME_SV
Program Name: SAPLCOM_PME_SV
Main Program: SAPLCOM_PME_SV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COM_PME_SESSION_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 'COM_PME_SESSION_SAVE'".
EXPORTING
CRM_HIERARCHY_GUID = "
* I_UPDATE_TASK = ' ' "
IMPORTING
ES_LOG_MSG = "Application Log: Message Data
EXCEPTIONS
NO_ACTIVE_SESSION = 1 API_ERROR = 2
IMPORTING Parameters details for COM_PME_SESSION_SAVE
CRM_HIERARCHY_GUID -
Data type: COMT_PME_CRM_GUIDOptional: No
Call by Reference: Yes
I_UPDATE_TASK -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for COM_PME_SESSION_SAVE
ES_LOG_MSG - Application Log: Message Data
Data type: BAL_S_MSGOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ACTIVE_SESSION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
API_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for COM_PME_SESSION_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_es_log_msg | TYPE BAL_S_MSG, " | |||
| lv_no_active_session | TYPE BAL_S_MSG, " | |||
| lv_crm_hierarchy_guid | TYPE COMT_PME_CRM_GUID, " | |||
| lv_api_error | TYPE COMT_PME_CRM_GUID, " | |||
| lv_i_update_task | TYPE C. " SPACE |
|   CALL FUNCTION 'COM_PME_SESSION_SAVE' " |
| EXPORTING | ||
| CRM_HIERARCHY_GUID | = lv_crm_hierarchy_guid | |
| I_UPDATE_TASK | = lv_i_update_task | |
| IMPORTING | ||
| ES_LOG_MSG | = lv_es_log_msg | |
| EXCEPTIONS | ||
| NO_ACTIVE_SESSION = 1 | ||
| API_ERROR = 2 | ||
| . " COM_PME_SESSION_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM COM_PME_SESSION_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_i_update_task) | = ' '. | |||
Search for further information about these or an SAP related objects