SAP FRML341_PUT Function Module for NOTRANSL: RMS-FRM: Schreiben des Entitätytypen in Zwischenpuffer
FRML341_PUT is a standard frml341 put 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: Schreiben des Entitätytypen in Zwischenpuffer 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 frml341 put FM, simply by entering the name FRML341_PUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FRML341
Program Name: SAPLFRML341
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FRML341_PUT 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 'FRML341_PUT'"NOTRANSL: RMS-FRM: Schreiben des Entitätytypen in Zwischenpuffer.
EXPORTING
I_FURTHER_SETTINGS = "
TABLES
X_API_TAB = "RMS-FRM: API LoM Output Item (Material)
IMPORTING Parameters details for FRML341_PUT
I_FURTHER_SETTINGS -
Data type: FRM32_FURTHER_SETTINGS_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FRML341_PUT
X_API_TAB - RMS-FRM: API LoM Output Item (Material)
Data type: FRMLS_API_OUSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FRML341_PUT 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_x_api_tab | TYPE STANDARD TABLE OF FRMLS_API_OUS, " | |||
| lv_i_further_settings | TYPE FRM32_FURTHER_SETTINGS_TYPE. " |
|   CALL FUNCTION 'FRML341_PUT' "NOTRANSL: RMS-FRM: Schreiben des Entitätytypen in Zwischenpuffer |
| EXPORTING | ||
| I_FURTHER_SETTINGS | = lv_i_further_settings | |
| TABLES | ||
| X_API_TAB | = lt_x_api_tab | |
| . " FRML341_PUT | ||
ABAP code using 7.40 inline data declarations to call FM FRML341_PUT
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