Table extension 20507 "Subc. Vendor"

Subcontracting · Microsoft.Manufacturing.Subcontracting · BC29-30 · source at ea08af5e · facts from BC29

Extends Vendor.

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
20515	Subc. Location Code	Code[10]	Specifies the subcontracting location where items from the vendor must be received by default after having performed an outside work. via Page extension 20516 “Subc. Vendor Card”	TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(false))); DataClassification CustomerContent
20516	Subc. Linked to Work Center	Boolean	Specifies if a work center is related to the vendor. via Page extension 20516 “Subc. Vendor Card”	FlowField: exist(“Work Center” where(“Subcontractor No.” = field(“No.”))); not editable
20517	Subc. Work Center No.	Code[20]	Work Center No. caption	TableRelation Table 99000754 “Work Center” (“Work Center” where(“Subcontractor No.” = field(“No.”))); DataClassification CustomerContent

Keys

SubcLocationCode: Subc. Location Code

Relations

Subc. Location Code: TableRelation Table 14 “Location”
extends Table 23 “Vendor”
Subc. Linked to Work Center: CalcFormula Table 99000754 “Work Center”
Subc. Work Center No.: TableRelation Table 99000754 “Work Center”

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: "tableextension", object_name: "Subc. Vendor"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.