Page 5237 "Employee Ledger Entries"
Base Application · Microsoft.HumanResources.Payables
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.HumanResources.Payables · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Employee Ledger Entries |
| SourceTable | Employee Ledger Entry |
| PageType | List |
| UsageCategory | History |
| ApplicationArea | BasicHR |
| Permissions | TableData “Employee Ledger Entry” = m |
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 |
|---|---|---|---|
| Group | Posting Date | Posting Date | Specifies the employee entry’s posting date. from the table field |
| Document Type | Document Type | Specifies the document type that the employee entry belongs to. from the table field | |
| Document No. | Document No. | Specifies the employee entry’s document number. from the table field | |
| Employee No. | Employee No. | Specifies the number of the employee that the entry is linked to. from the table field | |
| Message to Recipient | Message to Recipient | Specifies the message exported to the payment file when you use the Export Payments to File function in the Payment Journal window. from the table field | |
| Description | Description | Specifies a description of the employee entry. from the table field | |
| Currency Code | Currency Code | Specifies the currency code for the amount on the line. from the table field | |
| Payment Method Code | Payment Method Code | Specifies the payment method that was used to make the payment that resulted in the entry. from the table field | |
| Original Amount | Original Amount | Specifies the amount of the original entry. from the table field | |
| Original Amt. (LCY) | Original Amt. (LCY) | Specifies the amount that the entry originally consisted of, in LCY. | |
| Amount | Amount | Specifies the amount of the entry. from the table field | |
| Amount (LCY) | Amount (LCY) | Specifies the amount of the entry in LCY. | |
| Remaining Amount | Remaining Amount | Specifies the amount that remains to be applied to before the entry is totally applied to. from the table field | |
| Remaining Amt. (LCY) | Remaining Amt. (LCY) | Specifies the amount that remains to be applied to before the entry is totally applied to. | |
| Bal. Account Type | Bal. Account Type | Specifies the type of balancing account that is used for the entry. from the table field | |
| Bal. Account No. | Bal. Account No. | Specifies the number of the balancing account that is used for the entry. from the table field | |
| Open | Open | Specifies whether the amount on the entry has been fully paid or there is still a remaining amount that must be applied to. from the table field | |
| Amount to Apply | Amount to Apply | Specifies the amount to apply. from the table field | |
| Applies-to ID | Applies-to ID | Specifies the ID of entries that will be applied to when you choose the Apply Entries action. from the table field | |
| Applying Entry | Applying Entry | Specifies whether the entry will be applied to when you choose the Apply Entries action. from the table field | |
| Exported to Payment File | Exported to Payment File | Specifies that the entry was created as a result of exporting a payment journal line. from the table field | |
| Payment Reference | Payment Reference | Specifies the payment of the employee document. | |
| Entry No. | Entry No. | Specifies the entry number that is assigned to the entry. from the table field | |
| G/L Register No. | G/L Register No. | Specifies the G/L register number that groups related G/L entries from the same posting. from the table field | |
| Transaction No. | Transaction No. | Specifies the transaction number that groups related G/L entries from the same posting. 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 | |
| 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 |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Entry | Applied Entries | View the ledger entries that have been applied to this record. | Page 63 “Applied Employee 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. | ||
| Detailed Ledger Entries | View a summary of the all posted entries and adjustments related to a specific employee ledger entry | Page 5238 “Detailed Empl. Ledger Entries” | |
| 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.) | ||
| Functions | Apply Entries | Select one or more ledger entries that you want to apply this record to so that the related posted documents are closed as paid or refunded. | |
| Unapply Entries | Unselect one or more ledger entries that you want to unapply this record. | ||
| Create Payment | Create a payment journal based on the selected entries. | ||
| Reverse Transaction | Reverse an erroneous employee ledger entry. |
Procedures
2 local procedures, no public ones.
Triggers
OnOpenPage
Relations
- source table Table 5222 “Employee Ledger Entry”
Pages and codeunits on this table
- Table 5222 “Employee Ledger Entry” (drill-down page)
- Table 5222 “Employee Ledger Entry” (lookup page)
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)) - Page 344 “Navigate” (1 call:
ShowEmployeeLedgerEntries → (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: "Employee Ledger Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.