pageInventoryofficial - Microsoftderived - from the source, no model text

Page 521 "Application Worksheet"

Base Application · Microsoft.Inventory.Ledger

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 32 "Item Ledger Entry" (relates to)Item Ledger EntryCodeunit 22 "Item Jnl.-Post Line" (calls, 7 links)Item Jnl.-Post LineRemove 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 Application Worksheet
SourceTable Item Ledger Entry
PageType Worksheet
UsageCategory Tasks
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
General Date Filter DateFilter Specifies the date interval by which values are filtered.
Item Filter ItemFilter Specifies a filter to limit the item ledger entries in the first table of the application worksheet to those that have item numbers.
Document No. Filter DocumentFilter Specifies a filter to limit the item ledger entries in the first table of the application worksheet, to those that have document numbers.
Location Filter LocationFilter Specifies a filter to limit the item ledger entries in the first table of the application worksheet to those that have locations.
Control1 Item No. Item No. Specifies the number of the item in the entry. from the table field
Document No. Document No. Specifies the document number on the entry. The document is the voucher that the entry was based on, for example, a receipt. from the table field
Location Code Location Code Specifies the code for the location that the entry is linked to. from the table field
Posting Date Posting Date Specifies the entry’s posting date. from the table field
Entry Type Entry Type Specifies which type of transaction that the entry is created from. from the table field
Source Type Source Type Specifies the source type that applies to the source number, shown in the Source No. field. from the table field
Document Type Document Type Specifies what type of document was posted to create the item ledger entry. from the table field
Document Line No. Document Line No. Specifies the number of the line on the posted document that corresponds to the item ledger entry. from the table field
Variant Code Variant Code Specifies the variant of the item on the line. from the table field
Serial No. Serial No. Specifies a serial number if the posted item carries such a number. from the table field
Lot No. Lot No. Specifies a lot number if the posted item carries such a number. from the table field
Source No. Source No. Specifies where the entry originated. from the table field
Description Description Specifies a description of the entry. from the table field
Quantity Quantity Specifies the number of units of the item in the item entry. from the table field
Remaining Quantity Remaining Quantity Specifies the quantity in the Quantity field that remains to be processed. from the table field
Invoiced Quantity Invoiced Quantity Specifies how many units of the item on the line have been invoiced. from the table field
Reserved Quantity Reserved Quantity Specifies how many units of the item on the line have been reserved. from the table field
Shipped Qty. Not Returned Shipped Qty. Not Returned Specifies the quantity for this item ledger entry that was shipped and has not yet been returned. from the table field
Cost Amount (Actual) Cost Amount (Actual) Specifies the adjusted cost, in LCY, of the quantity posting.
Unit Cost(LCY) Rec.GetUnitCostLCY() Specifies the cost of one unit of the item.
Open Open Specifies whether the entry has been fully applied to. from the table field
Positive Positive Specifies whether the item in the item ledge entry is positive. from the table field
Applies-to Entry Applies-to Entry Specifies if the quantity on the journal line must be applied to an already-posted entry. In that case, enter the entry number that the quantity will be applied to. from the table field
Applied Entry to Adjust Applied Entry to Adjust Specifies whether there is one or more applied entries, which need to be adjusted. 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
FactBoxes Control1903523907 part Page 9125 “Item Application FactBox” —

Actions

Group Action ToolTip Runs
View Applied Entries View the ledger entries that have been applied to this record.
Unapplied Entries View entries that you have unapplied.
Entry Dimensions View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.
Value Entries View the history of posted amounts that affect the value of the item. Value entries are created for every transaction with the item. Page 5802 “Value Entries”
Reservation Entries View the entries for every reservation that is made, either manually or automatically.
Functions Reapply Reapply entries that you have removed.
Undo Manual Changes Undo your previous application change.

Procedures

  • SetRecordToShow(RecordToSet: Record "Item Ledger Entry")

Plus 9 local procedures.

Triggers

OnAfterGetCurrRecord, OnFindRecord, OnOpenPage, OnQueryClosePage

Relations

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

Evidence 2 sources