Page 9303 "Blanket Sales Orders"
Base Application · Microsoft.Sales.Document
Across versions
- BC23-26present
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Sales.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Blanket Sales Orders |
| SourceTable | Sales Header |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | 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 code for the location from where the items are shipped. When you select the customer and the customer has a location assigned, the value is taken from the Customer card. If the customer has no location, but a Responsibility Center is populated, the location code is taken from the Respo… from the table field | |
| 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 | |
| Status | Status | Specifies whether the record is open, waiting to be approved, invoiced for prepayment, or released to the next stage of processing. | |
| FactBoxes | Documents | part Page 1178 “Doc. Attachment List Factbox” | — |
| Control1902018507 | part Page 9082 “Customer Statistics FactBox” | — | |
| Control1900316107 | part Page 9084 “Customer Details FactBox” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Order | Statistics | View statistical information, such as the value of posted entries, for the record. | Page 402 “Sales Order 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. | ||
| Functions | 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 | ||
| Delete Invoiced Blanket Sales Orders | — | Report 291 “Delete Invd Blnkt Sales Orders” | |
| Processing | Make Order | Convert the blanket sales order to a sales order. | |
| Prepare to print the document. A report request window for the document opens where you can specify what to include on the print-out. | |||
| Attach as PDF | Create a PDF file and attach it to the document. | ||
| Request Approval | Send Approval Request | Request approval of the document. | |
| Cancel Approval Request | Cancel the approval request. |
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetRecord, OnAfterGetCurrRecord, OnOpenPage
Relations
- card page Page 507 “Blanket Sales Order”
- source table Table 36 “Sales Header”
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 1535 “Approvals Mgmt.” (2 calls:
SetControlAppearance → CanCancelApprovalForRecord,SetControlAppearance → HasOpenApprovalEntries)
Documented on Microsoft Learn
- Analyze data in lists with Copilot (preview)
- Analyze list page and query data using data analysis
- Work with blanket sales orders or purchase orders
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: "Blanket Sales Orders"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.