Table 343 "Item Application Entry History"

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

Properties

Property	Value
Caption	Item Application Entry History
DataClassification	CustomerContent
Permissions	TableData “Item Application Entry History” = ri

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	Entry No. Δ BC28	Integer	Specifies the number of the entry, as assigned from the specified number series when the entry was created.
2	Item Ledger Entry No. Δ BC28	Integer	Specifies the entry number of the item ledger entry, for which the item application entry was recorded.	TableRelation Table 32 “Item Ledger Entry” (Item Ledger Entry)
3	Inbound Item Entry No. Δ BC28	Integer	Specifies the number of the item ledger entry corresponding to the inventory increase or positive quantity in inventory for this entry.	TableRelation Table 32 “Item Ledger Entry” (Item Ledger Entry)
4	Outbound Item Entry No. Δ BC28	Integer	Specifies the number of the item ledger entry corresponding to the inventory decrease for this entry.	TableRelation Table 32 “Item Ledger Entry” (Item Ledger Entry)
9	Primary Entry No. Δ BC28	Integer	Specifies a unique identifying number for each item application entry history record.
11	Quantity Δ BC28	Decimal	Specifies the item quantity being applied from the inventory decrease in the Outbound Item Entry No. field, to the inventory increase in the Inbound Item Entry No. field.
21	Posting Date Δ BC28	Date	Specifies a date that corresponds to the posting date of the item ledger entry, for which this item application entry was created.
23	Transferred-from Entry No. Δ BC28	Integer	Specifies the item ledger entry number of the inventory increase, if an item application entry originates from an item location transfer.	TableRelation Table 32 “Item Ledger Entry” (Item Ledger Entry)
25	Creation Date	DateTime	—
26	Created By User	Code[50]	—	TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation
27	Last Modified Date	DateTime	—
28	Last Modified By User	Code[50]	—	TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation
29	Deleted Date	DateTime	—
30	Deleted By User	Code[50]	—	TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation
5800	Cost Application Δ BC28	Boolean	Specifies which application entries should have the cost forwarded, or simply included, in an average cost calculation.
5804	Output Completely Invd. Date Δ BC28	Date	Specifies the outbound item entries have been completely invoiced.

Keys

Key1: Primary Entry No. (clustered)
Key2: Entry No.

Procedures

GetNextEntryNo(): Integer + BC26
GetLastEntryNo(): Integer Δ BC26

Relations

drill-down page Page 523 “Item Application Entry History”
lookup page Page 523 “Item Application Entry History”
Inbound Item Entry No.: TableRelation Table 32 “Item Ledger Entry”
Item Ledger Entry No.: TableRelation Table 32 “Item Ledger Entry”
Outbound Item Entry No.: TableRelation Table 32 “Item Ledger Entry”
Transferred-from Entry No.: TableRelation Table 32 “Item Ledger Entry”

Pages and codeunits on this table

Page 523 “Item Application Entry History” (source table)

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 703 “Find Record Management” (1 call: GetLastEntryNo → GetLastEntryIntFieldValue)
Codeunit 9500 “Sequence No. Mgt.” (1 call: GetNextEntryNo → GetNextSeqNo)

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: "table", object_name: "Item Application Entry History"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.