pageInventoryofficial - Microsoftderived - from the source, no model text

Page 353 "Item Availability Lines"

Base Application · Microsoft.Inventory.Availability

Across versions

  1. BC23present
  2. BC241 events changed
  3. BC25-30unchanged

Neighbourhood 7 connected objects and pages

Table 925 "Item Availability Buffer" (relates to)Item Availability BufferPage extension 6483 "Serv. ItemAvailabilityLines" (extended by)Serv. ItemAvailabilityLinesPage extension 99000767 "Mfg. Item Availability Lines" (extended by)Mfg. Item Availability LinesCodeunit 6450 "Serv. Integration Mgt." (event subscribers)Serv. Integration Mgt.Codeunit 353 "Item Availability Forms Mgt" (calls, 2 links)Item Availability Forms MgtCodeunit 920 "Period Form Lines Mgt." (calls, 2 links)Period Form Lines Mgt.Get an availability overview (Learn pages)Get an availability overview

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Inventory.Availability · captioned “Lines” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Lines
SourceTable Item Availability Buffer
PageType ListPart

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
Control1 Period Start Period Start Specifies the first period that item availability is shown for. from the table field
Period Name Period Name Specifies the type of period that item availability is shown for. from the table field
Gross Requirement Gross Requirement 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… from the table field
Scheduled Receipt Scheduled Receipt Specifies the sum of items from replenishment orders. from the table field
Planned Order Receipt Planned Order Receipt Specifies the item’s availability figures for the planned order receipt. from the table field
Projected Available Balance Projected Available Balance 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. from the table field
Inventory Inventory Specifies the inventory level of an item. from the table field
Qty. on Purch. Order Qty. on Purch. Order Specifies how many units of the item are inbound on purchase orders, meaning listed on outstanding purchase order lines.
Qty. on Sales Order Qty. on Sales Order Specifies how many units of the item are allocated to sales orders, meaning listed on outstanding sales orders lines.
Qty. on Project Order Qty. on Job Order 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.
Trans. Ord. Shipment (Qty.) Trans. Ord. Shipment (Qty.) 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.
Qty. in Transit Qty. in Transit Specifies the quantity of the items that are currently in transit.
Trans. Ord. Receipt (Qty.) Trans. Ord. Receipt (Qty.) 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.
Qty. on Asm. Comp. Lines Qty. on Asm. Comp. Lines Specifies how many units of the item are allocated to assembly component orders.
Qty. on Assembly Order Qty. on Assembly Order Specifies how many units of the item are allocated to assembly orders, which is how many are listed on outstanding assembly order headers.
Expected Inventory Expected Inventory Specifies how many units of the assembly component are expected to be available for the current assembly order on the due date. from the table field
Available Inventory Available Inventory Specifies the quantity of the item that is currently in inventory and not reserved for other demand. from the table field
Planned Order Releases Planned Order Releases 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 … from the table field
Net Change Net Change Specifies the net change in the inventory of the item during the period entered in the Date Filter field.

Events published

  • OnAfterCalcAvailQuantities(var ItemAvailabilityBuffer: Record "Item Availability Buffer"; var Item: Record Item) Δ BC24 (integration)
  • OnAfterSet(var Item: Record Item; PeriodType: Integer; AmountType: Enum "Analysis Amount Type") (integration)
  • OnAfterSetItemFilter(var Item: Record Item; PeriodStart: Date; PeriodEnd: Date) (integration)

Procedures

  • SetLines(var NewItem: Record Item; NewPeriodType: Enum "Analysis Period Type"; NewAmountType: Enum "Analysis Amount Type")

Plus 3 local procedures.

Triggers

OnAfterGetRecord, OnInit, OnFindRecord, OnNextRecord, OnOpenPage

Relations

Extended by

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Documented on Microsoft Learn

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). The call sections above are our own, per object, from the BC29 call graph. 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: "page", object_name: "Item Availability Lines"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources