SAP FRML331_GET Function Module for NOTRANSL: RMS-FRM: Lesen des Entitätytypen vom Zwischenpuffer









FRML331_GET is a standard frml331 get 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: Lesen des Entitätytypen vom 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 frml331 get FM, simply by entering the name FRML331_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function FRML331_GET 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 'FRML331_GET'"NOTRANSL: RMS-FRM: Lesen des Entitätytypen vom Zwischenpuffer
EXPORTING
I_FURTHER_SETTINGS = "

TABLES
E_API_TAB = "RMS-FRM: Header of Structural Part
.



IMPORTING Parameters details for FRML331_GET

I_FURTHER_SETTINGS -

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

TABLES Parameters details for FRML331_GET

E_API_TAB - RMS-FRM: Header of Structural Part

Data type: FRMLS_API_HDR
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FRML331_GET 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_e_api_tab  TYPE STANDARD TABLE OF FRMLS_API_HDR, "   
lv_i_further_settings  TYPE FRM32_FURTHER_SETTINGS_TYPE. "   

  CALL FUNCTION 'FRML331_GET'  "NOTRANSL: RMS-FRM: Lesen des Entitätytypen vom Zwischenpuffer
    EXPORTING
         I_FURTHER_SETTINGS = lv_i_further_settings
    TABLES
         E_API_TAB = lt_e_api_tab
. " FRML331_GET




ABAP code using 7.40 inline data declarations to call FM FRML331_GET

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



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!