Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
AB (Package) Application Development R/3: Asset Accounting
Basic Data
| Data Element | AFASL |
| Short Description | Depreciation key |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AFASL | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | T090NA |
Further Characteristics
| Search Help: Name | SH_AFASL | |
| Search Help: Parameters | AFASL | |
| 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 | Dep. key |
| Medium | 15 | Dep. key |
| Long | 20 | Depreciation key |
| Heading | 5 | DepKy |
Documentation
Definition
The depreciation key (valuation key) controls the valuation of the asset in the particular depreciation areas.
The depreciation key consists of the following:
- Calculation method for the automatic calculation of interest, ordinary and special depreciation
- Possibly a cutoff value key
- Various control indicators
Supplementary Documentation - AFASL 0410
Use (Simulation version)
In this field, you can limit the simulation version to assets with the depreciation key you enter.
Procedure
Examples
Dependencies
Supplementary Documentation - AFASL 4411
Use
Here you can limit the validity of the simulation version. In this screen you can make a generic (masked) entry. To make a generic entry, you enter a '+' sign, starting from the right and moving to the left. The '+' sign always represents a single character.
Examples
Depreciation key DG30: only depreciation key DG30
Depreciation key L+++: depreciation keys LAAA to LZZZ
Note
If the system finds several possible entries when using the simulation version, it follows this logic:
- Unmasked entries always take precendence.
- When there is more than one masked entry, the system uses the first appropriate entry.
- If the system finds only masked entries and no unmasked entries, it uses the entry that has the least masking.
Supplementary Documentation - AFASL 4412
Use (Simulation version)
Enter the depreciation key here that the system should use for the simulation, in place of the original depreciation key.
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in |
