SAP RHOM_CHECK_DELETE Function Module for









RHOM_CHECK_DELETE is a standard rhom check 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 rhom check delete FM, simply by entering the name RHOM_CHECK_DELETE into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHOM_OBJECTS_CREATE
Program Name: SAPLRHOM_OBJECTS_CREATE
Main Program: SAPLRHOM_OBJECTS_CREATE
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RHOM_CHECK_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 'RHOM_CHECK_DELETE'"
  EXPORTING
*  TERMINATION_BEGDA = SY-DATUM "
*  TERMINATION_ENDDA = HIGH_DATE "
*  PLVAR =  "
*  OTYPE = 'O ' "
   OBJID =  "
*  DELETE_COMPLETE = 'X' "General Flag

 IMPORTING
   ACT_PLVAR =  "
   FIRST_FOUND_OBJECT =  "

EXCEPTIONS
   FORBIDDEN_OTYPE = 1    OBJECT_NOT_FOUND = 2    OBJECT_NOT_EMPTY = 3    NO_PLVAR_FOUND = 4    NO_EXTENSION_OF_ENDDA = 5    OUT_OF_VALID_PERIOD = 6    GENERAL_ERROR = 7    PROHIBITED_BY_BADI = 8
.



IMPORTING Parameters details for RHOM_CHECK_DELETE

TERMINATION_BEGDA -

Data type: DATS
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

TERMINATION_ENDDA -

Data type: DATS
Default: HIGH_DATE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PLVAR -

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

OTYPE -

Data type: OTYPE
Default: 'O '
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJID -

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

DELETE_COMPLETE - General Flag

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RHOM_CHECK_DELETE

ACT_PLVAR -

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

FIRST_FOUND_OBJECT -

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

EXCEPTIONS details

FORBIDDEN_OTYPE -

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

OBJECT_NOT_FOUND -

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

OBJECT_NOT_EMPTY -

Data type:
Optional: No
Call by Reference: Yes

NO_PLVAR_FOUND -

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

NO_EXTENSION_OF_ENDDA -

Data type:
Optional: No
Call by Reference: Yes

OUT_OF_VALID_PERIOD -

Data type:
Optional: No
Call by Reference: Yes

GENERAL_ERROR -

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

PROHIBITED_BY_BADI -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RHOM_CHECK_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_act_plvar  TYPE PLVAR, "   
lv_forbidden_otype  TYPE PLVAR, "   
lv_termination_begda  TYPE DATS, "   SY-DATUM
lv_object_not_found  TYPE DATS, "   
lv_termination_endda  TYPE DATS, "   HIGH_DATE
lv_first_found_object  TYPE OBJEC, "   
lv_plvar  TYPE PLVAR, "   
lv_object_not_empty  TYPE PLVAR, "   
lv_otype  TYPE OTYPE, "   'O '
lv_no_plvar_found  TYPE OTYPE, "   
lv_objid  TYPE OTYPE, "   
lv_no_extension_of_endda  TYPE OTYPE, "   
lv_delete_complete  TYPE FLAG, "   'X'
lv_out_of_valid_period  TYPE FLAG, "   
lv_general_error  TYPE FLAG, "   
lv_prohibited_by_badi  TYPE FLAG. "   

  CALL FUNCTION 'RHOM_CHECK_DELETE'  "
    EXPORTING
         TERMINATION_BEGDA = lv_termination_begda
         TERMINATION_ENDDA = lv_termination_endda
         PLVAR = lv_plvar
         OTYPE = lv_otype
         OBJID = lv_objid
         DELETE_COMPLETE = lv_delete_complete
    IMPORTING
         ACT_PLVAR = lv_act_plvar
         FIRST_FOUND_OBJECT = lv_first_found_object
    EXCEPTIONS
        FORBIDDEN_OTYPE = 1
        OBJECT_NOT_FOUND = 2
        OBJECT_NOT_EMPTY = 3
        NO_PLVAR_FOUND = 4
        NO_EXTENSION_OF_ENDDA = 5
        OUT_OF_VALID_PERIOD = 6
        GENERAL_ERROR = 7
        PROHIBITED_BY_BADI = 8
. " RHOM_CHECK_DELETE




ABAP code using 7.40 inline data declarations to call FM RHOM_CHECK_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_termination_begda) = SY-DATUM.
 
 
DATA(ld_termination_endda) = HIGH_DATE.
 
 
 
 
DATA(ld_otype) = 'O '.
 
 
 
 
DATA(ld_delete_complete) = 'X'.
 
 
 
 


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!