SAP FMS2_GET_STAT_GEN Function Module for
FMS2_GET_STAT_GEN is a standard fms2 get stat gen SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fms2 get stat gen FM, simply by entering the name FMS2_GET_STAT_GEN into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMS2
Program Name: SAPLFMS2
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMS2_GET_STAT_GEN 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 'FMS2_GET_STAT_GEN'".
EXPORTING
I_FIKRS = "
* I_FIPOS = ' ' "
I_CTR_OBJNR = "
I_GEBER = "
I_GJAHR = "
* I_DATUM = SY-DATUM "
* I_POSIT = ' ' "
* I_NO_CHECK = ' ' "
IMPORTING
E_STATUS = "
EXCEPTIONS
FICTR_NOT_FOUND = 1 FIKRS_NOT_FOUND = 2 FIPOS_NOT_FOUND = 3 GEBER_NOT_FOUND = 4 STATUS_NOT_FOUND = 5 MISSING_ENTRY = 6
IMPORTING Parameters details for FMS2_GET_STAT_GEN
I_FIKRS -
Data type: FM01-FIKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_FIPOS -
Data type: FMFPO-FIPOSDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CTR_OBJNR -
Data type: FMFCTR-CTR_OBJNROptional: No
Call by Reference: No ( called with pass by value option)
I_GEBER -
Data type: FMAPSTAT-GEBEROptional: No
Call by Reference: No ( called with pass by value option)
I_GJAHR -
Data type: FMAPSTAT-GJAHROptional: No
Call by Reference: No ( called with pass by value option)
I_DATUM -
Data type: FMAPSTAT-DATBISDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_POSIT -
Data type: FMAPSTAT-POSITDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NO_CHECK -
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FMS2_GET_STAT_GEN
E_STATUS -
Data type: IFMAPSTATOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FICTR_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FIKRS_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FIPOS_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GEBER_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STATUS_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MISSING_ENTRY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FMS2_GET_STAT_GEN 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_fikrs | TYPE FM01-FIKRS, " | |||
| lv_e_status | TYPE IFMAPSTAT, " | |||
| lv_fictr_not_found | TYPE IFMAPSTAT, " | |||
| lv_i_fipos | TYPE FMFPO-FIPOS, " ' ' | |||
| lv_fikrs_not_found | TYPE FMFPO, " | |||
| lv_i_ctr_objnr | TYPE FMFCTR-CTR_OBJNR, " | |||
| lv_fipos_not_found | TYPE FMFCTR, " | |||
| lv_i_geber | TYPE FMAPSTAT-GEBER, " | |||
| lv_geber_not_found | TYPE FMAPSTAT, " | |||
| lv_i_gjahr | TYPE FMAPSTAT-GJAHR, " | |||
| lv_status_not_found | TYPE FMAPSTAT, " | |||
| lv_i_datum | TYPE FMAPSTAT-DATBIS, " SY-DATUM | |||
| lv_missing_entry | TYPE FMAPSTAT, " | |||
| lv_i_posit | TYPE FMAPSTAT-POSIT, " ' ' | |||
| lv_i_no_check | TYPE FMAPSTAT. " ' ' |
|   CALL FUNCTION 'FMS2_GET_STAT_GEN' " |
| EXPORTING | ||
| I_FIKRS | = lv_i_fikrs | |
| I_FIPOS | = lv_i_fipos | |
| I_CTR_OBJNR | = lv_i_ctr_objnr | |
| I_GEBER | = lv_i_geber | |
| I_GJAHR | = lv_i_gjahr | |
| I_DATUM | = lv_i_datum | |
| I_POSIT | = lv_i_posit | |
| I_NO_CHECK | = lv_i_no_check | |
| IMPORTING | ||
| E_STATUS | = lv_e_status | |
| EXCEPTIONS | ||
| FICTR_NOT_FOUND = 1 | ||
| FIKRS_NOT_FOUND = 2 | ||
| FIPOS_NOT_FOUND = 3 | ||
| GEBER_NOT_FOUND = 4 | ||
| STATUS_NOT_FOUND = 5 | ||
| MISSING_ENTRY = 6 | ||
| . " FMS2_GET_STAT_GEN | ||
ABAP code using 7.40 inline data declarations to call FM FMS2_GET_STAT_GEN
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 FIKRS FROM FM01 INTO @DATA(ld_i_fikrs). | ||||
| "SELECT single FIPOS FROM FMFPO INTO @DATA(ld_i_fipos). | ||||
| DATA(ld_i_fipos) | = ' '. | |||
| "SELECT single CTR_OBJNR FROM FMFCTR INTO @DATA(ld_i_ctr_objnr). | ||||
| "SELECT single GEBER FROM FMAPSTAT INTO @DATA(ld_i_geber). | ||||
| "SELECT single GJAHR FROM FMAPSTAT INTO @DATA(ld_i_gjahr). | ||||
| "SELECT single DATBIS FROM FMAPSTAT INTO @DATA(ld_i_datum). | ||||
| DATA(ld_i_datum) | = SY-DATUM. | |||
| "SELECT single POSIT FROM FMAPSTAT INTO @DATA(ld_i_posit). | ||||
| DATA(ld_i_posit) | = ' '. | |||
| DATA(ld_i_no_check) | = ' '. | |||
Search for further information about these or an SAP related objects