SAP DMC_ACPLAN_BTC_CALC_READ_DATA Function Module for batch calculation of access plans - read cluster data
DMC_ACPLAN_BTC_CALC_READ_DATA is a standard dmc acplan btc calc read data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for batch calculation of access plans - read cluster data 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 dmc acplan btc calc read data FM, simply by entering the name DMC_ACPLAN_BTC_CALC_READ_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV0
Program Name: SAPLCNV0
Main Program: SAPLCNV0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DMC_ACPLAN_BTC_CALC_READ_DATA 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 'DMC_ACPLAN_BTC_CALC_READ_DATA'"batch calculation of access plans - read cluster data.
EXPORTING
IM_CLUSTERKEY = "
IMPORTING
EX_ADMIN_DATA = "
ET_MESSAGES = "Application Log: Table with Messages
TABLES
* EX_INTERVAL_BOUNDARIES = "
* EX_RECCOUNTS = "
* EX_TABWIDTHS = "
* EX_SEL_CRITERIA = "
EXCEPTIONS
INVALID_KEY = 1 DOES_NOT_EXIST = 2 IMPORT_FAILED = 3
IMPORTING Parameters details for DMC_ACPLAN_BTC_CALC_READ_DATA
IM_CLUSTERKEY -
Data type: INDX-SRTFDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DMC_ACPLAN_BTC_CALC_READ_DATA
EX_ADMIN_DATA -
Data type: DMCCALCADMOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGES - Application Log: Table with Messages
Data type: DMC_BAL_T_MSGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DMC_ACPLAN_BTC_CALC_READ_DATA
EX_INTERVAL_BOUNDARIES -
Data type: DMCINTERVLOptional: Yes
Call by Reference: No ( called with pass by value option)
EX_RECCOUNTS -
Data type: DMCRECCNTOptional: Yes
Call by Reference: No ( called with pass by value option)
EX_TABWIDTHS -
Data type: DMCTABWIDTOptional: Yes
Call by Reference: No ( called with pass by value option)
EX_SEL_CRITERIA -
Data type: DMC_QRYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DOES_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IMPORT_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DMC_ACPLAN_BTC_CALC_READ_DATA 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_invalid_key | TYPE STRING, " | |||
| lv_ex_admin_data | TYPE DMCCALCADM, " | |||
| lv_im_clusterkey | TYPE INDX-SRTFD, " | |||
| lt_ex_interval_boundaries | TYPE STANDARD TABLE OF DMCINTERVL, " | |||
| lv_et_messages | TYPE DMC_BAL_T_MSG, " | |||
| lt_ex_reccounts | TYPE STANDARD TABLE OF DMCRECCNT, " | |||
| lv_does_not_exist | TYPE DMCRECCNT, " | |||
| lt_ex_tabwidths | TYPE STANDARD TABLE OF DMCTABWIDT, " | |||
| lv_import_failed | TYPE DMCTABWIDT, " | |||
| lt_ex_sel_criteria | TYPE STANDARD TABLE OF DMC_QRY. " |
|   CALL FUNCTION 'DMC_ACPLAN_BTC_CALC_READ_DATA' "batch calculation of access plans - read cluster data |
| EXPORTING | ||
| IM_CLUSTERKEY | = lv_im_clusterkey | |
| IMPORTING | ||
| EX_ADMIN_DATA | = lv_ex_admin_data | |
| ET_MESSAGES | = lv_et_messages | |
| TABLES | ||
| EX_INTERVAL_BOUNDARIES | = lt_ex_interval_boundaries | |
| EX_RECCOUNTS | = lt_ex_reccounts | |
| EX_TABWIDTHS | = lt_ex_tabwidths | |
| EX_SEL_CRITERIA | = lt_ex_sel_criteria | |
| EXCEPTIONS | ||
| INVALID_KEY = 1 | ||
| DOES_NOT_EXIST = 2 | ||
| IMPORT_FAILED = 3 | ||
| . " DMC_ACPLAN_BTC_CALC_READ_DATA | ||
ABAP code using 7.40 inline data declarations to call FM DMC_ACPLAN_BTC_CALC_READ_DATA
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 SRTFD FROM INDX INTO @DATA(ld_im_clusterkey). | ||||
Search for further information about these or an SAP related objects