Table 5811 "Post Value Entry to G/L"
Base Application · Microsoft.Inventory.Costing
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Inventory.Costing · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Post Value Entry to G/L |
| 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 | Value Entry No. | Integer | — | TableRelation Table 5802 “Value Entry” (Value Entry) |
| 2 | Item No. | Code[20] | — | TableRelation Table 27 “Item” |
| 3 | Posting Date | Date | — |
Keys
- Key1: Value Entry No. (clustered)
- Key2: Item No., Posting Date
- Key3: Item No.
Relations
- Item No.: TableRelation Table 27 “Item”
- Value Entry No.: TableRelation Table 5802 “Value Entry”
Referenced by
1 fields in 1 objects relate to this table (TableRelation or CalcFormula).
- Table 27 “Item”: Cost is Posted to G/L
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: "table", object_name: "Post Value Entry to G/L"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.