FVD_ARC_VZZBEPP_FILL SAP Function module - Fills VZZBEPP Table with Plan, Actual, and Read Reorganization Records

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

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

Pattern for FM FVD_ARC_VZZBEPP_FILL - FVD ARC VZZBEPP FILL

CALL FUNCTION 'FVD_ARC_VZZBEPP_FILL' "Fills VZZBEPP Table with Plan, Actual, and Read Reorganization Records
  EXPORTING
    i_bukrs =                   " vdarl-bukrs   Company Code
    i_ranl =                    " vdarl-ranl    Loan Contract Number
    i_vdbeki =                  " trty_vdbeki   Table Type for Table VDBEKI
    i_vdbepi =                  " trty_vdbepi   Table Type for Table VDBEPI
    i_vdbepp =                  " trty_vdbepp   Table Type for Table VDBEPP
  IMPORTING
    o_vzzbepp =                 " trty_vzzbepp  Table Type for Structure VZZBEPP
* CHANGING
*   o_vdarc_doc_adm =           " vdarc_doc_adm  Verwaltungstabelle der Darlehensbelegdatenreorganisation
  EXCEPTIONS
    RANL_NOT_FOUND = 1          "               Eingegebene Vertragsnummer ist ungültig.
    .  "  FVD_ARC_VZZBEPP_FILL

ABAP code example for Function Module FVD_ARC_VZZBEPP_FILL

The ABAP code below is a full code listing to execute function module FVD_ARC_VZZBEPP_FILL 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_o_vzzbepp  
 
 TYPE TRTY_VZZBEPP
.


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

SELECT single BUKRS 
  FROM VDARL 
  INTO @DATA(ld_i_bukrs).

 

SELECT single RANL 
  FROM VDARL 
  INTO @DATA(ld_i_ranl).


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

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

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

CALL FUNCTION 'FVD_ARC_VZZBEPP_FILL'
  EXPORTING
    i_bukrs =                    ld_i_bukrs
    i_ranl =                     ld_i_ranl
    i_vdbeki =                   ld_i_vdbeki
    i_vdbepi =                   ld_i_vdbepi
    i_vdbepp =                   ld_i_vdbepp
  IMPORTING
    o_vzzbepp =                  ld_o_vzzbepp
* CHANGING
*   o_vdarc_doc_adm =            ld_o_vdarc_doc_adm
  EXCEPTIONS
    RANL_NOT_FOUND =             1
    .  "  FVD_ARC_VZZBEPP_FILL

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_o_vdarc_doc_adm
 
 TYPE VDARC_DOC_ADM ,
ld_o_vzzbepp
 
 TYPE TRTY_VZZBEPP ,
ld_i_bukrs
 
 TYPE VDARL-BUKRS ,
ld_i_ranl
 
 TYPE VDARL-RANL ,
ld_i_vdbeki
 
 TYPE TRTY_VDBEKI ,
ld_i_vdbepi
 
 TYPE TRTY_VDBEPI ,
ld_i_vdbepp
 
 TYPE TRTY_VDBEPP .


ld_o_vdarc_doc_adm = 'Check type of data required'.

SELECT single BUKRS 
  FROM VDARL 
  INTO ld_i_bukrs.


SELECT single RANL 
  FROM VDARL 
  INTO ld_i_ranl.

ld_i_vdbeki = 'Check type of data required'.
ld_i_vdbepi = 'Check type of data required'.
ld_i_vdbepp = 'Check type of data required'.