Page 137 "Posted Purchase Rcpt. Subform"
Base Application · Microsoft.Purchases.History
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Purchases.History · captioned “Lines” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Lines |
| SourceTable | Purch. Rcpt. Line |
| PageType | ListPart |
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 | Type | Type | Specifies the line type. from the table field |
| Type | Rec.FormatType() |
Specifies the type of transaction that was posted with the line. | |
| No. | No. | Specifies the number of the involved entry or record, according to the specified number series. from the table field | |
| Item Reference No. | Item Reference No. | Specifies the referenced item number. 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 the item or service on the line. | |
| Description 2 | Description 2 | Specifies information in addition to the description. from the table field | |
| Return Reason Code | Return Reason Code | Specifies the code explaining why the item was returned. from the table field | |
| Location Code | Location Code | Specifies a code for the location where you want the items to be placed when they are received. from the table field | |
| Bin Code | Bin Code | Specifies the bin where the items are picked or put away. from the table field | |
| Quantity | Quantity | Specifies the quantity of the item or service on the line. | |
| 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 | |
| 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 | |
| Quantity Invoiced | Quantity Invoiced | Specifies how many units of the item on the line have been posted as invoiced. from the table field | |
| Qty. Rcd. Not Invoiced | Qty. Rcd. Not Invoiced | Specifies how many units of the item on the line have been received and not yet invoiced. | |
| 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 | |
| Promised Receipt Date | Promised Receipt Date | Specifies the date that the vendor has promised to deliver the order. from the table field | |
| Planned Receipt Date | Planned Receipt Date | Specifies the date when the item is planned to arrive in inventory. Forward calculation: planned receipt date = order date + vendor lead time (per the vendor calendar and rounded to the next working day in first the vendor calendar and then the location calendar). If no vendor calendar exists, then:… from the table field | |
| Expected Receipt Date | Expected Receipt Date | Specifies the date you expect the items to be available in your warehouse. If you leave the field blank, it will be calculated as follows: Planned Receipt Date + Safety Lead Time + Inbound Warehouse Handling Time = Expected Receipt Date. from the table field | |
| Order Date | Order Date | Specifies the date when the related order was created. from the table field | |
| Lead Time Calculation | Lead Time Calculation | Specifies a date formula for the amount of time it takes to replenish the item. from the table field | |
| Job No. | Job No. | Specifies the number of the related project. from the table field | |
| Job Task No. | Job Task No. | Specifies the number of the related project task. from the table field | |
| Inbound Whse. Handling Time | Inbound Whse. Handling Time | Specifies the time it takes to make items part of available inventory, after the items have been posted as received. 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 | |
| Correction | Correction | Specifies the entry as a corrective entry. You can use the field if you need to post a corrective entry to an account. 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 | |
| ShortcutDimCode[3] | ShortcutDimCode[3] |
— | |
| ShortcutDimCode[4] | ShortcutDimCode[4] |
— | |
| ShortcutDimCode[5] | ShortcutDimCode[5] |
— | |
| ShortcutDimCode[6] | ShortcutDimCode[6] |
— | |
| ShortcutDimCode[7] | ShortcutDimCode[7] |
— | |
| ShortcutDimCode[8] | ShortcutDimCode[8] |
— | |
| Unit Gross Weight | Gross Weight | Specifies the gross weight of one unit of the item. In the purchase statistics window, the gross weight on the line is included in the total gross weight of all the lines for the particular purchase document. from the table field | |
| Unit Net Weight | Net Weight | Specifies the net weight of one unit of the item. In the purchase statistics window, the net weight on the line is included in the total net weight of all the lines for the particular purchase document. from the table field | |
| Unit Volume | Unit Volume | Specifies the volume of one unit of the item. In the purchase statistics window, the volume of one unit of the item on the line is included in the total volume of all the lines for the particular purchase document. from the table field | |
| Units per Parcel | Units per Parcel | Specifies the number of units per parcel of the item. In the purchase statistics window, the number of units per parcel on the line helps to determine the total number of units for all the lines for the particular purchase document. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Functions | Order Tracking | Tracks the connection of a supply to its corresponding demand. This can help you find the original demand that created a specific production order or purchase order. | |
| Undo Receipt | Cancel the quantity posting on the selected posted receipt line. A corrective line is inserted under the selected receipt line. If the quantity was received in a warehouse receipt, then a corrective line is inserted in the posted warehouse receipt. The Quantity Received and Qty. Rcd. Not Invoiced fi… | ||
| Line | 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. | |
| Comments | View or add comments for the record. | ||
| Item Tracking Entries | View serial, lot or package numbers that are assigned to items. | ||
| Item Invoice Lines | View posted purchase invoice lines for the item. | ||
| Document Line Tracking | View related open, posted, or archived documents or document lines. |
Events published
OnAfterSetDimensionsVisibility()(integration)
Procedures
ShowDocumentLineTracking()
Plus 4 local procedures.
Triggers
OnAfterGetRecord, OnInit, OnOpenPage
Relations
- source table Table 121 “Purch. Rcpt. Line”
Extended by
- Page extension 6322 “EUDR Posted Purch. Rcpt Sub.”
- Page extension 99000784 “Mfg. PostedPurchRcptSubform”
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 408 “DimensionManagement” (1 call:
SetDimensionsVisibility → UseShortcutDims) - Codeunit 5813 “Undo Purchase Receipt Line” (1 call:
UndoReceiptLine → (object)) - Codeunit 9179 “Application Area Mgmt. Facade” (1 call:
OnInit → IsFoundationEnabled)
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: "Posted Purchase Rcpt. Subform"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.