Page extension 20511 "Subc. Planning Comp"
Subcontracting · Microsoft.Manufacturing.Subcontracting
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
Subcontracting · Microsoft.Manufacturing.Subcontracting · BC29-30 · source at ea08af5e · facts from BC29
Extends Planning Components.
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 |
|---|---|---|---|
| addlast(Control1) | Component Supply Method | Component Supply Method | Specifies how components are supplied to the subcontractor for the planning component. Vendor-supplied - components are provided by the subcontractor. Consignment at Vendor - components are owned by your company but stored at the subcontractor location. Transfer to Vendor - components are sent to th… from the table field |
Relations
Recent changes
- 2026-08-18 #9892 [main] Bug 644283: Renumber Subcontracting app object ids as it clashes with partner range (main, BC30, refactor)
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: "Subc. Planning Comp"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.