Page 5415 "Item Avail. by Variant Lines"
Base Application · Microsoft.Inventory.Availability
Across versions
- BC23-30present
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Inventory.Availability · captioned “Lines” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Lines |
| SourceTable | Item Variant |
| 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 | Code | Code | Specifies a code to identify the variant. from the table field |
| Description | Description | Specifies text that describes the item variant. from the table field | |
| Gross Requirement | GrossRequirement |
Specifies the sum of the all demand for the item. | |
| Scheduled Receipt | ScheduledRcpt |
Specifies the sum of items from replenishment orders. | |
| Planned Receipt | PlannedOrderRcpt |
Specifies the quantity on planned production orders plus planning worksheet lines plus requisition worksheet lines. | |
| Projected Available Balance | ProjAvailableBalance |
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. | |
| Inventory | Item.Inventory |
Specifies the inventory level of an item. | |
| Qty. on Purch. Order | Item."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 | Item."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 | Item."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.) | Item."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. on Asm. Comp. Lines | Item."Qty. on Asm. Component" |
Specifies how many units of the item are allocated to assembly component orders. | |
| Qty. on Assembly Order | Item."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. | |
| Qty. in Transit | Item."Qty. in Transit" |
Specifies the quantity of the items that are currently in transit. | |
| Trans. Ord. Receipt (Qty.) | Item."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. | |
| Expected Inventory | ExpectedInventory |
Specifies how many units of the assembly component are expected to be available for the current assembly order on the due date. | |
| Available Qty. on Hand | QtyAvailable |
Specifies the quantity of the item that is currently in inventory and not reserved for other demand. | |
| Planned Order Releases | PlannedOrderReleases |
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 … | |
| Net Change | Item."Net Change" |
Specifies the net change in the inventory of the item during the period entered in the Date Filter field. |
Events published
OnAfterCalcQuantities(ItemVariant: Record "Item Variant"; var Item: Record Item; var GrossRequirement: Decimal; var PlannedOrderRcpt: Decimal; var ScheduledRcpt: Decimal; var PlannedOrderReleases: Decimal; var ProjAvailableBalance: Decimal; var ExpectedInventory: Decimal; var QtyAvailable: Decimal)(integration)OnAfterSet(var ItemVariant: record "Item Variant"; var Item: Record Item; AmountType: Enum "Analysis Amount Type")(integration)
Procedures
Set(var NewItem: Record Item; NewAmountType: Enum "Analysis Amount Type")
Plus 3 local procedures.
Triggers
OnAfterGetRecord, OnOpenPage
Relations
- source table Table 5401 “Item Variant”
Extended by
- Page extension 6476 “Serv. ItemAvailbyVariantLines”
- Page extension 99000775 “Mfg. ItemAvailByVariantLines”
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.
- Codeunit 353 “Item Availability Forms Mgt” (2 calls:
CalcAvailQuantities → CalcAvailQuantities,ShowItemAvailLineList → ShowItemAvailLineList)
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 Avail. by Variant Lines"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.