SAP RPM_DROP_DATA Function Module for Delete RPM Matrixes
RPM_DROP_DATA is a standard rpm drop data 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 RPM Matrixes 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 rpm drop data FM, simply by entering the name RPM_DROP_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPM_LCC_LCCHECK
Program Name: SAPLRPM_LCC_LCCHECK
Main Program: SAPLRPM_LCC_LCCHECK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RPM_DROP_DATA 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 'RPM_DROP_DATA'"Delete RPM Matrixes.
EXPORTING
IV_SIMVERSION = "Name of Planning Version
* IV_RPMSESSION = "Flag for Temporary Planning Data
IT_TRPID = "Table of GUIDs for IPPE Objects
EXCEPTIONS
ERROR_DELETE_MATRIX = 1
IMPORTING Parameters details for RPM_DROP_DATA
IV_SIMVERSION - Name of Planning Version
Data type: /SAPAPO/OM_VRSIOIDOptional: No
Call by Reference: Yes
IV_RPMSESSION - Flag for Temporary Planning Data
Data type: RPM_SESSIONOptional: Yes
Call by Reference: Yes
IT_TRPID - Table of GUIDs for IPPE Objects
Data type: /SAPAPO/OM_IPPE_ID_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_DELETE_MATRIX -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RPM_DROP_DATA 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_iv_simversion | TYPE /SAPAPO/OM_VRSIOID, " | |||
| lv_error_delete_matrix | TYPE /SAPAPO/OM_VRSIOID, " | |||
| lv_iv_rpmsession | TYPE RPM_SESSION, " | |||
| lv_it_trpid | TYPE /SAPAPO/OM_IPPE_ID_TAB. " |
|   CALL FUNCTION 'RPM_DROP_DATA' "Delete RPM Matrixes |
| EXPORTING | ||
| IV_SIMVERSION | = lv_iv_simversion | |
| IV_RPMSESSION | = lv_iv_rpmsession | |
| IT_TRPID | = lv_it_trpid | |
| EXCEPTIONS | ||
| ERROR_DELETE_MATRIX = 1 | ||
| . " RPM_DROP_DATA | ||
ABAP code using 7.40 inline data declarations to call FM RPM_DROP_DATA
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