SAP RM_LOAD_HIST_STATE_OF_DATA Function Module for RM: Vorbereiten/Laden eines gesicherten Datenstandes von DB (V3 -> SFGDTs)
RM_LOAD_HIST_STATE_OF_DATA is a standard rm load hist state of data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RM: Vorbereiten/Laden eines gesicherten Datenstandes von DB (V3 -> SFGDTs) 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 load hist state of data FM, simply by entering the name RM_LOAD_HIST_STATE_OF_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBRB
Program Name: SAPLJBRB
Main Program: SAPLJBRB
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_LOAD_HIST_STATE_OF_DATA 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_LOAD_HIST_STATE_OF_DATA'"RM: Vorbereiten/Laden eines gesicherten Datenstandes von DB (V3 -> SFGDTs).
EXPORTING
HIST_STATE_ID = "
IMPORTING
SICHTID = "
PHID = "
PKNOTEN = "
DATE = "
SAVE_TEXT = "
TABLES
ET_FOB = "
ET_PHBAUM = "
ET_PHTEXT = "
ET_PHZUORDN = "
ERROR_ITAB = "
EXCEPTIONS
NO_SUCH_STATE_OF_DATA = 1 SFGDT_REBUILD_ERROR = 2
IMPORTING Parameters details for RM_LOAD_HIST_STATE_OF_DATA
HIST_STATE_ID -
Data type: JBRSVKO-SV_STATE_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RM_LOAD_HIST_STATE_OF_DATA
SICHTID -
Data type: JBRSI-SICHTIDOptional: No
Call by Reference: Yes
PHID -
Data type: JBRPH-PHIDOptional: No
Call by Reference: Yes
PKNOTEN -
Data type: JBRPHBAUM-PKNOTENOptional: No
Call by Reference: Yes
DATE -
Data type: SY-DATUMOptional: No
Call by Reference: Yes
SAVE_TEXT -
Data type: JBRSVSTATE-SV_STATE_TEXTOptional: No
Call by Reference: Yes
TABLES Parameters details for RM_LOAD_HIST_STATE_OF_DATA
ET_FOB -
Data type: JBRFOBOptional: No
Call by Reference: No ( called with pass by value option)
ET_PHBAUM -
Data type: JBRPHBAUMOptional: No
Call by Reference: No ( called with pass by value option)
ET_PHTEXT -
Data type: JBRNAMEDATOptional: No
Call by Reference: No ( called with pass by value option)
ET_PHZUORDN -
Data type: JBRZUORDNOptional: No
Call by Reference: No ( called with pass by value option)
ERROR_ITAB -
Data type: BAPIERROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_SUCH_STATE_OF_DATA -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SFGDT_REBUILD_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_LOAD_HIST_STATE_OF_DATA 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_et_fob | TYPE STANDARD TABLE OF JBRFOB, " | |||
| lv_sichtid | TYPE JBRSI-SICHTID, " | |||
| lv_hist_state_id | TYPE JBRSVKO-SV_STATE_ID, " | |||
| lv_no_such_state_of_data | TYPE JBRSVKO, " | |||
| lv_phid | TYPE JBRPH-PHID, " | |||
| lt_et_phbaum | TYPE STANDARD TABLE OF JBRPHBAUM, " | |||
| lv_sfgdt_rebuild_error | TYPE JBRPHBAUM, " | |||
| lv_pknoten | TYPE JBRPHBAUM-PKNOTEN, " | |||
| lt_et_phtext | TYPE STANDARD TABLE OF JBRNAMEDAT, " | |||
| lv_date | TYPE SY-DATUM, " | |||
| lt_et_phzuordn | TYPE STANDARD TABLE OF JBRZUORDN, " | |||
| lv_save_text | TYPE JBRSVSTATE-SV_STATE_TEXT, " | |||
| lt_error_itab | TYPE STANDARD TABLE OF BAPIERR. " |
|   CALL FUNCTION 'RM_LOAD_HIST_STATE_OF_DATA' "RM: Vorbereiten/Laden eines gesicherten Datenstandes von DB (V3 -> SFGDTs) |
| EXPORTING | ||
| HIST_STATE_ID | = lv_hist_state_id | |
| IMPORTING | ||
| SICHTID | = lv_sichtid | |
| PHID | = lv_phid | |
| PKNOTEN | = lv_pknoten | |
| DATE | = lv_date | |
| SAVE_TEXT | = lv_save_text | |
| TABLES | ||
| ET_FOB | = lt_et_fob | |
| ET_PHBAUM | = lt_et_phbaum | |
| ET_PHTEXT | = lt_et_phtext | |
| ET_PHZUORDN | = lt_et_phzuordn | |
| ERROR_ITAB | = lt_error_itab | |
| EXCEPTIONS | ||
| NO_SUCH_STATE_OF_DATA = 1 | ||
| SFGDT_REBUILD_ERROR = 2 | ||
| . " RM_LOAD_HIST_STATE_OF_DATA | ||
ABAP code using 7.40 inline data declarations to call FM RM_LOAD_HIST_STATE_OF_DATA
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 SICHTID FROM JBRSI INTO @DATA(ld_sichtid). | ||||
| "SELECT single SV_STATE_ID FROM JBRSVKO INTO @DATA(ld_hist_state_id). | ||||
| "SELECT single PHID FROM JBRPH INTO @DATA(ld_phid). | ||||
| "SELECT single PKNOTEN FROM JBRPHBAUM INTO @DATA(ld_pknoten). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_date). | ||||
| "SELECT single SV_STATE_TEXT FROM JBRSVSTATE INTO @DATA(ld_save_text). | ||||
Search for further information about these or an SAP related objects