SAP DMC_REMOVE_SHDW_OBJ_REMOTE Function Module for Deregister shaddow DDIC consumer

Search SAP Function Modules

DMC_REMOVE_SHDW_OBJ_REMOTE is a standard dmc remove shdw obj remote SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Deregister shaddow DDIC consumer 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 remove shdw obj remote FM, simply by entering the name DMC_REMOVE_SHDW_OBJ_REMOTE into the relevant SAP transaction such as SE37 or SE38.

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

Function DMC_REMOVE_SHDW_OBJ_REMOTE 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_REMOVE_SHDW_OBJ_REMOTE'"Deregister shaddow DDIC consumer
  EXPORTING
   IV_OBJECT_ID =  "Identifier for Shadow Object
   IV_SENDER_STRUCT_GUID =  "owner of shadow ddic element
*  IV_SYSTEM_ID =  "Sytem Identifier

 IMPORTING
   EV_DEL_SHDW_IDENT =  "boolean variable (X=true, -=false, space=unknown)
   EV_DEL_SHDW_CONSUM =  "boolean variable (X=true, -=false, space=unknown)

EXCEPTIONS
   NO_AUTHORITY = 1    NO_LOCK = 2 

.

IMPORTING Parameters details for DMC_REMOVE_SHDW_OBJ_REMOTE

IV_OBJECT_ID - Identifier for Shadow Object

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

IV_SENDER_STRUCT_GUID - owner of shadow ddic element

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

IV_SYSTEM_ID - Sytem Identifier

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

EXPORTING Parameters details for DMC_REMOVE_SHDW_OBJ_REMOTE

EV_DEL_SHDW_IDENT - boolean variable (X=true, -=false, space=unknown)

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

EV_DEL_SHDW_CONSUM - boolean variable (X=true, -=false, space=unknown)

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

EXCEPTIONS details

NO_AUTHORITY - No Authority

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

NO_LOCK - No exclusive lock obtained

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

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

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