pagePurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Page 5709 "Get Receipt Lines"

Base Application · Microsoft.Purchases.History

Across versions

  1. BC23-27present
  2. BC281 procedures added, 1 procedures removed
  3. BC29-30unchanged

Neighbourhood 4 connected objects and pages

Table 121 "Purch. Rcpt. Line" (relates to)Purch. Rcpt. LinePage extension 99000781 "Mfg. Get Receipt Lines" (extended by)Mfg. Get Receipt LinesCodeunit 74 "Purch.-Get Receipt" (calls, 2 links)Purch.-Get ReceiptUse item charges to account for extra trade costs (Learn pages)Use item charges to account …

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Properties

Property Value
Caption Get Receipt Lines
SourceTable Purch. Rcpt. Line
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 Document No. Document No. Specifies the number of the related document. from the table field
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 a description of additional receipts posted.
Description 2 Description 2 Specifies information in addition to the description. from the table field
Currency Code Currency Code Specifies the currency that is used on the entry. 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 a code for the location where you want the items to be placed when they are received. 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
Quantity Quantity Specifies the quantity of the item on the line.
Job No. Job No. Specifies the number of the related project. from the table field
Expected Receipt Date Expected Receipt Date Specifies the date you expect the items to be available in your warehouse. If you leave the field blank, it will be calculated as follows: Planned Receipt Date + Safety Lead Time + Inbound Warehouse Handling Time = Expected Receipt Date. from the table field
Quantity Invoiced Quantity Invoiced Specifies how many units of the item on the line have been posted as invoiced. from the table field
Qty. Rcd. Not Invoiced Qty. Rcd. Not Invoiced Specifies the quantity of the received item that has been posted as received but that has not yet been posted as invoiced. from the table field
Order No. Order No. Specifies the line number of the order that created the entry.
Vendor Order No. Vendor Order No. Specifies the vendor’s order number.
Vendor Shipment No. Vendor Shipment No. Specifies the vendor’s shipment number. It is inserted in the corresponding field on the source document during posting.
Vendor Item No. Vendor Item No. Specifies the number that the vendor uses for this item. from the table field
Item Reference No. Item Reference No. Specifies the referenced item number.
Your Reference Your Reference Specifies the vendor’s reference.
Pay-to Vendor No. Pay-to Vendor No. Specifies the number of the vendor that you received the invoice from. from the table field
Purchasing Code Purchasing Code Specifies the purchasing code associated with the receipt line. from the table field

Actions

Group Action ToolTip Runs
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 Entries View serial, lot or package numbers that are assigned to items.

Events published

  • OnBeforeSetPurchHeader(var PurchaseHeader: Record "Purchase Header"; var IsHandled: Boolean; var PurchHeader: Record "Purchase Header") (integration)
  • OnBeforeOnQueryClosePage(CloseAction: Action; var Result: Boolean; var IsHandled: Boolean) (integration)
  • OnBeforeIsFirstDocLine(var PurchRcptLine: Record "Purch. Rcpt. Line"; var TempPurchRcptLine: Record "Purch. Rcpt. Line" temporary) (integration)

Procedures

  • SetPurchHeader(var PurchHeader2: Record "Purchase Header")
  • IsFirstDocLine(): Boolean (protected)
  • SetSelectionOnly(NewSelectionOnly: Boolean) + BC28

Plus 2 local procedures.

Triggers

OnAfterGetRecord, OnQueryClosePage

Relations

Extended by

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.

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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: "Get Receipt Lines"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources