codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 20340 "Fin Charge Posting Handler"

INTaxEngine · Microsoft.Finance.TaxEngine.PostingHandler

Across versions

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

Neighbourhood 2 connected objects and pages

Codeunit 20343 "Tax Posting Buffer Mgmt." (calls, 5 links)Tax Posting Buffer Mgmt.Codeunit 20341 "Tax Document GL Posting" (calls, 3 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.PostingHandler · BC29-30 · source at ea08af5e · facts from BC29

Event subscriptions

  • OnBeforePostServiceDoc subscribes to Codeunit “FinChrgMemo-Issue” OnBeforeIssueFinChargeMemo
  • OnBeforePost subscribes to Codeunit “FinChrgMemo-Issue” OnAfterGetFinChrgMemoLine
  • OnAfterIsueFinChargeMemo subscribes to Codeunit “FinChrgMemo-Issue” OnAfterInsertIssuedFinChrgMemoLine
  • OnBeforePostCustomerEntry subscribes to Codeunit “FinChrgMemo-Issue” OnBeforeGenJnlPostLineRunWithCheck

Procedures

2 local procedures, no public ones.

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: "codeunit", object_name: "Fin Charge Posting Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources