Codeunit 920 "Period Form Lines Mgt."

Base Application · Microsoft.Foundation.Period · BC23-30 · source at ea08af5e · facts from BC29

Events published

• OnNextDateOnAfterCalcShouldInsertLine(var BufferRecord: Variant; var DateRec: Record Date; var ResultSteps: Integer; var ShouldInsertLine: Boolean) (integration)

Procedures

• FindDate(var BufferRecord: Variant; var DateRec: Record Date; Which: Text[3]; PeriodType: Option): Boolean
• NextDate(var BufferRecord: Variant; var DateRec: Record Date; Steps: Integer; PeriodType: Option): Integer

Plus 10 local procedures.

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 362 “PeriodPageManagement” (3 calls: FindDate → FindDate, FindDateRec → FindDate, NextDate → NextDate)

Called by

• Page 2624 “Stat. Account Balance Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 350 “G/L Acc. Balance/Budget Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 351 “Customer Sales Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 352 “Vendor Purchase Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 353 “Item Availability Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 354 “Item Turnover Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 355 “Receivables-Payables Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 361 “Res. Availability Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 362 “Res. Gr. Availability Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 378 “Bank Account Balance Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 416 “G/L Account Balance Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 5984 “Service Item Trend Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 6007 “Res. Availability Lines (SM)” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 6012 “Res.Gr Availability Lines (SM)” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 6061 “Contract Trend Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 866 “Cash Flow Availability Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 99000888 “Work Center Load Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 99000890 “Machine Center Load Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)
• Page 99000892 “Work Center Group Load Lines” (2 calls: OnFindRecord → FindDate, OnNextRecord → NextDate)

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: "Period Form Lines Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.