Codeunit 99000861 "Mfg. Planning Integration"

Base Application · Microsoft.Inventory.Planning · BC26-30 · source at ea08af5e · facts from BC29

Event subscriptions

• PlanningAssignmentOnItemChange subscribes to Table “Planning Assignment” OnItemChange
• OnAfterGetUpdateFromSKU subscribes to Table “Planning Component” OnAfterGetUpdateFromSKU
• PlanningCompomentOnAfterValidateCalculationFormula subscribes to Table “Planning Component” OnAfterValidateCalculationFormula
• OnGetToBinOnBeforeGetWMSDefaultCode subscribes to Table “Planning Component” OnGetToBinOnBeforeGetWMSDefaultCode
• PlanningErrorLogOnShowError subscribes to Table “Planning Error Log” OnShowError
• OnSurplusQtyOnSetReservEntryFilters subscribes to Codeunit “Planning Transparency” OnSurplusQtyOnSetReservEntryFilters
• OnFindReasonOnAfterSetSurplusType subscribes to Codeunit “Planning Transparency” OnFindReasonOnAfterSetSurplusType
• OnAtSKUOnBeforeSetSafetyLeadTime subscribes to Codeunit “Planning-Get Parameters” OnAtSKUOnBeforeSetSafetyLeadTime
• OnGetComponentsAtLocation subscribes to Table “Inventory Setup” OnGetComponentsAtLocation

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.

• Page 99000754 “Work Center Card” (1 call: PlanningErrorLogOnShowError → (object))
• Page 99000760 “Machine Center Card” (1 call: PlanningErrorLogOnShowError → (object))
• Page 99000766 “Routing” (1 call: PlanningErrorLogOnShowError → (object))
• Page 99000786 “Production BOM” (1 call: PlanningErrorLogOnShowError → (object))
• Page 99000809 “Production BOM Version” (1 call: PlanningErrorLogOnShowError → (object))
• Page 99000810 “Routing Version” (1 call: PlanningErrorLogOnShowError → (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: "Mfg. Planning Integration"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.