SAP FRML370_FRML_DATA_BUFFER Function Module for NOTRANSL: RMS-FRM: API Auflösung - Datenpuffer Formulas (NUR intern !!)
FRML370_FRML_DATA_BUFFER is a standard frml370 frml data buffer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: RMS-FRM: API Auflösung - Datenpuffer Formulas (NUR intern !!) 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 frml370 frml data buffer FM, simply by entering the name FRML370_FRML_DATA_BUFFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: FRML370
Program Name: SAPLFRML370
Main Program: SAPLFRML370
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FRML370_FRML_DATA_BUFFER 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 'FRML370_FRML_DATA_BUFFER'"NOTRANSL: RMS-FRM: API Auflösung - Datenpuffer Formulas (NUR intern !!).
EXPORTING
* I_RECN = "RMS-FRM: Object Identifier
* IS_FRML_DATA = "
* I_FLG_UPD = "General Indicator
IMPORTING
E_EXIST = "DE-EN-LANG-SWITCH-NO-TRANSLATION
ES_FRML_DATA = "
ETS_FRML_DATA = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
INTERNAL_ERROR = 1
IMPORTING Parameters details for FRML370_FRML_DATA_BUFFER
I_RECN - RMS-FRM: Object Identifier
Data type: FRMLE_RECNOptional: Yes
Call by Reference: Yes
IS_FRML_DATA -
Data type: FRM35_TY_S_FRML_DATAOptional: Yes
Call by Reference: Yes
I_FLG_UPD - General Indicator
Data type: FLAGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FRML370_FRML_DATA_BUFFER
E_EXIST - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: FLAGOptional: No
Call by Reference: Yes
ES_FRML_DATA -
Data type: FRM35_TY_S_FRML_DATAOptional: No
Call by Reference: Yes
ETS_FRML_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: FRM35_TY_TS_FRML_DATAOptional: No
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FRML370_FRML_DATA_BUFFER 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_recn | TYPE FRMLE_RECN, " | |||
| lv_e_exist | TYPE FLAG, " | |||
| lv_internal_error | TYPE FLAG, " | |||
| lv_es_frml_data | TYPE FRM35_TY_S_FRML_DATA, " | |||
| lv_is_frml_data | TYPE FRM35_TY_S_FRML_DATA, " | |||
| lv_i_flg_upd | TYPE FLAG, " | |||
| lv_ets_frml_data | TYPE FRM35_TY_TS_FRML_DATA. " |
|   CALL FUNCTION 'FRML370_FRML_DATA_BUFFER' "NOTRANSL: RMS-FRM: API Auflösung - Datenpuffer Formulas (NUR intern !!) |
| EXPORTING | ||
| I_RECN | = lv_i_recn | |
| IS_FRML_DATA | = lv_is_frml_data | |
| I_FLG_UPD | = lv_i_flg_upd | |
| IMPORTING | ||
| E_EXIST | = lv_e_exist | |
| ES_FRML_DATA | = lv_es_frml_data | |
| ETS_FRML_DATA | = lv_ets_frml_data | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| . " FRML370_FRML_DATA_BUFFER | ||
ABAP code using 7.40 inline data declarations to call FM FRML370_FRML_DATA_BUFFER
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.Search for further information about these or an SAP related objects