SAP SXMI_XOM_ROMS_DELETE_INT Function Module for









SXMI_XOM_ROMS_DELETE_INT is a standard sxmi xom roms delete int 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 sxmi xom roms delete int FM, simply by entering the name SXMI_XOM_ROMS_DELETE_INT into the relevant SAP transaction such as SE37 or SE38.

Function Group: SXOM
Program Name: SAPLSXOM
Main Program: SAPLSXOM
Appliation area:
Release date: 23-Jan-2003
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SXMI_XOM_ROMS_DELETE_INT 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 'SXMI_XOM_ROMS_DELETE_INT'"
EXPORTING
ROMS = "

EXCEPTIONS
ROMS_UNKNOWN = 1 NOT_AUTHORIZED = 2 LOMS_STILL_EXISTS = 3 IS_LOCKED = 4 DB_OPERATION_FAILED = 5 ROMS_FLUSH_FAILED = 6
.



IMPORTING Parameters details for SXMI_XOM_ROMS_DELETE_INT

ROMS -

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

EXCEPTIONS details

ROMS_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED -

Data type:
Optional: No
Call by Reference: Yes

LOMS_STILL_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

IS_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

DB_OPERATION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

ROMS_FLUSH_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SXMI_XOM_ROMS_DELETE_INT 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_roms  TYPE SEXT_ROMS, "   
lv_roms_unknown  TYPE SEXT_ROMS, "   
lv_not_authorized  TYPE SEXT_ROMS, "   
lv_loms_still_exists  TYPE SEXT_ROMS, "   
lv_is_locked  TYPE SEXT_ROMS, "   
lv_db_operation_failed  TYPE SEXT_ROMS, "   
lv_roms_flush_failed  TYPE SEXT_ROMS. "   

  CALL FUNCTION 'SXMI_XOM_ROMS_DELETE_INT'  "
    EXPORTING
         ROMS = lv_roms
    EXCEPTIONS
        ROMS_UNKNOWN = 1
        NOT_AUTHORIZED = 2
        LOMS_STILL_EXISTS = 3
        IS_LOCKED = 4
        DB_OPERATION_FAILED = 5
        ROMS_FLUSH_FAILED = 6
. " SXMI_XOM_ROMS_DELETE_INT




ABAP code using 7.40 inline data declarations to call FM SXMI_XOM_ROMS_DELETE_INT

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



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!