SAP FM_COMB_CUST Function Module for Check in customizing for Comb Docs
FM_COMB_CUST is a standard fm comb cust SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check in customizing for Comb Docs 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 fm comb cust FM, simply by entering the name FM_COMB_CUST into the relevant SAP transaction such as SE37 or SE38.
Function Group: COMB_1
Program Name: SAPLCOMB_1
Main Program: SAPLCOMB_1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_COMB_CUST 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 'FM_COMB_CUST'"Check in customizing for Comb Docs.
EXPORTING
I_FMBLCOREIN = "Budgetary Ledger Interface
IMPORTING
E_JUMP = "Checkbox
E_COMB = "Combined Document Predecessors
IMPORTING Parameters details for FM_COMB_CUST
I_FMBLCOREIN - Budgetary Ledger Interface
Data type: FMBLCOREINOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FM_COMB_CUST
E_JUMP - Checkbox
Data type: XFELDOptional: No
Call by Reference: Yes
E_COMB - Combined Document Predecessors
Data type: FM_COMBOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FM_COMB_CUST 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_e_jump | TYPE XFELD, " | |||
| lv_i_fmblcorein | TYPE FMBLCOREIN, " | |||
| lv_e_comb | TYPE FM_COMB. " |
|   CALL FUNCTION 'FM_COMB_CUST' "Check in customizing for Comb Docs |
| EXPORTING | ||
| I_FMBLCOREIN | = lv_i_fmblcorein | |
| IMPORTING | ||
| E_JUMP | = lv_e_jump | |
| E_COMB | = lv_e_comb | |
| . " FM_COMB_CUST | ||
ABAP code using 7.40 inline data declarations to call FM FM_COMB_CUST
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