SAP MMPUR_DELETE_STAT_TRIGGER Function Module for Delete consumed status trigger entry in update task

Search SAP Function Modules

MMPUR_DELETE_STAT_TRIGGER is a standard mmpur delete stat trigger SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete consumed status trigger entry in update task 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 mmpur delete stat trigger FM, simply by entering the name MMPUR_DELETE_STAT_TRIGGER into the relevant SAP transaction such as SE37 or SE38.

Function Group: MMPUR_BTE_5010
Program Name: SAPLMMPUR_BTE_5010
Main Program: SAPLSUGZ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function MMPUR_DELETE_STAT_TRIGGER 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 'MMPUR_DELETE_STAT_TRIGGER'"Delete consumed status trigger entry in update task
  EXPORTING
   IT_STSTRIG_KEY =  "Table of GUID keys from the table STTRIG

.

IMPORTING Parameters details for MMPUR_DELETE_STAT_TRIGGER

IT_STSTRIG_KEY - Table of GUID keys from the table STTRIG

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

Copy and paste ABAP code example for MMPUR_DELETE_STAT_TRIGGER 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.

ABAP code using 7.40 inline data declarations to call FM MMPUR_DELETE_STAT_TRIGGER

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.

Search for further information about these or an SAP related objects