VB_GET_AND_WRITE_INOB_BUFFER SAP Function module

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

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

Pattern for FM VB_GET_AND_WRITE_INOB_BUFFER - VB GET AND WRITE INOB BUFFER

CALL FUNCTION 'VB_GET_AND_WRITE_INOB_BUFFER' "
  EXPORTING
    iv_matnr =                  " matnr         Material Number
*   iv_werks =                  " werks_d       Plant
    iv_charg =                  " charg_d       Batch Number
*   iv_bypass_buffer = SPACE    " xfeld         Checkbox
  IMPORTING
    ev_cuobj =                  " cuobj         Configuration (Internal Object Number)
    ev_already_buffered =       " xfeld         Checkbox
    ev_object =                 " objnum        Key of Object to Be Classified
  EXCEPTIONS
    NO_MATERIAL = 1             "
    NO_BATCH = 2                "
    NO_PLANT = 3                "
    .  "  VB_GET_AND_WRITE_INOB_BUFFER

ABAP code example for Function Module VB_GET_AND_WRITE_INOB_BUFFER

The ABAP code below is a full code listing to execute function module VB_GET_AND_WRITE_INOB_BUFFER 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_ev_cuobj  
 
 TYPE CUOBJ
,
ld_ev_already_buffered  
 
 TYPE XFELD
,
ld_ev_object  
 
 TYPE OBJNUM
.


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

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

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

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

CALL FUNCTION 'VB_GET_AND_WRITE_INOB_BUFFER'
  EXPORTING
    iv_matnr =                   ld_iv_matnr
*   iv_werks =                   ld_iv_werks
    iv_charg =                   ld_iv_charg
*   iv_bypass_buffer =           ld_iv_bypass_buffer
  IMPORTING
    ev_cuobj =                   ld_ev_cuobj
    ev_already_buffered =        ld_ev_already_buffered
    ev_object =                  ld_ev_object
  EXCEPTIONS
    NO_MATERIAL =                1
    NO_BATCH =                   2
    NO_PLANT =                   3
    .  "  VB_GET_AND_WRITE_INOB_BUFFER

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
ELSEIF SY-SUBRC EQ 3. "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_ev_cuobj
 
 TYPE CUOBJ ,
ld_iv_matnr
 
 TYPE MATNR ,
ld_ev_already_buffered
 
 TYPE XFELD ,
ld_iv_werks
 
 TYPE WERKS_D ,
ld_ev_object
 
 TYPE OBJNUM ,
ld_iv_charg
 
 TYPE CHARG_D ,
ld_iv_bypass_buffer
 
 TYPE XFELD .


ld_iv_matnr = 'Check type of data required'.
ld_iv_werks = 'Check type of data required'.
ld_iv_charg = 'Check type of data required'.
ld_iv_bypass_buffer = 'Check type of data required'.