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

Function FICO_COND_GET_COMP 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_GET_COMP'".
EXPORTING
I_LIST = "Condition List
I_COMP = "Condition
* I_T_STATUS = "Table for Status Selection
* I_MIN_VALID_FROM = G_CON_MINDATE "Minimum Value for Valid-From
* I_MAX_VALID_TO = G_CON_MAXDATE "Maximum Value for Valid-To
* I_LANGU = SY-LANGU "Language Key
* I_EXTEND = "
* I_BUFFER = "
* I_FLG_DB = ' ' "
IMPORTING
E_T_CONDI = "Conditions with Buffer Flag
E_T_COND_T = "Table Type: Texts for Conditions
E_T_POS = "Items of the Conditions with Buffering Flag
E_T_POS_REL = "
E_RC = "Return Value, Return Value After ABAP Statements
IMPORTING Parameters details for FICO_COND_GET_COMP
I_LIST - Condition List
Data type: FICO_ILISTOptional: No
Call by Reference: Yes
I_COMP - Condition
Data type: FICO_ICOMPOptional: No
Call by Reference: Yes
I_T_STATUS - Table for Status Selection
Data type: FICOT_STATUSOptional: Yes
Call by Reference: Yes
I_MIN_VALID_FROM - Minimum Value for Valid-From
Data type: FICO_DVALIDFROMDefault: G_CON_MINDATE
Optional: No
Call by Reference: Yes
I_MAX_VALID_TO - Maximum Value for Valid-To
Data type: FICO_DVALIDTODefault: G_CON_MAXDATE
Optional: No
Call by Reference: Yes
I_LANGU - Language Key
Data type: SPRASDefault: SY-LANGU
Optional: No
Call by Reference: Yes
I_EXTEND -
Data type: XFELDOptional: Yes
Call by Reference: Yes
I_BUFFER -
Data type: FICO_FBUFFEROptional: Yes
Call by Reference: Yes
I_FLG_DB -
Data type: XFELDDefault: SPACE
Optional: No
Call by Reference: Yes
EXPORTING Parameters details for FICO_COND_GET_COMP
E_T_CONDI - Conditions with Buffer Flag
Data type: FICO_TYP_TAS_CONDI_BUFFOptional: No
Call by Reference: Yes
E_T_COND_T - Table Type: Texts for Conditions
Data type: FICO_TYP_TAS_COND_TOptional: No
Call by Reference: Yes
E_T_POS - Items of the Conditions with Buffering Flag
Data type: FICO_TYP_TAS_POS_BUFFOptional: No
Call by Reference: Yes
E_T_POS_REL -
Data type: FICO_TYP_TAS_POS_REL_BUFFOptional: No
Call by Reference: Yes
E_RC - Return Value, Return Value After ABAP Statements
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FICO_COND_GET_COMP 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_list | TYPE FICO_ILIST, " | |||
| lv_e_t_condi | TYPE FICO_TYP_TAS_CONDI_BUFF, " | |||
| lv_i_comp | TYPE FICO_ICOMP, " | |||
| lv_e_t_cond_t | TYPE FICO_TYP_TAS_COND_T, " | |||
| lv_e_t_pos | TYPE FICO_TYP_TAS_POS_BUFF, " | |||
| lv_i_t_status | TYPE FICOT_STATUS, " | |||
| lv_e_t_pos_rel | TYPE FICO_TYP_TAS_POS_REL_BUFF, " | |||
| lv_i_min_valid_from | TYPE FICO_DVALIDFROM, " G_CON_MINDATE | |||
| lv_e_rc | TYPE SY-SUBRC, " | |||
| lv_i_max_valid_to | TYPE FICO_DVALIDTO, " G_CON_MAXDATE | |||
| lv_i_langu | TYPE SPRAS, " SY-LANGU | |||
| lv_i_extend | TYPE XFELD, " | |||
| lv_i_buffer | TYPE FICO_FBUFFER, " | |||
| lv_i_flg_db | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'FICO_COND_GET_COMP' " |
| EXPORTING | ||
| I_LIST | = lv_i_list | |
| I_COMP | = lv_i_comp | |
| I_T_STATUS | = lv_i_t_status | |
| I_MIN_VALID_FROM | = lv_i_min_valid_from | |
| I_MAX_VALID_TO | = lv_i_max_valid_to | |
| I_LANGU | = lv_i_langu | |
| I_EXTEND | = lv_i_extend | |
| I_BUFFER | = lv_i_buffer | |
| I_FLG_DB | = lv_i_flg_db | |
| IMPORTING | ||
| E_T_CONDI | = lv_e_t_condi | |
| E_T_COND_T | = lv_e_t_cond_t | |
| E_T_POS | = lv_e_t_pos | |
| E_T_POS_REL | = lv_e_t_pos_rel | |
| E_RC | = lv_e_rc | |
| . " FICO_COND_GET_COMP | ||
ABAP code using 7.40 inline data declarations to call FM FICO_COND_GET_COMP
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.| DATA(ld_i_min_valid_from) | = G_CON_MINDATE. | |||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_rc). | ||||
| DATA(ld_i_max_valid_to) | = G_CON_MAXDATE. | |||
| DATA(ld_i_langu) | = SY-LANGU. | |||
| DATA(ld_i_flg_db) | = ' '. | |||
Search for further information about these or an SAP related objects