SAP PROD_VERSIONS_SUB_SCREEN Function Module for Determine screen modules for production versions according to T437A
PROD_VERSIONS_SUB_SCREEN is a standard prod versions sub screen SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine screen modules for production versions according to T437A 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 prod versions sub screen FM, simply by entering the name PROD_VERSIONS_SUB_SCREEN into the relevant SAP transaction such as SE37 or SE38.
Function Group: MSA0
Program Name: SAPLMSA0
Main Program: SAPLMSA0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PROD_VERSIONS_SUB_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 'PROD_VERSIONS_SUB_SCREEN'"Determine screen modules for production versions according to T437A.
EXPORTING
* GET_PA_LINIE = ' ' "Carry out indic. 'Get Parameter' for line 1
* KZANZ = ' ' "Indicator 'Display only'
IMPORTING
SUB_SCREEN_1 = "Screen module 1
SUB_SCREEN_2 = "Screen module 2
T437A_WA = "GI T437A
EXCEPTIONS
T437A_NOT_FOUND = 1
IMPORTING Parameters details for PROD_VERSIONS_SUB_SCREEN
GET_PA_LINIE - Carry out indic. 'Get Parameter' for line 1
Data type: SY-MARKYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
KZANZ - Indicator 'Display only'
Data type: SY-MARKYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PROD_VERSIONS_SUB_SCREEN
SUB_SCREEN_1 - Screen module 1
Data type: SY-DYNNROptional: No
Call by Reference: No ( called with pass by value option)
SUB_SCREEN_2 - Screen module 2
Data type: SY-DYNNROptional: No
Call by Reference: No ( called with pass by value option)
T437A_WA - GI T437A
Data type: T437AOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
T437A_NOT_FOUND - Entry in T437A is missing
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PROD_VERSIONS_SUB_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.| DATA: | ||||
| lv_get_pa_linie | TYPE SY-MARKY, " SPACE | |||
| lv_sub_screen_1 | TYPE SY-DYNNR, " | |||
| lv_t437a_not_found | TYPE SY, " | |||
| lv_kzanz | TYPE SY-MARKY, " SPACE | |||
| lv_sub_screen_2 | TYPE SY-DYNNR, " | |||
| lv_t437a_wa | TYPE T437A. " |
|   CALL FUNCTION 'PROD_VERSIONS_SUB_SCREEN' "Determine screen modules for production versions according to T437A |
| EXPORTING | ||
| GET_PA_LINIE | = lv_get_pa_linie | |
| KZANZ | = lv_kzanz | |
| IMPORTING | ||
| SUB_SCREEN_1 | = lv_sub_screen_1 | |
| SUB_SCREEN_2 | = lv_sub_screen_2 | |
| T437A_WA | = lv_t437a_wa | |
| EXCEPTIONS | ||
| T437A_NOT_FOUND = 1 | ||
| . " PROD_VERSIONS_SUB_SCREEN | ||
ABAP code using 7.40 inline data declarations to call FM PROD_VERSIONS_SUB_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.| "SELECT single MARKY FROM SY INTO @DATA(ld_get_pa_linie). | ||||
| DATA(ld_get_pa_linie) | = ' '. | |||
| "SELECT single DYNNR FROM SY INTO @DATA(ld_sub_screen_1). | ||||
| "SELECT single MARKY FROM SY INTO @DATA(ld_kzanz). | ||||
| DATA(ld_kzanz) | = ' '. | |||
| "SELECT single DYNNR FROM SY INTO @DATA(ld_sub_screen_2). | ||||
Search for further information about these or an SAP related objects