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

Codeunit 7388 "Scan Warehouse Activity Line"

Base Application · Microsoft.Warehouse.Activity

Open in Claude7388.mdSource on GitHub

Across versions

  1. BC23not present
  2. BC24added
  3. BC253 procedures added
  4. BC26-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 6500 "Item Tracking Management" (calls)Item Tracking Management

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.Warehouse.Activity · BC24-30 · source at ea08af5e · facts from BC29

Procedures

  • CheckAndSetBarcode(var WarehouseActivityLine: Record "Warehouse Activity Line"; Barcode: Text; var NeedsRefresh: Boolean; var AllLinesAreDone: Boolean) + BC25 (internal)
  • ValidateBarcode(var WarehouseActivityLine: Record "Warehouse Activity Line"; Barcode: Text): Boolean (internal)
  • UnfullfilledLineExists(var WarehouseActivityLine: Record "Warehouse Activity Line"): Boolean + BC25 (internal)

Plus 6 local procedures.

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.

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: "Scan Warehouse Activity Line"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources