---
id: object/table/925
type: object
title: Table 925 "Item Availability Buffer"
summary: Table 925 "Item Availability Buffer" in Base Application (Microsoft.Inventory.Availability). 25 fields. Present since at least BC23, still in BC30, changed in BC28.
tier: official
language: en
tags:
  - table
  - base application
versions:
  introduced: null
  last_changed: "28"
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: 71a36fa5f08fe045d6414b4c4400eb054febe8a5073bf8c9f29a61c68adabc45
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Inventory/Availability/ItemAvailabilityBuffer.Table.al
    title: src/Layers/W1/BaseApp/Inventory/Availability/ItemAvailabilityBuffer.Table.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/inventory-how-availability-overview
  objects: []
  features: []
  topics:
    - topic/business-central/business-functionality/inventory
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: table
object_id: 925
name: Item Availability Buffer
namespace: Microsoft.Inventory.Availability
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "28"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 25
  procedures: 0
  events: 0
  subscribers: 0
relations:
  out: 0
  referenced_by: 0
  pages: 1
  extended_by: 0
  event_subscribers: 0
  calls: 0
  called_by: 0
  implements: 0
---

# Table 925 "Item Availability Buffer"

> Table 925 "Item Availability Buffer" in Base Application (Microsoft.Inventory.Availability). 25 fields. Present since at least BC23, still in BC30, changed in BC28.

Base Application · Microsoft.Inventory.Availability · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Inventory/Availability/ItemAvailabilityBuffer.Table.al) · facts from BC29

Learn documents this table through its pages: [Page 353 "Item Availability Lines"](../page/353.md) (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 | Text[50] | Specifies the type of period that item availability is shown for. |  |
| 7 | Period Start | Date | Specifies the first period that item availability is shown for. |  |
| 8 | Period End | Date | — |  |
| 10 | Gross Requirement | 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 | Decimal | Specifies the sum of items from replenishment orders. |  |
| 12 | Planned Order Receipt | Decimal | Specifies the item's availability figures for the planned order receipt. |  |
| 13 | Projected Available Balance | 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 | Decimal | Specifies the inventory level of an item. |  |
| 15 | Qty. on Purch. Order | Decimal | Specifies how many units of the item are inbound on purchase orders, meaning listed on outstanding purchase order lines. <small>via [Page 353 "Item Availability Lines"](../page/353.md)</small> |  |
| 16 | Qty. on Sales Order | Decimal | Specifies how many units of the item are allocated to sales orders, meaning listed on outstanding sales orders lines. <small>via [Page 353 "Item Availability Lines"](../page/353.md)</small> |  |
| 17 | Qty. on Service Order | Decimal | Specifies how many units of the item are allocated to service orders, meaning listed on outstanding service order lines. <small>via [Page extension 6483 "Serv. ItemAvailabilityLines"](../pageextension/6483.md)</small> |  |
| 18 | Qty. on Job Order | 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. <small>via [Page 353 "Item Availability Lines"](../page/353.md)</small> |  |
| 19 | Trans. Ord. Shipment (Qty.) | 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. <small>via [Page 353 "Item Availability Lines"](../page/353.md)</small> |  |
| 20 | Qty. in Transit | Decimal | Specifies the quantity of the items that are currently in transit. <small>via [Page 353 "Item Availability Lines"](../page/353.md)</small> |  |
| 21 | Trans. Ord. Receipt (Qty.) | 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. <small>via [Page 353 "Item Availability Lines"](../page/353.md)</small> |  |
| 22 | Qty. on Asm. Comp. Lines | Decimal | Specifies how many units of the item are allocated to assembly component orders. <small>via [Page 353 "Item Availability Lines"](../page/353.md)</small> |  |
| 23 | Qty. on Assembly Order | Decimal | Specifies how many units of the item are allocated to assembly orders, which is how many are listed on outstanding assembly order headers. <small>via [Page 353 "Item Availability Lines"](../page/353.md)</small> |  |
| 24 | Expected Inventory | 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 | Decimal | Specifies the quantity of the item that is currently in inventory and not reserved for other demand. |  |
| 26 | Scheduled Receipt (Qty.) | 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. <small>via [Page extension 99000767 "Mfg. Item Availability Lines"](../pageextension/99000767.md)</small> |  |
| 27 | Scheduled Issue (Qty.) | Decimal | Specifies the sum of items from planned production orders. <small>via [Page extension 99000767 "Mfg. Item Availability Lines"](../pageextension/99000767.md)</small> |  |
| 28 | Planned Order Releases | 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 | Decimal | Specifies the net change in the inventory of the item during the period entered in the Date Filter field. <small>via [Page 353 "Item Availability Lines"](../page/353.md)</small> |  |

## Keys

- Key1: Period Type, Period Start (clustered)

## Pages and codeunits on this table

- [Page 353 "Item Availability Lines"](../page/353.md) (source table)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: BC28

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). 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.