Page 145 "Posted Purchase Receipts"
Base Application · Microsoft.Purchases.History
Across versions
- BC23present
- BC24declaration changed
- BC25unchanged
- BC26declaration changed
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Purchases.History · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Posted Purchase Receipts |
| SourceTable | Purch. Rcpt. Header |
| 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 | No. | No. | Specifies the number of the involved entry or record, according to the specified number series. |
| Buy-from Vendor No. | Buy-from Vendor No. | Specifies the name of the vendor who delivered the items. from the table field | |
| Order Address Code | Order Address Code | Specifies the order address of the related vendor. from the table field | |
| Buy-from Vendor Name | Buy-from Vendor Name | Specifies the name of the vendor who delivered the items. from the table field | |
| Buy-from Post Code | Buy-from Post Code | Specifies the post code of the vendor who delivered the items. from the table field | |
| Buy-from Country/Region Code | Buy-from Country/Region Code | Specifies the city of the vendor who delivered the items. | |
| Buy-from Contact | Buy-from Contact | Specifies the name of the contact person at the vendor who delivered the items. from the table field | |
| Pay-to Vendor No. | Pay-to Vendor No. | Specifies the number of the vendor that you receiv or received the invoice from. from the table field | |
| Pay-to Name | Pay-to Name | Specifies the name of the vendor who you received the invoice from. from the table field | |
| Pay-to Post Code | Pay-to Post Code | Specifies the post code of the vendor that you received the invoice from. from the table field | |
| Pay-to Country/Region Code | Pay-to Country/Region Code | Specifies the country/region code of the address. | |
| Pay-to Contact | Pay-to Contact | Specifies the name of the person to contact about an invoice from this vendor. from the table field | |
| Ship-to Code | Ship-to Code | Specifies a code for an alternate shipment address if you want to ship to another address than the one that has been entered automatically. This field is also used in case of drop shipment. from the table field | |
| Ship-to Name | Ship-to Name | Specifies the name of the customer at the address that the items are shipped to. | |
| Ship-to Post Code | Ship-to Post Code | Specifies the postal code of the address that the items are shipped to. | |
| Ship-to Country/Region Code | Ship-to Country/Region Code | Specifies the country/region code of the address that the items are shipped to. | |
| Ship-to Contact | Ship-to Contact | Specifies the name of the contact person at the address that the items are shipped to. | |
| Posting Date | Posting Date | Specifies the date the purchase header was posted. from the table field | |
| Purchaser Code | Purchaser Code | Specifies which purchaser is assigned to the vendor. 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 items on the receipt were registered. | |
| No. Printed | No. Printed | Specifies how many times the document has been printed. from the table field | |
| Document Date | Document Date | Specifies the date when the related document was created. from the table field | |
| Shipment Method Code | Shipment Method Code | Specifies the delivery conditions of the related shipment, such as free on board (FOB). from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Receipt | Statistics | View statistical information, such as the value of posted entries, for the record. | Page 399 “Purchase Receipt Statistics” |
| Comments | View or add comments for the record. | Page 66 “Purch. Comment Sheet” | |
| 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. | ||
| Processing | Prepare to print the document. A report request window for the document opens where you can specify what to include on the print-out. | ||
| 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.) |
Events published
OnBeforePrintRecords(PurchRcptHeaderRec: Record "Purch. Rcpt. Header"; var ToPrint: Record "Purch. Rcpt. Header")(integration)
Procedures
GetSelectedRecords(var TempPurchRcptHeader: Record "Purch. Rcpt. Header" temporary)
Triggers
OnOpenPage
Relations
- card page Page 136 “Posted Purchase Receipt”
- source table Table 120 “Purch. Rcpt. Header”
Pages and codeunits on this table
- Table 120 “Purch. Rcpt. Header” (drill-down page)
- Table 120 “Purch. Rcpt. Header” (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 1630 “Office Management” (1 call:
OnOpenPage → IsAvailable)
Called by
- Page 46 “Sales Order Subform” (1 call:
OpenSpecialPurchOrderForm → (object))
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: "Posted Purchase Receipts"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.