Table extension 99000751 "Mfg. Purchase Line"

Base Application · Microsoft.Purchases.Document · BC26-30 · source at ea08af5e · facts from BC29

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
5401	Prod. Order No.	Code[20]	Specifies the dependent Production Order of this Subcontracting Purchase Order. via Page 20518 “Subc. Purchase Line Factbox”	TableRelation Table 5405 “Production Order” (“Production Order”.“No.” where(Status = const(Released))); not editable; DataClassification CustomerContent
99000750	Routing No.	Code[20]	—	TableRelation Table 99000763 “Routing Header” (Routing Header); DataClassification CustomerContent
99000751	Operation No.	Code[10]	Specifies the number of the related production operation. via Page extension 99000765 “Mfg. Purchase Order Subform”	TableRelation Table 5409 “Prod. Order Routing Line” (“Prod. Order Routing Line”.“Operation No.” where(Status = const(Released), “Prod. Order No.” = field(“Prod. Order No.”), “Routing No.” = field(“Routing No.”))); not editable; DataClassification CustomerContent
99000752	Work Center No.	Code[20]	Specifies the work center number of the journal line. via Page extension 99000765 “Mfg. Purchase Order Subform”	TableRelation Table 99000754 “Work Center” (Work Center); not editable; DataClassification CustomerContent
99000753	Finished	Boolean	Specifies that any related service or operation is finished. via Page extension 99000765 “Mfg. Purchase Order Subform”	DataClassification CustomerContent
99000754	Prod. Order Line No.	Integer	Specifies the number of the related production order line. via Page extension 99000765 “Mfg. Purchase Order Subform”	TableRelation Table 5406 “Prod. Order Line” (“Prod. Order Line”.“Line No.” where(Status = filter(Released ..), “Prod. Order No.” = field(“Prod. Order No.”))); not editable; DataClassification CustomerContent
99000759	Routing Reference No.	Integer	—	DataClassification CustomerContent

Keys

Key8: Prod. Order No., Prod. Order Line No., Routing No., Operation No.

Events published

OnBeforeCheckDropShipment(var IsHandled: Boolean; var PurchaseLine: Record "Purchase Line") (integration)
OnBeforeValidateProdOrderOnPurchLine(var PurchLine: Record "Purchase Line"; var IsHandled: Boolean) + BC27 (integration)
OnAfterTransferFromReqLineToPurchLine(var PurchOrderLine: Record "Purchase Line"; var ReqLine: Record "Requisition Line") + BC27 (integration)
OnBeforeTransferFromReqLineToPurchLine(var PurchOrderLine: Record "Purchase Line"; var ReqLine: Record "Requisition Line"; var IsHandled: Boolean) + BC27 (integration)
OnTransferFromReqLineToPurchLineOnBeforeBeforeAssignOverheadRate(var WordCenter: Record Microsoft.Manufacturing.WorkCenter."Work Center"; var OrderDate: Date) + BC27 (integration)

Procedures

CheckDropShipment()
ValidateProdOrderOnPurchLine() + BC27
TransferFromReqLineToPurchLine(var PurchOrderLine: Record "Purchase Line"; ReqLine: Record "Requisition Line") + BC27

Relations

extends Table 39 “Purchase Line”
Prod. Order No.: TableRelation Table 5405 “Production Order”
Prod. Order Line No.: TableRelation Table 5406 “Prod. Order Line”
Operation No.: TableRelation Table 5409 “Prod. Order Routing Line”
Work Center No.: TableRelation Table 99000754 “Work Center”
Routing No.: TableRelation Table 99000763 “Routing Header”

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.

Codeunit 5836 “Cost Calculation Management” (1 call: TransferFromReqLineToPurchLine → GetRndgSetup)

Recent changes

2026-10-02 #12066 Bugs/remove asm inv mfg clean27 tags for wave2 2026 (main, BC30, obsoletion)
2026-08-16 #9067 Production Definition Wizard - Implementation (main, BC30, feature)

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