OSPIH_DEFAULT_EMAIL_ITEM SAP Function module - To call the email proxy

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

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

Pattern for FM OSPIH_DEFAULT_EMAIL_ITEM - OSPIH DEFAULT EMAIL ITEM

CALL FUNCTION 'OSPIH_DEFAULT_EMAIL_ITEM' "To call the email proxy
  EXPORTING
*   iv_bound_item_type =        " string        Groupware Object-Bound Item type
    iv_owner =                  " syuname       User Names
*   iv_data_source =            " string        Data source ID
*   is_scenario_type =          " ospwscenario  Proxy Structure (generated)
*   is_email_item =             " ospwemail     Proxy Structure (generated)
*   iv_unbind_only =            " char5         unbind flag
  IMPORTING
    et_return =                 " bapirettab    Table with BAPI Return Information
    .  "  OSPIH_DEFAULT_EMAIL_ITEM

ABAP code example for Function Module OSPIH_DEFAULT_EMAIL_ITEM

The ABAP code below is a full code listing to execute function module OSPIH_DEFAULT_EMAIL_ITEM 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_et_return  
 
 TYPE BAPIRETTAB
.


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

DATA(ld_iv_owner) = 'some text here'.

DATA(ld_iv_data_source) = 'some text here'.

DATA(ld_is_scenario_type) = 'some text here'.

DATA(ld_is_email_item) = 'some text here'.

DATA(ld_iv_unbind_only) = 'some text here'.
.

CALL FUNCTION 'OSPIH_DEFAULT_EMAIL_ITEM'
  EXPORTING
*   iv_bound_item_type =         ld_iv_bound_item_type
    iv_owner =                   ld_iv_owner
*   iv_data_source =             ld_iv_data_source
*   is_scenario_type =           ld_is_scenario_type
*   is_email_item =              ld_is_email_item
*   iv_unbind_only =             ld_iv_unbind_only
  IMPORTING
    et_return =                  ld_et_return
    .  "  OSPIH_DEFAULT_EMAIL_ITEM

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_et_return
 
 TYPE BAPIRETTAB ,
ld_iv_bound_item_type
 
 TYPE STRING ,
ld_iv_owner
 
 TYPE SYUNAME ,
ld_iv_data_source
 
 TYPE STRING ,
ld_is_scenario_type
 
 TYPE OSPWSCENARIO ,
ld_is_email_item
 
 TYPE OSPWEMAIL ,
ld_iv_unbind_only
 
 TYPE CHAR5 .


ld_iv_bound_item_type = 'some text here'.
ld_iv_owner = 'some text here'.
ld_iv_data_source = 'some text here'.
ld_is_scenario_type = 'some text here'.
ld_is_email_item = 'some text here'.
ld_iv_unbind_only = 'some text here'.