SAP ABAP Data Element SDOC_RSDCU_MO (List SAP Extensions (old) in Worklist)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DOC-DTL (Application Component) Documentation Tools
⤷ SDOC (Package) Documentation Maintenance
⤷ BC-DOC-DTL (Application Component) Documentation Tools
⤷ SDOC (Package) Documentation Maintenance
Basic Data
Data Element | SDOC_RSDCU_MO |
Short Description | List SAP Extensions (old) 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 documentation on SAP extensions customer exits (document class MO) created in transaction SMOD in the documentation worklist.
Dependencies
You should document SAP extensions only in consultation with the responsible developer and Knowledge Manager.
SAP extensions are no longer created with transaction SMOD. Business Add-Ins have now replaced SMOD. These are created with the BAdI Builder (transaction SE18). Existing SAP extensions are gradually being migrated into the BAdI Builder.
To create a worklist for BAdIs, create a worklist for hypertext documents, including IMG texts. This worklist contains the documentation on BAdIs, since the BAdI documentation is based on the same template as an IMG chapter is.
Example
History
Last changed by/on | SAP | 20041216 |
SAP Release Created in | 700 |