RM_PROT_REPORT SAP Function module - Schreibt allgemeine Daten zum Programm ins Protokoll

RM_PROT_REPORT 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 RM_PROT_REPORT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM RM_PROT_REPORT - RM PROT REPORT

CALL FUNCTION 'RM_PROT_REPORT' "Schreibt allgemeine Daten zum Programm ins Protokoll
  EXPORTING
*   level = '1'                 " sprot-level   Log Level
*   lines = 1                   " i
    date =                      " vtv_para-tvaktdat
    hori =                      " vtv_para-tvhori  Horizon
    eval =                      " jbreval-auswertung  Evaluation Type
*   szen =                      " vtvszko-szenari  Business Scenario
    curr =                      " jbrbest-wgschft  Display Currency
*   date_end =                  " tv_aktudat    Berechnungsdatum Periodenende
*   hori_end =                  " tv_horizon    Horizont Periodenende
    .  "  RM_PROT_REPORT

ABAP code example for Function Module RM_PROT_REPORT

The ABAP code below is a full code listing to execute function module RM_PROT_REPORT 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_level) = Check type of data required

DATA(ld_lines) = 'Check type of data required'.


DATA(ld_date) = 20210129


DATA(ld_hori) = 20210129
 

SELECT single AUSWERTUNG 
  FROM JBREVAL 
  INTO @DATA(ld_eval).

 

SELECT single SZENARI 
  FROM VTVSZKO 
  INTO @DATA(ld_szen).



DATA(ld_curr) = Check type of data required

DATA(ld_date_end) = 'Check type of data required'.

DATA(ld_hori_end) = 'Check type of data required'.
.

CALL FUNCTION 'RM_PROT_REPORT'
  EXPORTING
*   level =                      ld_level
*   lines =                      ld_lines
    date =                       ld_date
    hori =                       ld_hori
    eval =                       ld_eval
*   szen =                       ld_szen
    curr =                       ld_curr
*   date_end =                   ld_date_end
*   hori_end =                   ld_hori_end
    .  "  RM_PROT_REPORT

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_level
 
 TYPE SPROT-LEVEL ,
ld_lines
 
 TYPE I ,
ld_date
 
 TYPE VTV_PARA-TVAKTDAT ,
ld_hori
 
 TYPE VTV_PARA-TVHORI ,
ld_eval
 
 TYPE JBREVAL-AUSWERTUNG ,
ld_szen
 
 TYPE VTVSZKO-SZENARI ,
ld_curr
 
 TYPE JBRBEST-WGSCHFT ,
ld_date_end
 
 TYPE TV_AKTUDAT ,
ld_hori_end
 
 TYPE TV_HORIZON .



ld_level = Check type of data required
ld_lines = 'Check type of data required'.

ld_date = 20210129

ld_hori = 20210129

SELECT single AUSWERTUNG 
  FROM JBREVAL 
  INTO ld_eval.


SELECT single SZENARI 
  FROM VTVSZKO 
  INTO ld_szen.


ld_curr = Check type of data required
ld_date_end = 'Check type of data required'.
ld_hori_end = 'Check type of data required'.