BC Observatoryunofficial, made by waldo
codeunitPurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Codeunit 402 "Purchase Header Apply"

Base Application · Microsoft.Purchases.Payables

Open in Claude402.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Table 38 "Purchase Header" (relates to)Purchase Header

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.Payables · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Purchase Header

Events published

  • OnAfterOnRun(var PurchHeader: Record "Purchase Header") (integration)
  • OnRunOnAfterFilterVendLedgEntry(var VendorLedgerEntry: Record "Vendor Ledger Entry"; var PurchaseHeader: Record "Purchase Header") (integration)
  • OnRunOnBeforeVendLedgEntryFindFirst(var VendorLedgerEntry: Record "Vendor Ledger Entry") (integration)

Triggers

OnRun

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "Purchase Header Apply"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources