SAP FRML301_API_INIT Function Module for NOTRANSL: RMS-FRM: Initialisierung des APIs









FRML301_API_INIT is a standard frml301 api init 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: Initialisierung des APIs 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 frml301 api init FM, simply by entering the name FRML301_API_INIT into the relevant SAP transaction such as SE37 or SE38.

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



Function FRML301_API_INIT 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 'FRML301_API_INIT'"NOTRANSL: RMS-FRM: Initialisierung des APIs
EXPORTING
I_VALFR = "
I_VALTO = "
* I_AENNR = "
* I_FORCE_BUFFER_INIT = TRUE "

EXCEPTIONS
PARAMETER_ERROR = 1
.



IMPORTING Parameters details for FRML301_API_INIT

I_VALFR -

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

I_VALTO -

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

I_AENNR -

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

I_FORCE_BUFFER_INIT -

Data type: ESP1_BOOLEAN
Default: TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FRML301_API_INIT 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_valfr  TYPE FRM31_DATE_TYPE, "   
lv_parameter_error  TYPE FRM31_DATE_TYPE, "   
lv_i_valto  TYPE FRM31_DATE_TYPE, "   
lv_i_aennr  TYPE FRM31_AENNR_TYPE, "   
lv_i_force_buffer_init  TYPE ESP1_BOOLEAN. "   TRUE

  CALL FUNCTION 'FRML301_API_INIT'  "NOTRANSL: RMS-FRM: Initialisierung des APIs
    EXPORTING
         I_VALFR = lv_i_valfr
         I_VALTO = lv_i_valto
         I_AENNR = lv_i_aennr
         I_FORCE_BUFFER_INIT = lv_i_force_buffer_init
    EXCEPTIONS
        PARAMETER_ERROR = 1
. " FRML301_API_INIT




ABAP code using 7.40 inline data declarations to call FM FRML301_API_INIT

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.

 
 
 
 
DATA(ld_i_force_buffer_init) = TRUE.
 


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!