Enum 5602 "FA Journal Line FA Posting Type"
Base Application · Microsoft.FixedAssets.Journal
Across versions
- BC23-27present
- BC28declaration changed
- BC29-30unchanged
Base Application · Microsoft.FixedAssets.Journal · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | true |
Values
| Ordinal | Name | Caption | Notes |
|---|---|---|---|
| 0 | Acquisition Cost | Acquisition Cost | |
| 1 | Depreciation | Depreciation | |
| 2 | Write-Down | Write-Down | |
| 3 | Appreciation | Appreciation | |
| 4 | Custom 1 | Custom 1 | |
| 5 | Custom 2 | Custom 2 | |
| 6 | Disposal | Disposal | |
| 7 | Maintenance | Maintenance | |
| 8 | Salvage Value | Salvage Value | |
| 10 | Bonus Depreciation | Bonus Depreciation |
Countries that replace it
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "enum", object_name: "FA Journal Line FA Posting Type"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.