FVARC_OBJECT_BALANCE_CHECK SAP Function module

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

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

Pattern for FM FVARC_OBJECT_BALANCE_CHECK - FVARC OBJECT BALANCE CHECK

CALL FUNCTION 'FVARC_OBJECT_BALANCE_CHECK' "
  EXPORTING
    i_obart =                   " tbo01-obart   Object Type
    i_bukrs =                   " viob01-bukrs  Company Code
    i_objnr =                   " viob01-j_objnr  CO Object Number
    i_imkey =                   " viob01-imkey  IMKEY
*   i_key_for_output =          " vvobjkey-objid
  IMPORTING
    e_subrc =                   " sy-subrc      Return Code
  TABLES
    t_messages =                " sprot_u       Table of Messages
    .  "  FVARC_OBJECT_BALANCE_CHECK

ABAP code example for Function Module FVARC_OBJECT_BALANCE_CHECK

The ABAP code below is a full code listing to execute function module FVARC_OBJECT_BALANCE_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_subrc  
 
 TYPE SY-SUBRC
,
it_t_messages  
 
 TYPE STANDARD TABLE OF SPROT_U,"TABLES PARAM
wa_t_messages
 
 LIKE LINE OF it_t_messages
.

 

SELECT single OBART 
  FROM TBO01 
  INTO @DATA(ld_i_obart).

 

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

 

SELECT single J_OBJNR 
  FROM VIOB01 
  INTO @DATA(ld_i_objnr).

 

SELECT single IMKEY 
  FROM VIOB01 
  INTO @DATA(ld_i_imkey).



DATA(ld_i_key_for_output) = some text here
 

"populate fields of struture and append to itab
append wa_t_messages to it_t_messages.
.

CALL FUNCTION 'FVARC_OBJECT_BALANCE_CHECK'
  EXPORTING
    i_obart =                    ld_i_obart
    i_bukrs =                    ld_i_bukrs
    i_objnr =                    ld_i_objnr
    i_imkey =                    ld_i_imkey
*   i_key_for_output =           ld_i_key_for_output
  IMPORTING
    e_subrc =                    ld_e_subrc
  TABLES
    t_messages =                 it_t_messages
    .  "  FVARC_OBJECT_BALANCE_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_subrc
 
 TYPE SY-SUBRC ,
ld_i_obart
 
 TYPE TBO01-OBART ,
it_t_messages
 
 TYPE STANDARD TABLE OF SPROT_U ,
wa_t_messages
 
 LIKE LINE OF it_t_messages,
ld_i_bukrs
 
 TYPE VIOB01-BUKRS ,
ld_i_objnr
 
 TYPE VIOB01-J_OBJNR ,
ld_i_imkey
 
 TYPE VIOB01-IMKEY ,
ld_i_key_for_output
 
 TYPE VVOBJKEY-OBJID .



SELECT single OBART 
  FROM TBO01 
  INTO ld_i_obart.
 

"populate fields of struture and append to itab
append wa_t_messages to it_t_messages.

SELECT single BUKRS 
  FROM VIOB01 
  INTO ld_i_bukrs.


SELECT single J_OBJNR 
  FROM VIOB01 
  INTO ld_i_objnr.


SELECT single IMKEY 
  FROM VIOB01 
  INTO ld_i_imkey.


ld_i_key_for_output = some text here