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 | WRTAFB |
| Short Description | Adoption of values from depreciation area |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AFABE | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | T093 |
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 | Val.adopt. |
| Medium | 20 | Adopt values from |
| Long | 40 | Adoption of values frm depreciation area |
| Heading | 5 | ValAd |
Documentation
Definition
In this field, you specify the reference depreciation area that provides values to another depreciation area. The system transfers the posting amounts of any transactions that affect acquisition and production costs from this area to the dependent area (exception: if you specifically enter an amount for the dependent area). A depreciation area can only adopt values from an area that has a smaller key than itself. No transfer is therefore possible to area 01.
Examples
You can set up a linked series of adoption of values, so that area 03, for example, can indirectly adopt the values from area 01 via area 02 (changes in area 02, however, also affect area 03).
If no reference area is specified in a depreciation area that has a key greater than 01, you can only post in this depreciation area using transaction types that are specifically assigned to this area in its definition. In this way, accidental posting to special areas (such as for investment subsidy) can be avoided.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in | 470 |
