tableFinanceofficial - Microsoftderived - from the source, no model text

Table 253 "G/L Entry - VAT Entry Link"

Base Application · Microsoft.Finance.VAT.Ledger

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25unchanged
  4. BC26declaration changed
  5. BC27-30unchanged

Neighbourhood 3 connected objects and pages

Table 17 "G/L Entry" (relates to)G/L EntryTable 254 "VAT Entry" (relates to)VAT EntryCodeunit 338 "VAT Entry - Edit" (calls)VAT Entry - Edit

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

Properties

Property Value
Caption G/L Entry - VAT Entry Link
DataClassification CustomerContent
Permissions TableData “G/L Entry - VAT Entry Link” = rimd

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 G/L Entry No. Integer — TableRelation Table 17 “G/L Entry” (“G/L Entry”.“Entry No.”)
2 VAT Entry No. Integer — TableRelation Table 254 “VAT Entry” (“VAT Entry”.“Entry No.”)

Keys

  • Key1: G/L Entry No., VAT Entry No. (clustered)
  • Key2: VAT Entry No.

Events published

Procedures

  • InsertLinkSelf(GLEntryNo: Integer; VATEntryNo: Integer): Creates a link record in the current instance between a G/L entry and VAT entry. Raises integration event to notify subscribers of the new link creation.
  • InsertLinkWithGLAccountSelf(GLEntryNo: Integer; VATEntryNo: Integer): Creates a link between G/L and VAT entries and automatically adjusts the G/L account number on the VAT entry. Combines link creation with G/L account synchronization for data consistency.
  • AdjustGLAccountNoOnVATEntry(): Updates the G/L account number on the linked VAT entry to match the G/L entry’s account. Ensures consistency between VAT entries and their corresponding G/L account assignments.

Relations

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.

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: "table", object_name: "G/L Entry - VAT Entry Link"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources