Enum 7412 "Excise Entry Type"
ExciseTaxes · Microsoft.ExciseTaxes
Across versions
- BC23-28not present
- BC29-30present
ExciseTaxes · Microsoft.ExciseTaxes · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | true |
Values
| Ordinal | Name | Caption | Notes |
|---|---|---|---|
| 0 | (blank) | ||
| 1 | Purchase | Purchase | |
| 2 | Sale | Sales | |
| 3 | Positive Adjmt. | Positive Adjustment | |
| 4 | Negative Adjmt. | Negative Adjustment | |
| 5 | Output | Output | |
| 6 | Assembly Output | Assembly Output | |
| 7 | Transfer Shipment | Transfer Shipment | |
| 8 | Transfer Receipt | Transfer Receipt | |
| 9 | Consumption | Consumption |
Recent changes
- 2026-10-05 #11748 [Master] - Slice 626292: [Excise Tax][VENDOR] Bonded Locations for Excise Calculations (main, BC30, feature)
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: "enum", object_name: "Excise Entry Type"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.