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

Codeunit 99000887 "Planning Comp. Avail. Mgt."

Base Application · Microsoft.Inventory.Planning

Open in Claude99000887.mdSource on GitHub

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 353 "Item Availability Forms Mgt" (calls, 8 links)Item Availability Forms Mgt

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

Events published

  • OnBeforeShowItemAvailFromPlanningComp(var Item: Record Item; var PlanningComp: Record "Planning Component") (integration)

Event subscriptions

  • OnAfterMakeEntries subscribes to Page “Item Availability Line List” OnAfterMakeEntries
  • OnAfterLookupEntries subscribes to Page “Item Availability Line List” OnAfterLookupEntries

Procedures

  • ShowItemAvailabilityFromPlanningComp(var PlanningComp: Record "Planning Component"; AvailabilityType: Enum "Item Availability Type")

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.

  • Codeunit 353 “Item Availability Forms Mgt” (8 calls: ShowItemAvailabilityFromPlanningComp → FilterItem, ShowItemAvailabilityFromPlanningComp → SetForecastName, ShowItemAvailabilityFromPlanningComp → ShowItemAvailabilityByBOMLevel, …)

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

Evidence 1 sources