SAP EAM_TASKLIST_GET_STZU Function Module for Get STZU relating to a BOM
EAM_TASKLIST_GET_STZU is a standard eam tasklist get stzu 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 STZU relating to a BOM 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 eam tasklist get stzu FM, simply by entering the name EAM_TASKLIST_GET_STZU into the relevant SAP transaction such as SE37 or SE38.
Function Group: EAM_TL
Program Name: SAPLEAM_TL
Main Program: SAPLEAM_TL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EAM_TASKLIST_GET_STZU 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 'EAM_TASKLIST_GET_STZU'"Get STZU relating to a BOM.
EXPORTING
IV_STLNR = "Bill of material
IV_STLTY = "BOM category
IMPORTING
ES_STZUB = "Permanent BOM data
EXCEPTIONS
KEY_INCOMPLETE = 1 NO_RECORD_FOUND = 2
IMPORTING Parameters details for EAM_TASKLIST_GET_STZU
IV_STLNR - Bill of material
Data type: STNUMOptional: No
Call by Reference: Yes
IV_STLTY - BOM category
Data type: STLTYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for EAM_TASKLIST_GET_STZU
ES_STZUB - Permanent BOM data
Data type: STZUBOptional: No
Call by Reference: Yes
EXCEPTIONS details
KEY_INCOMPLETE -
Data type:Optional: No
Call by Reference: Yes
NO_RECORD_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EAM_TASKLIST_GET_STZU 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_es_stzub | TYPE STZUB, " | |||
| lv_iv_stlnr | TYPE STNUM, " | |||
| lv_key_incomplete | TYPE STNUM, " | |||
| lv_iv_stlty | TYPE STLTY, " | |||
| lv_no_record_found | TYPE STLTY. " |
|   CALL FUNCTION 'EAM_TASKLIST_GET_STZU' "Get STZU relating to a BOM |
| EXPORTING | ||
| IV_STLNR | = lv_iv_stlnr | |
| IV_STLTY | = lv_iv_stlty | |
| IMPORTING | ||
| ES_STZUB | = lv_es_stzub | |
| EXCEPTIONS | ||
| KEY_INCOMPLETE = 1 | ||
| NO_RECORD_FOUND = 2 | ||
| . " EAM_TASKLIST_GET_STZU | ||
ABAP code using 7.40 inline data declarations to call FM EAM_TASKLIST_GET_STZU
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