Codeunit 1854 "Sales Forecast Notifier"
SalesAndInventoryForecast · Microsoft.Inventory.InventoryForecast
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
SalesAndInventoryForecast · Microsoft.Inventory.InventoryForecast · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SingleInstance | true |
| Permissions | TableData “My Notifications” = rimd, TableData “MS - Sales Forecast Setup” = r |
Event subscriptions
- OnAfterCurrPurchaseInvoice subscribes to Page “Purchase Invoice” OnAfterGetCurrRecordEvent
- OnAfterCurrPurchaseOrder subscribes to Page “Purchase Order” OnAfterGetCurrRecordEvent
- OnAfterBuyFromVendorNameValidate subscribes to Page “Purchase Invoice” OnAfterValidateEvent (Buy-from Vendor Name)
- OnAfterInsertPurchaseHeader subscribes to Page “Purchase Invoice” OnInsertRecordEvent
- OnAfterTableInsert subscribes to Table “Purchase Header” OnAfterInsertEvent
- OnInitializingNotificationWithDefaultState subscribes to Page “My Notifications” OnInitializingNotificationWithDefaultState
Procedures
CreatePurchaseLineAction(StockoutNotification: Notification)DeactivateNotification(SetupNotification: Notification)CreateAndShowPurchaseInvoice(ItemNo: Code[20])CreateAndShowPurchaseOrder(ItemNo: Code[20])GetNotificationGuid(): Guid
Plus 13 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.
- Codeunit 362 “PeriodPageManagement” (1 call:
InitializeSalesForecastQuery → MoveDateByPeriod) - Page 50 “Purchase Order” (1 call:
CreateAndShowPurchaseDocument → (object)) - Page 51 “Purchase Invoice” (1 call:
CreateAndShowPurchaseDocument → (object))
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 Notifier"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.