pageInventoryofficial - Microsoftderived - from the source, no model text

Page 9091 "Item Planning FactBox"

Base Application · Microsoft.Inventory.Item

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Table 27 "Item" (relates to)ItemPage 30 "Item Card" (calls)Item CardCreate item cards for goods or services (Learn pages)Create item cards for goods …Manage product variants (Learn pages)Manage product variants

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.Item · captioned “Item Details - Planning” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Item Details - Planning
SourceTable Item
PageType CardPart

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
Content Item No. No. Specifies the number of the item. from the table field
Reordering Policy Reordering Policy Specifies the reordering policy that is used to calculate the lot size per planning period (time bucket). from the table field
Reorder Point Reorder Point Specifies a stock quantity that sets the inventory below the level that you must replenish the item. from the table field
Reorder Quantity Reorder Quantity Specifies a standard lot size quantity to be used for all order proposals. from the table field
Maximum Inventory Maximum Inventory Specifies a quantity that you want to use as a maximum inventory level. from the table field
Overflow Level Overflow Level Specifies a quantity you allow projected inventory to exceed the reorder point, before the system suggests to decrease supply orders. from the table field
Time Bucket Time Bucket Specifies a time period that defines the recurring planning horizon used with Fixed Reorder Qty. or Maximum Qty. reordering policies. from the table field
Lot Accumulation Period Lot Accumulation Period Specifies a period in which multiple demands are accumulated into one supply order when you use the Lot-for-Lot reordering policy. from the table field
Rescheduling Period Rescheduling Period Specifies a period within which any suggestion to change a supply date always consists of a Reschedule action and never a Cancel + New action. from the table field
Safety Lead Time Safety Lead Time Specifies a date formula to indicate a safety lead time that can be used as a buffer period for production and other delays. from the table field
Safety Stock Quantity Safety Stock Quantity Specifies a quantity of stock to have in inventory to protect against supply-and-demand fluctuations during replenishment lead time. from the table field
Minimum Order Quantity Minimum Order Quantity Specifies a minimum allowable quantity for an item order proposal. from the table field
Maximum Order Quantity Maximum Order Quantity Specifies a maximum allowable quantity for an item order proposal. from the table field
Order Multiple Order Multiple Specifies a parameter used by the planning system to round the quantity of planned supply orders to a multiple of this value. from the table field
Dampener Period Dampener Period Specifies a period of time during which you do not want the planning system to propose to reschedule existing supply orders. from the table field
Dampener Quantity Dampener Quantity Specifies a dampener quantity to block insignificant change suggestions for an existing supply, if the change quantity is lower than the dampener quantity. from the table field

Procedures

1 local procedures, no public ones.

Relations

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.

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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: "page", object_name: "Item Planning FactBox"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 3 sources