Codeunit 5885 "Phys. Invt. Order-Post + Print"
Base Application · Microsoft.Inventory.Counting.Document
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Inventory.Counting.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Phys. Invt. Order Header |
Events published
OnAfterPostPhysInvtOrder(var PhysInvtOrderHeader: Record "Phys. Invt. Order Header")(integration)OnPhysInvtOrderPostPrintOnAfterConfirmBeforePost(var PhysInvtOrderHeader: Record "Phys. Invt. Order Header"; var IsHandled: Boolean)(integration)OnRunOnBeforeConfirm(var PhysInvtOrderHeader: Record "Phys. Invt. Order Header"; var IsHandled: Boolean)(integration)
Triggers
OnRun
Relations
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 229 “Document-Print” (1 call:
OnRun → PrintPostedInvtOrder) - Codeunit 5884 “Phys. Invt. Order-Post” (1 call:
OnRun → (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: "Phys. Invt. Order-Post + Print"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.