Page 99000861 "Planning Component List"

Base Application · Microsoft.Inventory.Planning · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Planning Component List
SourceTable	Planning Component
PageType	List

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
Control1	Item No.	Item No.	Specifies the item number of the component. from the table field
	Variant Code	Variant Code	Specifies the variant of the item on the line. from the table field
	Due Date	Due Date	Specifies the date when this planning component must be finished. from the table field
	Description	Description	Specifies the description of the component. from the table field
	Description 2	Description 2	Specifies additional description text. from the table field
	Calculation Formula	Calculation Formula	Specifies how to calculate the Quantity field. from the table field
	Length	Length	Specifies the length of one item unit when measured in the specified unit of measure. from the table field
	Width	Width	Specifies the width of one item unit when measured in the specified unit of measure. from the table field
	Weight	Weight	Specifies the weight of one item unit when measured in the specified unit of measure. from the table field
	Depth	Depth	Specifies the depth of one item unit when measured in the specified unit of measure. from the table field
	Quantity per	Quantity per	Specifies how many units of the component are required to produce the parent item. from the table field
	Unit of Measure Code	Unit of Measure Code	Specifies how each unit of the item or resource is measured, such as in pieces or hours. By default, the value in the Base Unit of Measure field on the item or resource card is inserted. from the table field
	Expected Quantity	Expected Quantity	Specifies the expected quantity of this planning component line. from the table field
	Expected Quantity (Base)	Expected Quantity (Base)	Specifies the contents of the Expected Quantity field on the line, in base units of measure.
	Shortcut Dimension 1 Code	Shortcut Dimension 1 Code	Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 2 Code	Shortcut Dimension 2 Code	Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field
	Location Code	Location Code	Specifies the code for the inventory location, where the item on the planning component line will be registered. from the table field
	Unit Cost	Unit Cost	Specifies the cost of one unit of the item or resource on the line. from the table field
	Cost Amount	Cost Amount	Specifies the total cost for this planning component line. from the table field
	Position	Position	Specifies the position of the component on the bill of material. from the table field
	Position 2	Position 2	Specifies the second reference number for the component position, such as the alternate position number of a component on a circuit board. from the table field
	Position 3	Position 3	Specifies the third reference number for the component position on a bill of material, such as the alternate position number of a component on a print card. from the table field
	Lead-Time Offset	Lead-Time Offset	Specifies the lead-time offset for the planning component. from the table field

Actions

Group	Action	ToolTip	Runs
Line	Item Tracking Lines	View or edit serial, lot and package numbers that are assigned to the item on the document or journal line.

Relations

source table Table 99000829 “Planning Component”

Pages and codeunits on this table

Table 99000829 “Planning Component” (drill-down page)
Table 99000829 “Planning Component” (lookup page)

Extended by

Page extension 99000834 “Mfg. Planning Component List”

Documented on Microsoft Learn

Replan or refresh production orders directly

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