SAP Function Modules

CONFIRMATION_OBJECT_DISPATCHER SAP Function module - Distributes the Function Calls to the Relevant Function Modules







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

Associated Function Group: FVZLWF
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM CONFIRMATION_OBJECT_DISPATCHER - CONFIRMATION OBJECT DISPATCHER





CALL FUNCTION 'CONFIRMATION_OBJECT_DISPATCHER' "Distributes the Function Calls to the Relevant Function Modules
  EXPORTING
    action =                    " vconaction
    i_wrk_vzfgd =               " vzfgd         Release data (Informative data for the release procedure)
    i_tab_vzfgd =               " trty_vzfgd    Tabellentyp zur Tabelle VZFGD (Freigabedaten)
  IMPORTING
    e_success =                 " c
  EXCEPTIONS
    OBJECT_NOT_FOUND = 1        "
    NO_VALID_ACTION = 2         "
    .  "  CONFIRMATION_OBJECT_DISPATCHER

ABAP code example for Function Module CONFIRMATION_OBJECT_DISPATCHER





The ABAP code below is a full code listing to execute function module CONFIRMATION_OBJECT_DISPATCHER 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_success  TYPE C .

DATA(ld_action) = 'Check type of data required'.
DATA(ld_i_wrk_vzfgd) = 'Check type of data required'.
DATA(ld_i_tab_vzfgd) = 'Check type of data required'. . CALL FUNCTION 'CONFIRMATION_OBJECT_DISPATCHER' EXPORTING action = ld_action i_wrk_vzfgd = ld_i_wrk_vzfgd i_tab_vzfgd = ld_i_tab_vzfgd IMPORTING e_success = ld_e_success EXCEPTIONS OBJECT_NOT_FOUND = 1 NO_VALID_ACTION = 2 . " CONFIRMATION_OBJECT_DISPATCHER
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_e_success  TYPE C ,
ld_action  TYPE VCONACTION ,
ld_i_wrk_vzfgd  TYPE VZFGD ,
ld_i_tab_vzfgd  TYPE TRTY_VZFGD .

ld_action = 'Check type of data required'.
ld_i_wrk_vzfgd = 'Check type of data required'.
ld_i_tab_vzfgd = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CONFIRMATION_OBJECT_DISPATCHER or its description.