SAP DTL_GET_DB_SETGET_BOUNDARIES Function Module for get key values for DB_SETGET parallelization
DTL_GET_DB_SETGET_BOUNDARIES is a standard dtl get db setget boundaries SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for get key values for DB_SETGET parallelization 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 get db setget boundaries FM, simply by entering the name DTL_GET_DB_SETGET_BOUNDARIES 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_GET_DB_SETGET_BOUNDARIES 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_GET_DB_SETGET_BOUNDARIES'"get key values for DB_SETGET parallelization.
EXPORTING
I_MT_ID = "DMC: Indicator for Mass Transfer
I_COBJ_GUID = "DMC: Globally Unique Key (22 Characters)
I_ACPL_ID = "DMC: Key
IMPORTING
ET_GENERIC_KEY = "Table Type for DMC_INDX2
IMPORTING Parameters details for DTL_GET_DB_SETGET_BOUNDARIES
I_MT_ID - DMC: Indicator for Mass Transfer
Data type: DMC_MT_IDENTIFIEROptional: No
Call by Reference: No ( called with pass by value option)
I_COBJ_GUID - DMC: Globally Unique Key (22 Characters)
Data type: DMC_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
I_ACPL_ID - DMC: Key
Data type: DMC_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DTL_GET_DB_SETGET_BOUNDARIES
ET_GENERIC_KEY - Table Type for DMC_INDX2
Data type: DMC_GENERIC_TRANSFER_TABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DTL_GET_DB_SETGET_BOUNDARIES 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_et_generic_key | TYPE DMC_GENERIC_TRANSFER_TAB, " | |||
| lv_i_cobj_guid | TYPE DMC_GUID, " | |||
| lv_i_acpl_id | TYPE DMC_ID. " |
|   CALL FUNCTION 'DTL_GET_DB_SETGET_BOUNDARIES' "get key values for DB_SETGET parallelization |
| EXPORTING | ||
| I_MT_ID | = lv_i_mt_id | |
| I_COBJ_GUID | = lv_i_cobj_guid | |
| I_ACPL_ID | = lv_i_acpl_id | |
| IMPORTING | ||
| ET_GENERIC_KEY | = lv_et_generic_key | |
| . " DTL_GET_DB_SETGET_BOUNDARIES | ||
ABAP code using 7.40 inline data declarations to call FM DTL_GET_DB_SETGET_BOUNDARIES
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