SAP UC_CALL_SEL_SCREEN Function Module for

Search SAP Function Modules

UC_CALL_SEL_SCREEN is a standard uc call sel screen 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 uc call sel screen FM, simply by entering the name UC_CALL_SEL_SCREEN into the relevant SAP transaction such as SE37 or SE38.

Function Group: UCUM_02
Program Name: SAPLUCUM_02
Main Program: SAPLUCUM_02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UC_CALL_SEL_SCREEN 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 'UC_CALL_SEL_SCREEN'"
  EXPORTING
   IO_MODEL =  "Model (Field Catalog, ...)
   IO_AREA =  "Consolidation Area
   IO_PARAMETER =  "Consolidation Area
   IO_SSCR_GENERATE =  "
   I_DNUM =  "Screen Number
   I_AREA =  "Consolidation Area
*  I_TASKTYPE =  "Task Category
*  I_GROUP =  "
*  I_TASKGRP =  "Task Group

 IMPORTING
   ET_SEL =  "Sorted Table: Selection Condition (Range per Field)

CHANGING
   CS_SEL_FIX =  "Structure f. Fixed Subscreen
   CT_CHECKBOX =  "Table with Checkbox Parameters

EXCEPTIONS
   CANCELED = 1    SCREEN_NOT_AVAILABLE = 2 

.

IMPORTING Parameters details for UC_CALL_SEL_SCREEN

IO_MODEL - Model (Field Catalog, ...)

Data type: IF_UC_MODEL
Optional: No
Call by Reference: Yes

IO_AREA - Consolidation Area

Data type: IF_UC_AREA
Optional: No
Call by Reference: Yes

IO_PARAMETER - Consolidation Area

Data type: IF_UC_PARAMETER
Optional: No
Call by Reference: Yes

IO_SSCR_GENERATE -

Data type: CL_UC_SSCR_GENERATE
Optional: No
Call by Reference: Yes

I_DNUM - Screen Number

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

I_AREA - Consolidation Area

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

I_TASKTYPE - Task Category

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

I_GROUP -

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

I_TASKGRP - Task Group

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

EXPORTING Parameters details for UC_CALL_SEL_SCREEN

ET_SEL - Sorted Table: Selection Condition (Range per Field)

Data type: UC0_TS_SEL
Optional: No
Call by Reference: Yes

CHANGING Parameters details for UC_CALL_SEL_SCREEN

CS_SEL_FIX - Structure f. Fixed Subscreen

Data type: UCU_S_SSCR_FIX
Optional: No
Call by Reference: Yes

CT_CHECKBOX - Table with Checkbox Parameters

Data type: UCU_T_SSCR_VALUE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CANCELED - Cancel

Data type:
Optional: No
Call by Reference: Yes

SCREEN_NOT_AVAILABLE -

Data type:
Optional: No
Call by Reference: Yes

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

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