Codeunit 2847 "Cost Adj. Sch. Notif. Handler"
Base Application · Microsoft.Inventory.Costing
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Inventory.Costing · BC23-30 · source at ea08af5e · facts from BC29
Procedures
ShouldDisplayNotification(Rec: Record "Inventory Setup"; xRec: Record "Inventory Setup"): BooleanOnActionSchedule()OnActionLearnMore()
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 2849 “Cost Adj. Scheduling Manager” (2 calls:
ShouldDisplayNotification → AdjCostJobQueueExists,ShouldDisplayNotification → PostInvCostToGLJobQueueExists) - Page 2875 “Cost Adj. Scheduling Wizard” (1 call:
OnActionSchedule → (object))
Called by
- Codeunit 2848 “Cost Adj. Scheduling Notifier” (4 calls:
OnActionLearnMore → OnActionLearnMore,OnActionSchedule → OnActionSchedule,OnAfterValidateAutomaticCostAdjustment → ShouldDisplayNotification, …)
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: "Cost Adj. Sch. Notif. Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.