Page 167 "Item Ledger Entries Preview"

Base Application · Microsoft.Inventory.Ledger · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Item Ledger Entries Preview
SourceTable	Item Ledger Entry
PageType	List

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 entry’s posting date. from the table field
	Entry Type	Entry Type	Specifies which type of transaction the entry is created from.
	Document Type	Document Type	Specifies what type of document was posted to create the item ledger 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
	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
	Item No.	Item No.	Specifies the number of the item in the entry. from the table field
	Variant Code	Variant Code	Specifies the variant of the item on the line. from the table field
	Description	Description	Specifies a description of the entry. from the table field
	Return Reason Code	Return Reason Code	Specifies the code explaining why the item was returned. from the table field
	Global Dimension 1 Code	Global Dimension 1 Code	Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field
	Global Dimension 2 Code	Global Dimension 2 Code	Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field
	Expiration Date	Expiration Date	Specifies the last date that the item on the line can be used. 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
	Package No.	Package No.	Specifies a package number if the posted item carries such a number. from the table field
	Location Code	Location Code	Specifies the code for the location that the entry is linked to. from the table field
	Quantity	Quantity	Specifies the number of units of the item in the item entry. 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
	Remaining Quantity	Remaining Quantity	Specifies the quantity in the Quantity field that remains to be processed. 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
	Reserved Quantity	Reserved Quantity	Specifies how many units of the item on the line have been reserved. from the table field
	Qty. per Unit of Measure	Qty. per Unit of Measure	Specifies the quantity per item unit of measure. from the table field
	Sales Amount (Expected)	`SalesAmountExpected`	Specifies the expected sales amount in LCY. Choose the field to see the value entries that make up this amount.
	Sales Amount (Actual)	`SalesAmountActual`	Specifies the sum of the actual sales amounts if you post.
	Cost Amount (Expected)	`CostAmountExpected`	Specifies the expected cost amount of the item. Expected costs are calculated from yet non-invoiced documents.
	Cost Amount (Actual)	`CostAmountActual`	Specifies the sum of the actual cost amounts if you post.
	Cost Amount (Non-Invtbl.)	`CostAmountNonInvtbl`	Specifies the sum of the non-inventoriable cost amounts if you post. Typical non-inventoriable costs come from item charges.
	Cost Amount (Expected) (ACY)	`CostAmountExpectedACY`	Specifies the expected cost amount of the item. Expected costs are calculated from yet non-invoiced documents.
	Cost Amount (Actual) (ACY)	`CostAmountActualACY`	Specifies the actual cost amount of the item.
	Cost Amount (Non-Invtbl.) (ACY)	`CostAmountNonInvtblACY`	Specifies the sum of the non-inventoriable cost amounts if you post. Typical non-inventoriable costs come from item charges.
	Completely Invoiced	Completely Invoiced	Specifies if the entry has been fully invoiced or if more posted invoices are expected. Only completely invoiced entries can be revalued. from the table field
	Open	Open	Specifies if the entry has been fully applied to.
	Drop Shipment	Drop Shipment	Specifies if your vendor ships the items directly to your customer. from the table field
	Assemble to Order	Assemble to Order	Specifies if the posting represents an assemble-to-order sale. 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
	Order Type	Order Type	Specifies which type of transaction the entry is created from.
	Order No.	Order No.	Specifies the number of the order that created the entry. from the table field
	Order Line No.	Order Line No.	Specifies the line number of the order that created the entry. from the table field
	Prod. Order Comp. Line No.	Prod. Order Comp. Line No.	Specifies the line number of the production order component. from the table field
	Job No.	Job No.	Specifies the number of the related project. from the table field
	Job Task No.	Job Task No.	Specifies the number of the related project task. from the table field
	Dimension Set ID	Dimension Set ID	Specifies a reference to a combination of dimension values. The actual values are stored in the Dimension Set Entry table. from the table field
	Shortcut Dimension 3 Code	Shortcut Dimension 3 Code	Specifies the code for Shortcut Dimension 3, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 4 Code	Shortcut Dimension 4 Code	Specifies the code for Shortcut Dimension 4, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 5 Code	Shortcut Dimension 5 Code	Specifies the code for Shortcut Dimension 5, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 6 Code	Shortcut Dimension 6 Code	Specifies the code for Shortcut Dimension 6, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 7 Code	Shortcut Dimension 7 Code	Specifies the code for Shortcut Dimension 7, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 8 Code	Shortcut Dimension 8 Code	Specifies the code for Shortcut Dimension 8, which is one of dimension codes that you set up in the General Ledger Setup window. from the table field

Actions

Group	Action	ToolTip	Runs
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.
	Set Dimension Filter	Limit the entries according to the dimension filters that you specify. NOTE: If you use a high number of dimension combinations, this function may not work and can result in a message that the SQL server only supports a maximum of 2100 parameters.

Procedures

Set(var TempItemLedgerEntry2: Record "Item Ledger Entry" temporary; var TempValueEntry2: Record "Value Entry" temporary)

Plus 2 local procedures.

Triggers

OnAfterGetRecord, OnOpenPage

Relations

source table Table 32 “Item Ledger Entry”

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 408 “DimensionManagement” (1 call: SetDimVisibility → UseShortcutDims)

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