pageInventoryofficial - Microsoftderived - from the source, no model text

Page 506 "Item Application Entries"

Base Application · Microsoft.Inventory.Ledger

Across versions

  1. BC23-25present
  2. BC26declaration changed
  3. BC27-30unchanged

Neighbourhood 3 connected objects and pages

Table 339 "Item Application Entry" (relates to)Item Application EntryTable 339 "Item Application Entry" (pages and codeunits on it, 2 links)Item Application EntryRemove and reapply item entries (Learn pages)Remove and reapply item entr…

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.Ledger · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Item Application Entries
SourceTable Item Application Entry
PageType List
ApplicationArea Basic, Suite

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 Posting Date Posting Date Specifies the posting date that corresponds to the posting date of the item ledger entry, for which this item application entry was created. from the table field
Item Ledger Entry No. Item Ledger Entry No. Specifies one or more item application entries for each inventory transaction that is posted. from the table field
Inbound Item Entry No. Inbound Item Entry No. Specifies the number of the item ledger entry corresponding to the inventory increase or positive quantity in inventory. from the table field
Outbound Item Entry No. Outbound Item Entry No. Specifies the number of the item ledger entry corresponding to the inventory decrease for this entry. from the table field
Quantity Quantity Specifies the quantity of the item that is being applied from the inventory decrease in the Outbound Item Entry No. field, to the inventory increase in the Inbound Item Entry No. field. from the table field
Item No. Item No. Specifies the item number from the table field
Variant Code Variant Code Specifies the variant code of the item. from the table field
Location Code Location Code Specifies the location code from the table field
Latest Valuation Date Latest Valuation Date Specifies the latest valuation date of the item ledger entry. from the table field
Transferred-from Entry No. Transferred-from Entry No. Specifies the item ledger entry number of the original inventory increase of the item if the item application entry originates from a transfer. from the table field
Outbound Entry is Updated Outbound Entry is Updated Specifies that the cost of the related outbound item entry is already updated. If the field is selected, then the cost adjustment routine will not try to update any previous related outbound entries. from the table field
Cost Application Cost Application Specifies that the application entry should have the cost forwarded or simply included in an average cost calculation. from the table field
Entry No. Entry No. Specifies the number of the entry, as assigned from the specified number series when the entry was created. from the table field

Actions

Group Action ToolTip Runs
Edit Reset Outbound Entry is Updated Reset the Outbound Entry is Updated field to allow the cost adjustment routine to update the related outbound item entry.
Set/Reset Cost Application Set or reset the Cost Application field to indicate whether the cost of the related outbound item entry should be forwarded or simply included in an average cost calculation.
Traverse Filter by Inbound Filter the list to show only item application entries with the current inbound item entry number.
Filter by Outbound Filter the list to show only item application entries with the current outbound item entry number.

Relations

Pages and codeunits on this table

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). 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 Application Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources