tableFinanceofficial - Microsoftderived - from the source, no model text

Table 563 "VAT Clause by Doc. Type Trans."

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 ClauseTable 8 "Language" (relates to)LanguagePage 735 "VAT Clause by Doc. Type Trans." (pages and codeunits on it)VAT Clause by Doc. Type Trans.

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 Translation” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption VAT Clause by Document Type Translation
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 Enum “VAT Clause Document Type” — enum Enum 562 “VAT Clause Document Type”
3 Language Code Δ BC29 Code[10] Specifies the language that is used when translating specified text on documents to foreign business partner, such as an item description on an order confirmation. TableRelation Table 8 “Language”
4 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.
5 Description 2 Δ BC29 Text[250] Specifies the translation of the additional VAT clause description.

Keys

  • Key1: VAT Clause Code, Document Type, Language Code (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 Trans."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources