SAP DTL_SET_OBJECT_BLOCK_STATUS Function Module for set or reset block status for a migration object

Search SAP Function Modules

DTL_SET_OBJECT_BLOCK_STATUS is a standard dtl set object block status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for set or reset block status for a migration object 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 set object block status FM, simply by entering the name DTL_SET_OBJECT_BLOCK_STATUS 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_SET_OBJECT_BLOCK_STATUS 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_SET_OBJECT_BLOCK_STATUS'"set or reset block status for a migration object
  EXPORTING
   I_MT_ID =  "DMC: Indicator for Mass Transfer
*  IT_OBJECT_NAMES =  "Application Log: DDIC structure names table -- tablenames only as char20
*  IT_TABNAMES =  "Table names as char30
   I_BLOCK_STEP =  "Block a processing step of MWB mass transfers

EXCEPTIONS
   UNDEFINED_PROCESS_TYPE = 1    TABLE_NOT_IN_MT = 2 

.

IMPORTING Parameters details for DTL_SET_OBJECT_BLOCK_STATUS

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)

IT_OBJECT_NAMES - Application Log: DDIC structure names table -- tablenames only as char20

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

IT_TABNAMES - Table names as char30

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

I_BLOCK_STEP - Block a processing step of MWB mass transfers

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

EXCEPTIONS details

UNDEFINED_PROCESS_TYPE - undefined process type

Data type:
Optional: No
Call by Reference: Yes

TABLE_NOT_IN_MT - table name not known in mass transfer

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for DTL_SET_OBJECT_BLOCK_STATUS 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.

ABAP code using 7.40 inline data declarations to call FM DTL_SET_OBJECT_BLOCK_STATUS

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