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

Page extension 99000836 "Mfg. Planning Components"

Base Application · Microsoft.Inventory.Planning

Open in Claude99000836.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Page 99000862 "Planning Components" (relates to)Planning Components

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

Extends Planning Components.

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
addafter(Description) Scrap % Scrap % Specifies the percentage of the item that you expect to be scrapped in the production process.
addafter(Shortcut Dimension 2 Code) Routing Link Code Routing Link Code Specifies a routing link code to link a planning component with a specific operation.

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "pageextension", object_name: "Mfg. Planning Components"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources