SAP ABAP Data Element APPENDNAME (Help for append name selection)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷ SDTB (Package) ABAP/4 Dictionary: Tables
⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷ SDTB (Package) ABAP/4 Dictionary: Tables
Basic Data
Data Element | APPENDNAME |
Short Description | Help for append name selection |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TABNAME | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
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 | AppendName |
Medium | 16 | Name of append |
Long | 24 | Name of append structure |
Heading | 30 | Name of append structure |
Documentation
You want to add customer fields to the table in question. To protect these fields from being overwritten by SAP, they are stored in an append of the table. You have to define a name for this append. The system offers a list of appends that already exist for this table. If there is no reason for not doing so, you should choose an append from this list and then enhance it.
If the table does not yet have an append, you must choose a name from your namespace. (For information about namespaces, see the manual about "Changing and the Transport System".)
Caution: The append must be chosen from a customer development class whose transport attributes are the same as those of the table. The append may not be a local object if the table is not local.
History
Last changed by/on | SAP | 19990505 |
SAP Release Created in |