pageAssemblyofficial - Microsoftderived - from the source, no model text

Page 911 "Component - Item Details"

Base Application · Microsoft.Assembly.Document

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 27 "Item" (relates to)ItemCreate production BOMs (Learn pages)Create production BOMs

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.Assembly.Document · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Component - Item Details
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.
Base Unit of Measure Base Unit of Measure Specifies the base unit used to measure the item, such as piece, box, or pallet. The base unit of measure also serves as the conversion basis for alternate units of measure.
Unit Price Unit Price Specifies the price of one unit of the item or resource. You can enter a price manually or have it entered according to the Price/Profit Calculation field on the related card.
Unit Cost Unit Cost Specifies the cost of one unit of the item or resource on the line.
Standard Cost Standard Cost Specifies the unit cost that is used as an estimation to be adjusted with variances later. It is typically used in assembly and production where costs can vary.
No. of Substitutes No. of Substitutes Specifies the number of substitutions that have been registered for the item.
Replenishment System Replenishment System Specifies the type of supply order created by the planning system when the item needs to be replenished.
Vendor No. Vendor No. Specifies the vendor code of who supplies this item by default.

Relations

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

Evidence 2 sources