Table 925 "Item Availability Buffer"
Base Application · Microsoft.Inventory.Availability
Across versions
- BC23-27present
- BC2822 fields changed
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Inventory.Availability · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 353 “Item Availability Lines” (1 Learn page).
Properties
| Property | Value |
|---|---|
| DataClassification | SystemMetadata |
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 | Item No. | Code[20] | — | |
| 5 | Period Type | Option | — | |
| 6 | Period Name Δ BC28 | Text[50] | Specifies the type of period that item availability is shown for. | |
| 7 | Period Start Δ BC28 | Date | Specifies the first period that item availability is shown for. | |
| 8 | Period End | Date | — | |
| 10 | Gross Requirement Δ BC28 | Decimal | Specifies the sum of the total demand for the item. The gross requirement consists of independent demand (which include sales orders, service orders, transfer orders, and, if specified on the page, demand forecasts) and dependent demand (which include production order components for planned, firm pl… | |
| 11 | Scheduled Receipt Δ BC28 | Decimal | Specifies the sum of items from replenishment orders. | |
| 12 | Planned Order Receipt Δ BC28 | Decimal | Specifies the item’s availability figures for the planned order receipt. | |
| 13 | Projected Available Balance Δ BC28 | Decimal | Specifies the item’s availability. This quantity includes all known supply and demand but does not include anticipated demand from demand forecasts or blanket sales orders or suggested supplies from planning or requisition worksheets. | |
| 14 | Inventory Δ BC28 | Decimal | Specifies the inventory level of an item. | |
| 15 | Qty. on Purch. Order Δ BC28 | Decimal | Specifies how many units of the item are inbound on purchase orders, meaning listed on outstanding purchase order lines. via Page 353 “Item Availability Lines” | |
| 16 | Qty. on Sales Order Δ BC28 | Decimal | Specifies how many units of the item are allocated to sales orders, meaning listed on outstanding sales orders lines. via Page 353 “Item Availability Lines” | |
| 17 | Qty. on Service Order Δ BC28 | Decimal | Specifies how many units of the item are allocated to service orders, meaning listed on outstanding service order lines. via Page extension 6483 “Serv. ItemAvailabilityLines” | |
| 18 | Qty. on Job Order Δ BC28 | Decimal | Specifies how many units of the item are allocated to projects, meaning listed on outstanding project planning lines. The field is automatically updated based on the Remaining Qty. field in the Project Planning Lines window. via Page 353 “Item Availability Lines” | |
| 19 | Trans. Ord. Shipment (Qty.) Δ BC28 | Decimal | Specifies the quantity of the items that remains to be shipped. The program calculates this quantity as the difference between the Quantity and the Quantity Shipped fields. It automatically updates the field each time you either update the Quantity or Quantity Shipped field. via Page 353 “Item Availability Lines” | |
| 20 | Qty. in Transit Δ BC28 | Decimal | Specifies the quantity of the items that are currently in transit. via Page 353 “Item Availability Lines” | |
| 21 | Trans. Ord. Receipt (Qty.) Δ BC28 | Decimal | Specifies the quantity of the items that remain to be received but are not yet shipped. The program calculates this quantity as the difference between the Quantity and the Quantity Shipped fields. It automatically updates the field each time you either update the Quantity or Quantity Shipped field. via Page 353 “Item Availability Lines” | |
| 22 | Qty. on Asm. Comp. Lines Δ BC28 | Decimal | Specifies how many units of the item are allocated to assembly component orders. via Page 353 “Item Availability Lines” | |
| 23 | Qty. on Assembly Order Δ BC28 | Decimal | Specifies how many units of the item are allocated to assembly orders, which is how many are listed on outstanding assembly order headers. via Page 353 “Item Availability Lines” | |
| 24 | Expected Inventory Δ BC28 | Decimal | Specifies how many units of the assembly component are expected to be available for the current assembly order on the due date. | |
| 25 | Available Inventory Δ BC28 | Decimal | Specifies the quantity of the item that is currently in inventory and not reserved for other demand. | |
| 26 | Scheduled Receipt (Qty.) Δ BC28 | Decimal | Specifies how many units of the item are scheduled for production orders. The program automatically calculates and updates the contents of the field, using the Remaining Quantity field on production order lines. via Page extension 99000767 “Mfg. Item Availability Lines” | |
| 27 | Scheduled Issue (Qty.) Δ BC28 | Decimal | Specifies the sum of items from planned production orders. via Page extension 99000767 “Mfg. Item Availability Lines” | |
| 28 | Planned Order Releases Δ BC28 | Decimal | Specifies the sum of items from replenishment order proposals, which include planned production orders and planning or requisition worksheets lines, that are calculated according to the starting date in the planning worksheet and production order or the order date in the requisition worksheet. This … | |
| 29 | Net Change Δ BC28 | Decimal | Specifies the net change in the inventory of the item during the period entered in the Date Filter field. via Page 353 “Item Availability Lines” |
Keys
- Key1: Period Type, Period Start (clustered)
Pages and codeunits on this table
- Page 353 “Item Availability Lines” (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: "Item Availability Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.