SAP ISU_GET_USERID Function Module for









ISU_GET_USERID is a standard isu get userid 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 isu get userid FM, simply by entering the name ISU_GET_USERID into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_GET_USERID 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 'ISU_GET_USERID'"
  EXPORTING
   PSUSER =  "
   POST_CODE1 =  "
   EMAIL =  "
   PASSWORD =  "
   NAME_LAST =  "
   NAME_FIRST =  "
   DR_LICENSE =  "
   SOC_SECURE =  "
   STREET =  "
   HOUSE_NUM1 =  "
   HOUSE_NUM2 =  "

 IMPORTING
   Y_FAILED =  "
   Y_USER =  "
   Y_PASSWORD =  "
   Y_PARTNER =  "

EXCEPTIONS
   NOT_FOUND = 1    NOT_UNIQUE = 2    WRONG_PASSWORD = 3
.



IMPORTING Parameters details for ISU_GET_USERID

PSUSER -

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

POST_CODE1 -

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

EMAIL -

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

PASSWORD -

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

NAME_LAST -

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

NAME_FIRST -

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

DR_LICENSE -

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

SOC_SECURE -

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

STREET -

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

HOUSE_NUM1 -

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

HOUSE_NUM2 -

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

EXPORTING Parameters details for ISU_GET_USERID

Y_FAILED -

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

Y_USER -

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

Y_PASSWORD -

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

Y_PARTNER -

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

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NOT_UNIQUE -

Data type:
Optional: No
Call by Reference: Yes

WRONG_PASSWORD -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_GET_USERID 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_psuser  TYPE XUBNAME, "   
lv_y_failed  TYPE KENNZX, "   
lv_not_found  TYPE KENNZX, "   
lv_post_code1  TYPE AD_PSTCD1, "   
lv_email  TYPE AD_SMTPADR, "   
lv_y_user  TYPE XUBNAME, "   
lv_password  TYPE WWWPASS, "   
lv_not_unique  TYPE WWWPASS, "   
lv_name_last  TYPE BU_NAMEP_L, "   
lv_y_password  TYPE EXUNCODE, "   
lv_wrong_password  TYPE EXUNCODE, "   
lv_y_partner  TYPE BU_PARTNER, "   
lv_name_first  TYPE BU_NAMEP_F, "   
lv_dr_license  TYPE DR_LICENSE, "   
lv_soc_secure  TYPE E_SOC_SECU, "   
lv_street  TYPE AD_STREET, "   
lv_house_num1  TYPE AD_HSNM1, "   
lv_house_num2  TYPE AD_HSNM2. "   

  CALL FUNCTION 'ISU_GET_USERID'  "
    EXPORTING
         PSUSER = lv_psuser
         POST_CODE1 = lv_post_code1
         EMAIL = lv_email
         PASSWORD = lv_password
         NAME_LAST = lv_name_last
         NAME_FIRST = lv_name_first
         DR_LICENSE = lv_dr_license
         SOC_SECURE = lv_soc_secure
         STREET = lv_street
         HOUSE_NUM1 = lv_house_num1
         HOUSE_NUM2 = lv_house_num2
    IMPORTING
         Y_FAILED = lv_y_failed
         Y_USER = lv_y_user
         Y_PASSWORD = lv_y_password
         Y_PARTNER = lv_y_partner
    EXCEPTIONS
        NOT_FOUND = 1
        NOT_UNIQUE = 2
        WRONG_PASSWORD = 3
. " ISU_GET_USERID




ABAP code using 7.40 inline data declarations to call FM ISU_GET_USERID

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!