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

Page 922 "Posted Assembly Orders"

Base Application · Microsoft.Assembly.History

Open in Claude922.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 13 connected objects and pages

Table 910 "Posted Assembly Header" (relates to)Posted Assembly HeaderPage 920 "Posted Assembly Order" (pages and codeunits on it)Posted Assembly OrderTable 910 "Posted Assembly Header" (pages and codeunits on it)Posted Assembly HeaderAssemble Items (Learn pages)Assemble ItemsAssembly Management (Learn pages)Assembly ManagementAssembly 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)Quote an Assemble-to-Order S…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)

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

Properties

Property Value
Caption Posted Assembly Orders
SourceTable Posted Assembly Header
PageType List
UsageCategory History
ApplicationArea Assembly

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
Control2 No. No. Specifies the number of the involved entry or record, according to the specified number series. from the table field
Order No. Order No. Specifies the number of the assembly order that the posted assembly order line originates from. from the table field
Description Description Specifies the description of the posted assembly item. from the table field
Posting Date Posting Date Specifies the date when the assembly order was posted. 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 on which the posted assembly order started. from the table field
Ending Date Ending Date Specifies the date when the posted assembly order finished, which means the date on which all assembly items were output. from the table field
Item No. Item No. Specifies the number of the posted assembly item. from the table field
Quantity Quantity Specifies how many units of the assembly item were posted with this posted 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

Actions

Group Action ToolTip Runs
Line Show Document Open the document that the information on the line comes from. Page 920 “Posted Assembly Order”
Statistics View statistical information, such as the value of posted entries, for the record. Page 923 “Posted Asm. Order Statistics”
Dimensions View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.
Comments View or add comments for the record. Page 907 “Assembly Comment Sheet”
Processing Print Prepare to print the document. A report request window for the document opens where you can specify what to include on the print-out.
Find entries… Find entries and documents that exist for the document number and posting date on the selected document. (Formerly this action was named Navigate.)

Relations

Pages and codeunits on this table

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

Evidence 8 of 11 sources

Show 3 more