codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 20298 "Use Case Variables Mgmt."

INTaxEngine · Microsoft.Finance.TaxEngine.UseCaseBuilder

Across versions

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

Neighbourhood 6 connected objects and pages

Codeunit 20132 "Script Data Type Mgmt." (calls, 2 links)Script Data Type Mgmt.Codeunit 20133 "Script Symbols Mgmt." (calls, 2 links)Script Symbols Mgmt.Codeunit 20130 "App Object Helper" (calls)App Object HelperCodeunit 20235 "Use Case Data Type Mgmt." (calls)Use Case Data Type Mgmt.Codeunit 20291 "Tax Rate Computation" (calls)Tax Rate ComputationCodeunit 20297 "Use Case Symbols Handler" (calls)Use Case Symbols Handler

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

Procedures

  • GetTaxAttributeValue(CaseID: guid; var RecRef: RecordRef; AttributeID: Integer; var Value: Variant)

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.

Called by

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: "Use Case Variables Mgmt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources