Table 359 "Reservation Worksheet Log"
Base Application · Microsoft.Inventory.Tracking
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC281 fields changed
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Inventory.Tracking · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Reservation Worksheet Log |
| 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 | Journal Batch Name | Code[10] | — | TableRelation Table 345 “Reservation Wksh. Batch” (Reservation Wksh. Batch) |
| 2 | Entry No. | Integer | — | |
| 17 | Record ID | RecordId | — | |
| 20 | Quantity Δ BC28 | Decimal | Specifies how many units were reserved for the demand line. |
Keys
- Key1: Journal Batch Name, Entry No. (clustered)
Triggers
OnInsert
Relations
- Journal Batch Name: TableRelation Table 345 “Reservation Wksh. Batch”
Pages and codeunits on this table
- Page 331 “Reservation Wksh. Log Factbox” (source table)
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: "Reservation Worksheet Log"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.