Page 99000868 "Finished Prod. Order Lines"
Base Application · Microsoft.Manufacturing.Document
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Manufacturing.Document · captioned “Lines” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Lines |
| SourceTable | Prod. Order 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 | Item No. | Item No. | Specifies the number of the item that is to be produced. from the table field |
| Variant Code | Variant Code | Specifies the variant of the item on the line. from the table field | |
| Due Date | Due Date | Specifies the date when the produced item must be available. The date is copied from the header of the production order. from the table field | |
| Description | Description | Specifies the value of the Description field on the item card. If you enter a variant code, the variant description is copied to this field instead. from the table field | |
| Description 2 | Description 2 | Specifies an additional description. from the table field | |
| Production BOM No. | Production BOM No. | Specifies the number of the production BOM that is the basis for creating the Prod. Order Component list for this line. from the table field | |
| Routing No. | Routing No. | Specifies the number of the routing used as the basis for creating the production order routing for this line. from the table field | |
| Routing Version Code | Routing Version Code | Specifies the version number of the routing. from the table field | |
| Production BOM Version Code | Production BOM Version Code | Specifies the version code of the production BOM. from the table field | |
| Location Code | Location Code | Specifies the location code, if the produced items should be stored in a specific location. from the table field | |
| Bin Code | Bin Code | Specifies the bin that the produced item is posted to as output, and from where it can be taken to storage or cross-docked. from the table field | |
| Starting Date-Time | Starting Date-Time | Specifies the starting date and the starting time, which are combined in a format called “starting date-time”. from the table field | |
| Starting Time | StartingTime |
Specifies the entry’s starting time, which is retrieved from the production order routing. | |
| Starting Date | StartingDate |
Specifies the entry’s starting date, which is retrieved from the production order routing. | |
| Ending Date-Time | Ending Date-Time | Specifies the ending date and the ending time, which are combined in a format called “ending date-time”. from the table field | |
| Ending Time | EndingTime |
Specifies the entry’s ending time, which is retrieved from the production order routing. | |
| Ending Date | EndingDate |
Specifies the entry’s ending date, which is retrieved from the production order routing. | |
| Scrap % | Scrap % | Specifies the percentage of the item that you expect to be scrapped in the production process. from the table field | |
| Quantity | Quantity | Specifies the quantity to be produced if you manually fill in this line. from the table field | |
| Unit of Measure Code | Unit of Measure Code | Specifies how each unit of the item is measured, such as in pieces or tons. By default, the value in the Base Unit of Measure field on the item card is inserted. It will be changed if you switch Product BOM or Production BOM Version. from the table field | |
| Finished Quantity | Finished Quantity | Specifies how much of the quantity on this line has been produced. from the table field | |
| Unit Cost | Unit Cost | Specifies the cost of one unit of the item or resource on the line. from the table field | |
| Cost Amount | Cost Amount | Specifies the total cost on the line by multiplying the unit cost by the quantity. 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 | |
| Standard Task Code obsolete Pending 27.0; #if not CLEAN27 | Standard Task Code | Specifies a standard task. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| 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. | |
| Routing | View or edit the operations list of the parent item on the line. | ||
| Components | View or edit the production order components of the parent item on the line. | ||
| Attachments | Add a file as an attachment. You can attach images as well as documents. | ||
| Item Tracking Lines | View or edit serial, lot and package numbers that are assigned to the item on the document or journal line. |
Procedures
2 local procedures, no public ones.
Triggers
OnAfterGetRecord, OnInit, OnOpenPage
Relations
- source table Table 5406 “Prod. Order Line”
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.
- Page 99000818 “Prod. Order Components” (1 call:
ShowComponents → (object))
Recent changes
- 2026-10-02 #12066 Bugs/remove asm inv mfg clean27 tags for wave2 2026 (main, BC30, obsoletion)
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: "Finished Prod. Order Lines"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.