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

Page 904 "Assembly List"

Base Application · Microsoft.Assembly.Document

Open in Claude904.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 14 connected objects and pages

Table 900 "Assembly Header" (relates to)Assembly HeaderTable 900 "Assembly Header" (pages and codeunits on it, 2 links)Assembly HeaderCodeunit 925 "Assembly Header-Reserve" (calls)Assembly Header-ReserveReport 901 "Copy Assembly Document" (calls)Copy Assembly DocumentAssemble Items (Learn pages)Assemble ItemsAssembly Management (Learn pages)Assembly Reports and Analytics in Business Central (Learn pages)Assembly Reports and Analyti…Create Blanket Assembly Orders (Learn pages)Create Blanket Assembly OrdersQuote an Assemble-to-Order Sale (Learn pages)Sell Assemble-to-Order Items and Inventory Items Together (Learn pages)Sell Assemble-to-Order Items…Sell Inventory Items in Assemble-to-Order Flows (Learn pages)Sell Inventory Items in Asse…Sell Items Assembled to Order (Learn pages)Sell Items Assembled to OrderUnderstanding Assemble to Order and Assemble to Stock (Learn pages)Understanding Assemble to Or…Undo Assembly Posting (Learn pages)Undo Assembly Posting

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 Assembly List
SourceTable Assembly Header
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 Document Type Document Type Specifies the type of assembly document the record represents in assemble-to-order scenarios. from the table field
No. No. Specifies the number of the involved entry or record, according to the specified number series. from the table field
Description Description Specifies the description of the assembly item. from the table field
Description 2 Description 2 Specifies information in addition to the description. from the table field
Due Date Due Date Specifies the date when the assembled item is due to be available for use. from the table field
Starting Date Starting Date Specifies the date when the assembly order is expected to start. from the table field
Ending Date Ending Date Specifies the date when the assembly order is expected to finish. from the table field
Item No. Item No. Specifies the number of the item that is being assembled with the assembly order. from the table field
Quantity Quantity Specifies how many units of the assembly item that you expect to assemble with the assembly order. 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
Location Code Location Code Specifies the location to which you want to post output of the assembly item. from the table field
Variant Code Variant Code Specifies the variant of the item on the line. from the table field
Bin Code Bin Code Specifies the bin the assembly item is posted to as output and from where it is taken to storage or shipped if it is assembled to a sales order. from the table field
Remaining Quantity Remaining Quantity Specifies how many units of the assembly item remain to be posted as assembled output. from the table field

Actions

Group Action ToolTip Runs
Navigation Show Document Open the document that the information on the line comes from.
Reservation Entries View all reservations that are made for the item, either manually or automatically.
Item Tracking Lines View or edit serial, lot and package numbers that are assigned to the item on the document or journal line.

Relations

Pages and codeunits on this table

Called by

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

Evidence 8 of 11 sources

Show 3 more