Codeunit 5425 "Create Financial Report"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Finance · BC29-30 · source at ea08af5e · facts from BC29

Procedures

• CreateSetupFinancialReport() (internal)
• AccountCategoriesOverview(): Code[10]
• CapitalStructure(): Code[10]
• CalculationOfCashFlow(): Code[10]
• DataForCashCycleChart(): Code[10]
• DataForCashFlowChart(): Code[10]
• DataForIncomeExpenseChart(): Code[10]
• DataForReducedTrialBalanceInfoPart(): Code[10]
• Revenues(): Code[10]
• BalanceSheetDetailed(): Code[10]
• BalanceSheetSummarized(): Code[10]
• IncomeStatementDetailed(): Code[10]
• IncomeStatementSummarized(): Code[10]
• TrialBalance(): Code[10]

Triggers

OnRun

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 5223 “Create Acc. Schedule Name” (13 calls: CreateSetupFinancialReport → CashCycle, CreateSetupFinancialReport → CashFlow, CreateSetupFinancialReport → IncomeExpense, …)
• Codeunit 5401 “Create Column Layout Name” (8 calls: CreateSetupFinancialReport → PeriodsDefinition, OnRun → BalanceOnly, OnRun → BalanceSheetTrend, …)
• Codeunit 5239 “Contoso Account Schedule” (2 calls: CreateSetupFinancialReport → InsertFinancialReport, OnRun → InsertFinancialReport)

Called by

• Codeunit 5415 “Finance Module” (2 calls: CreateMasterData → (object), CreateSetupData → CreateSetupFinancialReport)

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