SAP LSO_IF_WS_GET_USER_TRACKING Function Module for









LSO_IF_WS_GET_USER_TRACKING is a standard lso if ws get user tracking 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 ws get user tracking FM, simply by entering the name LSO_IF_WS_GET_USER_TRACKING into the relevant SAP transaction such as SE37 or SE38.

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



Function LSO_IF_WS_GET_USER_TRACKING 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_WS_GET_USER_TRACKING'"
  EXPORTING
*  IS_CUSTOMER_AUTHORIZATION =  "Web Service: Customer Authorization in eLSP
*  IV_USER_LOGIN =  "User Back-End System
*  IV_USER_PASSWORD =  "Password Back-End User
*  IV_USER_ROLE = 'LEARNER' "WebService: User Role
   IV_LEARNER_ID =  "WebService: Learner ID (plvar, sclas, sobid)
*  IV_COMMUNICATION_LANGUAGE =  "Language According to ISO 639
   IS_PARTICIPATION_DATA =  "Web Service: External Participation/Course ID
*  IV_DATE =  "Key Date
*  IV_READ_ELSP_TRACKING =  "

 IMPORTING
   ET_RETURN =  "WebService: Answer from Booking WebService
.



IMPORTING Parameters details for LSO_IF_WS_GET_USER_TRACKING

IS_CUSTOMER_AUTHORIZATION - Web Service: Customer Authorization in eLSP

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

IV_USER_LOGIN - User Back-End System

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

IV_USER_PASSWORD - Password Back-End User

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

IV_USER_ROLE - WebService: User Role

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

IV_LEARNER_ID - WebService: Learner ID (plvar, sclas, sobid)

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

IV_COMMUNICATION_LANGUAGE - Language According to ISO 639

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

IS_PARTICIPATION_DATA - Web Service: External Participation/Course ID

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

IV_DATE - Key Date

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

IV_READ_ELSP_TRACKING -

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

EXPORTING Parameters details for LSO_IF_WS_GET_USER_TRACKING

ET_RETURN - WebService: Answer from Booking WebService

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

Copy and paste ABAP code example for LSO_IF_WS_GET_USER_TRACKING 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:
lv_et_return  TYPE LSO_WS_TRACKING_RET_LIST, "   
lv_is_customer_authorization  TYPE LSO_WS_CUSTOMER_AUTHORIZATION, "   
lv_iv_user_login  TYPE LSO_BACUS, "   
lv_iv_user_password  TYPE LSO_BACPW, "   
lv_iv_user_role  TYPE LSO_WS_USER_ROLE, "   'LEARNER'
lv_iv_learner_id  TYPE LSO_WS_LEARNER_ID, "   
lv_iv_communication_language  TYPE LAISO, "   
lv_is_participation_data  TYPE LSO_WS_PARTICIPATION_DATA, "   
lv_iv_date  TYPE SELDT, "   
lv_iv_read_elsp_tracking  TYPE FLAG_X. "   

  CALL FUNCTION 'LSO_IF_WS_GET_USER_TRACKING'  "
    EXPORTING
         IS_CUSTOMER_AUTHORIZATION = lv_is_customer_authorization
         IV_USER_LOGIN = lv_iv_user_login
         IV_USER_PASSWORD = lv_iv_user_password
         IV_USER_ROLE = lv_iv_user_role
         IV_LEARNER_ID = lv_iv_learner_id
         IV_COMMUNICATION_LANGUAGE = lv_iv_communication_language
         IS_PARTICIPATION_DATA = lv_is_participation_data
         IV_DATE = lv_iv_date
         IV_READ_ELSP_TRACKING = lv_iv_read_elsp_tracking
    IMPORTING
         ET_RETURN = lv_et_return
. " LSO_IF_WS_GET_USER_TRACKING




ABAP code using 7.40 inline data declarations to call FM LSO_IF_WS_GET_USER_TRACKING

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_iv_user_role) = 'LEARNER'.
 
 
 
 
 
 


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!