tableHuman Resourcesofficial - Microsoftderived - from the source, no model text

Table 5224 "Payable Employee Ledger Entry"

Base Application · Microsoft.HumanResources.Payables

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC281 fields changed
  5. BC29-30unchanged

Neighbourhood 3 connected objects and pages

Table 4 "Currency" (relates to)CurrencyTable 5200 "Employee" (relates to)EmployeeTable 5222 "Employee Ledger Entry" (relates to)Employee Ledger Entry

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.HumanResources.Payables · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Payable Employee Ledger Entry
DataClassification CustomerContent

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.

No. Name Type Explanation Notes
2 Employee No. Code[20] — TableRelation Table 5200 “Employee”
3 Entry No. Integer —
4 Employee Ledg. Entry No. Integer — TableRelation Table 5222 “Employee Ledger Entry” (Employee Ledger Entry)
5 Amount Δ BC28 Decimal —
7 Currency Code Code[10] — TableRelation Table 4 “Currency”
8 Positive Boolean —

Keys

  • Key1: Entry No. (clustered)

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "Payable Employee Ledger Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources