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

Codeunit 20453 "Qlty. Disp. Warehouse Put-away"

Quality Management · Microsoft.QualityManagement.Dispositions.PutAway

Open in Claude20453.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 2 connected objects and pages

Codeunit 20424 "Qlty. Workflow Response" (calls)Qlty. Workflow ResponsePage 20414 "Qlty. Inspections API" (calls)Qlty. Inspections API

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.

Quality Management · Microsoft.QualityManagement.Dispositions.PutAway · BC29-30 · source at ea08af5e · facts from BC29

Event subscriptions

  • HandleOnAfterPostReport subscribes to Report “Whse.-Source - Create Document” OnAfterPostReport

Procedures

  • PerformDisposition(QltyInspectionHeader: Record "Qlty. Inspection Header"; OptionalSpecificQuantity: Decimal; OptionalSourceLocationFilter: Text; OptionalSourceBinFilter: Text; QltyQuantityBehavior: Enum "Qlty. Quantity Behavior"): Boolean (internal): Create a warehouse put-away(s) from the supplied inspection. It’s possible that multiple put-away’s could be created if the lot is in multiple bins, but the typical scenario would be one internal put-away. You must be in a directed pick and put location, and you must be using lot warehouse tracking …
  • PerformDisposition(var QltyInspectionHeader: Record "Qlty. Inspection Header"; var TempInstructionQltyDispositionBuffer: Record "Qlty. Disposition Buffer" temporary): Boolean: Creates warehouse put-away documents through released internal put-away documents. It’s possible that multiple put-away’s could be created if the lot is in multiple bins, but the typical scenario would be one internal put-away. You must be in a directed pick and put location, and you must be using l…

Called by

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.

Implements

Recent changes

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: "codeunit", object_name: "Qlty. Disp. Warehouse Put-away"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources