SAP MDG_DQ_DET_PROCESSOR_CLEANSE Function Module for Determine processor for a cleanse change request
MDG_DQ_DET_PROCESSOR_CLEANSE is a standard mdg dq det processor cleanse SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine processor for a cleanse change request 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 mdg dq det processor cleanse FM, simply by entering the name MDG_DQ_DET_PROCESSOR_CLEANSE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MDG_SDQ_CLEANSE_WF
Program Name: SAPLMDG_SDQ_CLEANSE_WF
Main Program: SAPLMDG_SDQ_CLEANSE_WF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MDG_DQ_DET_PROCESSOR_CLEANSE 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 'MDG_DQ_DET_PROCESSOR_CLEANSE'"Determine processor for a cleanse change request.
TABLES
ACTOR_TAB = "Rule Resolution Result
AC_CONTAINER = "Instance Structure
EXCEPTIONS
NOBODY_FOUND = 1
TABLES Parameters details for MDG_DQ_DET_PROCESSOR_CLEANSE
ACTOR_TAB - Rule Resolution Result
Data type: SWHACTOROptional: No
Call by Reference: Yes
AC_CONTAINER - Instance Structure
Data type: SWCONTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOBODY_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MDG_DQ_DET_PROCESSOR_CLEANSE 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: | ||||
| lt_actor_tab | TYPE STANDARD TABLE OF SWHACTOR, " | |||
| lv_nobody_found | TYPE SWHACTOR, " | |||
| lt_ac_container | TYPE STANDARD TABLE OF SWCONT. " |
|   CALL FUNCTION 'MDG_DQ_DET_PROCESSOR_CLEANSE' "Determine processor for a cleanse change request |
| TABLES | ||
| ACTOR_TAB | = lt_actor_tab | |
| AC_CONTAINER | = lt_ac_container | |
| EXCEPTIONS | ||
| NOBODY_FOUND = 1 | ||
| . " MDG_DQ_DET_PROCESSOR_CLEANSE | ||
ABAP code using 7.40 inline data declarations to call FM MDG_DQ_DET_PROCESSOR_CLEANSE
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