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

Report 7313 "Whse. Shipment Status"

Base Application · Microsoft.Warehouse.Document

Open in Claude7313.mdSource on GitHub

Across versions

  1. BC23-28present
  2. BC29declaration changed
  3. BC30unchanged

Neighbourhood 5 connected objects and pages

Inventory analytics (Learn pages)Inventory analyticsInventory and Warehouse Reports and Analytics (Learn pages)Inventory and Warehouse Repo…Sales analytics (Learn pages)Sales analyticsSales report overview (Learn pages)Sales report overviewWarehouse Shipment Status (report) (Learn pages)Warehouse Shipment Status (r…

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.Document · captioned “Warehouse Shipment Status” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Warehouse Shipment Status
UsageCategory ReportsAndAnalysis
ApplicationArea Warehouse

Procedures

1 local procedures, no public ones.

Triggers

OnPreReport

Documented on Microsoft Learn

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). 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: "report", object_name: "Whse. Shipment Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 6 sources