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

Page 5647 "Ins. Coverage Ledger Entries"

Base Application · Microsoft.FixedAssets.Insurance

Across versions

  1. BC23-30present

Neighbourhood 5 connected objects and pages

Table 5629 "Ins. Coverage Ledger Entry" (relates to)Ins. Coverage Ledger EntryTable 5629 "Ins. Coverage Ledger Entry" (pages and codeunits on it, 2 links)Ins. Coverage Ledger EntryCodeunit 5658 "Ins. Reg.-Show Coverage Ledger" (calls)Ins. Reg.-Show Coverage LedgerPage 9275 "T. Value Insured per FA Matrix" (calls)T. Value Insured per FA MatrixInsure fixed assets (Learn pages)Insure 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.Insurance · captioned “Insurance Coverage Ledger Entries” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Insurance Coverage Ledger Entries
SourceTable Ins. Coverage Ledger Entry
PageType List
UsageCategory History
ApplicationArea FixedAssets

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 Posting Date Posting Date Specifies the entry’s posting date. 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
Insurance No. Insurance No. Specifies the number of the insurance policy the entry is linked to. from the table field
FA No. FA No. Specifies the number of the related fixed asset.
FA Description FA Description Specifies a description of the fixed asset that the insurance entry is linked to. from the table field
Description Description Specifies a description of the entry. 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
Amount Amount Specifies the amount of the entry. from the table field
Index Entry Index Entry Specifies that this entry is an index entry. from the table field
Disposed FA Disposed FA Specifies that the fixed asset linked to this entry has been disposed of. 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
Entry No. Entry No. Specifies the number of the entry, as assigned from the specified number series when the entry was created. 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.
Processing Find entries… Find entries and documents that exist for the document number and posting date on the selected document. (Formerly this action was named Navigate.)

Relations

Pages and codeunits on this table

Called by

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.

Documented on Microsoft Learn

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: "Ins. Coverage Ledger Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources