SAP ABAP Data Element BF_NDJAR (Planned useful life in years)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
ABAS (Package) Application Development R/3 Kernel

⤷

⤷

⤷

Basic Data
Data Element | BF_NDJAR |
Short Description | Planned useful life in years |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BF_JARAF | |
Data Type | NUMC | Character string with only digits |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | USF_LIF_YR | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Usefl.life |
Medium | 15 | Useful life |
Long | 20 | Useful life |
Heading | 3 | Use |
Documentation
Definition
Useful life (in years) over which the asset is to be used and depreciated.
Note
The asset class usually provides a default useful life when you create the asset master record. When the asset class does not provide a useful life, the useful life field is always a required entry field (regardless of the screen layout). The only exception is when the depreciation key is 0000. The useful life field is a required field since it is one of the most important entries needed for calculating depreciation.
If the system cannot determine a usual useful life for the asset, and if you are using a depreciation method that always operates independently of the useful life, you can enter a very long useful life (for example, 100 years).
History
Last changed by/on | SAP | 20010607 |
SAP Release Created in |