reportSales & Receivablesofficial - Microsoftderived - from the source, no model text

Report 113 "Customer/Item Sales"

Base Application · Microsoft.Sales.Reports

Across versions

  1. BC23-26present
  2. BC272 procedures added
  3. BC281 procedures removed
  4. BC29declaration changed
  5. BC30unchanged

Neighbourhood 4 connected objects and pages

Codeunit 368 "Format Document" (calls)Format DocumentCustomer/Item Sales (report) (Learn pages)Customer/Item Sales (report)Sales analytics (Learn pages)Sales analyticsSales report overview (Learn pages)Sales report overview

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.Sales.Reports · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Customer/Item Sales
UsageCategory ReportsAndAnalysis
ApplicationArea Basic, Suite

Events published

  • OnAfterGetValueEntryOnBeforeTempValueEntryBufferInsertModify(ValueEntry: Record "Value Entry"; var TempValueEntry: Record "Value Entry" temporary) (integration)

Procedures

  • CalculateProfitPercent(Amount: Decimal; ProfitAmt: Decimal): Decimal + BC27: Calculates the profit percentage based on amount and profit.

Plus 1 local procedures.

Triggers

OnPreReport, OnPostReport

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.

Recent changes

Countries that replace it

AU, NZ

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). 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: "report", object_name: "Customer/Item Sales"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 4 sources