---
id: object/page/1328
type: object
title: Page 1328 "Purch. Order From Sales Order"
summary: Page 1328 "Purch. Order From Sales Order" in Base Application (Microsoft.Purchases.Document). 3 public procedures. Present since at least BC23, still in BC30, changed in BC25-26.
tier: official
language: en
tags:
  - page
  - base application
versions:
  introduced: null
  last_changed: "26"
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: aae66b59a8d092f757aa37453dc13b30e702fd387115958a526715001416b53d
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Purchases/Document/PurchOrderFromSalesOrder.Page.al
    title: src/Layers/W1/BaseApp/Purchases/Document/PurchOrderFromSalesOrder.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 1328
name: Purch. Order From Sales Order
caption: Create Purchase Orders
namespace: Microsoft.Purchases.Document
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "25"
  - "26"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 0
  procedures: 7
  events: 0
  subscribers: 0
  controls: 7
  actions: 8
relations:
  out: 1
  referenced_by: 0
  pages: 0
  extended_by: 1
  event_subscribers: 0
  calls: 1
  called_by: 0
  implements: 0
---

# Page 1328 "Purch. Order From Sales Order"

> Page 1328 "Purch. Order From Sales Order" in Base Application (Microsoft.Purchases.Document). 3 public procedures. Present since at least BC23, still in BC30, changed in BC25-26.

Base Application · Microsoft.Purchases.Document · captioned "Create Purchase Orders" · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Purchases/Document/PurchOrderFromSalesOrder.Page.al) · 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.](../table/246.md#fields) | Specifies the number of the involved entry or record, according to the specified number series. |
|  | Description | [Description](../table/246.md#fields) | Specifies a description of the purchase order. |
|  | Demand Quantity | [Demand Quantity](../table/246.md#fields) | 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](../table/246.md#fields) | Specifies if demand is for drop shipment or not. |
|  | Quantity to Purchase | [Quantity](../table/246.md#fields) | Specifies the quantity to be purchased. |
|  | Reserve | [Reserve](../table/246.md#fields) | 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."](../page/520.md) |
|  | 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])`
- `SetJobTaskFilter(JobContractEntryNoFilter: Text)`

Plus 4 local procedures.

## Triggers

OnAfterGetRecord, OnOpenPage, OnQueryClosePage

## Relations

- source table [Table 246 "Requisition Line"](../table/246.md)

## Extended by

- [Page extension 20637 "PurchOrder From SalesOrder BF"](../pageextension/20637.md)

## 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."](../codeunit/5522.md) (3 calls: `PlanForOrder → PlanSpecificJob`, `PlanForOrder → PlanSpecificSalesOrder`, `PlanForOrder → SetTaskFilterOnReqLine`)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: BC25-26

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