Page 1328 "Purch. Order From Sales Order"

Base Application · Microsoft.Purchases.Document · captioned “Create Purchase Orders” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Create Purchase Orders
SourceTable	Requisition Line
PageType	Worksheet

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
Group	No.	No.	Specifies the number of the involved entry or record, according to the specified number series.
	Description	Description	Specifies a description of the purchase order.
	Demand Quantity	Demand Quantity	Specifies the quantity needed relating to the purchase order line item.
	Vendor	`VendorName`	Specifies the vendor who will ship the items in the purchase order.
	Drop Shipment	Drop Shipment	Specifies if demand is for drop shipment or not.
	Quantity to Purchase	Quantity	Specifies the quantity to be purchased.
	Reserve	Reserve	Specifies whether the item on the planning line has a setting of Always in the Reserve field on its item card.

Actions

Group	Action	ToolTip	Runs
Set View	Show All	Show lines both for items that are fully available and for items where a sales quantity is unavailable and must be purchased.
	Show Unavailable	Show lines only for items where a sales quantity is unavailable and must be purchased.
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	Show 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.

Procedures

SetSalesOrderNo(SalesOrderNo: Code[20])
SetJobNo(JobNo: Code[20]) + BC25
SetJobTaskFilter(JobContractEntryNoFilter: Text) + BC25

Plus 4 local procedures.

Triggers

OnAfterGetRecord, OnOpenPage, OnQueryClosePage

Relations

source table Table 246 “Requisition Line”

Extended by

Page extension 20637 “PurchOrder From SalesOrder BF”

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 5522 “Order Planning Mgt.” (3 calls: PlanForOrder → PlanSpecificJob, PlanForOrder → PlanSpecificSalesOrder, PlanForOrder → SetTaskFilterOnReqLine)

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: "Purch. Order From Sales Order"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.