Table extension 7419 "Excise Location Ext"
ExciseTaxes · Microsoft.ExciseTaxes
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
ExciseTaxes · Microsoft.ExciseTaxes · BC29-30 · source at ea08af5e · facts from BC29
Extends Location.
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 Bonded Location | Enum “Excise Bonded Handling” | Specifies whether this location is treated as non-bonded, bonded, or customs for excise duty purposes, to control whether excise tax is suspended or becomes due for inventory movements through this location. | enum Enum 7416 “Excise Bonded Handling”; DataClassification CustomerContent |
| 7413 | Excise Bond Identifier | Code[20] | Specifies the identifier of the excise bond or bonded warehouse that this location belongs to, for reporting, audit, and traceability of excise-suspended inventory. | DataClassification CustomerContent |
| 7414 | Bond Authorization No. | Text[100] | Specifies the official bond authorization or permit number assigned by customs or excise authorities for this bonded location. | DataClassification CustomerContent |
Relations
- extends Table 14 “Location”
Recent changes
- 2026-10-05 #11748 [Master] - Slice 626292: [Excise Tax][VENDOR] Bonded Locations for Excise Calculations (main, BC30, feature, added)
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 Location Ext"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.