Codeunit 9071 "Check Sales Document"
Base Application · Microsoft.Sales.Document
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Sales.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Sales Header |
Procedures
1 local procedures, no public ones.
Triggers
OnRun
Relations
- runs on Table 36 “Sales Header”
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 80 “Sales-Post” (2 calls:
RunCheck → CheckSalesDocument,RunCheck → PrepareCheckDocument)
Called by
- Codeunit 9072 “Check Sales Doc. Backgr.” (1 call:
RunSalesDocCheckCodeunit → (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 Sales Document"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.