Codeunit 99000759 "Calendar Absence Management"

Base Application · Microsoft.Manufacturing.Capacity · BC23-30 · source at ea08af5e · facts from BC29

Events published

• OnAfterUpdateAbsence(var CalendarAbsenceEntry: Record "Calendar Absence Entry") (integration)

Procedures

• UpdateAbsence(var CalAbsentEntry: Record "Calendar Absence Entry")
• RemoveAbsence(var CalAbsentEntry: Record "Calendar Absence Entry")

Plus 1 local procedures.

Triggers

OnRun

Called by

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.

• Table 99000760 “Calendar Absence Entry” (2 calls: OnDelete → RemoveAbsence, OnRename → RemoveAbsence)
• Codeunit 99000755 “Shop Calendar Management” (1 call: CalculateSchedule → UpdateAbsence)
• Report 99001047 “Recalculate Calendar” (1 call: HandleAbsence → UpdateAbsence)

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: "Calendar Absence Management"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.