SAP /FLDQ/GEN_SPAWN_MTC_CODE_TASKS Function Module for Read the Match code data and start desired tasks

Search SAP Function Modules

/FLDQ/GEN_SPAWN_MTC_CODE_TASKS is a standard /fldq/gen spawn mtc code tasks SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read the Match code data and start desired tasks 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 /fldq/gen spawn mtc code tasks FM, simply by entering the name /FLDQ/GEN_SPAWN_MTC_CODE_TASKS into the relevant SAP transaction such as SE37 or SE38.

Function Group: /FLDQ/AD_GEN_TBL
Program Name: /FLDQ/SAPLAD_GEN_TBL
Main Program: /FLDQ/SAPLAD_GEN_TBL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /FLDQ/GEN_SPAWN_MTC_CODE_TASKS 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 '/FLDQ/GEN_SPAWN_MTC_CODE_TASKS'"Read the Match code data and start desired tasks
  EXPORTING
   IM_NUM_TASKS =  "Max number of tasks to create
   IM_PKG_SIZE =  "Index of Internal Tables
   IM_USMD_MODEL =  "Data Model
   IM_ENTITY =  "Entity Type
   IM_KEY_TABLE =  "
   IM_PROCESS_GROUP =  "Logon/Server Group Name
   IM_FIELDNAME =  "Financial MDM: Field Name

 IMPORTING
   EX_SUCCESS_STATUS =  "Successful returns abap_true
   EX_ERROR_CODE =  "Error codes

.

IMPORTING Parameters details for /FLDQ/GEN_SPAWN_MTC_CODE_TASKS

IM_NUM_TASKS - Max number of tasks to create

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

IM_PKG_SIZE - Index of Internal Tables

Data type: SY-TABIX
Optional: No
Call by Reference: Yes

IM_USMD_MODEL - Data Model

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

IM_ENTITY - Entity Type

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

IM_KEY_TABLE -

Data type: ANY TABLE
Optional: No
Call by Reference: Yes

IM_PROCESS_GROUP - Logon/Server Group Name

Data type: RZLLITAB-CLASSNAME
Optional: No
Call by Reference: Yes

IM_FIELDNAME - Financial MDM: Field Name

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

EXPORTING Parameters details for /FLDQ/GEN_SPAWN_MTC_CODE_TASKS

EX_SUCCESS_STATUS - Successful returns abap_true

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

EX_ERROR_CODE - Error codes

Data type: /FLDQ/AD_ERR_CODE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /FLDQ/GEN_SPAWN_MTC_CODE_TASKS 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 /FLDQ/GEN_SPAWN_MTC_CODE_TASKS

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