Page 5708 "Get Shipment Lines"
Base Application · Microsoft.Sales.History
Across versions
- BC23-27present
- BC281 procedures removed
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Sales.History · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Get Shipment Lines |
| SourceTable | Sales Shipment Line |
| PageType | List |
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 | Document No. | Document No. | Specifies the number of the related document. |
| 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 | |
| Sell-to Customer No. | Sell-to Customer No. | Specifies the number of the customer. from the table field | |
| Type | Type | Specifies the line type. from the table field | |
| No. | No. | Specifies the number of the involved entry or record, according to the specified number series. from the table field | |
| Variant Code | Variant Code | Specifies the variant of the item on the line. from the table field | |
| Description | Description | Specifies a description of posted sales shipments. | |
| Description 2 | Description 2 | Specifies information in addition to the description. from the table field | |
| Currency Code | Currency Code | Specifies the currency that is used on the entry. 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 from where inventory items to the customer on the sales document are to be shipped by default. | |
| Unit of Measure Code | Unit of Measure Code | Specifies how each unit of the item or resource is measured, such as in pieces or hours. By default, the value in the Base Unit of Measure field on the item or resource card is inserted. from the table field | |
| Quantity | Quantity | Specifies the number of item units, resource hours, general ledger account payments, or cost that have been shipped to the customer. | |
| Unit of Measure | Unit of Measure | Specifies the name of the item or resource’s unit of measure, such as piece or hour. from the table field | |
| Appl.-to Item Entry | Appl.-to Item Entry | Specifies the number of the item ledger entry that the document or journal line is applied to. from the table field | |
| Job No. | Job No. | Specifies the number of the related project. 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 | |
| Quantity Invoiced | Quantity Invoiced | Specifies how many units of the item on the line have been posted as invoiced. from the table field | |
| Qty. Shipped Not Invoiced | Qty. Shipped Not Invoiced | Specifies the quantity of the shipped item that has been posted as shipped but that has not yet been posted as invoiced. from the table field | |
| Order No. | Order No. | Specifies the number of the sales order that this shipment was posted from. | |
| External Document No. | External Document No. | Specifies the number that the customer uses in their own system to refer to this sales document. | |
| Your Reference | Your Reference | Specifies the customer’s reference. The content will be printed on sales documents. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Line | Show Document | Open the document that the selected line exists on. | |
| 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. | ||
| Item Tracking Entries | View serial, lot or package numbers that are assigned to items. |
Events published
OnBeforeOnQueryClosePage(CloseAction: Action; var Result: Boolean; var IsHandled: Boolean; var SalesShipmentLine: Record "Sales Shipment Line")(integration)OnBeforeSetSalesHeader(var SalesHeader2: Record "Sales Header"; var IsHandled: Boolean; var SalesHeader: Record "Sales Header")(integration)OnCreateLinesOnAfterSalesGetShptSetSalesHeader(var SalesHeader: Record "Sales Header"; var SalesShipmentLine: Record "Sales Shipment Line")(integration)OnBeforeIsFirstDocLine(var SalesShipmentLine: Record "Sales Shipment Line"; var TempSalesShipmentLine: Record "Sales Shipment Line" temporary; var Result: Boolean; var IsHandled: Boolean)(integration)
Procedures
SetSalesHeader(var SalesHeader2: Record "Sales Header"): Sets the sales header for filtering shipment lines.CreateLines(): Creates invoice lines from the selected shipment lines.
Plus 2 local procedures.
Triggers
OnAfterGetRecord, OnQueryClosePage
Relations
- source table Table 111 “Sales Shipment Line”
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 64 “Sales-Get Shipment” (2 calls:
CreateLines → CreateInvLines,CreateLines → SetSalesHeader)
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: "Get Shipment Lines"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.