SAP /BDL/TASK_ATTRIBUTES_UI Function Module for Display and edit task attributes
/BDL/TASK_ATTRIBUTES_UI is a standard /bdl/task attributes ui SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display and edit task attributes 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 /bdl/task attributes ui FM, simply by entering the name /BDL/TASK_ATTRIBUTES_UI into the relevant SAP transaction such as SE37 or SE38.
Function Group: /BDL/TASK_UI
Program Name: /BDL/SAPLTASK_UI
Main Program: /BDL/SAPLTASK_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /BDL/TASK_ATTRIBUTES_UI 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 '/BDL/TASK_ATTRIBUTES_UI'"Display and edit task attributes.
EXPORTING
IR_TASK = "Reference to task object
EXCEPTIONS
CANCEL = 1 ERROR = 2 NO_TASK = 3
IMPORTING Parameters details for /BDL/TASK_ATTRIBUTES_UI
IR_TASK - Reference to task object
Data type: /BDL/IF_TASKOptional: No
Call by Reference: Yes
EXCEPTIONS details
CANCEL - Action cancelled by user
Data type:Optional: No
Call by Reference: Yes
ERROR - Error
Data type:Optional: No
Call by Reference: Yes
NO_TASK - No task was provided
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for /BDL/TASK_ATTRIBUTES_UI 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_cancel | TYPE STRING, " | |||
| lv_ir_task | TYPE /BDL/IF_TASK, " | |||
| lv_error | TYPE /BDL/IF_TASK, " | |||
| lv_no_task | TYPE /BDL/IF_TASK. " |
|   CALL FUNCTION '/BDL/TASK_ATTRIBUTES_UI' "Display and edit task attributes |
| EXPORTING | ||
| IR_TASK | = lv_ir_task | |
| EXCEPTIONS | ||
| CANCEL = 1 | ||
| ERROR = 2 | ||
| NO_TASK = 3 | ||
| . " /BDL/TASK_ATTRIBUTES_UI | ||
ABAP code using 7.40 inline data declarations to call FM /BDL/TASK_ATTRIBUTES_UI
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