SAP SCHEDULE_OWNER_GET_INTERNAL Function Module for Conversion of external to internal user name format

Search SAP Function Modules

SCHEDULE_OWNER_GET_INTERNAL is a standard schedule owner get internal SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conversion of external to internal user name format processing and below is the pattern details for this FM, 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 schedule owner get internal FM, simply by entering the name SCHEDULE_OWNER_GET_INTERNAL into the relevant SAP transaction such as SE37 or SE38.

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

Function SCHEDULE_OWNER_GET_INTERNAL 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 'SCHEDULE_OWNER_GET_INTERNAL'"Conversion of external to internal user name format
  EXPORTING
   OWNER_EXTERNAL_REPRESENTATION =  "External representation of user name
   WITH_DIALOG =  "ID for sending dialog window

TABLES
   OWNER_ADDRESS =  "User data

EXCEPTIONS
   OWNER_NOT_FOUND = 1 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLSSC1_001 Conversion of Internal to External User Name Format
EXIT_SAPLSSC1_002 Conversion of External to Internal User Name Format
EXIT_SAPLSSC1_003 User F4 Help

IMPORTING Parameters details for SCHEDULE_OWNER_GET_INTERNAL

OWNER_EXTERNAL_REPRESENTATION - External representation of user name

Data type: SCSADDRESS-NAME
Optional: No
Call by Reference: No ( called with pass by value option)

WITH_DIALOG - ID for sending dialog window

Data type: SCSDATAFLD-SC_FLAG
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SCHEDULE_OWNER_GET_INTERNAL

OWNER_ADDRESS - User data

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

EXCEPTIONS details

OWNER_NOT_FOUND - User name was not found

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

Copy and paste ABAP code example for SCHEDULE_OWNER_GET_INTERNAL 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.

ABAP code using 7.40 inline data declarations to call FM SCHEDULE_OWNER_GET_INTERNAL

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