SAP DMULI_DMUPOB_DELETE Function Module for NOTRANSL: DMU-Positionsobjekt löschen
DMULI_DMUPOB_DELETE is a standard dmuli dmupob delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: DMU-Positionsobjekt löschen 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 dmuli dmupob delete FM, simply by entering the name DMULI_DMUPOB_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: DMULI
Program Name: SAPLDMULI
Main Program: SAPLDMULI
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DMULI_DMUPOB_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 'DMULI_DMUPOB_DELETE'"NOTRANSL: DMU-Positionsobjekt löschen.
EXPORTING
* IM_MSG_HANDLING = 'A' "Generic Type
IM_DMUPOB = "
EXCEPTIONS
UNDEFINED_DMUPOB_KEY = 1 DMUPOB_DOES_NOT_EXIST = 2
IMPORTING Parameters details for DMULI_DMUPOB_DELETE
IM_MSG_HANDLING - Generic Type
Data type: CDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_DMUPOB -
Data type: DMUT_DMUPOB_LIOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UNDEFINED_DMUPOB_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DMUPOB_DOES_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DMULI_DMUPOB_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_im_msg_handling | TYPE C, " 'A' | |||
| lv_undefined_dmupob_key | TYPE C, " | |||
| lv_im_dmupob | TYPE DMUT_DMUPOB_LI, " | |||
| lv_dmupob_does_not_exist | TYPE DMUT_DMUPOB_LI. " |
|   CALL FUNCTION 'DMULI_DMUPOB_DELETE' "NOTRANSL: DMU-Positionsobjekt löschen |
| EXPORTING | ||
| IM_MSG_HANDLING | = lv_im_msg_handling | |
| IM_DMUPOB | = lv_im_dmupob | |
| EXCEPTIONS | ||
| UNDEFINED_DMUPOB_KEY = 1 | ||
| DMUPOB_DOES_NOT_EXIST = 2 | ||
| . " DMULI_DMUPOB_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM DMULI_DMUPOB_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.| DATA(ld_im_msg_handling) | = 'A'. | |||
Search for further information about these or an SAP related objects