Page 99000852 "Planning Worksheet"
Base Application · Microsoft.Inventory.Requisition
Across versions
- BC23present
- BC242 events changed
- BC25unchanged
- BC261 procedures added
- BC27declaration changed
- BC281 procedures added
- BC29-30unchanged
Neighbourhood 13 connected objects and pages
Base Application · Microsoft.Inventory.Requisition · captioned “Planning Worksheets” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Planning Worksheets |
| SourceTable | Requisition Line |
| PageType | Worksheet |
| UsageCategory | Tasks |
| ApplicationArea | Planning |
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 |
|---|---|---|---|
| Control120 | Name | CurrentWkshBatchName |
Specifies the name of the journal batch of the planning worksheet. |
| Approval Status | RequisitionWkshBatchApprovalStatus |
Specifies the approval status for planning worksheet batch. | |
| Control1 | Warning | Warning |
Specifies a warning text for any planning line that is created for an unusual situation. |
| Type | Type | Specifies the type of requisition worksheet line you are creating. 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 | |
| Planning Level | Planning Level | Indicates the planning level of the item in multi-level production orders. The planning level is calculated only for items that have Make-to-Order specified in the Manufacturing Policy field. from the table field | |
| Bin Code | Bin Code | Specifies the bin of the item on the line. from the table field | |
| Action Message | Action Message | Specifies an action to take to rebalance the demand-supply situation. from the table field | |
| Accept Action Message | Accept Action Message | Specifies whether to accept the action message proposed for the line. from the table field | |
| Original Due Date | Original Due Date | Specifies the due date stated on the production or purchase order, when an action message proposes to reschedule an order. from the table field | |
| Order Date | Order Date | Specifies the date when the related order was created. from the table field | |
| Due Date | Due Date | Specifies the date when you can expect to receive the items. from the table field | |
| Transfer Shipment Date | Transfer Shipment Date | Specifies the shipment date of the transfer order proposal. 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 | Starting Time | Specifies the starting time of the manufacturing process. from the table field | |
| Starting Date | Starting Date | Specifies the starting date of the manufacturing process, if the planned supply is a production order. from the table field | |
| 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 | Ending Time | Specifies the ending time for the manufacturing process. from the table field | |
| Ending Date | Ending Date | Specifies the ending date of the manufacturing process, if the planned supply is a production order. from the table field | |
| Low-Level Code | Low-Level Code | Specifies the planning level of this item entry in the planning worksheet. from the table field | |
| Description | Description | Specifies text that describes the entry. from the table field | |
| Description 2 | Description 2 | Specifies additional text describing the entry, or a remark about the requisition worksheet line. 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] |
Specifies the code for Shortcut Dimension 3. | |
| ShortcutDimCode[4] | ShortcutDimCode[4] |
Specifies the code for Shortcut Dimension 4. | |
| ShortcutDimCode[5] | ShortcutDimCode[5] |
Specifies the code for Shortcut Dimension 5. | |
| ShortcutDimCode[6] | ShortcutDimCode[6] |
Specifies the code for Shortcut Dimension 6. | |
| ShortcutDimCode[7] | ShortcutDimCode[7] |
Specifies the code for Shortcut Dimension 7. | |
| ShortcutDimCode[8] | ShortcutDimCode[8] |
Specifies the code for Shortcut Dimension 8. | |
| Transfer-from Code | Transfer-from Code | Specifies the code of the location that items are transferred from. from the table field | |
| Location Code | Location Code | Specifies a code for an inventory location where the items that are being ordered will be registered. from the table field | |
| Original Quantity | Original Quantity | Specifies the quantity stated on the production or purchase order, when an action message proposes to change the quantity on an order. from the table field | |
| MPS Order | MPS Order | Specifies whether the requisition worksheet line is an MPS order, that is, whether it is linked to a demand forecast or a sales order. from the table field | |
| Quantity | Quantity | Specifies the number of units of the item. from the table field | |
| 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 | |
| Replenishment System | Replenishment System | Specifies which kind of order to use to create replenishment orders and order proposals. from the table field | |
| Supply From | Supply From | Specifies a value, according to the selected replenishment system, before a supply order can be created for the line. from the table field | |
| Ref. Order Type | Ref. Order Type | Specifies whether the order is a purchase order, a production order, or a transfer order. from the table field | |
| Ref. Order No. | Ref. Order No. | Specifies the number of the relevant production or purchase order. from the table field | |
| Ref. Order Status | Ref. Order Status | Specifies the status of the production order. from the table field | |
| Ref. Line No. | Ref. Line No. | Specifies the number of the purchase or production order line. from the table field | |
| Planning Flexibility | Planning Flexibility | Specifies whether the supply, represented by the requisition worksheet line, is considered by the planning system, when calculating action messages. | |
| Blanket Purch. Order Exists | Blanket Purch. Order Exists | Specifies if a blanket purchase order exists for the item on the requisition line. from the table field | |
| Reserved Quantity | Reserved Quantity | Specifies how many units of this item have been reserved. from the table field | |
| Gen. Prod. Posting Group | Gen. Prod. Posting Group | Specifies the item’s product type to link transactions made for this item with the appropriate general ledger account according to the general posting setup. 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 | |
| Gen. Business Posting Group | Gen. Business Posting Group | Specifies the code of the general business posting group to be used for the item when you post the planning worksheet. from the table field | |
| Cost Amount | Cost Amount | Specifies the total costs for the requisition worksheet line. from the table field | |
| Vendor No. | Vendor No. | Specifies the number of the vendor who will ship the items in the purchase order. from the table field | |
| Item Description | ItemDescription | ItemDescription |
— |
| Routing Description | Routing Description | RoutingDescription |
Specifies a description of the routing for the item that is entered on the line. |
| FactBoxes | Control9 | part Page 9090 “Item Replenishment FactBox” | — |
| Batch Workflows | part Page 1528 “Workflow Status FactBox” | — | |
| Control11 | part Page 9091 “Item Planning FactBox” | — | |
| Control15 | part Page 9101 “Untracked Plng. Elements Part” | — | |
| Control13 | part Page 9109 “Item Warehouse FactBox” | — |
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. | |
| Item Tracking Lines | View or edit serial, lot and package numbers that are assigned to the item on the document or journal line. | ||
| Item | Components | View or edit the production order components of the parent item on the line. | Page 99000862 “Planning Components” |
| Item Availability by | Event | View how the actual and the projected available balance of an item will develop over time according to supply and demand events. | |
| Period | View the projected quantity of the item over time according to time periods, such as day, week, or month. | ||
| Variant | View or edit the item’s variants. Instead of setting up each color of an item as a separate item, you can set up the various colors as variants of the item. | ||
| Location | View the actual and projected quantity of the item per location. | ||
| Lot | View the current and projected quantity of the item in each lot. | Page 520 “Item Availability by Lot No.” | |
| BOM Level | View availability figures for items on bills of materials that show how many units of a parent item you can make based on the availability of child items. | ||
| Navigation | 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. | |
| Processing | Delete all lines in worksheet | Delete all lines in the current worksheet, disregarding any filters. | |
| Functions | Calculate Net Change Plan | Plan only for items that had the following types of changes to their demand-supply pattern since the last planning run: 1) Change in demand for the item, such as forecast, sales, or component lines. 2) Change in the master data or in the planned supply for the item, such as changes to the BOM or rou… | |
| Calculate Regenerative Plan | Plan for all items, regardless of changes since the previous planning run. You calculate a regenerative plan when there are changes to master data or capacity, such as shop calendars, that affect all items and therefore the whole supply plan. | ||
| Get Action Messages | Obtain an immediate view of the effect of schedule changes, without running a regenerative or net change planning process. This function serves as a short-term planning tool by issuing action messages to alert the user of any modifications made since the last regenerative or net change plan was calc… | ||
| Drop Shipment | Get Sales Orders | Copy sales lines to the planning worksheet. You can use the batch job to create planning worksheet proposal lines from sales lines for drop shipments or special orders. | |
| Sales Order | View the sales order that is the source of the line. This applies only to drop shipments and special orders. | ||
| Functions | Refresh Planning Line | Update the selected planning line with any changes that are made to planning components and routing lines since the planning line was created. | |
| Get Error Log | View detailed information for planning lines with a value in the Warning field. | Page 5430 “Planning Error Log” | |
| Carry Out Action Message | Use a batch job to help you create actual supply orders from the order proposals. | ||
| Reserve | Reserve the quantity that is required on the document line that you opened this window for. | ||
| 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. | ||
| Send Approval Request | Worksheet Batch | Send all worksheet lines for approval, also those that you may not see because of filters. | |
| Cancel Approval Request | Worksheet Batch | Cancel sending all worksheet lines for approval, also those that you may not see because of filters. | |
| Power Automate | Create approval flow | Create a new flow in Power Automate from a list of relevant flow templates. | |
| Approval | Approve | Approve the requested changes. | |
| Reject | Reject the approval request. | ||
| Delegate | Delegate the approval to a substitute approver. | ||
| Comments | View or add comments for the record. | ||
| Page | Edit in Excel | Send the data in the worksheet to an Excel file for analysis or editing. |
Events published
OnAfterLookupCurrentJnlBatchName(var RequisitionLine: Record "Requisition Line"; var CurrJnlBatchName: Code[10])(integration)OnBeforeCarryOutActionMsg(var RequisitionLine: Record "Requisition Line"; var IsHandled: Boolean)(integration)OnBeforeRefOrderNoOnFormat(var RequisitionLine: Record "Requisition Line"; var IsHandled: Boolean)(integration)OnBeforeCalculateRegenerativePlan(var RequisitionLine: Record "Requisition Line"; var IsHandled: Boolean)Δ BC24 (integration)OnBeforeCalculateNetChangePlan(var RequisitionLine: Record "Requisition Line"; var IsHandled: Boolean)Δ BC24 (integration)
Procedures
OpenPlanningComponent(var PlanningComponent: Record "Planning Component")CallFromItemAvailabilityByEvent(OpenFromItemAvailabilityByEvent: Boolean)+ BC26
Plus 8 local procedures.
Triggers
OnAfterGetCurrRecord, OnAfterGetRecord, OnInit, OnDeleteRecord, OnModifyRecord, OnNewRecord, OnOpenPage
Relations
- source table Table 246 “Requisition 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.
- Codeunit 330 “ReqJnlManagement” (3 calls:
CurrentWkshBatchNameOnAfterVal → SetName,OnOpenPage → OpenJnl,OnOpenPage → WkshTemplateSelection) - Codeunit 1535 “Approvals Mgmt.” (2 calls:
OnAfterGetCurrRecord → GetRequisitionWkshBatchApprovalStatus,OnModifyRecord → CleanRequisitionWkshApprovalStatus) - Codeunit 1563 “Privacy Notice” (1 call:
OnInit → GetPrivacyNoticeApprovalState) - Codeunit 4030 “Client Type Management” (1 call:
OnOpenPage → GetCurrentClientType) - Codeunit 457 “Environment Information” (1 call:
OnOpenPage → IsSaaS) - Codeunit 6400 “Flow Service Management” (1 call:
OnInit → GetPowerAutomatePrivacyNoticeId) - Codeunit 6723 “Server Setting” (1 call:
OnOpenPage → GetIsSaasExcelAddinEnabled) - Codeunit 99000812 “PlanningWkshManagement” (1 call:
OnAfterGetCurrRecord → GetDescriptionAndRcptName) - Codeunit 99000856 “Planning Transparency” (1 call:
PlanningWarningLevel → ReqLineWarningLevel) - Page 99000862 “Planning Components” (1 call:
OpenPlanningComponent → (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: "Planning Worksheet"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.