SAP RSDU_DIMTAB_EXIT_ORA Function Module for Exit that will be called after the creation of dimension tables









RSDU_DIMTAB_EXIT_ORA is a standard rsdu dimtab exit ora SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Exit that will be called after the creation of dimension tables 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 rsdu dimtab exit ora FM, simply by entering the name RSDU_DIMTAB_EXIT_ORA into the relevant SAP transaction such as SE37 or SE38.

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



Function RSDU_DIMTAB_EXIT_ORA 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 'RSDU_DIMTAB_EXIT_ORA'"Exit that will be called after the creation of dimension tables
EXPORTING
I_TABLNM = "Table Name
I_CALLER = "Calling Program

CHANGING
* C_PROCESSED = RS_C_FALSE "Boolean

EXCEPTIONS
NOT_FOUND = 1 INHERITED_ERROR = 2
.



IMPORTING Parameters details for RSDU_DIMTAB_EXIT_ORA

I_TABLNM - Table Name

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

I_CALLER - Calling Program

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

CHANGING Parameters details for RSDU_DIMTAB_EXIT_ORA

C_PROCESSED - Boolean

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

EXCEPTIONS details

NOT_FOUND - Transferred table was not found

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

INHERITED_ERROR -

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

Copy and paste ABAP code example for RSDU_DIMTAB_EXIT_ORA 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_tablnm  TYPE RSD_TABLNM, "   
lv_not_found  TYPE RSD_TABLNM, "   
lv_c_processed  TYPE RS_BOOL, "   RS_C_FALSE
lv_i_caller  TYPE RSDU_FUNCTION, "   
lv_inherited_error  TYPE RSDU_FUNCTION. "   

  CALL FUNCTION 'RSDU_DIMTAB_EXIT_ORA'  "Exit that will be called after the creation of dimension tables
    EXPORTING
         I_TABLNM = lv_i_tablnm
         I_CALLER = lv_i_caller
    CHANGING
         C_PROCESSED = lv_c_processed
    EXCEPTIONS
        NOT_FOUND = 1
        INHERITED_ERROR = 2
. " RSDU_DIMTAB_EXIT_ORA




ABAP code using 7.40 inline data declarations to call FM RSDU_DIMTAB_EXIT_ORA

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_c_processed) = RS_C_FALSE.
 
 
 


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!