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

Codeunit 99000812 "PlanningWkshManagement"

Base Application · Microsoft.Inventory.Requisition

Open in Claude99000812.mdSource on GitHub

Across versions

  1. BC23-26present
  2. BC271 events added
  3. BC28-30unchanged

Neighbourhood 2 connected objects and pages

Codeunit 99000866 "Mfg. Requisition Line" (event subscribers)Mfg. Requisition LinePage 99000852 "Planning Worksheet" (calls)Planning Worksheet

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

Events published

Procedures

  • SetName(CurrentWkshBatchName: Code[10]; var ReqLine: Record "Requisition Line")
  • GetDescriptionAndRcptName(var ReqLine: Record "Requisition Line"; var ItemDescription: Text[100]; var RoutingDescription: Text[100])

Triggers

OnRun

Called by

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

Evidence 1 sources