Codeunit 8810 "Customer Layout - Statement"

Base Application · Microsoft.Sales.Customer · BC23-30 · source at ea08af5e · facts from BC29

Procedures

• RunReport() Δ BC25: Runs the customer statement report with the standard request page for user input.
• RunReportWithParameters(Parameters: Text) Δ BC25: Runs the customer statement report with predefined request parameters.
• RunReportWithoutRequestPage() Δ BC25: Runs the customer statement report without displaying the request page.
• EnqueueReport() Δ BC25: Schedules the customer statement report to run via the job queue with user-specified parameters.
• CheckReportRunningInBackground() Δ BC25: Checks if the customer statement report is already scheduled in the job queue and raises an error if so.

Plus 1 local procedures.

Triggers

OnRun

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 8800 “Custom Layout Reporting” (9 calls: EnqueueReport → RunRequestPage, RunReport → ProcessReportData, RunReport → SetOutputFileBaseName, …)

Called by

• Codeunit 8800 “Custom Layout Reporting” (1 call: CheckForCustomLayoutReportingJob → CheckReportRunningInBackground)
• Codeunit 8811 “Customer Statement via Queue” (1 call: OnRun → RunReportWithParameters)
• Report 153 “Customer Statement” (1 call: OnInitReport → RunReport)

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: "codeunit", object_name: "Customer Layout - Statement"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.