Page 5671 "Maint. Ledg. Entries Preview"

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

Properties

Property	Value
Caption	Maint. Ledg. Entries Preview
SourceTable	Maintenance Ledger Entry
PageType	List

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
Control1	FA Posting Date	FA Posting Date	Specifies the posting date of the related fixed asset transaction, such as a depreciation. from the table field
	Document Type	Document Type	Specifies the document type that the entry belongs to. from the table field
	Document No.	Document No.	Specifies the document number on the entry. from the table field
	FA No.	FA No.	Specifies the number of the related fixed asset.
	Depreciation Book Code	Depreciation Book Code	Specifies the code for the depreciation book to which the line will be posted if you have selected Fixed Asset in the Type field for this line. from the table field
	Description	Description	Specifies a description of the entry. from the table field
	Amount	Amount	Specifies the amount of the entry. from the table field
	Debit Amount	Debit Amount	Specifies the total of the ledger entries that represent debits. from the table field
	Credit Amount	Credit Amount	Specifies the total of the ledger entries that represent credits. from the table field
	Maintenance Code	Maintenance Code	Specifies the maintenance code that the entry is linked to. from the table field
	Global Dimension 1 Code	Global Dimension 1 Code	Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field
	Global Dimension 2 Code	Global Dimension 2 Code	Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field
	Bal. Account Type	Bal. Account Type	Specifies the type of account that a balancing entry is posted to, such as BANK for a cash account. from the table field
	Bal. Account No.	Bal. Account No.	Specifies the number of the general ledger, customer, vendor, or bank account that the balancing entry is posted to, such as a cash account for cash purchases. from the table field
	User ID	User ID	Specifies the ID of the user who posted the entry, to be used, for example, in the change log. from the table field
	Source Code	Source Code	Specifies the source code that specifies where the entry was created. from the table field
	Reason Code	Reason Code	Specifies the reason code, a supplementary source code that enables you to trace the entry. from the table field
	Reversed	Reversed	Specifies whether the entry has been part of a reverse transaction (correction) made by the Reverse function. from the table field
	Reversed by Entry No.	Reversed by Entry No.	Specifies the number of the correcting entry. from the table field
	Reversed Entry No.	Reversed Entry No.	Specifies the number of the original entry that was undone by the reverse transaction. from the table field
	Posting Date	Posting Date	Specifies the entry’s posting date. from the table field
	Dimension Set ID	Dimension Set ID	Specifies a reference to a combination of dimension values. The actual values are stored in the Dimension Set Entry table. from the table field
	Shortcut Dimension 3 Code	Shortcut Dimension 3 Code	Specifies the code for Shortcut Dimension 3, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 4 Code	Shortcut Dimension 4 Code	Specifies the code for Shortcut Dimension 4, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 5 Code	Shortcut Dimension 5 Code	Specifies the code for Shortcut Dimension 5, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 6 Code	Shortcut Dimension 6 Code	Specifies the code for Shortcut Dimension 6, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 7 Code	Shortcut Dimension 7 Code	Specifies the code for Shortcut Dimension 7, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 8 Code	Shortcut Dimension 8 Code	Specifies the code for Shortcut Dimension 8, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field

Actions

Group	Action	ToolTip	Runs
Entry	Dimensions	View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.
	Set Dimension Filter	Limit the entries according to the dimension filters that you specify. NOTE: If you use a high number of dimension combinations, this function may not work and can result in a message that the SQL server only supports a maximum of 2100 parameters.

Procedures

1 local procedures, no public ones.

Triggers

OnOpenPage

Relations

source table Table 5625 “Maintenance Ledger Entry”

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.

Codeunit 408 “DimensionManagement” (1 call: SetDimVisibility → UseShortcutDims)

Called by

Codeunit 20 “Posting Preview Event Handler” (1 call: ShowEntries → (object))

Documented on Microsoft Learn

Manage fixed assets

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: "page", object_name: "Maint. Ledg. Entries Preview"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.