reportPurchasing & Payablesofficial - Microsoftderived - from the source, no model textobsolete - pending
Report 319 "Payments on Hold"
Base Application · Microsoft.Purchases.Reports
Across versionsobsolete pending since 28.0
- BC23-27present
- BC28declaration changed
- BC29declaration changed
- BC30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Purchases.Reports · captioned “Payments on Hold (Obsolete)” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Payments on Hold (Obsolete) |
| UsageCategory | ReportsAndAnalysis |
| ApplicationArea | Basic, Suite |
| ObsoleteState | Pending |
| ObsoleteTag | 28.0 |
| ObsoleteReason | This report is obsolete and will be removed in a future release. See the documentation for alternative options. |
Triggers
OnPreReport
Countries that replace it
Documented on Microsoft Learn
- Handle vendor payment disputes
- Accounts payables analytics
- Analytics in purchasing
- Payments on Hold (report)
Deprecations
- object: Pending 28.0 (#if not CLEAN28), “This report is obsolete and will be removed in a future release. See the documentation for alternative options.”
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: "Payments on Hold"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.