BC Observatoryunofficial, made by waldo
tableextensionInventoryofficial - Microsoftderived - from the source, no model text

Table extension 99000850 "Mfg. Planning Assignment"

Base Application · Microsoft.Inventory.Planning

Open in Claude99000850.mdSource on GitHub

Across versions

  1. BC23-25not present
  2. BC26added
  3. BC27-30unchanged

Neighbourhood 1 connected objects and pages

Table 99000850 "Planning Assignment" (relates to)Planning Assignment

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Inventory.Planning · BC26-30 · source at ea08af5e · facts from BC29

Extends Planning Assignment.

Events published

  • OnAfterRoutingReplace(var Item: Record Item; OldRoutingNo: Code[20]) (integration)
  • OnAfterBomReplace(var Item: Record Item; OldProductionBOMNo: Code[20]) (integration)
  • OnOldBomOnBeforeProcessProductionBOMLine(ProductionBOMNo: Code[20]; var EndLoop: Boolean) (integration)
  • OnAfterNewBOM(ProductionBOMNo: Code[20]) (integration)
  • OnAfterAssignPlannedOrders(ItemNo: Code[20]; CheckSKU: Boolean; var AssignThis: Boolean) (integration)

Procedures

  • RoutingReplace(var Item: Record Item; OldRoutingNo: Code[20])
  • BomReplace(var Item: Record Item; OldProductionBOMNo: Code[20])
  • OldBom(ProductionBOMNo: Code[20])
  • NewBOM(ProductionBOMNo: Code[20])
  • AssignPlannedOrders(ItemNo: Code[20]; CheckSKU: Boolean)

Relations

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: "Mfg. Planning Assignment"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources