Report 5984 "Contract Invoicing"
Base Application · Microsoft.Service.Reports
Across versions
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Service.Reports · captioned “Contract Invoicing - Test” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Contract Invoicing - Test |
| DefaultLayout | RDLC |
Events published
OnAfterSetInvoiceDates(var ServiceContractHeader: Record "Service Contract Header"; var InvoiceFrom: Date; var InvoiceTo: Date)(integration)OnAfterServiceContractHeaderOnPreDataItem(var ServiceContractHeader: Record "Service Contract Header"; PostingDate: Date; InvoiceToDate: Date)(integration)
Procedures
InitVariables(LocalPostingDate: Date; LocalInvoiceToDate: Date)
Plus 4 local procedures.
Triggers
OnInitReport, OnPreReport
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 5940 “ServContractManagement” (2 calls:
BuildInvoicePlan → GetInvoicePeriodText,CalcContrAmt → CalcContractLineAmount)
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: "Contract Invoicing"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.