SAP BC430_CHECK_INCLUDE Function Module for Check Include and Append Structures
BC430_CHECK_INCLUDE is a standard bc430 check include SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Include and Append Structures processing and below is the pattern details for this FM, 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 bc430 check include FM, simply by entering the name BC430_CHECK_INCLUDE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BC430
Program Name: SAPLBC430
Main Program:
Appliation area:
Release date: 24-Jan-2001
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BC430_CHECK_INCLUDE 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 'BC430_CHECK_INCLUDE'"Check Include and Append Structures.
EXPORTING
T_INCLUDE = "Particpant's Include or Append
M_INCLUDE = "Template for Include or Append
T_TAB = "Participant's Table To Be Included or Appended
INC_TYPE = "Include or Append
TABLES
ERRORS = "Causes of Errors that Occurred
TEMP_ERRORS = "BC430_COMP_AND_FILL: Causes of Errors
EXCEPTIONS
T_INC_NOT_EXIST = 1 T_INC_NOT_ACTIVE = 2 M_INC_NOT_ACTIVE = 3 T_TAB_NOT_ACTIVE = 4 SYSTEM_INCONSISTENT = 5
IMPORTING Parameters details for BC430_CHECK_INCLUDE
T_INCLUDE - Particpant's Include or Append
Data type: DD03L-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
M_INCLUDE - Template for Include or Append
Data type: DD03L-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
T_TAB - Participant's Table To Be Included or Appended
Data type: DD03L-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
INC_TYPE - Include or Append
Data type: CHAR8Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BC430_CHECK_INCLUDE
ERRORS - Causes of Errors that Occurred
Data type: BC430_ERROROptional: No
Call by Reference: Yes
TEMP_ERRORS - BC430_COMP_AND_FILL: Causes of Errors
Data type: BC430_ERROROptional: No
Call by Reference: Yes
EXCEPTIONS details
T_INC_NOT_EXIST - Particpant's Include not Available
Data type:Optional: No
Call by Reference: Yes
T_INC_NOT_ACTIVE - Participant's Include not Active
Data type:Optional: No
Call by Reference: Yes
M_INC_NOT_ACTIVE - Template not Available or not Active
Data type:Optional: No
Call by Reference: Yes
T_TAB_NOT_ACTIVE - Table To Be Included or Appended not Available or not Active
Data type:Optional: No
Call by Reference: Yes
SYSTEM_INCONSISTENT - Inconsistency, Dictionary Interfaces Are not Working
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BC430_CHECK_INCLUDE 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: | ||||
| lt_errors | TYPE STANDARD TABLE OF BC430_ERROR, " | |||
| lv_t_include | TYPE DD03L-TABNAME, " | |||
| lv_t_inc_not_exist | TYPE DD03L, " | |||
| lv_m_include | TYPE DD03L-TABNAME, " | |||
| lt_temp_errors | TYPE STANDARD TABLE OF BC430_ERROR, " | |||
| lv_t_inc_not_active | TYPE BC430_ERROR, " | |||
| lv_t_tab | TYPE DD03L-TABNAME, " | |||
| lv_m_inc_not_active | TYPE DD03L, " | |||
| lv_inc_type | TYPE CHAR8, " | |||
| lv_t_tab_not_active | TYPE CHAR8, " | |||
| lv_system_inconsistent | TYPE CHAR8. " |
|   CALL FUNCTION 'BC430_CHECK_INCLUDE' "Check Include and Append Structures |
| EXPORTING | ||
| T_INCLUDE | = lv_t_include | |
| M_INCLUDE | = lv_m_include | |
| T_TAB | = lv_t_tab | |
| INC_TYPE | = lv_inc_type | |
| TABLES | ||
| ERRORS | = lt_errors | |
| TEMP_ERRORS | = lt_temp_errors | |
| EXCEPTIONS | ||
| T_INC_NOT_EXIST = 1 | ||
| T_INC_NOT_ACTIVE = 2 | ||
| M_INC_NOT_ACTIVE = 3 | ||
| T_TAB_NOT_ACTIVE = 4 | ||
| SYSTEM_INCONSISTENT = 5 | ||
| . " BC430_CHECK_INCLUDE | ||
ABAP code using 7.40 inline data declarations to call FM BC430_CHECK_INCLUDE
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 TABNAME FROM DD03L INTO @DATA(ld_t_include). | ||||
| "SELECT single TABNAME FROM DD03L INTO @DATA(ld_m_include). | ||||
| "SELECT single TABNAME FROM DD03L INTO @DATA(ld_t_tab). | ||||
Search for further information about these or an SAP related objects