codeunitPurchasing & Payablesofficial - Microsoftderived - from the source, no model textobsolete - pending
Codeunit 4031 "SetupRemittanceReports"
UKSendRemittanceAdvice · Microsoft.Purchases.Vendor.RemittanceAdvice
Across versionsobsolete pending since 29.0
- BC23-28not present
- BC29-30present
UKSendRemittanceAdvice · Microsoft.Purchases.Vendor.RemittanceAdvice · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Subtype | Install |
| ObsoleteState | Pending |
| ObsoleteTag | 29.0 |
| ObsoleteReason | Report selection setup for V.Remittance and P.V.Remit. is now seeded by Microsoft.Foundation.Reporting.“Report Selection Mgt.”.InitReportSelectionPurch, called from CompanyInitialize. |
Procedures
2 local procedures, no public ones.
Triggers
OnInstallAppPerCompany
Recent changes
- 2026-08-11 #9578 [E-Documents Core] - Enabling remittance advice export via E-Documents (payment journal + posted payments) (main, BC30, feature)
Deprecations
- object: Pending 29.0 (#if not CLEAN29), “Report selection setup for V.Remittance and P.V.Remit. is now seeded by Microsoft.Foundation.Reporting.“Report Selection Mgt.”.InitReportSelectionPurch, called from CompanyInitialize.”
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: "codeunit", object_name: "SetupRemittanceReports"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.