Codeunit 9068 "Check Purch. Doc. Backgr."
Base Application · Microsoft.Purchases.Document
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Purchases.Document · BC23-30 · source at ea08af5e · facts from BC29
Procedures
RunCheck(Args: Dictionary of [Text, Text]; var TempErrorMessage: Record "Error Message" temporary)
Plus 4 local procedures.
Triggers
OnRun
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 28 “Error Message Management” (9 calls:
OnRun → PackErrorMessagesToResults,RunPurchaseDocCheckCodeunit → Activate,RunPurchaseDocCheckCodeunit → CollectErrors, …) - Codeunit 9066 “Check Purchase Document Line” (2 calls:
RunPurchaseDocLineCheckCodeunit → (object),RunPurchaseDocLineCheckCodeunit → SetPurchaseHeader) - Codeunit 9067 “Check Purchase Document” (1 call:
RunPurchaseDocCheckCodeunit → (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: "Check Purch. Doc. Backgr."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.