Table extension 20509 "Subc. Purchase Header"
Subcontracting · Microsoft.Manufacturing.Subcontracting
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
Subcontracting · Microsoft.Manufacturing.Subcontracting · BC29-30 · source at ea08af5e · facts from BC29
Extends Purchase Header.
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 |
|---|---|---|---|---|
| 20520 | Subc. Location Code | Code[10] | Specifies the code for the location where the subcontracted items are stored for pickup and delivery. | TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(false))); DataClassification CustomerContent |
| 20521 | Subc. Order | Boolean | Specifies the subcontracting orders that have been created. | FlowField: exist(“Purchase Line” where(“Document Type” = const(Order), “Document No.” = field(“No.”), “Subc. Purchase Line Type” = filter(<> None))); not editable |
Relations
- Subc. Location Code: TableRelation Table 14 “Location”
- extends Table 38 “Purchase Header”
- Subc. Order: CalcFormula Table 39 “Purchase Line”
Recent changes
- 2026-08-18 #9892 [main] Bug 644283: Renumber Subcontracting app object ids as it clashes with partner range (main, BC30, refactor)
- 2026-07-27 #8757 [Subcontracting] Bug 640115: Fix Subc. Order FlowField so subcontracting orders are visible in Purchase Order List (main, BC30, fix)
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: "tableextension", object_name: "Subc. Purchase Header"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.