Codeunit 61 "Sales-Disc. (Yes/No)"
Base Application · Microsoft.Sales.Document
Across versions
- BC23-30present
Neighbourhood 9 connected objects and pages
Base Application · Microsoft.Sales.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Sales Line |
Events published
OnBeforeOnRun(var SalesLine: Record "Sales Line"; var IsHandled: Boolean)(integration)
Triggers
OnRun
Relations
- runs on Table 37 “Sales Line”
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 27 “Confirm Management” (1 call:
OnRun → GetResponseOrDefault) - Codeunit 60 “Sales-Calc. Discount” (1 call:
OnRun → (object))
Called by
- Page 46 “Sales Order Subform” (1 call:
ApproveCalcInvDisc → (object)) - Page 47 “Sales Invoice Subform” (1 call:
ApproveCalcInvDisc → (object)) - Page 508 “Blanket Sales Order Subform” (1 call:
ApproveCalcInvDisc → (object)) - Page 6631 “Sales Return Order Subform” (1 call:
ApproveCalcInvDisc → (object)) - Page 95 “Sales Quote Subform” (1 call:
ApproveCalcInvDisc → (object)) - Page 96 “Sales Cr. Memo Subform” (1 call:
ApproveCalcInvDisc → (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: "Sales-Disc. (Yes/No)"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.