Hierarchy
![](/abap/icon/s_instal.gif)
⤷
![](/abap/icon/s_b_tree.gif)
⤷
![](/abap/icon/s_pckstd.gif)
Basic Data
Data Element | SIW_DTE_UI_TODO |
Short Description | Number of All / Completed Todos |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | All/Done |
Medium | 15 | All/Done |
Long | 20 | ToDo: All/Done |
Heading | 15 | All/Done |
Documentation
Definition
Contains the number of all and the number of all completed to-dos of a corresponding object. To-dos can be either optional or obligatory.
Use
When you double click the entry in this field, the system opens the To-Do Browser. From here, you can navigate directly to the relevant coding place to implement missing functionality to complete the service implementation.
When you have finished a to-do, you must change the metadata tag in the code slot's (by replacing the word NEW by DONE in the comment) to confirm your work to the tool.
Dependencies
The Service Implementation Architect determines if a to-do is optional or obligatory. He or she classifies the extension points in the templates of the corresponding configuration class accordingly.
Open obligatory to dos do have an effect on the project status. This status is only active, if you have successfully finished all obligatory to-dos.
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 100 |