SAP FC_LCC Function Module for
FC_LCC is a standard fc lcc 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 fc lcc FM, simply by entering the name FC_LCC into the relevant SAP transaction such as SE37 or SE38.
Function Group: FCLC
Program Name: SAPLFCLC
Main Program:
Appliation area: F
Release date: 01-Jan-1970
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FC_LCC 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 'FC_LCC'".
EXPORTING
E_DIMEN = "
ET_CU = "
* ET_PRGRP = "
* ET_CU_CURR = "
E_ITCLG = "
E_RVERS = "
E_RYEAR = "
E_PERID = "
E_GCURR = "
* E_EXRIND = "
ET_FIELDS = "
ET_KFIG = "
IMPORTING
I_ABORT = "
CHANGING
CT_DATA = "
* CT_MESSAGE = "
EXCEPTIONS
FIELDNAME_WRONG = 1 FIELDNAME_MISSING = 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_SAPLFCLC_001 Definition of an Exchange Rate for Changes in Local Currency
IMPORTING Parameters details for FC_LCC
E_DIMEN -
Data type: FC_DIMENOptional: No
Call by Reference: Yes
ET_CU -
Data type: FC05_T_IPI_CUOptional: No
Call by Reference: No ( called with pass by value option)
ET_PRGRP -
Data type: FC05_T_PRGRPOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_CU_CURR -
Data type: FC05_T_CU_CURROptional: Yes
Call by Reference: No ( called with pass by value option)
E_ITCLG -
Data type: FC_ITCLGOptional: No
Call by Reference: Yes
E_RVERS -
Data type: FC_RVERSOptional: No
Call by Reference: Yes
E_RYEAR -
Data type: FC_RYEAROptional: No
Call by Reference: Yes
E_PERID -
Data type: FC_PERIDOptional: No
Call by Reference: Yes
E_GCURR -
Data type: FC_CURROptional: No
Call by Reference: Yes
E_EXRIND -
Data type: FC_EXRINDOptional: Yes
Call by Reference: Yes
ET_FIELDS -
Data type: FC00_T_FIELDSOptional: No
Call by Reference: No ( called with pass by value option)
ET_KFIG -
Data type: FC00_T_FIELDSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FC_LCC
I_ABORT -
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
CHANGING Parameters details for FC_LCC
CT_DATA -
Data type: TABLEOptional: No
Call by Reference: Yes
CT_MESSAGE -
Data type: FC05_T_IPI_MESSAGEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
FIELDNAME_WRONG -
Data type:Optional: No
Call by Reference: Yes
FIELDNAME_MISSING -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FC_LCC 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_ct_data | TYPE TABLE, " | |||
| lv_e_dimen | TYPE FC_DIMEN, " | |||
| lv_i_abort | TYPE SY-SUBRC, " | |||
| lv_fieldname_wrong | TYPE SY, " | |||
| lv_et_cu | TYPE FC05_T_IPI_CU, " | |||
| lv_et_prgrp | TYPE FC05_T_PRGRP, " | |||
| lv_et_cu_curr | TYPE FC05_T_CU_CURR, " | |||
| lv_e_itclg | TYPE FC_ITCLG, " | |||
| lv_ct_message | TYPE FC05_T_IPI_MESSAGE, " | |||
| lv_fieldname_missing | TYPE FC05_T_IPI_MESSAGE, " | |||
| lv_e_rvers | TYPE FC_RVERS, " | |||
| lv_e_ryear | TYPE FC_RYEAR, " | |||
| lv_e_perid | TYPE FC_PERID, " | |||
| lv_e_gcurr | TYPE FC_CURR, " | |||
| lv_e_exrind | TYPE FC_EXRIND, " | |||
| lv_et_fields | TYPE FC00_T_FIELDS, " | |||
| lv_et_kfig | TYPE FC00_T_FIELDS. " |
|   CALL FUNCTION 'FC_LCC' " |
| EXPORTING | ||
| E_DIMEN | = lv_e_dimen | |
| ET_CU | = lv_et_cu | |
| ET_PRGRP | = lv_et_prgrp | |
| ET_CU_CURR | = lv_et_cu_curr | |
| E_ITCLG | = lv_e_itclg | |
| E_RVERS | = lv_e_rvers | |
| E_RYEAR | = lv_e_ryear | |
| E_PERID | = lv_e_perid | |
| E_GCURR | = lv_e_gcurr | |
| E_EXRIND | = lv_e_exrind | |
| ET_FIELDS | = lv_et_fields | |
| ET_KFIG | = lv_et_kfig | |
| IMPORTING | ||
| I_ABORT | = lv_i_abort | |
| CHANGING | ||
| CT_DATA | = lv_ct_data | |
| CT_MESSAGE | = lv_ct_message | |
| EXCEPTIONS | ||
| FIELDNAME_WRONG = 1 | ||
| FIELDNAME_MISSING = 2 | ||
| . " FC_LCC | ||
ABAP code using 7.40 inline data declarations to call FM FC_LCC
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 SUBRC FROM SY INTO @DATA(ld_i_abort). | ||||
Search for further information about these or an SAP related objects