Page 372 "Bank Account Ledger Entries"
Base Application · Microsoft.Bank.Ledger
Across versions
- BC23present
- BC24declaration changed
- BC25-26unchanged
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 11 connected objects and pages
Base Application · Microsoft.Bank.Ledger · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Bank Account Ledger Entries |
| SourceTable | Bank Account Ledger Entry |
| PageType | List |
| UsageCategory | History |
| ApplicationArea | Basic, Suite |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Control1 | Posting Date | Posting Date | Specifies the posting date for the entry. from the table field |
| Document Type | Document Type | Specifies the document type on the bank account entry. The document type will be Payment, Refund, or the field will be blank. from the table field | |
| Document No. | Document No. | Specifies the document number on the bank account entry. from the table field | |
| Bank Account No. | Bank Account No. | Specifies the number of the bank account used for the entry. from the table field | |
| Description | Description | Specifies the description of the bank account entry. from the table field | |
| Global Dimension 1 Code | Global Dimension 1 Code | Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field | |
| Global Dimension 2 Code | Global Dimension 2 Code | Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field | |
| Our Contact Code | Our Contact Code | Specifies the code for the employee who is responsible for the bank account. from the table field | |
| Currency Code | Currency Code | Specifies the currency that is used on the entry. from the table field | |
| Amount | Amount | Specifies the amount of the entry denominated in the applicable foreign currency. from the table field | |
| Debit Amount | Debit Amount | Specifies the total of the ledger entries that represent debits. from the table field | |
| Credit Amount | Credit Amount | Specifies the total of the ledger entries that represent credits. from the table field | |
| Running Balance | CalcRunningAccBalance.GetBankAccBalance(Rec) |
Specifies the running balance. | |
| Amount (LCY) | Amount (LCY) | Specifies the amount of the entry in LCY. | |
| Debit Amount (LCY) | Debit Amount (LCY) | Specifies the total of the ledger entries that represent debits, expressed in LCY. | |
| Credit Amount (LCY) | Credit Amount (LCY) | Specifies the total of the ledger entries that represent credits, expressed in LCY. | |
| Running Balance (LCY) | CalcRunningAccBalance.GetBankAccBalanceLCY(Rec) |
Specifies the running balance in LCY. | |
| Remaining Amount | Remaining Amount | Specifies the amount that remains to be applied to if the entry has not been completely applied to. | |
| Bal. Account Type | Bal. Account Type | Specifies the type of account that a balancing entry is posted to, such as BANK for a cash account. from the table field | |
| Bal. Account No. | Bal. Account No. | Specifies the number of the general ledger, customer, vendor, or bank account that the balancing entry is posted to, such as a cash account for cash purchases. from the table field | |
| Open | Open | Specifies whether the amount on the bank account entry has been fully applied to or if there is still a remaining amount that must be applied to. | |
| User ID | User ID | Specifies the ID of the user who posted the entry, to be used, for example, in the change log. from the table field | |
| Source Code | Source Code | Specifies the source code that specifies where the entry was created. from the table field | |
| Reason Code | Reason Code | Specifies the reason code, a supplementary source code that enables you to trace the entry. from the table field | |
| Reversed | Reversed | Specifies if the entry has been part of a reverse transaction. from the table field | |
| Reversed by Entry No. | Reversed by Entry No. | Specifies the number of the correcting entry that replaced the original entry in the reverse transaction. from the table field | |
| Reversed Entry No. | Reversed Entry No. | Specifies the number of the original entry that was undone by the reverse transaction. from the table field | |
| Entry No. | Entry No. | Specifies the number of the entry, as assigned from the specified number series when the entry was created. from the table field | |
| Dimension Set ID | Dimension Set ID | Specifies a reference to a combination of dimension values. The actual values are stored in the Dimension Set Entry table. from the table field | |
| Shortcut Dimension 3 Code | Shortcut Dimension 3 Code | Specifies the code for Shortcut Dimension 3, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field | |
| Shortcut Dimension 4 Code | Shortcut Dimension 4 Code | Specifies the code for Shortcut Dimension 4, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field | |
| Shortcut Dimension 5 Code | Shortcut Dimension 5 Code | Specifies the code for Shortcut Dimension 5, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field | |
| Shortcut Dimension 6 Code | Shortcut Dimension 6 Code | Specifies the code for Shortcut Dimension 6, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field | |
| Shortcut Dimension 7 Code | Shortcut Dimension 7 Code | Specifies the code for Shortcut Dimension 7, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field | |
| Shortcut Dimension 8 Code | Shortcut Dimension 8 Code | Specifies the code for Shortcut Dimension 8, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field | |
| FactBoxes | Related G/L Entries | part Page 19 “G/L Entries Part” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Entry | Check Ledger Entries | View check ledger entries that result from posting transactions in a payment journal for the relevant bank account. | Page 374 “Check Ledger Entries” |
| Dimensions | View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history. | ||
| Set Dimension Filter | Limit the entries according to the dimension filters that you specify. NOTE: If you use a high number of dimension combinations, this function may not work and can result in a message that the SQL server only supports a maximum of 2100 parameters. | ||
| Functions | Reverse Transaction | Undo an erroneous journal posting. | |
| Processing | Find entries… | Find entries and documents that exist for the document number and posting date on the selected document. (Formerly this action was named Navigate.) |
Procedures
1 local procedures, no public ones.
Triggers
OnOpenPage
Relations
- source table Table 271 “Bank Account Ledger Entry”
Pages and codeunits on this table
- Table 271 “Bank Account Ledger Entry” (drill-down page)
- Table 271 “Bank Account Ledger Entry” (lookup page)
Extended by
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 408 “DimensionManagement” (1 call:
SetDimVisibility → UseShortcutDims)
Called by
- Codeunit 14 “Gen. Jnl.-Show Entries” (1 call:
OnRun → (object)) - Codeunit 377 “G/L Reg.-Bank Account Ledger” (1 call:
OnRun → (object)) - Page 7251 “Bank Acc. Rec. AI Proposal Sub” (1 call:
OpenProposedRecord → (object)) - Table 1692 “Posted Bank Deposit Line” (1 call:
ShowAccountLedgerEntries → (object)) - Table 273 “Bank Acc. Reconciliation” (1 call:
DrillDownOnBalanceOnBankAccount → (object)) - Table 274 “Bank Acc. Reconciliation Line” (1 call:
DrillDownOnNoOfLedgerEntriesBasedOnAmount → (object))
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: "page", object_name: "Bank Account Ledger Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.