SAP RSDU_ODS_PART_INSTANTIATE_DB4 Function Module for Creates Database-Dependent Partition Properties in the SAP-DD









RSDU_ODS_PART_INSTANTIATE_DB4 is a standard rsdu ods part instantiate db4 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Creates Database-Dependent Partition Properties in the SAP-DD 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 ods part instantiate db4 FM, simply by entering the name RSDU_ODS_PART_INSTANTIATE_DB4 into the relevant SAP transaction such as SE37 or SE38.

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



Function RSDU_ODS_PART_INSTANTIATE_DB4 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_ODS_PART_INSTANTIATE_DB4'"Creates Database-Dependent Partition Properties in the SAP-DD
EXPORTING
I_ODSOBJECT = "Technical name of ODS Object
I_TABT = "Table type of ODS table
I_TABLNM = "ODS - Table Name
I_T_KEY = "Names of Key Fields
* I_PART_TYPE = RSDU_C_PARTYPE-HASH "
I_T_MDC_IOBJ = "InfoObjects for MD Clustering
I_ODSOTYPE = "ODS Object Type

IMPORTING
E_PROCESSED = "Boolean

EXCEPTIONS
ODS_INSTANTIATE_FAILED = 1 NO_KEY_FIELD = 2
.



IMPORTING Parameters details for RSDU_ODS_PART_INSTANTIATE_DB4

I_ODSOBJECT - Technical name of ODS Object

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

I_TABT - Table type of ODS table

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

I_TABLNM - ODS - Table Name

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

I_T_KEY - Names of Key Fields

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

I_PART_TYPE -

Data type: RSDU_PARTYPE
Default: RSDU_C_PARTYPE-HASH
Optional: No
Call by Reference: Yes

I_T_MDC_IOBJ - InfoObjects for MD Clustering

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

I_ODSOTYPE - ODS Object Type

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

EXPORTING Parameters details for RSDU_ODS_PART_INSTANTIATE_DB4

E_PROCESSED - Boolean

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

EXCEPTIONS details

ODS_INSTANTIATE_FAILED - ERROR writing DDSTORAGE ENTRIES

Data type:
Optional: No
Call by Reference: Yes

NO_KEY_FIELD - Partitioning key is no field of the technical key

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSDU_ODS_PART_INSTANTIATE_DB4 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_e_processed  TYPE RS_BOOL, "   
lv_i_odsobject  TYPE RSDODSOBJECT, "   
lv_ods_instantiate_failed  TYPE RSDODSOBJECT, "   
lv_i_tabt  TYPE RSDODSTABT, "   
lv_no_key_field  TYPE RSDODSTABT, "   
lv_i_tablnm  TYPE RSD_TABLNM, "   
lv_i_t_key  TYPE RSDU_T_KEYFIELD, "   
lv_i_part_type  TYPE RSDU_PARTYPE, "   RSDU_C_PARTYPE-HASH
lv_i_t_mdc_iobj  TYPE RSDO_T_MDC_IOBJ, "   
lv_i_odsotype  TYPE RSDODSOTYPE. "   

  CALL FUNCTION 'RSDU_ODS_PART_INSTANTIATE_DB4'  "Creates Database-Dependent Partition Properties in the SAP-DD
    EXPORTING
         I_ODSOBJECT = lv_i_odsobject
         I_TABT = lv_i_tabt
         I_TABLNM = lv_i_tablnm
         I_T_KEY = lv_i_t_key
         I_PART_TYPE = lv_i_part_type
         I_T_MDC_IOBJ = lv_i_t_mdc_iobj
         I_ODSOTYPE = lv_i_odsotype
    IMPORTING
         E_PROCESSED = lv_e_processed
    EXCEPTIONS
        ODS_INSTANTIATE_FAILED = 1
        NO_KEY_FIELD = 2
. " RSDU_ODS_PART_INSTANTIATE_DB4




ABAP code using 7.40 inline data declarations to call FM RSDU_ODS_PART_INSTANTIATE_DB4

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_i_part_type) = RSDU_C_PARTYPE-HASH.
 
 
 


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!