tableextensionSales & Receivablesofficial - Microsoftderived - from the source, no model text

Table extension 8067 "G/L Entry"

Subscription Billing · Microsoft.SubscriptionBilling

Across versions

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

Neighbourhood 3 connected objects and pages

Table 17 "G/L Entry" (relates to)G/L EntryTable 8052 "Customer Subscription Contract" (relates to)Customer Subscription ContractTable 8063 "Vendor Subscription Contract" (relates to)Vendor Subscription Contract

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.

Subscription Billing · Microsoft.SubscriptionBilling · BC29-30 · source at ea08af5e · facts from BC29

Extends G/L Entry.

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
8000 Subscription Contract No. Code[20] Specifies the contract number for which the contract deferral was released. via Page extension 8087 “General Ledger Entries” TableRelation Table 8052 “Customer Subscription Contract”, Table 8063 “Vendor Subscription Contract” (if (“Source Type” = const(Customer)) “Customer Subscription Contract” else if (“Source Type” = const(Vendor)) “Vendor Subscription Contract”); not editable; DataClassification CustomerContent

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: "tableextension", object_name: "G/L Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources