FVD_PROCESS_PLANNED_RECORDS SAP Function module

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

Associated Function Group: FVD_OBJ_PLANNED_RECORDS
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM FVD_PROCESS_PLANNED_RECORDS - FVD PROCESS PLANNED RECORDS

CALL FUNCTION 'FVD_PROCESS_PLANNED_RECORDS' "
  EXPORTING
    i_tab_vdarl_key =           " trty_vdarl_key
  IMPORTING
    e_ext_log_id =              " balnrext
    .  "  FVD_PROCESS_PLANNED_RECORDS

ABAP code example for Function Module FVD_PROCESS_PLANNED_RECORDS

The ABAP code below is a full code listing to execute function module FVD_PROCESS_PLANNED_RECORDS 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_ext_log_id  
 
 TYPE BALNREXT
.


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

CALL FUNCTION 'FVD_PROCESS_PLANNED_RECORDS'
  EXPORTING
    i_tab_vdarl_key =            ld_i_tab_vdarl_key
  IMPORTING
    e_ext_log_id =               ld_e_ext_log_id
    .  "  FVD_PROCESS_PLANNED_RECORDS

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_ext_log_id
 
 TYPE BALNREXT ,
ld_i_tab_vdarl_key
 
 TYPE TRTY_VDARL_KEY .


ld_i_tab_vdarl_key = 'Check type of data required'.