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

Codeunit 320 "PurchCrMemo-Printed"

Base Application · Microsoft.Purchases.History

Open in Claude320.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Table 124 "Purch. Cr. Memo Hdr." (relates to)Purch. Cr. Memo Hdr.

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

Properties

Property Value
TableNo Purch. Cr. Memo Hdr.
Permissions TableData “Purch. Cr. Memo Hdr.” = rimd

Events published

  • OnBeforeModify(var PurchCrMemoHdr: Record "Purch. Cr. Memo Hdr.") (integration)
  • OnBeforeOnRun(var PurchCrMemoHdr: Record "Purch. Cr. Memo Hdr."; var SuppressCommit: Boolean) (integration)

Procedures

  • SetSuppressCommit(NewSuppressCommit: Boolean)

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

Evidence 1 sources