SAP UDM_WORKAREA_SUBSCREEN_SET Function Module for









UDM_WORKAREA_SUBSCREEN_SET is a standard udm workarea subscreen set 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 udm workarea subscreen set FM, simply by entering the name UDM_WORKAREA_SUBSCREEN_SET into the relevant SAP transaction such as SE37 or SE38.

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



Function UDM_WORKAREA_SUBSCREEN_SET 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 'UDM_WORKAREA_SUBSCREEN_SET'"
EXPORTING
I_SCREEN = "Locator: Basis Class for MAIN_SCREEN and SUB_SCREEN
.



IMPORTING Parameters details for UDM_WORKAREA_SUBSCREEN_SET

I_SCREEN - Locator: Basis Class for MAIN_SCREEN and SUB_SCREEN

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

Copy and paste ABAP code example for UDM_WORKAREA_SUBSCREEN_SET 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_i_screen  TYPE CL_BUS_ABSTRACT_SUB_SCREEN. "   

  CALL FUNCTION 'UDM_WORKAREA_SUBSCREEN_SET'  "
    EXPORTING
         I_SCREEN = lv_i_screen
. " UDM_WORKAREA_SUBSCREEN_SET




ABAP code using 7.40 inline data declarations to call FM UDM_WORKAREA_SUBSCREEN_SET

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!