FRML811_ALLOWED_SUBCAT_CHECK SAP Function module - Formula: Check Whether Specification Type Is Permitted

FRML811_ALLOWED_SUBCAT_CHECK is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FRML811_ALLOWED_SUBCAT_CHECK into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FRML811
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FRML811_ALLOWED_SUBCAT_CHECK - FRML811 ALLOWED SUBCAT CHECK

CALL FUNCTION 'FRML811_ALLOWED_SUBCAT_CHECK' "Formula: Check Whether Specification Type Is Permitted
  EXPORTING
    i_recn =                    " estrh-recn    Internal Key of Specification
    i_level =                   " frmlc11-frml_level  View of a Formula
    i_view =                    " frmlc11-frml_view  Subview of a Formula
*   i_aennr = SPACE             " frmls_addinf-aennr  Change Number of Formula
*   i_valdat = SY-DATUM         " frmls_addinf-valdat  Key Date of Formula
  IMPORTING
    e_subcat =                  " tcg31-subcat  Specification Type
    e_flg_valid =               " esp1_boolean  Indicator: Specification Type is Allowed for Subview (Value "True")
    .  "  FRML811_ALLOWED_SUBCAT_CHECK

ABAP code example for Function Module FRML811_ALLOWED_SUBCAT_CHECK

The ABAP code below is a full code listing to execute function module FRML811_ALLOWED_SUBCAT_CHECK including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_subcat  
 
 TYPE TCG31-SUBCAT
,
ld_e_flg_valid  
 
 TYPE ESP1_BOOLEAN
.

 

SELECT single RECN 
  FROM ESTRH 
  INTO @DATA(ld_i_recn).

 

SELECT single FRML_LEVEL 
  FROM FRMLC11 
  INTO @DATA(ld_i_level).

 

SELECT single FRML_VIEW 
  FROM FRMLC11 
  INTO @DATA(ld_i_view).



DATA(ld_i_aennr) = some text here


DATA(ld_i_valdat) = 20210129
.

CALL FUNCTION 'FRML811_ALLOWED_SUBCAT_CHECK'
  EXPORTING
    i_recn =                     ld_i_recn
    i_level =                    ld_i_level
    i_view =                     ld_i_view
*   i_aennr =                    ld_i_aennr
*   i_valdat =                   ld_i_valdat
  IMPORTING
    e_subcat =                   ld_e_subcat
    e_flg_valid =                ld_e_flg_valid
    .  "  FRML811_ALLOWED_SUBCAT_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_subcat
 
 TYPE TCG31-SUBCAT ,
ld_i_recn
 
 TYPE ESTRH-RECN ,
ld_e_flg_valid
 
 TYPE ESP1_BOOLEAN ,
ld_i_level
 
 TYPE FRMLC11-FRML_LEVEL ,
ld_i_view
 
 TYPE FRMLC11-FRML_VIEW ,
ld_i_aennr
 
 TYPE FRMLS_ADDINF-AENNR ,
ld_i_valdat
 
 TYPE FRMLS_ADDINF-VALDAT .



SELECT single RECN 
  FROM ESTRH 
  INTO ld_i_recn.


SELECT single FRML_LEVEL 
  FROM FRMLC11 
  INTO ld_i_level.


SELECT single FRML_VIEW 
  FROM FRMLC11 
  INTO ld_i_view.


ld_i_aennr = some text here

ld_i_valdat = 20210129

SAP Documentation for FM FRML811_ALLOWED_SUBCAT_CHECK