codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 338 "VAT Entry - Edit"

Base Application · Microsoft.Finance.VAT.Ledger

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 254 "VAT Entry" (relates to)VAT EntryPage 315 "VAT Entries" (calls)VAT EntriesTable 253 "G/L Entry - VAT Entry Link" (calls)G/L Entry - VAT Entry Link

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
TableNo VAT Entry
Permissions TableData “VAT Entry” = m

Events published

  • OnBeforeVATEntryModify(var VATEntry: Record "VAT Entry"; FromVATEntry: Record "VAT Entry") (integration): Integration event raised before modifying a VAT entry during the edit process. Allows custom validation or additional field updates before the VAT entry is saved.
  • OnRunOnAfterVATEntryModify(var VATEntry: Record "VAT Entry"; FromVATEntry: Record "VAT Entry") (integration): Integration event raised after successfully modifying a VAT entry during the edit process. Enables custom processing or notifications after the VAT entry has been updated and saved.

Procedures

  • SetGLAccountNo(var VATEntryModify: Record "VAT Entry"; GLAccountNo: Code[20]): Updates the G/L account number on a VAT entry record and saves the changes. Ensures proper linking between VAT entries and their corresponding G/L accounts.
  • SetGLAccountNo(VATEntryNo: Integer; GLAccountNo: Code[20]): Updates the G/L account number for a specific VAT entry identified by entry number. Performs bulk modification without triggering individual record events.

Triggers

OnRun

Relations

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.

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: "codeunit", object_name: "VAT Entry - Edit"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources