VBWC_BATCH_DECOUPLED_CHECK_RFC SAP Function module

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

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

Pattern for FM VBWC_BATCH_DECOUPLED_CHECK_RFC - VBWC BATCH DECOUPLED CHECK RFC

CALL FUNCTION 'VBWC_BATCH_DECOUPLED_CHECK_RFC' "
  EXPORTING
    i_matnr =                   " matnr
    i_charg =                   " charg_d
*   i_werks =                   " werks_d
  EXCEPTIONS
    NO_MATERIAL = 1             "
    NO_BATCH = 2                "
    NO_PLANT = 3                "
    BATCH_IS_DECOUPLED = 4      "
    SYSTEM_FAILURE = 5          "
    COMMUNICATION_FAILURE = 6   "
    .  "  VBWC_BATCH_DECOUPLED_CHECK_RFC

ABAP code example for Function Module VBWC_BATCH_DECOUPLED_CHECK_RFC

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

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

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

CALL FUNCTION 'VBWC_BATCH_DECOUPLED_CHECK_RFC'
  EXPORTING
    i_matnr =                    ld_i_matnr
    i_charg =                    ld_i_charg
*   i_werks =                    ld_i_werks
  EXCEPTIONS
    NO_MATERIAL =                1
    NO_BATCH =                   2
    NO_PLANT =                   3
    BATCH_IS_DECOUPLED =         4
    SYSTEM_FAILURE =             5
    COMMUNICATION_FAILURE =      6
    .  "  VBWC_BATCH_DECOUPLED_CHECK_RFC

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
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "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_matnr
 
 TYPE MATNR ,
ld_i_charg
 
 TYPE CHARG_D ,
ld_i_werks
 
 TYPE WERKS_D .


ld_i_matnr = 'Check type of data required'.
ld_i_charg = 'Check type of data required'.
ld_i_werks = 'Check type of data required'.