Codeunit 1334 "Cancel PstdSalesCrM (Yes/No)"
Base Application · Microsoft.Sales.History
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Sales.History · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Sales Cr.Memo Header |
| Permissions | TableData “Sales Invoice Header” = rm, TableData “Sales Cr.Memo Header” = rm |
Events published
OnCancelInvoiceOnBeforePostedSalesInvoice(var SalesInvoiceHeader: Record "Sales Invoice Header"; var IsHandled: Boolean)(integration)
Procedures
1 local procedures, no public ones.
Triggers
OnRun
Relations
- runs on Table 114 “Sales Cr.Memo 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 1339 “Cancel Posted Sales Cr. Memo” (2 calls:
CancelCrMemo → CancelPostedCrMemo,CancelCrMemo → TestCorrectCrMemoIsAllowed) - Codeunit 700 “Page Management” (1 call:
CancelCrMemo → PageRun)
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: "Cancel PstdSalesCrM (Yes/No)"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.