BC Observatoryunofficial, made by waldo
codeunitSales & Receivablesofficial - Microsoftderived - from the source, no model text

Codeunit 84 "Blnkt Sales Ord. to Ord. (Y/N)"

Base Application · Microsoft.Sales.Document

Open in Claude84.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 36 "Sales Header" (relates to)Sales HeaderCodeunit 87 "Blanket Sales Order to Order" (calls, 2 links)Blanket Sales Order to Order

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 Header

Events published

  • OnAfterCreateSalesOrder(var SalesHeader: Record "Sales Header"; var SkipMessage: Boolean) (integration)
  • OnBeforeRun(var SalesHeader: Record "Sales Header"; var IsHandled: Boolean) (integration)
  • OnBeforeShouldExit(var SalesHeader: Record "Sales Header"; var Result: Boolean; var IsHandled: Boolean) (integration)

Procedures

2 local procedures, no public ones.

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.

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: "Blnkt Sales Ord. to Ord. (Y/N)"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources