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

Codeunit 207 "Alt. Cust. VAT Reg. Orchest."

Base Application · Microsoft.Finance.VAT.Registration

Open in Claude207.mdSource on GitHub

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 200 "Alt. Cust. VAT. Reg. Facade" (calls, 8 links)Alt. Cust. VAT. Reg. Facade

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

Properties

Property Value
Access Internal

Procedures

  • GetAltCustVATRegConsistencyImpl(): Interface "Alt. Cust. VAT Reg. Consist."
  • GetShipToAlCustVATRegImpl(): Interface "Ship-To Alt. Cust. VAT Reg."
  • GetAltCustVATRegDocImpl(): Interface "Alt. Cust. VAT Reg. Doc."

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.

  • Codeunit 200 “Alt. Cust. VAT. Reg. Facade” (8 calls: CheckAltCustVATRegConsistent → GetAltCustVATRegConsistencyImpl, CheckCustomerConsistency → GetAltCustVATRegConsistencyImpl, CopyFromCustomer → GetAltCustVATRegDocImpl, …)

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: "Alt. Cust. VAT Reg. Orchest."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources