Table 5800 "Item Charge"
Base Application · Microsoft.Inventory.Item
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC286 fields changed
- BC29-30unchanged
Neighbourhood 43 connected objects and pages
Base Application · Microsoft.Inventory.Item · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 5800 “Item Charges” (3 Learn pages).
Properties
| Property | Value |
|---|---|
| Caption | Item Charge |
| DataClassification | CustomerContent |
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 |
|---|---|---|---|---|
| 1 | No. Δ BC28 | Code[20] | Specifies the number of the involved entry or record, according to the specified number series. | NotBlank |
| 2 | Description Δ BC28 | Text[100] | Specifies a description of the item charge number that you are setting up. | |
| 3 | Gen. Prod. Posting Group Δ BC28 | Code[20] | Specifies the item charge’s product type to link transactions made for this item charge with the appropriate general ledger account according to the general posting setup. | TableRelation Table 251 “Gen. Product Posting Group” (Gen. Product Posting Group) |
| 4 | Tax Group Code Δ BC28 | Code[20] | Specifies the sales tax group code that this item charge belongs to. | TableRelation Table 321 “Tax Group” (Tax Group) |
| 5 | VAT Prod. Posting Group Δ BC28 | Code[20] | Specifies the VAT specification of the involved item or resource to link transactions made for this record with the appropriate general ledger account according to the VAT posting setup. | TableRelation Table 324 “VAT Product Posting Group” (VAT Product Posting Group) |
| 6 | Search Description Δ BC28 | Code[100] | Specifies text to search for when you do not know the number of the item charge. | |
| 7 | Global Dimension 1 Code | Code[20] | — | TableRelation Table 349 “Dimension Value” (“Dimension Value”.Code where(“Global Dimension No.” = const(1), Blocked = const(false))) |
| 8 | Global Dimension 2 Code | Code[20] | — | TableRelation Table 349 “Dimension Value” (“Dimension Value”.Code where(“Global Dimension No.” = const(2), Blocked = const(false))) |
Keys
- Key1: No. (clustered)
- Key2: Search Description
- Key3: Gen. Prod. Posting Group
- Key4: Description
Events published
OnAfterValidateShortcutDimCode(var ItemCharge: Record "Item Charge"; xItemCharge: Record "Item Charge"; FieldNumber: Integer; var ShortcutDimCode: Code[20])(integration)OnBeforeValidateShortcutDimCode(var ItemCharge: Record "Item Charge"; xItemCharge: Record "Item Charge"; FieldNumber: Integer; var ShortcutDimCode: Code[20])(integration)
Procedures
ValidateShortcutDimCode(FieldNumber: Integer; var ShortcutDimCode: Code[20])
Triggers
OnDelete, OnModify, OnRename
Relations
- drill-down page Page 5800 “Item Charges”
- lookup page Page 5800 “Item Charges”
- Gen. Prod. Posting Group: TableRelation Table 251 “Gen. Product Posting Group”
- Tax Group Code: TableRelation Table 321 “Tax Group”
- VAT Prod. Posting Group: TableRelation Table 324 “VAT Product Posting Group”
- Global Dimension 1 Code: TableRelation Table 349 “Dimension Value”
- Global Dimension 2 Code: TableRelation Table 349 “Dimension Value”
Referenced by
31 fields in 31 objects relate to this table (TableRelation or CalcFormula).
- Table 111 “Sales Shipment Line”: No.
- Table 113 “Sales Invoice Line”: No.
- Table 115 “Sales Cr.Memo Line”: No.
- Table 121 “Purch. Rcpt. Line”: No.
- Table 123 “Purch. Inv. Line”: No.
- Table 125 “Purch. Cr. Memo Line”: No.
- Table 174 “Standard Purchase Line”: No.
- Table 30131 “Shpfy Shipment Method Mapping”: Shipping Charges No.
- Table 427 “IC Outbox Sales Line”: IC Partner Reference
- Table 429 “IC Outbox Purchase Line”: IC Partner Reference
- Table 431 “Handled IC Outbox Sales Line”: IC Partner Reference
- Table 433 “Handled IC Outbox Purch. Line”: IC Partner Reference
- Table 435 “IC Inbox Sales Line”: IC Partner Reference
- Table 437 “IC Inbox Purchase Line”: IC Partner Reference
- Table 439 “Handled IC Inbox Sales Line”: IC Partner Reference
- Table 441 “Handled IC Inbox Purch. Line”: IC Partner Reference
- Table 5024 “Service Declaration Line”: Item Charge No.
- Table 5108 “Sales Line Archive”: No.
- Table 5110 “Purchase Line Archive”: No.
- Table 5802 “Value Entry”: Item Charge No.
- Table 5805 “Item Charge Assignment (Purch)”: Item Charge No.
- Table 5809 “Item Charge Assignment (Sales)”: Item Charge No.
- Table 5821 “Item Statistics Buffer”: Item Charge No. Filter
- Table 5851 “Invt. Document Line”: Item Charge No.
- Table 6105 “E-Document Line Mapping”: Purchase Type No.
- Table 6227 “Sustainability Value Entry”: No.
- Table 6651 “Return Shipment Line”: No.
- Table 6661 “Return Receipt Line”: No.
- Table 7190 “Sales Shipment Buffer”: No.
- Table 753 “Standard Item Journal Line”: Item Charge No.
- Table 83 “Item Journal Line”: Item Charge No.
Pages and codeunits on this table
- Page 5800 “Item Charges” (source table)
Extended by
- Table extension 5013 “Serv. Decl. Item Charge”
- Table extension 6229 “Sust. Item Charge”
- Table extension 6536 “E-Doc. Item Charge”
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” (5 calls:
OnDelete → DeleteDefaultDim,OnModify → UpdateDefaultDim,OnRename → RenameDefaultDim, …)
Countries that replace it
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: "Item Charge"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.