Page 528 "Posted Purchase Receipt Lines"

Base Application · Microsoft.Purchases.History · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Posted Purchase Receipt Lines
SourceTable	Purch. Rcpt. Line
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	Document No.	Document No.	Specifies the receipt number.
	Buy-from Vendor No.	Buy-from Vendor No.	Specifies the name of the vendor who delivered the items. from the table field
	Type	Type	Specifies the line type. from the table field
	No.	No.	Specifies the number of the involved entry or record, according to the specified number series. from the table field
	Variant Code	Variant Code	Specifies the variant of the item on the line. from the table field
	Description	Description	Specifies either the name of or a description of the item or general ledger account. from the table field
	Description 2	Description 2	Specifies information in addition to the description. from the table field
	Shortcut Dimension 1 Code	Shortcut Dimension 1 Code	Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 2 Code	Shortcut Dimension 2 Code	Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field
	Location Code	Location Code	Specifies the code for the location where the receipt line is registered.
	Quantity	Quantity	Specifies the number of units of the item specified on the line. from the table field
	Unit of Measure Code	Unit of Measure Code	Specifies how each unit of the item or resource is measured, such as in pieces or hours. By default, the value in the Base Unit of Measure field on the item or resource card is inserted. from the table field
	Unit of Measure	Unit of Measure	Specifies the name of the item or resource’s unit of measure, such as piece or hour. from the table field
	Appl.-to Item Entry	Appl.-to Item Entry	Specifies the number of the item ledger entry that the document or journal line is applied to. from the table field
	Order No.	Order No.	Specifies the order number this line is associated with.
	Job No.	Job No.	Specifies the number of the related project. from the table field
	Expected Receipt Date	Expected Receipt Date	Specifies the date the items were expected.
	Quantity Invoiced	Quantity Invoiced	Specifies how many units of the item on the line have been posted as invoiced. from the table field

Actions

Group	Action	ToolTip
Line	Show Document	Open the document that the selected line exists on.
	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.
	Item Tracking Lines	View or edit serial, lot and package numbers that are assigned to the item on the document or journal line.

Procedures

GetSelectedRecords(var TempPurchRcptLine: Record "Purch. Rcpt. Line" temporary)

Triggers

OnOpenPage

Relations

source table Table 121 “Purch. Rcpt. Line”

Pages and codeunits on this table

Table 121 “Purch. Rcpt. Line” (drill-down page)
Table 121 “Purch. Rcpt. Line” (lookup page)

Extended by

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.

Table 39 “Purchase Line” (1 call: ShowBlanketOrderPostedReceiptLines → (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: "Posted Purchase Receipt Lines"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.