codeunitPurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Codeunit 6454 "Serv. Purch.-Post"

Base Application · Microsoft.Purchases.Posting

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-27unchanged
  4. BC283 procedures changed
  5. BC29-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 5920 "ServItemManagement" (calls, 2 links)ServItemManagement

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Purchases.Posting · BC25-30 · source at ea08af5e · facts from BC29

Properties

Property Value
SingleInstance true
Permissions TableData “Service Item” = rimd

Event subscriptions

  • OnRunOnBeforeCheckAndUpdate subscribes to Codeunit “Purch.-Post” OnBeforeCheckAndUpdate
  • OnAfterInsertReceiptHeader subscribes to Codeunit “Purch.-Post” OnAfterInsertReceiptHeader
  • OnPostCombineSalesOrderShipmentOnAfterUpdateSalesOrderLine subscribes to Codeunit “Purch.-Post” OnPostCombineSalesOrderShipmentOnAfterUpdateSalesOrderLine

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 5920 “ServItemManagement” (2 calls: OnAfterInsertReceiptHeader → CopyReservation, OnPostCombineSalesOrderShipmentOnAfterUpdateSalesOrderLine → CreateServItemOnSalesLineShpt)

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: "Serv. Purch.-Post"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources