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

Table 46937 "BC14 Cust. Ledger Entry"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation

Across versions

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

Neighbourhood 2 connected objects and pages

Table 18 "Customer" (relates to)CustomerCodeunit 46939 "BC14 Cust. Ledger Migrator" (pages and codeunits on it)BC14 Cust. Ledger Migrator

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.

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

Properties

Property Value
Caption 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 —
3 Customer No. Code[20] — TableRelation Table 18 “Customer”
4 Posting Date Date —
5 Document Type Enum “Gen. Journal Document Type” — enum Enum 6 “Gen. Journal Document Type”
6 Document No. Code[20] —
7 Description Text[100] —
11 Currency Code Code[10] —
22 Customer Posting Group Code[20] —
23 Global Dimension 1 Code Code[20] —
24 Global Dimension 2 Code Code[20] —
28 Source Code Code[10] —
36 Open Boolean —
37 Due Date Date —
53 Transaction No. Integer —
63 External Document No. Code[35] —
100 Journal Batch Name Code[10] —

Keys

  • Key1: Entry No. (clustered)
  • Key2: Customer No., Posting Date
  • Key3: Open
  • Key4: Transaction No., Entry No.

Relations

Pages and codeunits on this table

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 Cust. Ledger Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources