Page 30226 "APIV2 - P. Assembly Orders"
APIV2 · Microsoft.API.V2
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
APIV2 · Microsoft.API.V2 · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | Posted Assembly Header |
| PageType | API |
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 |
|---|---|---|---|
| Group | Id | Rec.SystemId |
— |
| 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 | |
| Item No. | Item No. | Specifies the number of the posted assembly item. from the table field | |
| Description | Description | Specifies the description of the posted assembly item. from the table field | |
| Description 2 | Description 2 | — | |
| Variant Code | Variant Code | Specifies the variant of the item on the line. from the table field | |
| Location Code | Location Code | Specifies to which location the assembly item was output from this posted assembly order header. from the table field | |
| Bin Code | Bin Code | Specifies to which bin the assembly item was posted as output on the posted assembly order header. 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 | |
| Quantity | Quantity | Specifies how many units of the assembly item were posted with this posted assembly order. 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 | |
| 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 unit cost of the posted assembly order. from the table field | |
| Reversed | Reversed | Specifies if the posted assembly order has been undone. from the table field | |
| Shortcut Dimension 1 Code | Shortcut Dimension 1 Code | — | |
| Shortcut Dimension 2 Code | Shortcut Dimension 2 Code | — | |
| Last Modified Date Time | Rec.SystemModifiedAt |
— | |
| Dimension Set Lines | part Page 30022 “APIV2 - Dimension Set Lines” | — | |
| Lines | part Page 30227 “APIV2 - P. Asm. Order Lines” | — | |
| PDF Document | part Page 30056 “APIV2 - PDF Document” | — | |
| Attachments | part Page 30039 “APIV2 - Attachments” | — | |
| Document Attachments | part Page 30080 “APIV2 - Document Attachments” | — |
Relations
- source table Table 910 “Posted Assembly Header”
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: "APIV2 - P. Assembly Orders"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.