SAP COM_PME_CLASS_DELETE Function Module for









COM_PME_CLASS_DELETE is a standard com pme class delete 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 class delete FM, simply by entering the name COM_PME_CLASS_DELETE 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_CLASS_DELETE 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_CLASS_DELETE'"
EXPORTING
CRM_HIERARCHY_GUID = "
CRM_OBJECT_GUID = "
* CRM_PARENT_GUID = "
CRM_OBJECT_TYPE = "
PR_ORG_TYPE = "Sales Organization
* PR_ORG_ID = "Distribution Channel
* VALID_ON = SY-DATUM "

IMPORTING
LOCKING_USER = "SAP System, User Logon Name
ES_LOG_MSG = "Application Log: Message Data

EXCEPTIONS
NO_ACTIVE_SESSION = 1 CLASS_NOT_FOUND = 2 FOREIGN_LOCK = 3 CONFLICT = 4 API_ERROR = 5 SYSTEM_ERROR = 6 PME_DATA_NOT_FOUND = 7
.



IMPORTING Parameters details for COM_PME_CLASS_DELETE

CRM_HIERARCHY_GUID -

Data type: COMT_PME_CRM_GUID
Optional: No
Call by Reference: Yes

CRM_OBJECT_GUID -

Data type: COMT_PME_CRM_GUID
Optional: No
Call by Reference: Yes

CRM_PARENT_GUID -

Data type: COMT_PME_CRM_GUID
Optional: Yes
Call by Reference: Yes

CRM_OBJECT_TYPE -

Data type: COMT_PME_CLASS_TYPE
Optional: No
Call by Reference: Yes

PR_ORG_TYPE - Sales Organization

Data type: COMT_PR_ORG_TYPE
Optional: No
Call by Reference: Yes

PR_ORG_ID - Distribution Channel

Data type: COMT_PR_ORG_ID
Optional: Yes
Call by Reference: Yes

VALID_ON -

Data type: D
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for COM_PME_CLASS_DELETE

LOCKING_USER - SAP System, User Logon Name

Data type: SY-UNAME
Optional: No
Call by Reference: Yes

ES_LOG_MSG - Application Log: Message Data

Data type: BAL_S_MSG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_ACTIVE_SESSION -

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

CLASS_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

FOREIGN_LOCK - Class Locked

Data type:
Optional: No
Call by Reference: Yes

CONFLICT -

Data type:
Optional: No
Call by Reference: Yes

API_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_ERROR -

Data type:
Optional: No
Call by Reference: Yes

PME_DATA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for COM_PME_CLASS_DELETE 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_locking_user  TYPE SY-UNAME, "   
lv_no_active_session  TYPE SY, "   
lv_crm_hierarchy_guid  TYPE COMT_PME_CRM_GUID, "   
lv_es_log_msg  TYPE BAL_S_MSG, "   
lv_class_not_found  TYPE BAL_S_MSG, "   
lv_crm_object_guid  TYPE COMT_PME_CRM_GUID, "   
lv_foreign_lock  TYPE COMT_PME_CRM_GUID, "   
lv_crm_parent_guid  TYPE COMT_PME_CRM_GUID, "   
lv_conflict  TYPE COMT_PME_CRM_GUID, "   
lv_crm_object_type  TYPE COMT_PME_CLASS_TYPE, "   
lv_api_error  TYPE COMT_PME_CLASS_TYPE, "   
lv_pr_org_type  TYPE COMT_PR_ORG_TYPE, "   
lv_pr_org_id  TYPE COMT_PR_ORG_ID, "   
lv_system_error  TYPE COMT_PR_ORG_ID, "   
lv_valid_on  TYPE D, "   SY-DATUM
lv_pme_data_not_found  TYPE D. "   

  CALL FUNCTION 'COM_PME_CLASS_DELETE'  "
    EXPORTING
         CRM_HIERARCHY_GUID = lv_crm_hierarchy_guid
         CRM_OBJECT_GUID = lv_crm_object_guid
         CRM_PARENT_GUID = lv_crm_parent_guid
         CRM_OBJECT_TYPE = lv_crm_object_type
         PR_ORG_TYPE = lv_pr_org_type
         PR_ORG_ID = lv_pr_org_id
         VALID_ON = lv_valid_on
    IMPORTING
         LOCKING_USER = lv_locking_user
         ES_LOG_MSG = lv_es_log_msg
    EXCEPTIONS
        NO_ACTIVE_SESSION = 1
        CLASS_NOT_FOUND = 2
        FOREIGN_LOCK = 3
        CONFLICT = 4
        API_ERROR = 5
        SYSTEM_ERROR = 6
        PME_DATA_NOT_FOUND = 7
. " COM_PME_CLASS_DELETE




ABAP code using 7.40 inline data declarations to call FM COM_PME_CLASS_DELETE

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 UNAME FROM SY INTO @DATA(ld_locking_user).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_valid_on) = SY-DATUM.
 
 


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!