codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 763 "Aged Acc. Receivable"

Base Application · Microsoft.Finance.ReceivablesPayables

Across versions

  1. BC23-30present

Neighbourhood 7 connected objects and pages

Codeunit 764 "Aged Acc. Payable" (calls, 8 links)Aged Acc. PayableCodeunit 1315 "Chart Management" (calls, 4 links)Chart ManagementCodeunit 6306 "PBI Aged Acc. Calc" (calls, 3 links)PBI Aged Acc. CalcPage 768 "Aged Acc. Receivable Chart" (calls, 2 links)Aged Acc. Receivable ChartCodeunit 1630 "Office Management" (calls)Office ManagementCodeunit 32 "Customer Card Calculations" (calls)Customer Card CalculationsPage 25 "Customer Ledger Entries" (calls)Customer Ledger Entries

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Finance.ReceivablesPayables · BC23-30 · source at ea08af5e · facts from BC29

Procedures

  • UpdateDataPerCustomer(var BusChartBuf: Record "Business Chart Buffer"; CustomerNo: Code[20]; var TempEntryNoAmountBuf: Record "Entry No. Amount Buffer" temporary): Updates business chart buffer with aged receivable data for a specific customer. Generates aging analysis with default initialization settings.
  • UpdateDataPerCustomer(var BusChartBuf: Record "Business Chart Buffer"; CustomerNo: Code[20]; var TempEntryNoAmountBuf: Record "Entry No. Amount Buffer" temporary; AlreadyInitialized: Boolean): Updates business chart buffer with aged receivable data for a specific customer with initialization control. Configures chart structure and calculates aging buckets based on period settings.
  • UpdateDataPerGroup(var BusChartBuf: Record "Business Chart Buffer"; var TempEntryNoAmountBuf: Record "Entry No. Amount Buffer" temporary): Updates business chart buffer with aged receivable data grouped by customer posting groups. Creates stacked column chart showing aging distribution across posting groups.
  • DateFilterByAge(Index: Integer; var StartDate: Date; PeriodLength: Text[1]; NoOfPeriods: Integer; var EndDate: Date): Text: Generates date filter string for aging period based on index and period settings. Calculates appropriate date ranges for not due and overdue amounts.
  • InsertAmountBuffer(Index: Integer; BussUnitCode: Code[20]; AmountLCY: Decimal; StartDate: Date; EndDate: Date; var TempEntryNoAmountBuffer: Record "Entry No. Amount Buffer" temporary): Inserts calculated amount data into temporary buffer for aging period. Creates buffer entry with period information and calculated amounts.
  • InitParameters(BusChartBuf: Record "Business Chart Buffer"; var PeriodLength: Text[1]; var NoOfPeriods: Integer): Initializes aging parameters from business chart buffer settings. Extracts period length and number of periods for aging calculation.
  • InitParameters(BusChartBuf: Record "Business Chart Buffer"; var PeriodLength: Text[1]; var NoOfPeriods: Integer; var TempEntryNoAmountBuf: Record "Entry No. Amount Buffer" temporary): Initializes aging parameters and clears temporary buffer for fresh calculation. Prepares buffer and extracts period settings from chart configuration.
  • FormatColumnName(Index: Integer; PeriodLength: Text[1]; NoOfColumns: Integer; Period: Option): Text: Formats column name for aging chart based on period index and settings. Generates appropriate labels for aging buckets and periods.
  • DrillDown(var BusChartBuf: Record "Business Chart Buffer"; CustomerNo: Code[20]; var TempEntryNoAmountBuf: Record "Entry No. Amount Buffer" temporary): Handles drill-down navigation from aging chart to detailed customer ledger entries. Opens customer ledger entries filtered by aging period and customer.
  • DrillDownByGroup(var BusChartBuf: Record "Business Chart Buffer"; var TempEntryNoAmountBuf: Record "Entry No. Amount Buffer" temporary): Handles drill-down navigation from grouped aging chart to detailed entries. Opens customer ledger entries filtered by aging period and posting group.
  • DrillDownCustLedgEntries(CustomerNo: Code[20]; CustomerGroupCode: Code[20]; StartDate: Date; EndDate: Date): Opens customer ledger entries page with filters for aging period and customer/group. Provides detailed view of entries contributing to aging amounts.
  • Description(PerCustomer: Boolean): Text: Returns appropriate description text for aging chart based on analysis scope. Provides different descriptions for per-customer vs. summary analysis.
  • UpdateStatusText(BusChartBuf: Record "Business Chart Buffer"): Text: Generates status text for aging chart based on period settings and analysis type. Creates descriptive status showing period length and aging configuration.
  • SaveSettings(BusChartBuf: Record "Business Chart Buffer"): Saves user-specific chart settings for aging analysis preferences. Persists period length and chart configuration to user setup.
  • InvoicePaymentDaysAverage(CustomerNo: Code[20]): Decimal: Calculates average payment days for customer invoices for performance analysis. Provides rounded average days between invoice and payment dates.
  • RoundAmount(Amount: Decimal): Decimal: Rounds amount to the precision defined in General Ledger Setup.
  • OverDueText(): Text: Returns the localized text for overdue amounts in aged analysis reports.
  • AmountText(): Text: Returns the localized text for amount labels in aged analysis reports.

Plus 6 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.

Called by

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: "Aged Acc. Receivable"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources