Page extension 904 "Asm. Item Card"
Base Application · Microsoft.Inventory.Item
Across versions
- BC23-25not present
- BC26added
- BC27-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Inventory.Item · BC26-30 · source at ea08af5e · facts from BC29
Extends Item Card.
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 |
|---|---|---|---|
| addafter(Qty. on Job Order) | Qty. on Assembly Order | Qty. on Assembly Order | Specifies how many units of the item are allocated to assembly orders, which is how many are listed on outstanding assembly order headers. |
| Qty. on Asm. Component | Qty. on Asm. Component | Specifies how many units of the item are allocated as assembly components, which means how many are listed on outstanding assembly order lines. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| addafter(Where-Used) | Calc. Assembly Std. Cost | Calculate the unit cost of the item by rolling up the unit cost of each component and resource in the item’s assembly BOM. The unit cost of a parent item must equal the total of the unit costs of its components, subassemblies, and any resources. | |
| Calc. Unit Price | Calculate the unit price based on the unit cost and the profit percentage. |
Relations
- extends Page 30 “Item Card”
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: "pageextension", object_name: "Asm. Item Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.