Report 7139 "Date Comp. Item Budget Entries"

Base Application · Microsoft.Inventory.Analysis · captioned “Date Compr. Item Budget Entries” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• InitNewEntry(var NewItemBudgetEntry: Record "Item Budget Entry")
• InitializeRequest(AnalAreaSelection: Option; StartDate: Date; EndDate: Date; PeriodLength: Option; Desc: Text[100]; RetainDimensions: Text[250])
• InitializeRequest(AnalAreaSelection: Option; StartDate: Date; EndDate: Date; PeriodLength: Option; Desc: Text[100]; RetainDimensions: Text[250]; DoUseDataArchive: Boolean)
• SetSkipAnalysisViewUpdateCheck() Δ BC28

Plus 11 local procedures.

Triggers

OnPreReport, OnPostReport

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 411 “Dimension Buffer Management” (4 calls: ComprCollectedEntries → DeleteAllDimEntryNo, ComprCollectedEntries → FindFirstDimEntryNo, ComprCollectedEntries → NextDimEntryNo, …)
• Codeunit 408 “DimensionManagement” (2 calls: InsertNewEntry → CopyDimBufToDimSetEntry, InsertNewEntry → GetDimensionSetID)
• Codeunit 600 “Data Archive” (2 calls: InitializeVariables → DataArchiveProviderExists, SummarizeEntry → SaveRecord)
• Codeunit 9040 “Date Compression” (2 calls: InitializeVariables → CalcMaxEndDate, OnPreReport → VerifyDateCompressionDates)

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: "Date Comp. Item Budget Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.