SAP SCHEDULE_OWNER_MAINTAIN_DIALOG Function Module for
SCHEDULE_OWNER_MAINTAIN_DIALOG is a standard schedule owner maintain dialog 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 schedule owner maintain dialog FM, simply by entering the name SCHEDULE_OWNER_MAINTAIN_DIALOG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SSC4
Program Name: SAPLSSC4
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SCHEDULE_OWNER_MAINTAIN_DIALOG 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_MAINTAIN_DIALOG'".
EXPORTING
OWNER_ATTR_INPUT = "User
* START_COLUMN = '3' "Start column of pop-up
* START_ROW = '1' "Start row of pop-up
* ERROR_MESSAGE = "Error message
IMPORTING
OWNER_ATTR_OUTPUT = "User
OWNER_EXTERNAL_REPRESENTATION = "
LENGTH = "
RETURN_CODE = "Return value
IMPORTING Parameters details for SCHEDULE_OWNER_MAINTAIN_DIALOG
OWNER_ATTR_INPUT - User
Data type: SCSOATTROptional: No
Call by Reference: No ( called with pass by value option)
START_COLUMN - Start column of pop-up
Data type: SY-SCOLSDefault: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)
START_ROW - Start row of pop-up
Data type: SY-SROWSDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ERROR_MESSAGE - Error message
Data type: SCSERROROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SCHEDULE_OWNER_MAINTAIN_DIALOG
OWNER_ATTR_OUTPUT - User
Data type: SCSOATTROptional: No
Call by Reference: No ( called with pass by value option)
OWNER_EXTERNAL_REPRESENTATION -
Data type: SCSADDRESS-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
LENGTH -
Data type: SCSDATAFLD-LENGTHOptional: No
Call by Reference: No ( called with pass by value option)
RETURN_CODE - Return value
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SCHEDULE_OWNER_MAINTAIN_DIALOG 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_owner_attr_input | TYPE SCSOATTR, " | |||
| lv_owner_attr_output | TYPE SCSOATTR, " | |||
| lv_start_column | TYPE SY-SCOLS, " '3' | |||
| lv_owner_external_representation | TYPE SCSADDRESS-NAME, " | |||
| lv_length | TYPE SCSDATAFLD-LENGTH, " | |||
| lv_start_row | TYPE SY-SROWS, " '1' | |||
| lv_return_code | TYPE SY-SUBRC, " | |||
| lv_error_message | TYPE SCSERROR. " |
|   CALL FUNCTION 'SCHEDULE_OWNER_MAINTAIN_DIALOG' " |
| EXPORTING | ||
| OWNER_ATTR_INPUT | = lv_owner_attr_input | |
| START_COLUMN | = lv_start_column | |
| START_ROW | = lv_start_row | |
| ERROR_MESSAGE | = lv_error_message | |
| IMPORTING | ||
| OWNER_ATTR_OUTPUT | = lv_owner_attr_output | |
| OWNER_EXTERNAL_REPRESENTATION | = lv_owner_external_representation | |
| LENGTH | = lv_length | |
| RETURN_CODE | = lv_return_code | |
| . " SCHEDULE_OWNER_MAINTAIN_DIALOG | ||
ABAP code using 7.40 inline data declarations to call FM SCHEDULE_OWNER_MAINTAIN_DIALOG
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.| "SELECT single SCOLS FROM SY INTO @DATA(ld_start_column). | ||||
| DATA(ld_start_column) | = '3'. | |||
| "SELECT single NAME FROM SCSADDRESS INTO @DATA(ld_owner_external_representation). | ||||
| "SELECT single LENGTH FROM SCSDATAFLD INTO @DATA(ld_length). | ||||
| "SELECT single SROWS FROM SY INTO @DATA(ld_start_row). | ||||
| DATA(ld_start_row) | = '1'. | |||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_return_code). | ||||
Search for further information about these or an SAP related objects