Table 379 "Detailed Cust. Ledg. Entry"

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

Learn documents this table through its pages: Page 623 “Unapply Customer Entries” (1 Learn page).

Properties

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

Keys

• Key1: Entry No. (clustered)
• Key2: Customer No., Currency Code, Excluded from calculation
• Key3: Cust. Ledger Entry No., Entry Type, Posting Date
• Key5: Initial Document Type, Entry Type, Customer No., Currency Code, Initial Entry Global Dim. 1, Initial Entry Global Dim. 2, Posting Date
• Key6: Customer No., Currency Code, Initial Entry Global Dim. 1, Initial Entry Global Dim. 2, Initial Entry Due Date, Posting Date, Excluded from calculation
• Key7: Document No., Document Type, Posting Date
• Key8: Applied Cust. Ledger Entry No., Entry Type
• Key9: Transaction No., Customer No., Entry Type
• Key10: Application No., Customer No., Entry Type
• Key11: Customer No., Entry Type, Posting Date, Initial Document Type
• Key12: Document Type
• Key13: Initial Document Type, Initial Entry Due Date
• Key14: Customer No., Initial Entry Due Date

Events published

• OnBeforeSetLedgerEntryAmount(var DetailedCustLedgEntry: Record "Detailed Cust. Ledg. Entry"; var IsHandled: Boolean) (integration): Raised before setting the Ledger Entry Amount flag to allow custom logic.
• OnAfterUpdateDebitCredit(var DetailedCustLedgEntry: Record "Detailed Cust. Ledg. Entry"; Correction: Boolean) (integration): Raised after updating the debit and credit amounts on the entry.
• OnSetZeroTransNoOnBeforeDetailedCustLedgEntryModify(var DetailedCustLedgEntry: Record "Detailed Cust. Ledg. Entry") (integration): Raised before modifying the detailed customer ledger entry when setting transaction number to zero.

Trigger event subscribers

• OnAfterInsertEvent: Codeunit 20 “Posting Preview Event Handler” OnInsertDetailedCustLedgEntry
• OnAfterModifyEvent: Codeunit 20 “Posting Preview Event Handler” OnModifyDetailedCustLedgerEntry

Procedures

• GetLastEntryNo(): Integer Δ BC26: Gets the entry number of the last detailed customer ledger entry in the table.
• UpdateDebitCredit(Correction: Boolean): Updates the debit and credit amounts based on the sign of the amount and correction flag.
• SetZeroTransNo(TransactionNo: Integer): Sets the transaction number to zero and assigns an application number for all entries with the specified transaction number.
• GetUnrealizedGainLossAmount(EntryNo: Integer): Decimal: Calculates the sum of unrealized gain and loss amounts for a customer ledger entry.

Plus 1 local procedures.

Triggers

OnInsert

Relations

• drill-down page Page 573 “Detailed Cust. Ledg. Entries”
• lookup page Page 573 “Detailed Cust. Ledg. Entries”
• Customer No.: TableRelation Table 18 “Customer”
• Cust. Ledger Entry No.: TableRelation Table 21 “Cust. Ledger Entry”
• Source Code: TableRelation Table 230 “Source Code”
• Reason Code: TableRelation Table 231 “Reason Code”
• Gen. Bus. Posting Group: TableRelation Table 250 “Gen. Business Posting Group”
• Gen. Prod. Posting Group: TableRelation Table 251 “Gen. Product Posting Group”
• Tax Jurisdiction Code: TableRelation Table 320 “Tax Jurisdiction”
• VAT Bus. Posting Group: TableRelation Table 323 “VAT Business Posting Group”
• VAT Prod. Posting Group: TableRelation Table 324 “VAT Product Posting Group”
• Initial Entry Global Dim. 1: TableRelation Table 349 “Dimension Value”
• Initial Entry Global Dim. 2: TableRelation Table 349 “Dimension Value”
• Unapplied by Entry No.: TableRelation Table 379 “Detailed Cust. Ledg. Entry”
• Currency Code: TableRelation Table 4 “Currency”
• G/L Register No.: TableRelation Table 45 “G/L Register”
• Transaction No.: TableRelation Table 57 “G/L Transaction”
• Exch. Rate Adjmt. Reg. No.: TableRelation Table 86 “Exch. Rate Adjmt. Reg.”
• Posting Group: TableRelation Table 92 “Customer Posting Group”

Referenced by

50 fields in 11 objects relate to this table (TableRelation or CalcFormula).

• Table 18 “Customer”: Balance, Balance (LCY), Balance Due, Balance Due (LCY), Cr. Memo Amounts, Cr. Memo Amounts (LCY), Credit Amount, Credit Amount (LCY), Debit Amount, Debit Amount (LCY), Fin. Charge Memo Amounts (LCY), Finance Charge Memo Amounts, Inv. Amounts (LCY), Invoice Amounts, Net Change, Net Change (LCY), Other Amounts, Other Amounts (LCY), Payments, Payments (LCY), Pmt. Disc. Tolerance (LCY), Pmt. Discounts (LCY), Pmt. Tolerance (LCY), Refunds, Refunds (LCY), Reminder Amounts, Reminder Amounts (LCY)
• Table 21 “Cust. Ledger Entry”: Amount, Amount (LCY), Credit Amount, Credit Amount (LCY), Debit Amount, Debit Amount (LCY), Original Amount, Original Amt. (LCY), Remaining Amount, Remaining Amt. (LCY)
• Table 4 “Currency”: Customer Balance, Customer Balance (LCY), Customer Balance Due
• Table 1208 “Direct Debit Collection Entry”: Applies-to Entry Amount, Applies-to Entry Rem. Amount
• Table 9054 “Finance Cue”: Total Outstanding (LCY), Total Overdue (LCY)
• Table 112 “Sales Invoice Header”: Remaining Amount
• Table 114 “Sales Cr.Memo Header”: Remaining Amount
• Table 379 “Detailed Cust. Ledg. Entry”: Unapplied by Entry No.
• Table 86 “Exch. Rate Adjmt. Reg.”: Adjusted Customers
• Table 9150 “My Customer”: Balance (LCY)
• Table 98 “General Ledger Setup”: Cust. Balances Due

Pages and codeunits on this table

• Page 127 “Det. Cust. Ledg. Entr. Preview” (source table)
• Page 573 “Detailed Cust. Ledg. Entries” (source table)
• Page 623 “Unapply Customer Entries” (source table)

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 703 “Find Record Management” (1 call: GetLastEntryNo → GetLastEntryIntFieldValue)

Recent changes

• 2026-07-20 #9089 Merge-ES-Excluded-from-Calculation-to-W1 (main, BC30, feature)

Countries that replace it

AU, ES, FR, IT, NZ, RU

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: "table", object_name: "Detailed Cust. Ledg. Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.