Table extension 99000829 "Mfg. Planning Component"
Base Application · Microsoft.Inventory.Planning
Across versions
- BC23-25not present
- BC26added
- BC271 fields removed, 1 procedures removed
- BC281 fields changed
- BC29-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Inventory.Planning · BC26-30 · source at ea08af5e · facts from BC29
Extends Planning Component.
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 |
|---|---|---|---|---|
| 19 | Routing Link Code | Code[10] | Specifies a routing link code to link a planning component with a specific operation. via Page extension 99000834 “Mfg. Planning Component List” | TableRelation Table 99000777 “Routing Link” (Routing Link); DataClassification CustomerContent |
| 20 | Scrap % Δ BC28 | Decimal | Specifies the percentage of the item that you expect to be scrapped in the production process. via Page extension 99000834 “Mfg. Planning Component List” | DataClassification CustomerContent |
Events published
OnAfterPlanningNeeds(PlanningComponent: Record "Planning Component"; RequisitionLine: Record "Requisition Line"; PlanningRoutingLine: Record "Planning Routing Line"; var NeededQty: Decimal)(integration)OnAfterTransferFromComponent(var PlanningComponent: Record "Planning Component"; var ProdOrderComp: Record "Prod. Order Component")(integration)OnValidateRoutingLinkCodeOnBeforeValidateDueDate(var PlanningComponent: Record "Planning Component"; RequisitionLine: Record "Requisition Line"; var PlanningRoutingLine: Record "Planning Routing Line")(integration)OnBeforeGetRefOrderTypeBin(PlanningComponent: Record "Planning Component"; RequisitionLine: Record "Requisition Line"; Location: Record Location; var BinCode: Code[20]; var IsHandled: Boolean)(integration)OnGetRefOrderTypeBinOnAfterGetBinCodeFromRoutingLine(var PlanningComponent: Record "Planning Component"; var PlanningRoutingLine: Record "Planning Routing Line"; var RequisitionLine: Record "Requisition Line"; var BinCode: Code[20])(integration)OnBeforePlanningNeeds(var PlanningComponent: Record "Planning Component"; var NeededQty: Decimal; var IsHandled: Boolean)(integration)OnBeforeUpdateExpectedQuantityForPlanningNeeds(var PlanningComponent: Record "Planning Component"; var IsHandled: Boolean)(integration)
Procedures
PlanningNeeds(): DecimalTransferFromComponent(var ProdOrderComp: Record "Prod. Order Component")GetRefOrderTypeBin(): Code[20]UpdateExpectedQuantityForPlanningNeeds()
Plus 2 local procedures.
Relations
- Routing Link Code: TableRelation Table 99000777 “Routing Link”
- extends Table 99000829 “Planning Component”
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 5996 “Prod. Order Warehouse Mgt.” (1 call:
GetRefOrderTypeBin → GetProdCenterBinCode)
Countries that replace it
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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. Planning Component"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.