SAP RM_RB_SVSTATES_GET_SFGDT Function Module for Dataset Mgt: Get Risk Object of Dataset According to Financial ObjList









RM_RB_SVSTATES_GET_SFGDT is a standard rm rb svstates get sfgdt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Dataset Mgt: Get Risk Object of Dataset According to Financial ObjList 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 rm rb svstates get sfgdt FM, simply by entering the name RM_RB_SVSTATES_GET_SFGDT into the relevant SAP transaction such as SE37 or SE38.

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



Function RM_RB_SVSTATES_GET_SFGDT 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 'RM_RB_SVSTATES_GET_SFGDT'"Dataset Mgt: Get Risk Object of Dataset According to Financial ObjList
EXPORTING
I_STATE_ID = "
* I_ARCH_RUN = "

TABLES
* I_BP = "
I_FOB = "
E_SFGDT = "
.



IMPORTING Parameters details for RM_RB_SVSTATES_GET_SFGDT

I_STATE_ID -

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

I_ARCH_RUN -

Data type: ADMI_RUN-DOCUMENT
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RM_RB_SVSTATES_GET_SFGDT

I_BP -

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

I_FOB -

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

E_SFGDT -

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

Copy and paste ABAP code example for RM_RB_SVSTATES_GET_SFGDT 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:
lt_i_bp  TYPE STANDARD TABLE OF JBRBP, "   
lv_i_state_id  TYPE JBRSVSTATE-SV_STATE_ID, "   
lt_i_fob  TYPE STANDARD TABLE OF JBRFOB, "   
lv_i_arch_run  TYPE ADMI_RUN-DOCUMENT, "   
lt_e_sfgdt  TYPE STANDARD TABLE OF TVS_SFGDT_TAB. "   

  CALL FUNCTION 'RM_RB_SVSTATES_GET_SFGDT'  "Dataset Mgt: Get Risk Object of Dataset According to Financial ObjList
    EXPORTING
         I_STATE_ID = lv_i_state_id
         I_ARCH_RUN = lv_i_arch_run
    TABLES
         I_BP = lt_i_bp
         I_FOB = lt_i_fob
         E_SFGDT = lt_e_sfgdt
. " RM_RB_SVSTATES_GET_SFGDT




ABAP code using 7.40 inline data declarations to call FM RM_RB_SVSTATES_GET_SFGDT

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 SV_STATE_ID FROM JBRSVSTATE INTO @DATA(ld_i_state_id).
 
 
"SELECT single DOCUMENT FROM ADMI_RUN INTO @DATA(ld_i_arch_run).
 
 


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!