Page 390 "Phys. Inventory Ledger Entries"
Base Application · Microsoft.Inventory.Counting.Journal
Across versions
- BC23-30present
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Inventory.Counting.Journal · captioned “Physical Inventory Ledger Entries” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Physical Inventory Ledger Entries |
| SourceTable | Phys. Inventory Ledger Entry |
| PageType | List |
| UsageCategory | History |
| 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 date on which you posted the Physical Inventory Journal that created this ledger entry. from the table field |
| Entry Type | Entry Type | Specifies the type of transaction that was posted from the Physical Inventory Journal that created the ledger entry. from the table field | |
| Document No. | Document No. | Specifies the document number on the physical inventory ledger entry. from the table field | |
| Item No. | Item No. | Specifies the number of the item in the ledger 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 item in the ledger 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 of the location for the item in the ledger entry. from the table field | |
| Qty. (Calculated) | Qty. (Calculated) | Specifies the quantity on hand, as calculated by the program, of the item in the ledger entry. | |
| Qty. (Phys. Inventory) | Qty. (Phys. Inventory) | Specifies the actual quantity on hand, as determined by taking a physical inventory, of the item in the ledger entry. | |
| Quantity | Quantity | Specifies the difference between the quantities in the Quantity (Calculated) field and the Quantity (Physical Inventory) field for ledger entry. from the table field | |
| Unit Amount | Unit Amount | Specifies the amount for one unit of the item in the ledger entry. from the table field | |
| Amount | Amount | Specifies the total amount for the items in the ledger entry. from the table field | |
| Unit Cost | Unit Cost | Specifies the cost of one unit of the item or resource on the line. from the table field | |
| User ID | User ID | Specifies the ID of the user who posted the entry, to be used, for example, in the change log. from the table field | |
| Source Code | Source Code | Specifies the source code that specifies where the entry was created. from the table field | |
| Reason Code | Reason Code | Specifies the reason code, a supplementary source code that enables you to trace the entry. from the table field | |
| Last Item Ledger Entry No. | Last Item Ledger Entry No. | Specifies the number of the last item ledger entry that provided the basis for the physical inventory ledger 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 | |
| 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. | ||
| 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.) | |
| Delete Entries | — | Report 789 “Delete Phys. Inventory Ledger” |
Procedures
1 local procedures, no public ones.
Triggers
OnOpenPage
Relations
- source table Table 281 “Phys. Inventory Ledger Entry”
Pages and codeunits on this table
- Table 281 “Phys. Inventory Ledger Entry” (drill-down page)
- Table 281 “Phys. Inventory Ledger Entry” (lookup page)
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)
Called by
- Codeunit 20 “Posting Preview Event Handler” (1 call:
ShowEntries → (object)) - Codeunit 390 “Item Reg.-Show Inventory Ledg.” (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: "Phys. Inventory Ledger Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.