Codeunit 99000761 "Mfg. Item Journal Errors Mgt."

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

Event subscriptions

• OnDeleteRecordEventCapacityJournal subscribes to Page “Capacity Journal” OnDeleteRecordEvent
• OnModifyRecordEventCapacityJournal subscribes to Page “Capacity Journal” OnModifyRecordEvent
• OnInsertRecordEventCapacityJournal subscribes to Page “Capacity Journal” OnInsertRecordEvent
• OnDeleteRecordEventConsumptionJournal subscribes to Page “Consumption Journal” OnDeleteRecordEvent
• OnModifyRecordEventConsumptionJournal subscribes to Page “Consumption Journal” OnModifyRecordEvent
• OnInsertRecordEventConsumptionJournal subscribes to Page “Consumption Journal” OnInsertRecordEvent
• OnDeleteRecordEventOutputJournal subscribes to Page “Output Journal” OnDeleteRecordEvent
• OnModifyRecordEventOutputJournal subscribes to Page “Output Journal” OnModifyRecordEvent
• OnInsertRecordEventOutputJournal subscribes to Page “Output Journal” OnInsertRecordEvent

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 9077 “Item Journal Errors Mgt.” (9 calls: OnDeleteRecordEventCapacityJournal → InsertDeletedItemJnlLine, OnDeleteRecordEventConsumptionJournal → InsertDeletedItemJnlLine, OnDeleteRecordEventOutputJournal → InsertDeletedItemJnlLine, …)

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. Item Journal Errors Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.