BC Observatoryunofficial, made by waldo
codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 115 "G/L Entry-Edit"

Base Application · Microsoft.Finance.GeneralLedger.Ledger

Open in Claude115.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 17 "G/L Entry" (relates to)G/L EntryPage 20 "General Ledger Entries" (calls)General Ledger Entries

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

Properties

Property Value
TableNo G/L Entry
Permissions TableData “G/L Entry” = m

Events published

  • OnBeforeGLLedgEntryModify(var GLEntry: Record "G/L Entry"; FromGLEntry: Record "G/L Entry") (integration): Integration event raised before modifying a G/L entry.

Event subscriptions

  • OnAfterIsAlwaysLoggedTable subscribes to Codeunit “Change Log Management” OnAfterIsAlwaysLoggedTable

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

Evidence 1 sources