codeunitSales & Receivablesofficial - Microsoftderived - from the source, no model text

Codeunit 61 "Sales-Disc. (Yes/No)"

Base Application · Microsoft.Sales.Document

Across versions

  1. BC23-30present

Neighbourhood 9 connected objects and pages

Table 37 "Sales Line" (relates to)Sales LineCodeunit 27 "Confirm Management" (calls)Confirm ManagementCodeunit 60 "Sales-Calc. Discount" (calls)Sales-Calc. DiscountPage 46 "Sales Order Subform" (calls)Sales Order SubformPage 47 "Sales Invoice Subform" (calls)Page 508 "Blanket Sales Order Subform" (calls)Blanket Sales Order SubformPage 6631 "Sales Return Order Subform" (calls)Sales Return Order SubformPage 95 "Sales Quote Subform" (calls)Sales Quote SubformPage 96 "Sales Cr. Memo Subform" (calls)Sales Cr. Memo Subform

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.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

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.

Called by

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.

Evidence 1 sources