RCP323_STEXT_WRITE SAP Function module

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

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

Pattern for FM RCP323_STEXT_WRITE - RCP323 STEXT WRITE

CALL FUNCTION 'RCP323_STEXT_WRITE' "
  EXPORTING
    i_data_scenario =           " rcpe_datascen  Data Scenario for API Recipe
    i_valfrom =                 " rcpe_bdatum   Valid-To Date
*   i_applobj_type =            " pvs_applobj_type  Application Object Type for iPPE
  IMPORTING
    et_evt_obj_change =         " rmsaty_evt_obj_change  RMS-ATL: API - Table Type for Event Handling Obj-Spec. Attr.
    et_evt_relobj_change =      " rmsaty_evt_relobj_change  RMS-ATL: API - Table Type for Event Handling Dep. Objects
  CHANGING
    xt_stx =                    " rcpty_api_stx  RMS-RCP: API - Table Type for Short Texts
  EXCEPTIONS
    ERROR = 1                   "               Error When Writing
    .  "  RCP323_STEXT_WRITE

ABAP code example for Function Module RCP323_STEXT_WRITE

The ABAP code below is a full code listing to execute function module RCP323_STEXT_WRITE 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_evt_obj_change  
 
 TYPE RMSATY_EVT_OBJ_CHANGE
,
ld_et_evt_relobj_change  
 
 TYPE RMSATY_EVT_RELOBJ_CHANGE
.


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

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

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

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

CALL FUNCTION 'RCP323_STEXT_WRITE'
  EXPORTING
    i_data_scenario =            ld_i_data_scenario
    i_valfrom =                  ld_i_valfrom
*   i_applobj_type =             ld_i_applobj_type
  IMPORTING
    et_evt_obj_change =          ld_et_evt_obj_change
    et_evt_relobj_change =       ld_et_evt_relobj_change
  CHANGING
    xt_stx =                     ld_xt_stx
  EXCEPTIONS
    ERROR =                      1
    .  "  RCP323_STEXT_WRITE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_xt_stx
 
 TYPE RCPTY_API_STX ,
ld_et_evt_obj_change
 
 TYPE RMSATY_EVT_OBJ_CHANGE ,
ld_i_data_scenario
 
 TYPE RCPE_DATASCEN ,
ld_et_evt_relobj_change
 
 TYPE RMSATY_EVT_RELOBJ_CHANGE ,
ld_i_valfrom
 
 TYPE RCPE_BDATUM ,
ld_i_applobj_type
 
 TYPE PVS_APPLOBJ_TYPE .


ld_xt_stx = 'Check type of data required'.
ld_i_data_scenario = 'Check type of data required'.
ld_i_valfrom = 'Check type of data required'.
ld_i_applobj_type = 'Check type of data required'.