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

Function FC_BRKDOWN_CHECK 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_BRKDOWN_CHECK'".
EXPORTING
* E_RLDNR = "
* E_LANGU = SY-LANGU "
* E_EXIST_SUBACCNT = 'X' "
* E_EXIST_TOTALS = ' ' "
* E_DATA_ENTRY = 'X' "
* E_NO_INFO = 'X' "
* E_NO_WARNING = ' ' "
* ET_ITGRP_SIM = "
* ET_FIELDNAME_MAP = "
* ET_ITEM_NODEF = "
* E_ITCLG = "
* E_DIMEN = "
* E_RVERS = "
* E_RYEAR = "
* E_PERID = "
* E_BUNIT = "
* E_RLEVL = "
* E_DOCTY = "
IMPORTING
IT_MESSAGE = "
CHANGING
CT_DATA = "
EXCEPTIONS
COMPONENT_NOT_FOUND = 1
IMPORTING Parameters details for FC_BRKDOWN_CHECK
E_RLDNR -
Data type: FC_RLDNROptional: Yes
Call by Reference: Yes
E_LANGU -
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
E_EXIST_SUBACCNT -
Data type: FC_FLGDefault: 'X'
Optional: Yes
Call by Reference: Yes
E_EXIST_TOTALS -
Data type: FC_FLGDefault: SPACE
Optional: Yes
Call by Reference: Yes
E_DATA_ENTRY -
Data type: FC_FLGDefault: 'X'
Optional: Yes
Call by Reference: Yes
E_NO_INFO -
Data type: FC_FLGDefault: 'X'
Optional: Yes
Call by Reference: Yes
E_NO_WARNING -
Data type: FC_FLGDefault: SPACE
Optional: Yes
Call by Reference: Yes
ET_ITGRP_SIM -
Data type: FC01_T_ITGRP_SIMOptional: Yes
Call by Reference: Yes
ET_FIELDNAME_MAP -
Data type: FC01_T_FIELDNAME_MAPOptional: Yes
Call by Reference: Yes
ET_ITEM_NODEF -
Data type: SORTED TABLEOptional: Yes
Call by Reference: Yes
E_ITCLG -
Data type: FC_ITCLGOptional: Yes
Call by Reference: Yes
E_DIMEN -
Data type: FC_DIMENOptional: Yes
Call by Reference: Yes
E_RVERS -
Data type: FC_RVERSOptional: Yes
Call by Reference: Yes
E_RYEAR -
Data type: FC_RYEAROptional: Yes
Call by Reference: Yes
E_PERID -
Data type: FC_PERIDOptional: Yes
Call by Reference: Yes
E_BUNIT -
Data type: FC_BUNITOptional: Yes
Call by Reference: Yes
E_RLEVL -
Data type: FC_PLEVLOptional: Yes
Call by Reference: Yes
E_DOCTY -
Data type: FC_DOCTYOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FC_BRKDOWN_CHECK
IT_MESSAGE -
Data type: FC01_T_BD_MESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for FC_BRKDOWN_CHECK
CT_DATA -
Data type: STANDARD TABLEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
COMPONENT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FC_BRKDOWN_CHECK 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 STANDARD TABLE, " | |||
| lv_e_rldnr | TYPE FC_RLDNR, " | |||
| lv_it_message | TYPE FC01_T_BD_MESSAGE, " | |||
| lv_component_not_found | TYPE FC01_T_BD_MESSAGE, " | |||
| lv_e_langu | TYPE SY-LANGU, " SY-LANGU | |||
| lv_e_exist_subaccnt | TYPE FC_FLG, " 'X' | |||
| lv_e_exist_totals | TYPE FC_FLG, " SPACE | |||
| lv_e_data_entry | TYPE FC_FLG, " 'X' | |||
| lv_e_no_info | TYPE FC_FLG, " 'X' | |||
| lv_e_no_warning | TYPE FC_FLG, " SPACE | |||
| lv_et_itgrp_sim | TYPE FC01_T_ITGRP_SIM, " | |||
| lv_et_fieldname_map | TYPE FC01_T_FIELDNAME_MAP, " | |||
| lv_et_item_nodef | TYPE SORTED TABLE, " | |||
| lv_e_itclg | TYPE FC_ITCLG, " | |||
| lv_e_dimen | TYPE FC_DIMEN, " | |||
| lv_e_rvers | TYPE FC_RVERS, " | |||
| lv_e_ryear | TYPE FC_RYEAR, " | |||
| lv_e_perid | TYPE FC_PERID, " | |||
| lv_e_bunit | TYPE FC_BUNIT, " | |||
| lv_e_rlevl | TYPE FC_PLEVL, " | |||
| lv_e_docty | TYPE FC_DOCTY. " |
|   CALL FUNCTION 'FC_BRKDOWN_CHECK' " |
| EXPORTING | ||
| E_RLDNR | = lv_e_rldnr | |
| E_LANGU | = lv_e_langu | |
| E_EXIST_SUBACCNT | = lv_e_exist_subaccnt | |
| E_EXIST_TOTALS | = lv_e_exist_totals | |
| E_DATA_ENTRY | = lv_e_data_entry | |
| E_NO_INFO | = lv_e_no_info | |
| E_NO_WARNING | = lv_e_no_warning | |
| ET_ITGRP_SIM | = lv_et_itgrp_sim | |
| ET_FIELDNAME_MAP | = lv_et_fieldname_map | |
| ET_ITEM_NODEF | = lv_et_item_nodef | |
| E_ITCLG | = lv_e_itclg | |
| E_DIMEN | = lv_e_dimen | |
| E_RVERS | = lv_e_rvers | |
| E_RYEAR | = lv_e_ryear | |
| E_PERID | = lv_e_perid | |
| E_BUNIT | = lv_e_bunit | |
| E_RLEVL | = lv_e_rlevl | |
| E_DOCTY | = lv_e_docty | |
| IMPORTING | ||
| IT_MESSAGE | = lv_it_message | |
| CHANGING | ||
| CT_DATA | = lv_ct_data | |
| EXCEPTIONS | ||
| COMPONENT_NOT_FOUND = 1 | ||
| . " FC_BRKDOWN_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FC_BRKDOWN_CHECK
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 LANGU FROM SY INTO @DATA(ld_e_langu). | ||||
| DATA(ld_e_langu) | = SY-LANGU. | |||
| DATA(ld_e_exist_subaccnt) | = 'X'. | |||
| DATA(ld_e_exist_totals) | = ' '. | |||
| DATA(ld_e_data_entry) | = 'X'. | |||
| DATA(ld_e_no_info) | = 'X'. | |||
| DATA(ld_e_no_warning) | = ' '. | |||
Search for further information about these or an SAP related objects