pageFinanceofficial - Microsoftderived - from the source, no model text

Page 320 "VAT Statement Names"

Base Application · Microsoft.Finance.VAT.Reporting

Across versions

  1. BC23-30present

Neighbourhood 5 connected objects and pages

Table 257 "VAT Statement Name" (relates to)VAT Statement NameTable 257 "VAT Statement Name" (pages and codeunits on it)VAT Statement NameCodeunit 340 "VATStmtManagement" (calls)VATStmtManagementPrint VAT Audit Reports (Learn pages)Print VAT Audit ReportsSet up a VAT statement (Learn pages)Set up a VAT statement

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.Finance.VAT.Reporting · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption VAT Statement Names
SourceTable VAT Statement Name
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 Name Name Specifies the VAT statement name. from the table field
Description Description Specifies a description of the VAT statement name. from the table field

Actions

Group Action ToolTip Runs
Processing Edit VAT Statement View or edit how to calculate your VAT settlement amount for a period.
Print Prepare to print the document. A report request window for the document opens where you can specify what to include on the print-out.
Reporting EC Sales List View, print, or save an overview of your sales to other EU countries/regions. You can use the information when you report to the customs and tax authorities. Report 130 “EC Sales List”

Procedures

1 local procedures, no public ones.

Triggers

OnInit, OnOpenPage

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.

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: "VAT Statement Names"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 3 sources