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

Codeunit 99000850 "Sales Line-Planning"

Base Application · Microsoft.Sales.Document

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26declaration changed
  4. BC27-30unchanged

Neighbourhood 3 connected objects and pages

Codeunit 6500 "Item Tracking Management" (calls)Item Tracking ManagementPage 42 "Sales Order" (calls)Sales OrderPage 6630 "Sales Return Order" (calls)Sales Return 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 · BC25-30 · source at ea08af5e · facts from BC29

Event subscriptions

  • ReqLineOnSetDemandTypeFromUnplannedDemand subscribes to Table “Requisition Line” OnSetDemandTypeFromUnplannedDemand
  • OnValidateDemandOrderNoOnGetSourceFields subscribes to Table “Unplanned Demand” OnValidateDemandOrderNoOnGetSourceFields
  • CarryOutActionMsgPlanOnCheckDemandType subscribes to Report “Carry Out Action Msg. - Plan.” OnCheckDemandType
  • OnInsertDemandLinesOnCopyItemTracking subscribes to Codeunit “Order Planning Mgt.” OnInsertDemandLinesOnCopyItemTracking
  • OrderPlanningOnBeforeShowDemandOrder subscribes to Page “Order Planning” OnBeforeShowDemandOrder
  • OnSetRecDemandFilter subscribes to Page “Order Planning” OnSetRecDemandFilter
  • OnAfterStatusTextOnFormat subscribes to Page “Order Planning” OnAfterStatusTextOnFormat
  • OnAfterDemandTypeTextOnFormat subscribes to Page “Order Planning” OnAfterDemandTypeTextOnFormat
  • OnAfterDemandSubtypeTextOnFormat subscribes to Page “Order Planning” OnAfterDemandSubtypeTextOnFormat

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.

Recent changes

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

Evidence 1 sources