SAP DTL_ACPLAN_DATA_DB_WRITE Function Module for write access plan calc. data to DB tables









DTL_ACPLAN_DATA_DB_WRITE is a standard dtl acplan data db write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for write access plan calc. data to DB tables 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 dtl acplan data db write FM, simply by entering the name DTL_ACPLAN_DATA_DB_WRITE into the relevant SAP transaction such as SE37 or SE38.

Function Group: DMC_DTL
Program Name: SAPLDMC_DTL
Main Program: SAPLDMC_DTL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function DTL_ACPLAN_DATA_DB_WRITE 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 'DTL_ACPLAN_DATA_DB_WRITE'"write access plan calc. data to DB tables
EXPORTING
I_MT_ID = "DMC: Indicator for Mass Transfer
I_CONV_OBJ = "Name of an ABAP Dictionary object
I_ACPL_ID = "DMC: Key
* I_BLOCKSIZE = 16000000 "MWB: Size of an RFC Package
* I_WRITE_BEHAVIOUR = 1 "MWB: Transfer behavior of conversion

TABLES
IT_INTERVAL_BOUNDARIES = "DMC: Interval of a Portion of the Access Plan
IT_RECCOUNTS = "DMC: Number of records in a portion of the access plan
IT_TABWIDTHS = "DMC: Width of a Table in the Sender System

EXCEPTIONS
COBJ_NOT_EXIST = 1
.



IMPORTING Parameters details for DTL_ACPLAN_DATA_DB_WRITE

I_MT_ID - DMC: Indicator for Mass Transfer

Data type: DMC_MT_IDENTIFIER
Optional: No
Call by Reference: No ( called with pass by value option)

I_CONV_OBJ - Name of an ABAP Dictionary object

Data type: DDNAME
Optional: No
Call by Reference: No ( called with pass by value option)

I_ACPL_ID - DMC: Key

Data type: DMC_ID
Optional: No
Call by Reference: No ( called with pass by value option)

I_BLOCKSIZE - MWB: Size of an RFC Package

Data type: DMC_BLOCKSIZE
Default: 16000000
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_WRITE_BEHAVIOUR - MWB: Transfer behavior of conversion

Data type: DMC_RTO_BEHAVIOUR
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for DTL_ACPLAN_DATA_DB_WRITE

IT_INTERVAL_BOUNDARIES - DMC: Interval of a Portion of the Access Plan

Data type: DMCINTERVL
Optional: No
Call by Reference: Yes

IT_RECCOUNTS - DMC: Number of records in a portion of the access plan

Data type: DMCRECCNT
Optional: No
Call by Reference: Yes

IT_TABWIDTHS - DMC: Width of a Table in the Sender System

Data type: DMCTABWIDT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

COBJ_NOT_EXIST - conv. object does not exist

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for DTL_ACPLAN_DATA_DB_WRITE 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_i_mt_id  TYPE DMC_MT_IDENTIFIER, "   
lv_cobj_not_exist  TYPE DMC_MT_IDENTIFIER, "   
lt_it_interval_boundaries  TYPE STANDARD TABLE OF DMCINTERVL, "   
lv_i_conv_obj  TYPE DDNAME, "   
lt_it_reccounts  TYPE STANDARD TABLE OF DMCRECCNT, "   
lv_i_acpl_id  TYPE DMC_ID, "   
lt_it_tabwidths  TYPE STANDARD TABLE OF DMCTABWIDT, "   
lv_i_blocksize  TYPE DMC_BLOCKSIZE, "   16000000
lv_i_write_behaviour  TYPE DMC_RTO_BEHAVIOUR. "   1

  CALL FUNCTION 'DTL_ACPLAN_DATA_DB_WRITE'  "write access plan calc. data to DB tables
    EXPORTING
         I_MT_ID = lv_i_mt_id
         I_CONV_OBJ = lv_i_conv_obj
         I_ACPL_ID = lv_i_acpl_id
         I_BLOCKSIZE = lv_i_blocksize
         I_WRITE_BEHAVIOUR = lv_i_write_behaviour
    TABLES
         IT_INTERVAL_BOUNDARIES = lt_it_interval_boundaries
         IT_RECCOUNTS = lt_it_reccounts
         IT_TABWIDTHS = lt_it_tabwidths
    EXCEPTIONS
        COBJ_NOT_EXIST = 1
. " DTL_ACPLAN_DATA_DB_WRITE




ABAP code using 7.40 inline data declarations to call FM DTL_ACPLAN_DATA_DB_WRITE

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.

 
 
 
 
 
 
 
DATA(ld_i_blocksize) = 16000000.
 
DATA(ld_i_write_behaviour) = 1.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!