tableFixed Assetsofficial - Microsoftderived - from the source, no model text

Table 5617 "FA Register"

Base Application · Microsoft.FixedAssets.Ledger

Across versions

  1. BC23present
  2. BC242 fields changed
  3. BC25unchanged
  4. BC262 fields changed, 2 procedures changed
  5. BC271 fields changed
  6. BC2810 fields changed
  7. BC29-30unchanged

Neighbourhood 9 connected objects and pages

Table 5601 "FA Ledger Entry" (relates to, 2 links)FA Ledger EntryTable 5625 "Maintenance Ledger Entry" (relates to, 2 links)Maintenance Ledger EntryTable 230 "Source Code" (relates to)Source CodeTable 45 "G/L Register" (relates to)G/L RegisterPage 5627 "FA Registers" (pages and codeunits on it, 2 links)FA RegistersCodeunit 5620 "FA Reg.-FALedger" (pages and codeunits on it)FA Reg.-FALedgerCodeunit 5650 "FA Reg.-MaintLedger" (pages and codeunits on it)FA Reg.-MaintLedgerCodeunit 703 "Find Record Management" (calls, 2 links)Find Record ManagementSet Up General Fixed Assets (FA) Information (Learn pages)Set Up General Fixed Assets …

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.FixedAssets.Ledger · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 5627 “FA Registers” (1 Learn page).

Properties

Property Value
Caption FA Register
DataClassification CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 No. Δ BC28 Integer Specifies the number of the involved entry or record, according to the specified number series.
2 From Entry No. Δ BC28 Integer Specifies the first item entry number in the register. TableRelation Table 5601 “FA Ledger Entry” (FA Ledger Entry)
3 To Entry No. Δ BC28 Integer Specifies the last FA entry number in the register. TableRelation Table 5601 “FA Ledger Entry” (FA Ledger Entry)
4 Creation Date Δ BC24 Δ BC26 Date —
5 Source Code Δ BC28 Code[10] Specifies the source code that specifies where the entry was created. TableRelation Table 230 “Source Code” (Source Code)
6 User ID Δ BC28 Code[50] Specifies the ID of the user who posted the entry, to be used, for example, in the change log. TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation
7 Journal Batch Name Δ BC28 Code[10] Specifies the name of the journal batch, a personalized journal layout, that the entries were posted from.
8 Journal Type Δ BC28 Enum “FA Journal Type” Specifies the type of journal (G/L or Fixed Asset) that the entries were posted from. enum Enum 5621 “FA Journal Type”
9 G/L Register No. Δ BC28 Integer Specifies the number of the G/L register that was created when the entries were posted. TableRelation Table 45 “G/L Register” (G/L Register)
10 From Maintenance Entry No. Δ BC28 Integer Specifies the first maintenance entry number in the register. TableRelation Table 5625 “Maintenance Ledger Entry” (Maintenance Ledger Entry)
11 To Maintenance Entry No. Δ BC28 Integer Specifies the last maintenance entry number in the register. TableRelation Table 5625 “Maintenance Ledger Entry” (Maintenance Ledger Entry)
13 Creation Time Δ BC24 Δ BC26 Δ BC27 Time — obsolete Removed 27.0; #if not CLEANSCHEMA27

Keys

  • Key1: No. (clustered)
  • Key3: Source Code, Journal Batch Name

Procedures

  • GetLastEntryNo(): Integer Δ BC26
  • GetLastGLRegisterNo(): Integer Δ BC26

Relations

Pages and codeunits on this table

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Deprecations

  • field Creation Time: Removed 27.0 (#if not CLEANSCHEMA27), “Use the system audit field “System Created at” instead.”

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). The call sections above are our own, per object, from the BC29 call graph. 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: "table", object_name: "FA Register"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources