Page 9302 "Sales Credit Memos"
Base Application · Microsoft.Sales.Document
Across versions
- BC23-26present
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 13 connected objects and pages
Base Application · Microsoft.Sales.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Sales Credit Memos |
| SourceTable | Sales 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. |
| Sell-to Customer No. | Sell-to Customer No. | Specifies the number of the customer. | |
| Sell-to Customer Name | Sell-to Customer Name | Specifies the name of the customer. | |
| External Document No. | External Document No. | Specifies a document number that refers to the customer’s or vendor’s numbering system. from the table field | |
| Sell-to Post Code | Sell-to Post Code | Specifies the postal code of the customer’s main address. from the table field | |
| Sell-to Country/Region Code | Sell-to Country/Region Code | Specifies the country/region code of the customer’s main address. from the table field | |
| Sell-to Contact | Sell-to Contact | Specifies the name of the contact person at the customer’s main address. from the table field | |
| Bill-to Customer No. | Bill-to Customer No. | Specifies the number of the customer that you send or sent the invoice or credit memo to. from the table field | |
| Bill-to Name | Bill-to Name | Specifies the name of the customer that you send or sent the invoice or credit memo to. from the table field | |
| Bill-to Post Code | Bill-to Post Code | Specifies the postal code of the customer’s billing address. from the table field | |
| Bill-to Country/Region Code | Bill-to Country/Region Code | Specifies the country/region code of the customer’s billing address. from the table field | |
| Bill-to Contact | Bill-to Contact | Specifies the name of the contact person at the customer’s billing address. 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 sales 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 placed when they are received. This field acts as the default location for new lines. You can update the location code for individual lines as needed. | |
| Salesperson Code | Salesperson Code | Specifies the name of the sales person who is assigned to the customer. | |
| 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 currency of amounts on the sales document. from the table field | |
| Document Date | Document Date | Specifies the date when the related document was created. from the table field | |
| Campaign No. | Campaign No. | Specifies the number of the campaign that the document is linked to. | |
| Status | Status | Specifies whether the document is open, waiting to be approved, has been invoiced for prepayment, or has been 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 sales invoice must be paid. from the table field | |
| Shipment Date | Shipment Date | Specifies when items on the document are shipped or were shipped. A shipment date is usually calculated from a requested delivery date plus lead time. 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 or task that handles the posting of sales credit memos. | |
| 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 | |
| FactBoxes | Documents | part Page 1178 “Doc. Attachment List Factbox” | — |
| Control1902018507 | part Page 9082 “Customer Statistics FactBox” | — | |
| Control1900316107 | part Page 9084 “Customer Details FactBox” | — | |
| IncomingDocAttachFactBox | part Page 193 “Incoming Doc. Attach. FactBox” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Cr. Memo | Statistics | View statistical information, such as the value of posted entries, for the record. | Page 160 “Sales Statistics” |
| Customer Statistics | View statistical information, such as the value of posted entries, for the sell-to customer on the sales document. | Page 151 “Customer Statistics” | |
| Comments | View or add comments for the record. | Page 67 “Sales 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. | ||
| 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. | ||
| Credit Memo | Customer | View or edit detailed information about the customer. | Page 21 “Customer 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 | 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 Send | Finalize and prepare to send the document according to the customer’s sending profile, such as attached to an email. The Send document to window opens where you can confirm or select a sending profile. | ||
| 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 Reports | Customer - Top 10 List (Obsolete) obsolete Pending 28.0; #if not CLEAN28 | View which customers purchase the most or owe the most in a selected period. Only customers that have either purchases during the period or a balance at the end of the period will be included. | Report 111 “Customer - Top 10 List” |
| Customer - Sales List obsolete Pending 28.0; #if not CLEAN28 | View customer sales for a period, for example, to report sales activity to customs and tax authorities. You can choose to include only customers with total sales that exceed a minimum amount. You can also specify whether you want the report to show address details for each customer. | Report 119 “Customer - Sales List” | |
| Sales Statistics obsolete Pending 28.0; #if not CLEAN28 | View the customer’s total cost, sale, and profit over time, for example, to analyze earnings trends. The report shows amounts for original and adjusted cost, sales, profit, invoice discount, payment discount, and profit percentage in three adjustable periods. | Report 112 “Sales Statistics” | |
| Finance Reports | Statement | — | Report 153 “Customer Statement” |
| Customer - Balance to Date | — | Report 121 “Customer - Balance to Date” | |
| Customer - Trial Balance | — | Report 129 “Customer - Trial Balance” | |
| Customer - Detail Trial Bal. | — | Report 104 “Customer - Detail Trial Bal.” | |
| Customer - Summary Aging | — | Report 105 “Customer - Summary Aging” | |
| Customer - Detailed Aging | — | Report 106 “Customer Detailed Aging” | |
| Aged Accounts Receivable (Obsolete) obsolete Pending 28.0; #if not CLEAN28 | View an overview of when customer payments 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 120 “Aged Accounts Receivable” | |
| Customer - Payment Receipt | — | Report 211 “Customer - Payment Receipt” |
Events published
Procedures
PostDocument(PostingCodeunitID: Integer)(protected)
Plus 3 local procedures.
Triggers
OnAfterGetCurrRecord, OnAfterGetRecord, OnOpenPage
Relations
- card page Page 44 “Sales Credit Memo”
- source table Table 36 “Sales Header”
Extended by
- Page extension 30121 “Shpfy Sales Credit Memos”
- Page extension 4441 “EXR Sales Credit Memos”
- Page extension 8059 “Sales Credit Memos”
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 1320 “Lines Instruction Mgt.” (2 calls:
CheckSalesCheckAllLinesHaveQuantityAssigned → SalesCheckAllLinesHaveQuantityAssigned,PostDocument → SalesCheckAllLinesHaveQuantityAssigned) - Codeunit 1535 “Approvals Mgmt.” (2 calls:
SetControlAppearance → CanCancelApprovalForRecord,SetControlAppearance → HasOpenApprovalEntries) - Codeunit 1543 “Workflow Webhook Management” (1 call:
SetControlAppearance → GetCanRequestAndCanCancel) - Codeunit 9179 “Application Area Mgmt. Facade” (1 call:
PostDocument → IsFoundationEnabled)
Called by
- Codeunit 1302 “Customer Mgt.” (1 call:
DrillDownOnUnpostedCrMemos → (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: "Sales Credit Memos"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.