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

Codeunit 20136 "Archive Management Handler"

INTaxEngine · Microsoft.Finance.TaxEngine.Core

Open in Claude20136.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Codeunit 20341 "Tax Document GL Posting" (calls, 4 links)Tax Document GL Posting

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.

INTaxEngine · Microsoft.Finance.TaxEngine.Core · BC29-30 · source at ea08af5e · facts from BC29

Event subscriptions

  • OnAfterStorePurchLineArchive subscribes to Codeunit “ArchiveManagement” OnAfterStorePurchLineArchive
  • OnAfterStoreSalesLineArchive subscribes to Codeunit “ArchiveManagement” OnAfterStoreSalesLineArchive

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.

  • Codeunit 20341 “Tax Document GL Posting” (4 calls: OnAfterStorePurchLineArchive → PrepareTransactionValueToPost, OnAfterStorePurchLineArchive → TransferTransactionValue, OnAfterStoreSalesLineArchive → PrepareTransactionValueToPost, …)

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: "Archive Management Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources