BC Observatoryunofficial, made by waldo
codeunitManufacturingofficial - Microsoftderived - from the source, no model text

Codeunit 99000808 "PlanningRoutingManagement"

Base Application · Microsoft.Manufacturing.Routing

Open in Claude99000808.mdSource on GitHub

Across versions

  1. BC23-26present
  2. BC275 procedures added, 5 events added
  3. BC28-30unchanged

Neighbourhood 4 connected objects and pages

Table 99000830 "Planning Routing Line" (calls, 8 links)Planning Routing LineCodeunit 99000810 "Calculate Planning Route Line" (calls, 3 links)Calculate Planning Route LineCodeunit 5402 "Unit of Measure Management" (calls)Unit of Measure ManagementCodeunit 99000755 "Shop Calendar Management" (calls)Shop Calendar Management

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.Manufacturing.Routing · BC23-30 · source at ea08af5e · facts from BC29

Events published

  • OnCalculateRoutingOnAfterUpdateReqLine(var RequisitionLine: Record "Requisition Line"; Direction: Option Forward,Backward) + BC27 (integration)
  • OnAfterCalculatePlanningLineDates(var RequisitionLine: Record "Requisition Line") + BC27 (integration)
  • OnBeforeSetRtngLineSequenceBack(RoutingType: Option Serial,Parallel; var PlanningRoutingLine: Record "Planning Routing Line"; MaxSequences: Integer; ActSequences: Integer; TotalCalculation: Boolean) + BC27 (integration)
  • OnBeforeSetRtngLineSequenceForward(RoutingType: Option Serial,Parallel; var PlanningRoutingLine: Record "Planning Routing Line"; MaxSequences: Integer; ActSequences: Integer; TotalCalculation: Boolean) + BC27 (integration)
  • OnBeforeCalcSequenceFromActual(PlanningRoutingLine: Record "Planning Routing Line"; Direction: Option Forward,Backward; var RequisitionLine: Record "Requisition Line") + BC27 (integration)

Event subscriptions

  • OnGetResiliencyErrorOnRouting subscribes to Codeunit “Planning Line Management” OnGetResiliencyErrorOnRouting
  • OnBeforeRecalculateWithOptionalModify subscribes to Codeunit “Planning Line Management” OnBeforeRecalculateWithOptionalModify

Procedures

  • NeedsCalculation(WkShName: Code[10]; BatchName: Code[10]; LineNo: Integer): Boolean
  • SetRtngLineSequenceBack(RoutingType: Option Serial,Parallel; PlanningRtngLine: Record "Planning Routing Line"; Maxsequences: Integer; Actsequences: Integer; TotalCalculation: Boolean)
  • SetRtngLineSequenceForward(RoutingType: Option Serial,Parallel; PlanningRtngLine: Record "Planning Routing Line"; MaxSequences: Integer; ActSequences: Integer; TotalCalculation: Boolean)
  • CalcSequenceFromActual(PlanningRtngLine: Record "Planning Routing Line"; Direction: Option Forward,Backward; ReqLine: Record "Requisition Line")
  • Calculate(ReqLine: Record "Requisition Line")
  • CalculatePlanningLineDates(var ReqLine2: Record "Requisition Line") + BC27
  • CalculateRouting(var ReqLine: Record "Requisition Line"; Direction: Option Forward,Backward) + BC27
  • CalculateRoutingFromActual(var ReqLine: Record "Requisition Line"; PlanningRtngLine: Record "Planning Routing Line"; Direction: Option Forward,Backward; CalcStartEndDate: Boolean; PlanningResiliency: Boolean) + BC27

Plus 5 local procedures.

Triggers

OnRun

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

  • Table 99000830 “Planning Routing Line” (8 calls: CalcStartingEndingDates → CalcSequenceFromActual, CalcStartingEndingDates → CalculateRoutingFromActual, CalculateRoutingBack → CalcSequenceFromActual, …)

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

Evidence 1 sources