SAP G_COMBINATION_GET_EXIT Function Module for
G_COMBINATION_GET_EXIT is a standard g combination get exit 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 g combination get exit FM, simply by entering the name G_COMBINATION_GET_EXIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: GUMD
Program Name: SAPLGUMD
Main Program: SAPLGUMD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function G_COMBINATION_GET_EXIT 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 'G_COMBINATION_GET_EXIT'".
EXPORTING
* FIRST_CALL = ' ' "Indicator: 'X' = first valid combi
* TAB_FLAG = ' ' "'X' = additional output of the val
TABLES
COMB_FIELDS = "Pass on from G_COMBINATIONS_BUILD
RECORD_TAB = "Return of the valid value combinat
EXCEPTIONS
NO_EXIT = 1 NO_MORE_COMBINATIONS = 2 NO_PERIODS_EXIT2 = 3 NO_VALID_COMBINATION = 4
IMPORTING Parameters details for G_COMBINATION_GET_EXIT
FIRST_CALL - Indicator: 'X' = first valid combi
Data type: SY-BATCHDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TAB_FLAG - 'X' = additional output of the val
Data type: SY-BATCHDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for G_COMBINATION_GET_EXIT
COMB_FIELDS - Pass on from G_COMBINATIONS_BUILD
Data type: GMD02Optional: No
Call by Reference: No ( called with pass by value option)
RECORD_TAB - Return of the valid value combinat
Data type: TABLEOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_EXIT - no exit in tab.800D, in spite of Z
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_MORE_COMBINATIONS - No further value combinations avai
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PERIODS_EXIT2 - G/L account number
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VALID_COMBINATION - No value combination found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for G_COMBINATION_GET_EXIT 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_no_exit | TYPE STRING, " | |||
| lv_first_call | TYPE SY-BATCH, " ' ' | |||
| lt_comb_fields | TYPE STANDARD TABLE OF GMD02, " | |||
| lv_tab_flag | TYPE SY-BATCH, " ' ' | |||
| lt_record_tab | TYPE STANDARD TABLE OF TABLE, " | |||
| lv_no_more_combinations | TYPE TABLE, " | |||
| lv_no_periods_exit2 | TYPE TABLE, " | |||
| lv_no_valid_combination | TYPE TABLE. " |
|   CALL FUNCTION 'G_COMBINATION_GET_EXIT' " |
| EXPORTING | ||
| FIRST_CALL | = lv_first_call | |
| TAB_FLAG | = lv_tab_flag | |
| TABLES | ||
| COMB_FIELDS | = lt_comb_fields | |
| RECORD_TAB | = lt_record_tab | |
| EXCEPTIONS | ||
| NO_EXIT = 1 | ||
| NO_MORE_COMBINATIONS = 2 | ||
| NO_PERIODS_EXIT2 = 3 | ||
| NO_VALID_COMBINATION = 4 | ||
| . " G_COMBINATION_GET_EXIT | ||
ABAP code using 7.40 inline data declarations to call FM G_COMBINATION_GET_EXIT
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 BATCH FROM SY INTO @DATA(ld_first_call). | ||||
| DATA(ld_first_call) | = ' '. | |||
| "SELECT single BATCH FROM SY INTO @DATA(ld_tab_flag). | ||||
| DATA(ld_tab_flag) | = ' '. | |||
Search for further information about these or an SAP related objects