Page 9308 "Purchase Invoices"
Base Application · Microsoft.Purchases.Document
- 42controls
- 16actions
- 5procedures
- 1events
- 7Learn pages
- 1countries replace it
- 5objects it calls
- 1objects call it
Across versions
- BC23-26present
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 17 connected objects and pages
Base Application · Microsoft.Purchases.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Purchase Invoices |
| SourceTable | Purchase Header |
| PageType | List |
| UsageCategory | Lists |
| 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. | |
| 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. | |
| Vendor Authorization No. | Vendor Authorization No. | Specifies the compensation agreement identification number, sometimes referred to as the RMA No. (Returns Materials Authorization). from the table field | |
| Vendor Invoice No. | Vendor Invoice No. | Specifies the document number of the original document you received from the vendor. You can require the document number for posting, or let it be optional. By default, it’s required, so that this document references the original. Making document numbers optional removes a step from the posting proc… 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. from the table field | |
| 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 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. from the table field | |
| 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. from the table field | |
| Ship-to Post Code | Ship-to Post Code | Specifies the postal code of the address that the items are shipped to. from the table field | |
| Ship-to Country/Region Code | Ship-to Country/Region Code | Specifies the country/region code of the address that the items are shipped to. from the table field | |
| Ship-to Contact | Ship-to Contact | Specifies the name of the contact person at the address that the items are shipped to. from the table field | |
| Posting Date | Posting Date | Specifies the date when the posting of the purchase document will be recorded. 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 are to be received. When you select the vendor and the vendor has a location assigned, the value is taken from the Vendor card. If the vendor has no location, but a Responsibility Center is populated, the location code is taken from the Responsibil… from the table field | |
| Purchaser Code | Purchaser Code | Specifies which purchaser is assigned to the vendor. from the table field | |
| Assigned User ID | Assigned User ID | Specifies the ID of the user who is responsible for the document. from the table field | |
| Currency Code | Currency Code | Specifies the code of the currency of the amounts on the purchase lines. from the table field | |
| Document Date | Document Date | Specifies the date when the related document was created. from the table field | |
| Status | Status | Specifies whether the record is open, waiting to be approved, invoiced for prepayment, or released to the next stage of processing. from the table field | |
| Payment Terms Code | Payment Terms Code | Specifies a formula that calculates the payment due date, payment discount date, and payment discount amount. from the table field | |
| Due Date | Due Date | Specifies when the invoice is due. | |
| Payment Discount % | Payment Discount % | Specifies the payment discount percent granted if payment is made on or before the date in the Pmt. Discount Date field. from the table field | |
| Payment Method Code | Payment Method Code | Specifies how to make payment, such as with bank transfer, cash, or check. 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 | |
| Requested Receipt Date | Requested Receipt Date | Specifies the date that you want the vendor to deliver your order. The field is used to calculate the latest date you can order, as follows: requested receipt date - lead time calculation = order date. If you do not need delivery on a specific date, you can leave the field blank. | |
| Your Reference | Your Reference | Specifies the vendor’s reference. from the table field | |
| Job Queue Status | Job Queue Status | Specifies the status of a job queue entry that handles the posting of purchase invoices. | |
| Amount | Amount | Specifies the sum of amounts on all the lines in the document. This will include invoice discounts. from the table field | |
| Amount Including VAT | Amount Including VAT | Specifies the sum of amounts, including VAT, on all the lines in the document. This will include invoice discounts. from the table field | |
| FactBoxes | Documents | part Page 1178 “Doc. Attachment List Factbox” | — |
| PowerBIEmbeddedReportPart | part Page 6325 “Power BI Embedded Report Part” | — | |
| IncomingDocAttachFactBox | part Page 193 “Incoming Doc. Attach. FactBox” | — | |
| Control1901138007 | part Page 9093 “Vendor Details FactBox” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Invoice | Statistics | View statistical information, such as the value of posted entries, for the record. | Page 161 “Purchase Statistics” |
| Vendor Statistics | View statistical information, such as the value of posted entries, for the buy-from vendor on the purchase document. | Page 152 “Vendor 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. | ||
| Invoice | Approvals | View a list of the records that are waiting to be approved. For example, you can see who requested the record to be approved, when it was sent, and when it is due to be approved. | |
| Vendor | View or edit detailed information about the vendor on the purchase document. | Page 26 “Vendor Card” | |
| Release | Release | Release the document to the next stage of processing. You must reopen the document before you can make changes to it. | |
| Reopen | Reopen the document to change it after it has been approved. Approved documents have the Released status and must be opened before they can be changed | ||
| Request Approval | Send Approval Request | Request approval of the document. | |
| Cancel Approval Request | Cancel the approval request. | ||
| Posting | Post | Finalize the document or journal by posting the amounts and quantities to the related accounts in your company books. | |
| Preview Posting | Review the different types of entries that will be created when you post the document or journal. | ||
| Test Report | View a test report so that you can find and correct any errors before you perform the actual posting of the journal or document. | ||
| Post and Print | Finalize and print the document or journal. The values and quantities are posted to the related accounts. | ||
| Post Batch | Post several documents at once. A report request window opens where you can specify which documents to post. | ||
| Remove From Job Queue | Remove the scheduled processing of this record from the job queue. |
Events published
Procedures
Post(PostingCodeunitID: Integer)VerifyTotal(PurchaseHeader: Record "Purchase Header")
Plus 2 local procedures.
Triggers
OnAfterGetRecord, OnAfterGetCurrRecord, OnInit, OnOpenPage
Relations
- card page Page 51 “Purchase Invoice”
- source table Table 38 “Purchase Header”
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.
- Codeunit 1330 “Instruction Mgt.” (3 calls:
ShowPostedConfirmationMessage → ShowConfirm,ShowPostedConfirmationMessage → ShowPostedConfirmationMessageCode,ShowPostedConfirmationMessage → ShowPostedDocument) - Codeunit 1535 “Approvals Mgmt.” (2 calls:
SetControlAppearance → CanCancelApprovalForRecord,SetControlAppearance → HasOpenApprovalEntries) - Codeunit 1320 “Lines Instruction Mgt.” (1 call:
Post → PurchaseCheckAllLinesHaveQuantityAssigned) - Codeunit 1543 “Workflow Webhook Management” (1 call:
SetControlAppearance → GetCanRequestAndCanCancel) - Codeunit 9179 “Application Area Mgmt. Facade” (1 call:
Post → IsFoundationEnabled)
Called by
- Codeunit 1312 “Vendor Mgt.” (1 call:
DrillDownOnOutstandingInvoices → (object))
Countries that replace it
Documented on Microsoft Learn
- Settle purchase invoices promptly
- Use E-Documents in the purchase process
- Match Purchase Invoice Drafts to Purchase Orders
- Process returns or cancellations
- Purchase items for a sale
- Record purchases with purchase invoices
- Combine Receipts or PO Lines on a Single Invoice
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: "Purchase Invoices"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.
Evidence 8 sources
- codesrc/Layers/W1/BaseApp/Purchases/Document/PurchaseInvoices.Page.alreleases/29.x @ ea08af5e
- learnSettle purchase invoices promptly
- learnUse E-Documents in the purchase process
- learnMatch Purchase Invoice Drafts to Purchase Orders
- learnProcess returns or cancellations
- learnPurchase items for a sale
- learnRecord purchases with purchase invoices
- learnCombine Receipts or PO Lines on a Single Invoice