SAP ALM_GAPART_SELECT_FOR_TASK Function Module for Choose ALM Valuation Type for Manual Transport
ALM_GAPART_SELECT_FOR_TASK is a standard alm gapart select for task SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Choose ALM Valuation Type for Manual Transport 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 alm gapart select for task FM, simply by entering the name ALM_GAPART_SELECT_FOR_TASK into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBGAPART
Program Name: SAPLJBGAPART
Main Program: SAPLJBGAPART
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALM_GAPART_SELECT_FOR_TASK 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 'ALM_GAPART_SELECT_FOR_TASK'"Choose ALM Valuation Type for Manual Transport.
TABLES
E_TAB_JBRBG2 = "Gap Analysis - Global Control
EXCEPTIONS
CANCELED_BY_USER = 1
TABLES Parameters details for ALM_GAPART_SELECT_FOR_TASK
E_TAB_JBRBG2 - Gap Analysis - Global Control
Data type: JBRBG2Optional: No
Call by Reference: Yes
EXCEPTIONS details
CANCELED_BY_USER - Process cancelled by user
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ALM_GAPART_SELECT_FOR_TASK 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: | ||||
| lt_e_tab_jbrbg2 | TYPE STANDARD TABLE OF JBRBG2, " | |||
| lv_canceled_by_user | TYPE JBRBG2. " |
|   CALL FUNCTION 'ALM_GAPART_SELECT_FOR_TASK' "Choose ALM Valuation Type for Manual Transport |
| TABLES | ||
| E_TAB_JBRBG2 | = lt_e_tab_jbrbg2 | |
| EXCEPTIONS | ||
| CANCELED_BY_USER = 1 | ||
| . " ALM_GAPART_SELECT_FOR_TASK | ||
ABAP code using 7.40 inline data declarations to call FM ALM_GAPART_SELECT_FOR_TASK
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