FVD_BO_OL_SET_VDBOHEAD SAP Function module - Return Business Operation Header Data to Memory

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

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

Pattern for FM FVD_BO_OL_SET_VDBOHEAD - FVD BO OL SET VDBOHEAD

CALL FUNCTION 'FVD_BO_OL_SET_VDBOHEAD' "Return Business Operation Header Data to Memory
  EXPORTING
*   i_log_handle =              " balloghndl    Application Log: Log Handle
    i_s_vdarl_key =             " vdarl_key     VDARL Key Structure
    i_rbo =                     " rbo           Business operation number (loans)
    i_sworkid =                 " sworkid       Processing Unit in the Business Operations
    i_s_vdbohead =              " vdbohead      Business Operation: Header
  EXCEPTIONS
    INPUT_NOT_FILLED = 1        "               Input parameter missing
    FAILED = 2                  "               Operation in table failed
    .  "  FVD_BO_OL_SET_VDBOHEAD

ABAP code example for Function Module FVD_BO_OL_SET_VDBOHEAD

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

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

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

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

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

CALL FUNCTION 'FVD_BO_OL_SET_VDBOHEAD'
  EXPORTING
*   i_log_handle =               ld_i_log_handle
    i_s_vdarl_key =              ld_i_s_vdarl_key
    i_rbo =                      ld_i_rbo
    i_sworkid =                  ld_i_sworkid
    i_s_vdbohead =               ld_i_s_vdbohead
  EXCEPTIONS
    INPUT_NOT_FILLED =           1
    FAILED =                     2
    .  "  FVD_BO_OL_SET_VDBOHEAD

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "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_i_log_handle
 
 TYPE BALLOGHNDL ,
ld_i_s_vdarl_key
 
 TYPE VDARL_KEY ,
ld_i_rbo
 
 TYPE RBO ,
ld_i_sworkid
 
 TYPE SWORKID ,
ld_i_s_vdbohead
 
 TYPE VDBOHEAD .


ld_i_log_handle = 'Check type of data required'.
ld_i_s_vdarl_key = 'Check type of data required'.
ld_i_rbo = 'Check type of data required'.
ld_i_sworkid = 'Check type of data required'.
ld_i_s_vdbohead = 'Check type of data required'.