RSDC_CUBE_F4_DYNP_UPDATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name RSDC_CUBE_F4_DYNP_UPDATE into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
RSDC
Released Date:
Not Released
Processing type: Normal fucntion module
CALL FUNCTION 'RSDC_CUBE_F4_DYNP_UPDATE' "F4 for InfoCubes, Multi / Hybrid provider with screen update
EXPORTING
i_repid = " syrepid Program Name (Dynpro)
i_dynnr = " sydynnr Screen Number
i_fname = " dynfnam Field Name
* i_fname_txt = " dynfnam Field Name (Text Field)
* i_t_cubetype = " rsd_t_cubetype List of Valid InfoCube Types
* i_t_cubesubtype = " rsd_t_cubesubtype List of Valid InfoCube Subtypes
* i_incl_owned_by = " rs_char1 Included OWNED BY Level (See N_C_OWNED_BY)
* i_ds_suitable_only = RS_C_FALSE " rs_bool only Prov., whose DS can be used
* i_objvers = RS_C_OBJVERS-ACTIVE " rs_objvers Version
* i_display = RS_C_FALSE " rs_bool Flag: Display Only
IMPORTING
e_infocube = " rsd_infocube InfoCube (Selected Value)
e_txtlg = " rs_txtlg Description
. " RSDC_CUBE_F4_DYNP_UPDATE
The ABAP code below is a full code listing to execute function module RSDC_CUBE_F4_DYNP_UPDATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_e_infocube | TYPE RSD_INFOCUBE , |
| ld_e_txtlg | TYPE RS_TXTLG . |
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_e_infocube | TYPE RSD_INFOCUBE , |
| ld_i_repid | TYPE SYREPID , |
| ld_e_txtlg | TYPE RS_TXTLG , |
| ld_i_dynnr | TYPE SYDYNNR , |
| ld_i_fname | TYPE DYNFNAM , |
| ld_i_fname_txt | TYPE DYNFNAM , |
| ld_i_t_cubetype | TYPE RSD_T_CUBETYPE , |
| ld_i_t_cubesubtype | TYPE RSD_T_CUBESUBTYPE , |
| ld_i_incl_owned_by | TYPE RS_CHAR1 , |
| ld_i_ds_suitable_only | TYPE RS_BOOL , |
| ld_i_objvers | TYPE RS_OBJVERS , |
| ld_i_display | TYPE RS_BOOL . |
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name RSDC_CUBE_F4_DYNP_UPDATE or its description.