tableFinanceofficial - Microsoftderived - from the source, no model text

Table 562 "VAT Clause by Doc. Type"

Base Application · Microsoft.Finance.VAT.Clause

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-28unchanged
  4. BC293 fields changed
  5. BC30unchanged

Neighbourhood 3 connected objects and pages

Table 560 "VAT Clause" (relates to)VAT ClausePage 734 "VAT Clauses by Doc. Type" (pages and codeunits on it)VAT Clauses by Doc. TypeSet up value-added tax (Learn pages)Set up value-added tax

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.Clause · captioned “VAT Clause by Document Type” · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 734 “VAT Clauses by Doc. Type” (1 Learn page).

Properties

Property Value
Caption VAT Clause by Document Type
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 VAT Clause Code Code[20] — TableRelation Table 560 “VAT Clause” (VAT Clause)
2 Document Type Δ BC29 Enum “VAT Clause Document Type” Specifies the document type, which is used to provide a VAT description associated with a sales line on a sales invoice, credit memo, or other sales document. enum Enum 562 “VAT Clause Document Type”
3 Description Δ BC29 Text[250] Specifies the translation of the VAT clause description. The translated version of the description is displayed as the VAT clause, based on the Language Code setting on the customer card.
4 Description 2 Δ BC29 Text[250] Specifies the translation of the additional VAT clause description.

Keys

  • Key1: VAT Clause Code, Document Type (clustered)

Relations

Pages and codeunits on this table

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: "table", object_name: "VAT Clause by Doc. Type"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources