codeunitInventoryofficial - Microsoftderived - from the source, no model text

Codeunit 1852 "Sales Forecast Scheduler"

SalesAndInventoryForecast · Microsoft.Inventory.InventoryForecast

Across versions

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

Neighbourhood 7 connected objects and pages

Codeunit 456 "Job Queue Management" (calls, 2 links)Job Queue ManagementCodeunit 1853 "Sales Forecast Update" (calls)Sales Forecast UpdateCodeunit 453 "Job Queue - Enqueue" (calls)Job Queue - EnqueueCodeunit 457 "Environment Information" (calls)Environment InformationCodeunit 9026 "User Login Time Tracker" (calls)User Login Time TrackerPage 1853 "Sales Forecast Setup Card" (calls)Sales Forecast Setup CardPage 673 "Job Queue Entry Card" (calls)Job Queue Entry Card

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.

SalesAndInventoryForecast · Microsoft.Inventory.InventoryForecast · BC29-30 · source at ea08af5e · facts from BC29

Event subscriptions

  • OnOpenSalesInventoryForecastSetup subscribes to Page “Sales Forecast Setup Card” OnOpenPageEvent
  • OnOpenItemList subscribes to Page “Item List” OnOpenPageEvent
  • OnInitializingNotificationWithDefaultState subscribes to Page “My Notifications” OnInitializingNotificationWithDefaultState

Procedures

  • CreateJobQueueEntryAndOpenCard()
  • CreateJobQueueEntry(var JobQueueEntry: Record "Job Queue Entry"; Recurring: Boolean)
  • RemoveScheduledTaskIfUserInactive()
  • SetupScheduledForecasting(SetupNotification: Notification)
  • DeactivateNotification(SetupNotification: Notification)
  • GetSetupNotificationID(): Guid
  • JobQueueEntryCreationInProcess(): Boolean

Plus 4 local procedures.

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: "Sales Forecast Scheduler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources