Page 5804 "Applied Item Entries"
Base Application · Microsoft.Inventory.Ledger
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Inventory.Ledger · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Applied Item Entries |
| 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 that the entry is created from. 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 | |
| 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 | |
| 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 | |
| Location Code | Location Code | Specifies the code for the location that the entry is linked to. from the table field | |
| Applied Quantity | ApplQty |
Specifies how many units of the item that have been applied. | |
| Quantity | Qty |
Specifies the total quantity of items that have been applied. | |
| 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 | |
| Reserved Quantity | Reserved Quantity | Specifies how many units of the item on the line have been reserved. from the table field | |
| Open | Open | Specifies whether the entry has been fully applied to. 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 | |
| Drop Shipment | Drop Shipment | Specifies if your vendor ships the items directly to your customer. 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 order that the entry was created in. from the table field | |
| Order No. | Order No. | Specifies the number of the order that created the entry. 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 |
|---|---|---|---|
| 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” | |
| Application | Applied Entries | View the ledger entries that have been applied to this record. | |
| Reservation Entries | View the entries for every reservation that is made, either manually or automatically. | ||
| Functions | Order Tracking | Tracks the connection of a supply to its corresponding demand. This can help you find the original demand that created a specific production order or purchase order. | |
| Processing | Find entries… | Find entries and documents that exist for the document number and posting date on the selected document. (Formerly this action was named Navigate.) |
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetRecord
Relations
- source table Table 32 “Item Ledger Entry”
Called by
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 5801 “Show Applied Entries” (1 call:
OnRun → (object))
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: "Applied Item Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.