SAP FICO_COND_TYPE_FMOD_GET Function Module for
FICO_COND_TYPE_FMOD_GET is a standard fico cond type fmod 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 fico cond type fmod get FM, simply by entering the name FICO_COND_TYPE_FMOD_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FICOB3
Program Name: SAPLFICOB3
Main Program: SAPLFICOB3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FICO_COND_TYPE_FMOD_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 'FICO_COND_TYPE_FMOD_GET'".
EXPORTING
I_APPL = "
I_CONDTYPE = "Condition Type
TABLES
E_T_CFG_CONDTYPE_BDT_FMOD = "Define Condition Type - BDT
IMPORTING Parameters details for FICO_COND_TYPE_FMOD_GET
I_APPL -
Data type: FICO_OAPPLOptional: No
Call by Reference: Yes
I_CONDTYPE - Condition Type
Data type: FICO_OCONDTYPEOptional: No
Call by Reference: Yes
TABLES Parameters details for FICO_COND_TYPE_FMOD_GET
E_T_CFG_CONDTYPE_BDT_FMOD - Define Condition Type - BDT
Data type: FICOC_COND_BDTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FICO_COND_TYPE_FMOD_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.| DATA: | ||||
| lv_i_appl | TYPE FICO_OAPPL, " | |||
| lt_e_t_cfg_condtype_bdt_fmod | TYPE STANDARD TABLE OF FICOC_COND_BDT, " | |||
| lv_i_condtype | TYPE FICO_OCONDTYPE. " |
|   CALL FUNCTION 'FICO_COND_TYPE_FMOD_GET' " |
| EXPORTING | ||
| I_APPL | = lv_i_appl | |
| I_CONDTYPE | = lv_i_condtype | |
| TABLES | ||
| E_T_CFG_CONDTYPE_BDT_FMOD | = lt_e_t_cfg_condtype_bdt_fmod | |
| . " FICO_COND_TYPE_FMOD_GET | ||
ABAP code using 7.40 inline data declarations to call FM FICO_COND_TYPE_FMOD_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