Hierarchy
⤷ BC-DOC-DTL (Application Component) Documentation Tools
⤷ SDOC (Package) Documentation Maintenance
Basic Data
Data Element | SDOC_RSDCU_DZ |
Short Description | List Data Element Supplements in Worklist |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1 | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | 8 | RSDCU_FU |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
Use
Lists the documentaton on data element supplements (document class DZ) in the worklist for documentation.
You use data element supplements to overwrite data element documentation depending on the screen in question. Data elements are often used on several screens. If the data element is not used for the same purpose on all screens, the data element documentation may not be appropriate for each screen.
The definition of the underlying data element documentation (keyblock &DEFINITION&) remains unaffected. The documentation on the data element supplement is displayed from the &USE& keyblock downwards.
Dependencies
You can then only easily create a data element supplement if the underlying data element originally comes from the system in which you want to create the data element supplement. If this condition is not met, make a modification to the data element in question that is not release-dependent.
Data element supplements must always be linked to a screen as well as to a data element. Documentation authors create this link.
The underlying data element documentation is not overwritten, only the text appearing in the field help is overwritten.
When a new data element supplement documentation is created, it is automatically assigned to the package that the underlying data element documentation belongs to.
This may affect your worklist or the worklist of your colleagues.
- Check whether the package belongs to your area of responsibility, or whether you have to notify your colleagues.
- Make sure that the packet the data element supplement is assigned to will be delivered as part of your product.
- Check with your developers whether they can provide a new data element for the field in question.
Example
The field "Bank Control Key" in financial accounting is used several times. The documentation for the data element underlying each field describes the function the field on each respective screen performs. On one of the screens for financial transactions with foreign countries the field help points out to you that in certain named countries decisions different to those in Germany depend on the contents of this field.
History
Last changed by/on | SAP | 20041216 |
SAP Release Created in | 700 |