BC Observatoryunofficial, made by waldo
pagePurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Page 9307 "Purchase Order List"

Base Application · Microsoft.Purchases.Document

Open in Claude9307.mdSource on GitHub

Across versions

  1. BC23-26present
  2. BC27declaration changed
  3. BC28-30unchanged

Neighbourhood 21 connected objects and pages

Table 38 "Purchase Header" (relates to)Purchase HeaderPage 50 "Purchase Order" (pages and codeunits on it)Purchase OrderPage extension 20525 "Subc. PurchOrderList" (extended by)Subc. PurchOrderListPage extension 6137 "E-Doc. Purchase Order List" (extended by)E-Doc. Purchase Order ListCodeunit 1535 "Approvals Mgmt." (calls, 2 links)Approvals Mgmt.Codeunit 1018 "Purchase Doc. From Job" (calls)Purchase Doc. From JobCodeunit 1314 "Purch. Doc. From Sales Doc." (calls)Purch. Doc. From Sales Doc.Codeunit 1543 "Workflow Webhook Management" (calls)Workflow Webhook ManagementTable 9055 "Purchase Cue" (calls)Purchase CueAd-hoc analyses in purchasing (Learn pages)Ad-hoc analyses in purchasingAnalytics in purchasing (Learn pages)Analytics in purchasingAnalyze data in lists with Copilot (preview) (Learn pages)Analyze data in lists with C…Analyze list page and query data using data analysis (Learn pages)Analyze list page and query …Correct prepayments (Learn pages)Create prepayment invoices (Learn pages)Create prepayment invoicesInvoice prepayments (Learn pages)Overview of tasks to manage to purchase (Learn pages)Process returns or cancellations (Learn pages)Record purchases with purchase invoices (Learn pages)Record special purchase prices and discounts (Learn pages)Use E-Documents in the purchase process (Learn pages)

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.Document · captioned “Purchase Orders” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Purchase Orders
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 a unique number that identifies the purchase order. The number can be generated automatically from a number series, or you can number each of them manually. from the table field
Buy-from Vendor No. Buy-from Vendor No. Specifies the vendor who will deliver the goods or services. Each vendor has a unique number to help you track related documents. The number can come from a number series or be added manually. 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 that you’re buying from. By default, the same vendor is suggested as the pay-to vendor. If needed, you can specify a different pay-to vendor on the document. from the table field
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
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 purchase invoice is due for payment. from the table field
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 to the ship-to address. The value in the field is used to calculate the latest date you can order the items to have them delivered on the requested receipt date. If you do not need delivery on a specific date, you can leave the field blank. from the table field
Job Queue Status Job Queue Status Specifies the status of a job queue entry that handles the posting of purchase orders. from the table field
Amount Received Not Invoiced excl. VAT (LCY) A. Rcd. Not Inv. Ex. VAT (LCY) Specifies the amount excluding VAT for the items on the order that have been received but are not yet invoiced. from the table field
Amount Received Not Invoiced (LCY) Amt. Rcd. Not Invoiced (LCY) Specifies the sum, in LCY, for items that have been received but have not yet been invoiced. The value in the Amt. Rcd. Not Invoiced (LCY) field is used for entries in the Purchase Line table of document type Order to calculate and update the contents of this field. from the table field
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
Posting Description Posting Description Specifies additional posting information for the document. After you post the document, the description can add detail to vendor and customer ledger entries. from the table field
Your Reference Your Reference Specifies the vendor’s reference. from the table field
Vendor Order No. Vendor Order No. Specifies the vendor’s order number. from the table field
FactBoxes Documents part Page 1178 “Doc. Attachment List Factbox” —
IncomingDocAttachFactBox part Page 193 “Incoming Doc. Attach. FactBox” —
Control1901138007 part Page 9093 “Vendor Details FactBox” —

Actions

Group Action ToolTip Runs
Order 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.
Statistics View statistical information, such as the value of posted entries, for the record. Page 403 “Purchase Order 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”
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.
Comments View or add comments for the record. Page 66 “Purch. Comment Sheet”
Documents Receipts View a list of posted purchase receipts for the order. Page 145 “Posted Purchase Receipts”
Invoices View a list of ongoing purchase invoices for the order.
Prepayment Invoices View related posted purchase invoices that involve a prepayment. Page 146 “Posted Purchase Invoices”
Prepayment Credit Memos View related posted purchase credit memos that involve a prepayment. Page 147 “Posted Purchase Credit Memos”
Warehouse Invt. Put-away/Pick Lines View items that are inbound or outbound on inventory put-away or inventory pick documents for the purchase order. Page 5774 “Warehouse Activity List”
Whse. Receipt Lines View ongoing warehouse receipts for the document, in advanced warehouse configurations. Page 7342 “Whse. Receipt Lines”
Warehouse Put-away Lines View items that are inbound on warehouse put-away documents for the purchase order. Page 5785 “Warehouse Activity Lines”
Print Print Prepare to print the document. The report request window for the document opens where you can specify what to include on the print-out.
Send by Email Finalize and prepare to email the document. The Send Email window opens prefilled with the vendor’s email address so you can add or edit information.
Send Prepare to send the document according to the vendor’s sending profile, such as attached to an email. The Send document to window opens first so you can confirm or select a sending profile.
Attach as PDF Create a PDF file and attach it to the document.
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
Functions Send IC Purchase Order Send the document to the intercompany outbox or directly to the intercompany partner if automatic transaction sending is enabled.
Delete Invoiced Orders — Report 499 “Delete Invoiced Purch. Orders”
Request Approval Send Approval Request Request approval of the document.
Cancel Approval Request Cancel the approval request.
Warehouse Create Whse. Receipt Create a warehouse receipt to start a receive and put-away process according to an advanced warehouse configuration.
Create Inventory Put-away/Pick Create an inventory put-away or inventory pick to handle items on the document according to a basic warehouse configuration that does not require warehouse receipt or shipment documents.
Posting 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 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.
Post and Print Finalize and prepare to print the document or journal. The values and quantities are posted to the related accounts. A report request window where you can specify what to include on the print-out.
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.
Reporting Analyze Purchase Orders Analyze (group, summarize, pivot) your Purchase Order performance against vendors and goods/services bought, including outstanding vs. posted quantities and amounts. Query 488 “Purch. Order Perf. Analysis”

Procedures

  • SkipShowingLinesWithoutVAT()

Plus 2 local procedures.

Triggers

OnAfterGetRecord, OnAfterGetCurrRecord, OnOpenPage

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.

Called by

Recent changes

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: "Purchase Order List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 8 of 13 sources

Show 5 more