Report 400 "Remittance Advice - Entries"
Base Application · Microsoft.Purchases.Reports
Across versions
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Purchases.Reports · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Remittance Advice - Entries |
Procedures
CurrencyCode(SrcCurrCode: Code[10]): Code[10]
Plus 2 local procedures.
Triggers
OnPreReport
Extended by
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.
- Codeunit 365 “Format Address” (1 call:
OnPreReport → Company)
Recent changes
- 2026-09-21 #11567 [29.x]Report 400 (Remittance Advice) Does Not Include Applied Vendor Refund Entries Resulting in Incorrect Total Calculation (releases/29.x, BC29, fix)
- 2026-09-21 #11336 [master] Report 400 (Remittance Advice) Does Not Include Applied Vendor Refund Entries Resulting in Incorrect Total Calculation (main, BC30, fix)
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: "Remittance Advice - Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.