SAP G_COMBINATION_GET Function Module for

Search SAP Function Modules

G_COMBINATION_GET is a standard g combination get 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 FM, simply by entering the name G_COMBINATION_GET 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 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'"
  EXPORTING
*  FIRST_CALL = ' ' "Indicator: 'X' = first valid combi
*  TAB_FLAG = ' ' "'X' = additional output of the val

 IMPORTING
   RECORD_KEY =  "Header of the user table

TABLES
   COMBINATION_TAB =  "Table with value combination and f

EXCEPTIONS
   NO_MORE_COMBINATIONS = 1    NO_VALID_COMBINATION = 2 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLGUMD_001 Master Data User Exits for Reading Text
EXIT_SAPLGUMD_002 User exits for master data - check value
EXIT_SAPLGUMD_003 Master data user exits for reading value set
EXIT_SAPLGUMD_004 Master data user exits - FREE internally used tables
EXIT_SAPLGUMD_005 User exits for master data - REFRESH internally used tables
EXIT_SAPLGUMD_006 User exits for master data - add record with period-dependent add. info.
EXIT_SAPLGUMD_007 User Exits for Master Data - Derive Record with Period-Independent Info.

IMPORTING Parameters details for G_COMBINATION_GET

FIRST_CALL - Indicator: 'X' = first valid combi

Data type: SY-BATCH
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TAB_FLAG - 'X' = additional output of the val

Data type: SY-BATCH
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for G_COMBINATION_GET

RECORD_KEY - Header of the user table

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

TABLES Parameters details for G_COMBINATION_GET

COMBINATION_TAB - Table with value combination and f

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

EXCEPTIONS details

NO_MORE_COMBINATIONS - No further value combinations avai

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 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 G_COMBINATION_GET

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