SAP UBC_CE_DELETE Function Module for









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

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



Function UBC_CE_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 'UBC_CE_DELETE'"
EXPORTING
* I_CHECK = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

TABLES
IT_CEDATA = "Cost Events

EXCEPTIONS
WRONG_STATUS = 1
.



IMPORTING Parameters details for UBC_CE_DELETE

I_CHECK - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for UBC_CE_DELETE

IT_CEDATA - Cost Events

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

EXCEPTIONS details

WRONG_STATUS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UBC_CE_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_i_check  TYPE BOOLE-BOOLE, "   
lt_it_cedata  TYPE STANDARD TABLE OF UBC_TB_CEDATA, "   
lv_wrong_status  TYPE UBC_TB_CEDATA. "   

  CALL FUNCTION 'UBC_CE_DELETE'  "
    EXPORTING
         I_CHECK = lv_i_check
    TABLES
         IT_CEDATA = lt_it_cedata
    EXCEPTIONS
        WRONG_STATUS = 1
. " UBC_CE_DELETE




ABAP code using 7.40 inline data declarations to call FM UBC_CE_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.

"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_check).
 
 
 


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!