tableFinanceofficial - Microsoftderived - from the source, no model text

Table 185 "Pmt. Rec. Applied-to Entry"

Base Application · Microsoft.Bank.Reconciliation

Across versions

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

Base Application · Microsoft.Bank.Reconciliation · captioned “Payment Reconciliation Applied-to Entry” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Payment Reconciliation Applied-to 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
1 Entry No. Integer —
2 Entry Type Enum “Gen. Journal Source Type” — enum Enum 82 “Gen. Journal Source Type”
3 Bank Account No. Code[20] —
4 Statement No. Code[20] —
5 Statement Line No. Integer —
6 Applied by Entry No. Integer —
7 Amount Δ BC28 Decimal —

Keys

  • Key1: Entry No., Entry Type, Bank Account No., Statement No., Statement Line No., Applied by Entry No. (clustered)

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: "Pmt. Rec. Applied-to Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources