SAP FC_CHECK_BUNIT_LCURR_CHANGE Function Module for
FC_CHECK_BUNIT_LCURR_CHANGE is a standard fc check bunit lcurr change 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 check bunit lcurr change FM, simply by entering the name FC_CHECK_BUNIT_LCURR_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FC11
Program Name: SAPLFC11
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FC_CHECK_BUNIT_LCURR_CHANGE 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_CHECK_BUNIT_LCURR_CHANGE'".
EXPORTING
E_DIMEN = "
E_RYEAR = "
IMPORTING
IT_MESSAGE = "
CHANGING
CT_CU_LC_CHANGE = "
IMPORTING Parameters details for FC_CHECK_BUNIT_LCURR_CHANGE
E_DIMEN -
Data type: FC_DIMENOptional: No
Call by Reference: Yes
E_RYEAR -
Data type: FC_RYEAROptional: No
Call by Reference: Yes
EXPORTING Parameters details for FC_CHECK_BUNIT_LCURR_CHANGE
IT_MESSAGE -
Data type: FC00_T_MESSAGEOptional: No
Call by Reference: Yes
CHANGING Parameters details for FC_CHECK_BUNIT_LCURR_CHANGE
CT_CU_LC_CHANGE -
Data type: FC01_TH_CU_LCURR_CHANGEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FC_CHECK_BUNIT_LCURR_CHANGE 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_dimen | TYPE FC_DIMEN, " | |||
| lv_it_message | TYPE FC00_T_MESSAGE, " | |||
| lv_ct_cu_lc_change | TYPE FC01_TH_CU_LCURR_CHANGE, " | |||
| lv_e_ryear | TYPE FC_RYEAR. " |
|   CALL FUNCTION 'FC_CHECK_BUNIT_LCURR_CHANGE' " |
| EXPORTING | ||
| E_DIMEN | = lv_e_dimen | |
| E_RYEAR | = lv_e_ryear | |
| IMPORTING | ||
| IT_MESSAGE | = lv_it_message | |
| CHANGING | ||
| CT_CU_LC_CHANGE | = lv_ct_cu_lc_change | |
| . " FC_CHECK_BUNIT_LCURR_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM FC_CHECK_BUNIT_LCURR_CHANGE
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