Codeunit 2849 "Cost Adj. Scheduling Manager"

Base Application · Microsoft.Inventory.Costing · BC23-30 · source at ea08af5e · facts from BC29

Procedures

• AdjCostJobQueueExists(): Boolean
• PostInvCostToGLJobQueueExists(): Boolean
• CreateAdjCostJobQueue()
• CreatePostInvCostToGLJobQueue()
• SetupDisplayJobQueueEntriesFilter(var JobQueueEntry: Record "Job Queue Entry")

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 88 “Sales Post via Job Queue” (3 calls: CreateAdjCostJobQueue → GetJobQueueCategoryCode, CreatePostInvCostToGLJobQueue → GetJobQueueCategoryCode, SetupDisplayJobQueueEntriesFilter → GetJobQueueCategoryCode)

Called by

• Page 2875 “Cost Adj. Scheduling Wizard” (5 calls: OnFinish → CreateAdjCostJobQueue, OnFinish → CreatePostInvCostToGLJobQueue, OnFinish → SetupDisplayJobQueueEntriesFilter, …)
• Codeunit 2847 “Cost Adj. Sch. Notif. Handler” (2 calls: ShouldDisplayNotification → AdjCostJobQueueExists, ShouldDisplayNotification → PostInvCostToGLJobQueueExists)
• Page 461 “Inventory Setup” (2 calls: SetAdjustCostWizardActionVisibility → AdjCostJobQueueExists, SetAdjustCostWizardActionVisibility → PostInvCostToGLJobQueueExists)

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. Scheduling Manager"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.