Table 387 "Allocation Policy"
Base Application · Microsoft.Inventory.Tracking
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC282 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 | Allocation Policy |
| DataClassification | CustomerContent |
| LookupPageId | Allocation Policies |
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 | Text[10] | — | TableRelation Table 345 “Reservation Wksh. Batch” (Reservation Wksh. Batch) |
| 2 | Line No. Δ BC28 | Integer | Specifies the step number of the allocation policy. | |
| 3 | Allocation Rule Δ BC28 | Enum “Allocation Rules Impl.” | Specifies the name of the allocation policy. Click or tap the AssistEdit button to see an example of how the allocation policy will be applied. | enum Enum 300 “Allocation Rules Impl.”; NotBlank |
Keys
- Key1: Journal Batch Name, Line No. (clustered)
Procedures
GetAllocationPolicyDescription(): TextGetNextLineNo(): Integer
Relations
- lookup page Page 316 “Allocation Policies”
- Journal Batch Name: TableRelation Table 345 “Reservation Wksh. Batch”
Pages and codeunits on this table
- Page 316 “Allocation Policies” (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: "Allocation Policy"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.