codeunitInventoryofficial - Microsoftderived - from the source, no model text

Codeunit 99000867 "Mfg. Order Planning Mgt."

Base Application · Microsoft.Inventory.Requisition

Across versions

  1. BC23-26not present
  2. BC27added
  3. BC28-30unchanged

Neighbourhood 3 connected objects and pages

Codeunit 5522 "Order Planning Mgt." (calls, 2 links)Order Planning Mgt.Codeunit 99000809 "Planning Line Management" (calls)Planning Line ManagementCodeunit 99000898 "Mfg. Item Substitution" (calls)Mfg. Item Substitution

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 · BC27-30 · source at ea08af5e · facts from BC29

Properties

Property Value
SingleInstance true

Events published

  • OnBeforeReqLineModify(var RequisitionLine: Record "Requisition Line"; RequisitionLine2: Record "Requisition Line"; ProdOrderComponent: Record Microsoft.Manufacturing.Document."Prod. Order Component") (integration)

Event subscriptions

  • OnInsertAltSupplyLocationOnAfterSelectSubstitution subscribes to Codeunit “Order Planning Mgt.” OnInsertAltSupplyLocationOnAfterSelectSubstitution
  • OnInsertAltSupplyLocationOnUpdateReqLine subscribes to Codeunit “Order Planning Mgt.” OnInsertAltSupplyLocationOnUpdateReqLine
  • OnSubstitutionPossibleOnAfterCheckReqLine subscribes to Codeunit “Order Planning Mgt.” OnSubstitutionPossibleOnAfterCheckReqLine

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

Evidence 1 sources