Table extension 7417 "Excise Item Ext"
ExciseTaxes · Microsoft.ExciseTaxes
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
ExciseTaxes · Microsoft.ExciseTaxes · BC29-30 · source at ea08af5e · facts from BC29
Extends Item.
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 | Code[20] | Specifies which excise tax type applies to this item. via Page extension 7415 “Excise Item Card Ext” | obsolete Pending 29.0; TableRelation Table 7412 “Excise Tax Type” (“Excise Tax Type”.Code where(Enabled = const(true))); DataClassification CustomerContent |
| 7413 | Quantity for Excise Tax | Decimal | Specifies the amount per unit based on tax basis. via Page extension 7415 “Excise Item Card Ext” | obsolete Pending 29.0; DataClassification CustomerContent |
| 7414 | Excise Unit of Measure Code | Code[10] | Specifies the unit of measure for tax basis. via Page extension 7415 “Excise Item Card Ext” | obsolete Pending 29.0; TableRelation Table 204 “Unit of Measure” (“Unit of Measure”.Code); DataClassification CustomerContent |
Relations
- Excise Unit of Measure Code: TableRelation Table 204 “Unit of Measure”
- extends Table 27 “Item”
- Excise Tax Type: TableRelation Table 7412 “Excise Tax Type”
Recent changes
- 2026-08-11 #9725 [Master] - Slice 626127: [Excise Tax][VENDOR] Multiple Excise Taxes per Item (main, BC30, feature)
Deprecations
- field Excise Tax Type: Pending 29.0, “Replaced by the Item Excise Tax table to support multiple excise taxes per item.”
- field Excise Unit of Measure Code: Pending 29.0, “Replaced by the Item Excise Tax table to support multiple excise taxes per item.”
- field Quantity for Excise Tax: Pending 29.0, “Replaced by the Item Excise Tax table to support multiple excise taxes per item.”
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "Excise Item Ext"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.