Auto Order — entity reference

A replenishment-planning header that first proposes what to buy and then generates the purchase order from the accepted proposal. AutoOrderType is the discriminator the engine branches on, and only four values are implemented: 'Minimum Stock Level' and 'Replenish' build proposal lines from stock settings and recent allocations, 'Forecasting' runs the projected-stock reorder-point calculation with pipeline netting, and 'Template' is a reusable configuration that spawns a fresh dated Forecasting order rather than holding lines of its own. GenerateAutoOrderLines builds (and on re-run replaces) the proposal, then prices it and applies the BudgetAmount cap; PerformOrderGeneration or SelectiveOrderGeneration turns accepted lines into a PurchaseOrder that links back through PurchaseOrder.PurchaseAutoOrderId. The Include and Exclude flags scope which items and which supply and demand sources the Forecasting calculation may see.

Fields

Field	Label	Type	Required	What it does
`AIRecommendation`	AI Recommendation	PickList		Nothing in the platform reads or writes it, and no recommendation engine is wired to auto ordering; the suggested quantities come from the deterministic minimum-stock, replenish and forecasting calculations. Values: Einstein 1, DemandSense AI, Einstein 2, AutoProcure AI, SmartReplenish AI, Einstein 3, Einstein 4, InventoryPilot AI.
`ApplyInventoryAttributeSettings`	Apply Inventory Attribute Settings	PickList		Values: Auto Min Max Settings, Manual Min Max Settings, Average of Auto & Manual Settings, Prefer Auto.
`AutoOrderType`	Auto Order Type	PickList		Values: Back Order, Minimum Stock Level, Forecasting, Template, Replenish.
`AutoPurchaseOrderId`	Auto Purchase Order	Lookup		On an order spawned from a template, this points back at the template it was cloned from. The scheduled sweep uses exactly this link to decide whether a template has already produced its order for today, so it is what keeps template generation to one dated order per template per day.
`BranchId`	Branch	Lookup → Branch
`BudgetAmount`	Budget Amount	Currency		A spend cap applied after the proposal lines are priced: when the priced total exceeds it, every line that carries a non-zero amount has its quantity, suggested, derived and pending quantities scaled down by the same factor so the order fits, with values rounded to two decimals. Empty or zero means no cap, and lines priced at zero (no applicable price rule found) are deliberately left untouched rather than trimmed.
`CreatedById`	Created By	Lookup → UserAccount	Yes
`CreatedDateTime`	Created Date	DateAndTime	Yes
`CreateTemplate`	Create Template	Boolean	Yes	A flag with no code behind it anywhere in the platform. A reusable planning configuration is created by setting AutoOrderType to Template, not by ticking this.
`DocumentDate`	Document Date	Date
`ExcludeACategoryItems`	Exclude A Category Items	Boolean	Yes	Excludes items whose inventory attributes classify them in the A value band from the proposal, applied before any quantity is computed. The three ABC flags and the three fast/slow/non-moving flags are tested against the item's inventory-attribute row, and an item with no such row is never excluded.
`ExcludeBCategoryItems`	Exclude B Category Items	Boolean	Yes
`ExcludeCCategoryItems`	Exclude C Category Items	Boolean	Yes
`ExcludeFastMovingItems`	Exclude Fast Moving Items	Boolean	Yes
`ExcludeNonMovingItems`	Exclude Non Moving Items	Boolean	Yes	Drops items classified as non-moving from the proposal. Because the movement category comes from the item's inventory-attribute row, an item that has never been classified is not excluded by this flag.
`ExcludeSlowMovingItems`	Exclude Slow Moving Items	Boolean	Yes	Drops items classified as slow-moving from the proposal. The exclusion is applied by all three line-building engines, matching the item's movement category exactly, and an item with no inventory-attribute row has no category to test and so survives the filter.
`ExternalId`	External	Text, unique
`Id`	Id	Guid	Yes
`IncludeHighProbabilityQuote`	Include High Probability Quote	Boolean	Yes
`IncludeInTransitShipments`	Include In-Transit Shipments	Boolean	Yes
`IncludeOpenSaleOrders`	Include Open Sale Orders	Boolean	Yes	Forecasting only: when set, committed outbound demand from open sale orders is subtracted when projecting stock forward, which lowers the projected quantity and makes replenishment more likely to trigger. Left off, open sale orders are invisible to the calculation.
`IncludePendingPurchaseOrders`	Include Pending Purchase Orders	Boolean	Yes
`IncludePurchaseRequisition`	Include Purchase Requisition	Boolean	Yes
`IsOrderGenerated`	Is Order Generated	Calculated (calculated)	Yes	Meant to be the one-shot latch that stops an auto order being converted twice: generation and line regeneration are both refused when it is true, and the scheduled forecast sweep skips orders carrying it. In practice no code path ever sets it to true, so the guard never actually fires and order generation can be re-run against the same auto order. Judge whether a purchase order already came out of it by looking for PurchaseOrder rows whose PurchaseAutoOrderId is this record.
`LastAutoOrderDate`	Last Auto Order Date	Date		The replenish engine does need a 'since last run' boundary, but it derives it independently as the latest document date among the branch's replenish auto orders rather than reading this field.
`ModifiedById`	Modified By	Lookup → UserAccount	Yes
`Name`	Document Number	Text, unique
`OwnerId`	Owner	Lookup → UserAccount	Yes
`PartnerAccountId`	Partner Account	Lookup → Account
`PerformOpenOrderCalculation`	Perform Open Order Calculation	Boolean	Yes	Switches on the on-order netting for the minimum-stock and replenish engines: with it set, each proposal line's OpenOrderQuantity is filled from the outstanding pending quantity of existing purchase-order lines for the same partner, branch, item and SKU. The forecasting engine does not use it - it nets pending purchase orders through its own include flag instead.
`PerformOrderGeneration`	Perform Order Generation	Boolean	Yes	A legacy trigger boolean.
`PriceAsOnDate`	Price As On Date	Date
`PriceListId`	Price List	Lookup → PriceList
`RecordTypeId`	Record Type	Guid, hidden
`Remarks`	Remarks	Text
`ResourceId`	Generated By	Lookup → Resource
`Status`	Status	PickList		Carries a seeded draft and generated vocabulary but is never assigned by code; the only place it moves at all is when a template clone copies the template's value verbatim. The meaningful state is held in IsOrderGenerated and in whether proposal lines exist. Values: Draft, Order Generated.
`SupplierAccountId`	Supplier Account	Lookup → Account
`TotalAmount`	Total Amount	Calculated (calculated)
`TotalPendingQuantity`	Total Pending Quantity	Calculated (calculated)
`UIProps`	UI Props	Text
`UpdatedDateTime`	Modified Date	DateAndTime	Yes

Actions

Action	Label	Type	What it does
`BulkDelete`	Delete	Delete	Delete the selected records.
`Clone`	Clone	ServerAction (`Clone`)	Create a copy of this record
`Delete`	Delete	Delete	Delete
`DeleteInList`	Delete	Delete	Delete in a list page
`Edit`	Edit	Edit	Edit
`EditInLine`	Edit	EditInline	Edit
`EditInList`	Edit	EditInline	Edit
`EditPopUp`	Edit	Edit	Edit
`GenerateForecastLines`	Lines	ServerAction (`GenerateAutoOrderLines`)	Generate AutoOrder Lines
`GenerateTemplateOrder`	Order from Template	ServerAction (`GenerateTemplateOrder`)	Generate Order from Template
`New`	New	New	New
`PerformOrderGeneration`	Purchase Order	ServerAction (`PerformOrderGeneration`)	Generate Purchase Order
`SelectiveOrderGeneration`	Selective Order	ServerAction (`SelectiveOrderGeneration`)	Selective Order Generation

Validations

Validation	Applies to	Error message	Notes
Budget Amount Rule Validation	`BudgetAmount`, Error	Budgeted Amount Can not be Less than 0	Budgeted Amount Can not be Less than 0
Last Auto Order Date Validation	`LastAutoOrderDate`, Error	Last auto order date cannot go beyond today's date	Last auto order date cannot go beyond today's date

Lookup filters

Filter	Lookup field	Notes
Branch For Partner Account	`BranchId`
Only Partner Account	`PartnerAccountId`
Only Supplier	`SupplierAccountId`

Account — looks up via PartnerAccountId
UserAccount — looks up via CreatedById
Resource — looks up via ResourceId
Branch — looks up via BranchId
PriceList — looks up via PriceListId
UserAccount — looks up via OwnerId
UserAccount — looks up via ModifiedById
Account — looks up via SupplierAccountId
AutoPurchaseOrderLine — referenced by via AutoOrderId
PurchaseOrderRequisition — referenced by via AutoOrderId
PurchaseOrder — referenced by via PurchaseAutoOrderId

Auto Order — entity reference

Fields

Actions

Validations

Lookup filters

Related entities

Related topics