Page 9309 "Purchase Credit Memos"
Base Application · Microsoft.Purchases.Document
Across versions
- BC23-26present
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 14 connected objects and pages
Base Application · Microsoft.Purchases.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Purchase Credit Memos |
| 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 Cr. Memo No. | Vendor Cr. Memo 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 location where the items are to be shipped. This field acts as the default location for new lines. You can update the location code for individual lines as needed. | |
| 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. The program calculates the date using the Payment Terms Code and Document Date fields. | |
| 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 | |
| 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 | |
| Applies-to Doc. Type | Applies-to Doc. Type | Specifies the type of the posted document that this document or journal line will be applied to when you post, for example to register payment. from the table field | |
| Job Queue Status | Job Queue Status | Specifies the status of a job queue entry that handles the posting of purchase credit memos. | |
| 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 |
|---|---|---|---|
| Credit Memo | 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” | |
| Vendor | View or edit detailed information about the vendor on the purchase document. | Page 26 “Vendor Card” | |
| 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. | ||
| 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. | ||
| 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 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. | ||
| Sales | Vendor - Top 10 List (Obsolete) obsolete Pending 28.0; #if not CLEAN28 | View a list of the vendors from whom you purchase the most or to whom you owe the most. | Report 311 “Vendor - Top 10 List” |
| Vendor - Purchase List | — | Report 309 “Vendor - Purchase List” | |
| Purchase Statistics | — | Report 312 “Purchase Statistics” | |
| Finance | Vendor - Balance to Date | — | Report 321 “Vendor - Balance to Date” |
| Vendor - Trial Balance | — | Report 329 “Vendor - Trial Balance” | |
| Vendor - Detail. Trial Balance | — | Report 304 “Vendor - Detail Trial Balance” | |
| Vendor - Summary Aging (Obsolete) obsolete Pending 28.0; #if not CLEAN28 | View, print, or save a summary of the payables owed to each vendor, divided into three time periods. The report can be used to prepare liquidity analyses. | Report 305 “Vendor - Summary Aging” | |
| Aged Accounts Payable (Obsolete) obsolete Pending 28.0; #if not CLEAN28 | View an overview of when your payables to vendors are due or overdue (divided into four periods). You must specify the date you want aging calculated from and the length of the period that each column will contain data for. | Report 322 “Aged Accounts Payable” | |
| Vendor - Payment Receipt | — | Report 411 “Vendor - Payment Receipt” |
Events published
Procedures
4 local procedures, no public ones.
Triggers
OnAfterGetRecord, OnAfterGetCurrRecord, OnOpenPage
Relations
- card page Page 52 “Purchase Credit Memo”
- 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.” (5 calls:
PostDocument → IsEnabled,PostDocument → ShowPostedConfirmationMessageCode,ShowPostedConfirmationMessage → ShowConfirm, …) - Codeunit 1320 “Lines Instruction Mgt.” (2 calls:
CheckPurchaseCheckAllLinesHaveQuantityAssigned → PurchaseCheckAllLinesHaveQuantityAssigned,PostDocument → PurchaseCheckAllLinesHaveQuantityAssigned) - Codeunit 1535 “Approvals Mgmt.” (2 calls:
SetControlAppearance → CanCancelApprovalForRecord,SetControlAppearance → HasOpenApprovalEntries) - Codeunit 1543 “Workflow Webhook Management” (1 call:
SetControlAppearance → GetCanRequestAndCanCancel) - Codeunit 1630 “Office Management” (1 call:
OnOpenPage → IsAvailable) - Page 140 “Posted Purchase Credit Memo” (1 call:
PostDocument → (object))
Called by
- Codeunit 1312 “Vendor Mgt.” (1 call:
DrillDownOnOutstandingCrMemos → (object))
Recent changes
- 2026-08-04 #9549 636017 Move Purchases report action tooltips to report objects (main, BC30, refactor)
Documented on Microsoft Learn
- Analyze data in lists with Copilot (preview)
- Analyze list page and query data using data analysis
- Process returns or cancellations
- Record purchases with purchase invoices
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 Credit Memos"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.