SAP LSO_IF_VERSIONUPDATE Function Module for









LSO_IF_VERSIONUPDATE is a standard lso if versionupdate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for lso if versionupdate FM, simply by entering the name LSO_IF_VERSIONUPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: LSO_VERSIONING
Program Name: SAPLLSO_VERSIONING
Main Program: SAPLLSO_VERSIONING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function LSO_IF_VERSIONUPDATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'LSO_IF_VERSIONUPDATE'"
  EXPORTING
   PLANVERSION =  "Plan Version
   TRAINING_TYPE =  "Object Type of Course
   TRAINING_ID =  "Course
   TRAINING_LANGU =  "Course Language
*  TRAININGTYPE_TYPE =  "Object Type of Course Type
*  TRAININGTYPE_ID =  "Course Type Object ID
   TPARTDOC =  "Course Participation - Document
*  UPDATE_IN = 'A' "
*  UPDATE_STRUC_IN =  "

 IMPORTING
   UPDATE_NECESSARY =  "
   UPDATE_STATUS =  "
   UPDATE_OUT =  "
   ERROR_OCCURED =  "Errors have occurred

TABLES
*  RETURN =  "Return Parameter(s)
.



IMPORTING Parameters details for LSO_IF_VERSIONUPDATE

PLANVERSION - Plan Version

Data type: PLVAR
Optional: No
Call by Reference: No ( called with pass by value option)

TRAINING_TYPE - Object Type of Course

Data type: LSO_TRAINING_TYPE_C
Optional: No
Call by Reference: No ( called with pass by value option)

TRAINING_ID - Course

Data type: LSO_TRAINING_ID_C
Optional: No
Call by Reference: No ( called with pass by value option)

TRAINING_LANGU - Course Language

Data type: LSO_TRAINING_LANGU_C
Optional: No
Call by Reference: No ( called with pass by value option)

TRAININGTYPE_TYPE - Object Type of Course Type

Data type: LSO_TRAINTYPE_TYPE_C
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRAININGTYPE_ID - Course Type Object ID

Data type: LSO_TRAINTYPE_ID_C
Optional: Yes
Call by Reference: No ( called with pass by value option)

TPARTDOC - Course Participation - Document

Data type: LSO_TPARTDOC_C
Optional: No
Call by Reference: No ( called with pass by value option)

UPDATE_IN -

Data type: CHAR1
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPDATE_STRUC_IN -

Data type: LSO_VERSION_UPDATE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for LSO_IF_VERSIONUPDATE

UPDATE_NECESSARY -

Data type: LSO_UPDATE_NECESSARY
Optional: No
Call by Reference: No ( called with pass by value option)

UPDATE_STATUS -

Data type: CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

UPDATE_OUT -

Data type: LSO_VERSION_UPDATE
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_OCCURED - Errors have occurred

Data type: LSO_X_C
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for LSO_IF_VERSIONUPDATE

RETURN - Return Parameter(s)

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for LSO_IF_VERSIONUPDATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_planversion  TYPE PLVAR, "   
lv_update_necessary  TYPE LSO_UPDATE_NECESSARY, "   
lv_training_type  TYPE LSO_TRAINING_TYPE_C, "   
lv_update_status  TYPE CHAR1, "   
lv_update_out  TYPE LSO_VERSION_UPDATE, "   
lv_training_id  TYPE LSO_TRAINING_ID_C, "   
lv_error_occured  TYPE LSO_X_C, "   
lv_training_langu  TYPE LSO_TRAINING_LANGU_C, "   
lv_trainingtype_type  TYPE LSO_TRAINTYPE_TYPE_C, "   
lv_trainingtype_id  TYPE LSO_TRAINTYPE_ID_C, "   
lv_tpartdoc  TYPE LSO_TPARTDOC_C, "   
lv_update_in  TYPE CHAR1, "   'A'
lv_update_struc_in  TYPE LSO_VERSION_UPDATE. "   

  CALL FUNCTION 'LSO_IF_VERSIONUPDATE'  "
    EXPORTING
         PLANVERSION = lv_planversion
         TRAINING_TYPE = lv_training_type
         TRAINING_ID = lv_training_id
         TRAINING_LANGU = lv_training_langu
         TRAININGTYPE_TYPE = lv_trainingtype_type
         TRAININGTYPE_ID = lv_trainingtype_id
         TPARTDOC = lv_tpartdoc
         UPDATE_IN = lv_update_in
         UPDATE_STRUC_IN = lv_update_struc_in
    IMPORTING
         UPDATE_NECESSARY = lv_update_necessary
         UPDATE_STATUS = lv_update_status
         UPDATE_OUT = lv_update_out
         ERROR_OCCURED = lv_error_occured
    TABLES
         RETURN = lt_return
. " LSO_IF_VERSIONUPDATE




ABAP code using 7.40 inline data declarations to call FM LSO_IF_VERSIONUPDATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_update_in) = 'A'.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!