Table 914 "Posted Assemble-to-Order Link"
Base Application · Microsoft.Assembly.History
Across versions
- BC23present
- BC242 fields added, 1 fields changed
- BC25-26unchanged
- BC272 fields changed
- BC28-30unchanged
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Assembly.History · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Posted Assemble-to-Order Link |
| DataClassification | CustomerContent |
| Permissions | TableData “Posted Assembly Header” = d, TableData “Posted Assemble-to-Order Link” = d |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Assembly Document Type | Option | — | OptionCaption: ,Assembly |
| 2 | Assembly Document No. | Code[20] | — | TableRelation Table 910 “Posted Assembly Header” (if (“Assembly Document Type” = const(Assembly)) “Posted Assembly Header” where(“No.” = field(“Assembly Document No.”))) |
| 12 | Document Type Δ BC24 | enum “Posted Assembly Link Type” | — | enum Enum 914 “Posted Assembly Link Type” |
| 13 | Document No. | Code[20] | — | TableRelation Table 111 “Sales Shipment Line” (if (“Document Type” = const(“Sales Shipment”)) “Sales Shipment Line” where(“Document No.” = field(“Document No.”), “Line No.” = field(“Document Line No.”))) |
| 14 | Document Line No. | Integer | — | |
| 20 | Assembled Quantity Δ BC27 | Decimal | — | |
| 21 | Assembled Quantity (Base) Δ BC27 | Decimal | — | |
| 32 | Assembly Order No. | Code[20] | — | |
| 33 | Order No. | Code[20] | — | |
| 34 | Order Line No. | Integer | — | |
| 40 | Job No. + BC24 | Code[20] | Project No. caption | TableRelation Table 167 “Job” |
| 41 | Job Task No. + BC24 | Code[20] | Project Task No. caption | TableRelation Table 1001 “Job Task” (“Job Task”.“Job Task No.” where(“Job No.” = field(“Job No.”))) |
Keys
- Key1: Assembly Document Type, Assembly Document No. (clustered)
- Key2: Document Type, Document No., Document Line No.
- Key3: Order No., Order Line No.
- Key4: Job No., Job Task No., Document Line No.
Events published
OnBeforeShowSalesShpt(var PostedAssembletoOrderLink: Record "Posted Assemble-to-Order Link"; PostedAsmHeader: Record "Posted Assembly Header"; var IsHandled: Boolean)(integration)
Procedures
AsmExistsForPostedShipmentLine(SalesShipmentLine: Record "Sales Shipment Line"): BooleanDeleteAsmFromSalesShptLine(SalesShptLine: Record "Sales Shipment Line")ShowPostedAsm(SalesShptLine: Record "Sales Shipment Line")ShowSalesShpt(PostedAsmHeader: Record "Posted Assembly Header")FindLinksFromSalesLine(SalesLine: Record "Sales Line"): Boolean
Plus 1 local procedures.
Relations
- Job Task No.: TableRelation Table 1001 “Job Task”
- Document No.: TableRelation Table 111 “Sales Shipment Line”
- Job No.: TableRelation Table 167 “Job”
- Assembly Document No.: TableRelation Table 910 “Posted Assembly Header”
Referenced by
1 fields in 1 objects relate to this table (TableRelation or CalcFormula).
- Table 910 “Posted Assembly Header”: Assemble to Order
Calls
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.
- Page 130 “Posted Sales Shipment” (1 call:
ShowSalesShpt → (object)) - Page 920 “Posted Assembly Order” (1 call:
ShowPostedAsm → (object))
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: "table", object_name: "Posted Assemble-to-Order Link"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.