OUTBOUND_CALL_00106131_P SAP Function module

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

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

Pattern for FM OUTBOUND_CALL_00106131_P - OUTBOUND CALL 00106131 P

CALL FUNCTION 'OUTBOUND_CALL_00106131_P' "
* EXPORTING
*   u_screen_name =             " ddshdynfld
*   u_screen_group1 =           " char3
*   u_screen_group2 =           " char3
*   u_screen_group3 =           " char3
*   u_screen_group4 =           " char3
*   u_others_sel_crit =         " xfeld
* CHANGING
*   c_screen_required =         " char1
*   c_screen_input =            " char1
*   c_screen_output =           " char1
*   c_screen_intensified =      " char1
*   c_screen_invisible =        " char1
*   c_screen_active =           " char1
*   c_screen_display_3d =       " char1
*   c_screen_value_help =       " char1
*   c_screen_request =          " char1
*   c_flg_modify =              " xfeld
    .  "  OUTBOUND_CALL_00106131_P

ABAP code example for Function Module OUTBOUND_CALL_00106131_P

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

CALL FUNCTION 'OUTBOUND_CALL_00106131_P'
* EXPORTING
*   u_screen_name =              ld_u_screen_name
*   u_screen_group1 =            ld_u_screen_group1
*   u_screen_group2 =            ld_u_screen_group2
*   u_screen_group3 =            ld_u_screen_group3
*   u_screen_group4 =            ld_u_screen_group4
*   u_others_sel_crit =          ld_u_others_sel_crit
* CHANGING
*   c_screen_required =          ld_c_screen_required
*   c_screen_input =             ld_c_screen_input
*   c_screen_output =            ld_c_screen_output
*   c_screen_intensified =       ld_c_screen_intensified
*   c_screen_invisible =         ld_c_screen_invisible
*   c_screen_active =            ld_c_screen_active
*   c_screen_display_3d =        ld_c_screen_display_3d
*   c_screen_value_help =        ld_c_screen_value_help
*   c_screen_request =           ld_c_screen_request
*   c_flg_modify =               ld_c_flg_modify
    .  "  OUTBOUND_CALL_00106131_P

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_c_screen_required
 
 TYPE CHAR1 ,
ld_u_screen_name
 
 TYPE DDSHDYNFLD ,
ld_c_screen_input
 
 TYPE CHAR1 ,
ld_u_screen_group1
 
 TYPE CHAR3 ,
ld_c_screen_output
 
 TYPE CHAR1 ,
ld_u_screen_group2
 
 TYPE CHAR3 ,
ld_c_screen_intensified
 
 TYPE CHAR1 ,
ld_u_screen_group3
 
 TYPE CHAR3 ,
ld_c_screen_invisible
 
 TYPE CHAR1 ,
ld_u_screen_group4
 
 TYPE CHAR3 ,
ld_c_screen_active
 
 TYPE CHAR1 ,
ld_u_others_sel_crit
 
 TYPE XFELD ,
ld_c_screen_display_3d
 
 TYPE CHAR1 ,
ld_c_screen_value_help
 
 TYPE CHAR1 ,
ld_c_screen_request
 
 TYPE CHAR1 ,
ld_c_flg_modify
 
 TYPE XFELD .


ld_c_screen_required = 'Check type of data required'.
ld_u_screen_name = 'Check type of data required'.
ld_c_screen_input = 'Check type of data required'.
ld_u_screen_group1 = 'Check type of data required'.
ld_c_screen_output = 'Check type of data required'.
ld_u_screen_group2 = 'Check type of data required'.
ld_c_screen_intensified = 'Check type of data required'.
ld_u_screen_group3 = 'Check type of data required'.
ld_c_screen_invisible = 'Check type of data required'.
ld_u_screen_group4 = 'Check type of data required'.
ld_c_screen_active = 'Check type of data required'.
ld_u_others_sel_crit = 'Check type of data required'.
ld_c_screen_display_3d = 'Check type of data required'.
ld_c_screen_value_help = 'Check type of data required'.
ld_c_screen_request = 'Check type of data required'.
ld_c_flg_modify = 'Check type of data required'.

SAP Documentation for FM OUTBOUND_CALL_00106131_P