Report 7112 "Analysis Report"

Base Application · Microsoft.Inventory.Analysis · BC23-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• InitAnalysisLine()
• SetParameters(NewAnalysisArea: Enum "Analysis Area Type"; NewReportName: Code[10]; NewLineTemplateName: Code[10]; NewColumnTemplateName: Code[10])
• SetFilters(NewDateFilter: Text; NewItemBudgetFilter: Text; NewLocationFilter: Text; NewDim1Filter: Text; NewDim2Filter: Text; NewDim3Filter: Text; NewSourceTypeFilter: Option " ",Customer,Vendor,Item; NewSourceNoFilter: Text)

Plus 5 local procedures.

Triggers

OnPreReport

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 7110 “Analysis Report Management” (4 calls: CalcColumns → CalcCell, CalcColumns → GetDivisionError, CalcColumns → GetPeriodError, …)
• Codeunit 360 “Accounting Period Mgt.” (1 call: InitAnalysisLine → FindFiscalYear)
• Codeunit 9200 “Matrix Management” (1 call: CalcColumns → FormatAmount)

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: "report", object_name: "Analysis Report"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.