LSO_VERSIONUPDATE_SET SAP Function module

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

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

Pattern for FM LSO_VERSIONUPDATE_SET - LSO VERSIONUPDATE SET

CALL FUNCTION 'LSO_VERSIONUPDATE_SET' "
  EXPORTING
    training_type =             " lso_training_type_c  Object Type of Course
    training_id =               " lso_training_id_c  Course
    training_langu =            " lso_training_langu_c  Course Language
    participation_id =          " lso_tpartdoc_c  Course Participation - Document
    update =                    " lso_version_update  Auxiliary Structure for Chain of Update Options
  IMPORTING
    error_occured =             " lso_x_c       Errors have occurred
  TABLES
    return =                    " bapiret2      Error Table
    .  "  LSO_VERSIONUPDATE_SET

ABAP code example for Function Module LSO_VERSIONUPDATE_SET

The ABAP code below is a full code listing to execute function module LSO_VERSIONUPDATE_SET 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_error_occured  
 
 TYPE LSO_X_C
,
it_return  
 
 TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_return
 
 LIKE LINE OF it_return
.


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

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

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

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

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

"populate fields of struture and append to itab
append wa_return to it_return.
.

CALL FUNCTION 'LSO_VERSIONUPDATE_SET'
  EXPORTING
    training_type =              ld_training_type
    training_id =                ld_training_id
    training_langu =             ld_training_langu
    participation_id =           ld_participation_id
    update =                     ld_update
  IMPORTING
    error_occured =              ld_error_occured
  TABLES
    return =                     it_return
    .  "  LSO_VERSIONUPDATE_SET

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_error_occured
 
 TYPE LSO_X_C ,
ld_training_type
 
 TYPE LSO_TRAINING_TYPE_C ,
it_return
 
 TYPE STANDARD TABLE OF BAPIRET2 ,
wa_return
 
 LIKE LINE OF it_return,
ld_training_id
 
 TYPE LSO_TRAINING_ID_C ,
ld_training_langu
 
 TYPE LSO_TRAINING_LANGU_C ,
ld_participation_id
 
 TYPE LSO_TPARTDOC_C ,
ld_update
 
 TYPE LSO_VERSION_UPDATE .


ld_training_type = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_return to it_return.
ld_training_id = 'Check type of data required'.
ld_training_langu = 'Check type of data required'.
ld_participation_id = 'Check type of data required'.
ld_update = 'Check type of data required'.