BC Observatoryunofficial, made by waldo
tableextensionFinanceofficial - Microsoftderived - from the source, no model text

Table extension 7412 "Sustainability Batch Excise"

ExciseTaxes · Microsoft.ExciseTaxes

Open in Claude7412.mdSource on GitHub

Across versions

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

Neighbourhood 2 connected objects and pages

Table 6239 "Sust. Excise Journal Batch" (relates to)Sust. Excise Journal BatchTable 7412 "Excise Tax Type" (relates to)Excise Tax Type

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.

ExciseTaxes · Microsoft.ExciseTaxes · BC29-30 · source at ea08af5e · facts from BC29

Extends Sust. Excise Journal Batch.

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
7412 Excise Tax Type Filter Code[20] Specifies the excise tax type filter for this batch. Only journal lines with this tax type will be allowed. via Page extension 7413 “Excise Journal Batch Ext” TableRelation Table 7412 “Excise Tax Type” (“Excise Tax Type”.Code where(Enabled = const(true))); DataClassification CustomerContent

Procedures

  • ValidateTaxTypeForBatch(ExciseTaxType: Code[20])

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: "Sustainability Batch Excise"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources