Table 6241 "Sust. Excise Taxes Trans. Log"

Sustainability · Microsoft.Sustainability.ExciseTax · captioned “Excise Taxes Transaction Log” · BC29-30 · source at ea08af5e · facts from BC29

Properties

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.

Keys

• PK: Entry No. (clustered)

Events published

• OnAfterCopyFromSustainabilityExciseJnlLine(var SustExciseTaxesTransactionLog: Record "Sust. Excise Taxes Trans. Log"; SustainabilityExciseJnlLine: Record "Sust. Excise Jnl. Line") (integration)
  • subscribers: Codeunit 7413 “Excise Tax Trans Subscriber” OnAfterCopyFromSustainabilityExciseJnlLine

Procedures

• CopyFromSustainabilityExciseJnlLine(SustainabilityExciseJnlLine: Record "Sust. Excise Jnl. Line")

Plus 1 local procedures.

Relations

• lookup page Page 6288 “Sust. Excise Taxes Trans. Logs”
• Source No.: TableRelation Table 15 “G/L Account” (conditional)
• Partner No.: TableRelation Table 18 “Customer” (conditional)
• CO2e Unit of Measure: TableRelation Table 204 “Unit of Measure”
• Material Breakdown UOM: TableRelation Table 204 “Unit of Measure”
• Source Unit of Measure Code: TableRelation Table 204 “Unit of Measure”
• Partner No.: TableRelation Table 23 “Vendor” (conditional)
• Source No.: TableRelation Table 27 “Item” (conditional)
• Item Ledger Entry No.: TableRelation Table 32 “Item Ledger Entry”
• Global Dimension 1 Code: TableRelation Table 349 “Dimension Value”
• Global Dimension 2 Code: TableRelation Table 349 “Dimension Value”
• Shortcut Dimension 3 Code: CalcFormula Table 480 “Dimension Set Entry”
• Shortcut Dimension 4 Code: CalcFormula Table 480 “Dimension Set Entry”
• Shortcut Dimension 5 Code: CalcFormula Table 480 “Dimension Set Entry”
• Shortcut Dimension 6 Code: CalcFormula Table 480 “Dimension Set Entry”
• Shortcut Dimension 7 Code: CalcFormula Table 480 “Dimension Set Entry”
• Shortcut Dimension 8 Code: CalcFormula Table 480 “Dimension Set Entry”
• Dimension Set ID: TableRelation Table 480 “Dimension Set Entry”
• Source No.: TableRelation Table 5600 “Fixed Asset” (conditional)
• Responsibility Center: TableRelation Table 5714 “Responsibility Center”
• Account No.: TableRelation Table 6210 “Sustainability Account”
• Account Category: TableRelation Table 6211 “Sustain. Account Category”
• Account Subcategory: TableRelation Table 6212 “Sustain. Account Subcategory”
• Journal Template Name: TableRelation Table 6238 “Sust. Excise Journal Template”
• Journal Batch Name: TableRelation Table 6239 “Sust. Excise Journal Batch”
• Country/Region Code: TableRelation Table 9 “Country/Region”

Pages and codeunits on this table

• Page 6288 “Sust. Excise Taxes Trans. Logs” (source table)

Extended by

• Table extension 7414 “Excise Taxes Trans. Log Ext”

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 408 “DimensionManagement” (1 call: ShowDimensions → ShowDimensionSet)

Recent changes

• 2026-08-27 #10675 Temporarily suppress AS0072 (ObsoleteTag 29.0) on 10 Base App elements for v30 prep (main, BC30, fix)

Deprecations

• field Account Category: Pending 28.0 (#if not CLEANSCHEMA29), “This field is no longer required and will be removed in a future release.”
• field Account Name: Pending 28.0 (#if not CLEANSCHEMA29), “This field is no longer required and will be removed in a future release.”
• field Account No.: Pending 28.0 (#if not CLEANSCHEMA29), “This field is no longer required and will be removed in a future release.”
• field Account Subcategory: Pending 28.0 (#if not CLEANSCHEMA29), “This field is no longer required and will be removed in a future release.”

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). The call sections above are our own, per object, from the BC29 call graph. 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: "table", object_name: "Sust. Excise Taxes Trans. Log"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.