tableAdministration & Setupofficial - Microsoftderived - from the source, no model text

Table 46938 "BC14 Detailed Cust. LE"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation

Across versions

  1. BC23-28not present
  2. BC29-30present

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · captioned “Detailed Customer Ledger Entry Migration Data” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Detailed Customer Ledger Entry Migration Data
Extensible false
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 Cust. Ledger Entry No. Integer —
3 Entry Type Enum “Detailed CV Ledger Entry Type” — enum Enum 379 “Detailed CV Ledger Entry Type”
4 Posting Date Date —
7 Amount Decimal —
8 Amount (LCY) Decimal —
10 Currency Code Code[10] —
43 Ledger Entry Amount Boolean —

Keys

  • Key1: Entry No. (clustered)
  • Key2: Cust. Ledger Entry No.

Recent changes

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: "BC14 Detailed Cust. LE"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources