An orphan entity: the metadata and domain type exist but nothing else does. Its metadata field names have also drifted away from the domain type - the metadata declares AutoPurchaseOrderLine, ItemSKU and DocumentNumber where the class declares AutoPurchaseOrderLineId, SKUId and AutoPurchaseOrderLineRelationNumber, and metadata treats PendingQuantity as a calculated field where the class stores it. Treat it as unused scaffolding for tying an auto-order proposal line to a fulfilment order line; the working link between a proposal and the resulting purchase order is PurchaseOrderLine.AutoPurchaseOrderLineId instead.
Fields
| Field | Label | Type | Required | What it does |
|---|
AutoPurchaseOrderId | Auto Purchase Order | Lookup | | |
AutoPurchaseOrderLine | Auto Purchase Order Line | Lookup | Yes | Named as a plain field here although the domain type declares it as an identifier column linking to the proposal line, one of several places where this table's metadata has drifted from the class. |
CreatedById | Created By | Lookup → UserAccount | Yes | |
CreatedDateTime | Created Date | DateAndTime | Yes | |
DocumentNumber | Document Number | Number | Yes | The metadata name for what the class declares as a per-relation sequence number. Neither is ever assigned, since nothing in the platform creates rows in this table. |
ExternalId | External | Text | | |
FulfillmentOrderLineId | Fulfillment Order Line | Lookup | | Intended to tie a proposed purchase quantity to the specific demand line it would fulfil, which is what would have made this table a demand-to-supply pegging record. Nothing creates such a link; demand netting in the working replenishment engine is done in aggregate, not line to line. |
Id | Id | Guid | Yes | |
ItemId | Item | Lookup | | |
ItemLotTypeId | Item Lot Type | Lookup | | |
ItemSKU | Item SKU | Lookup | | The metadata name for what the domain type declares as the SKU identifier, another instance of this unused table's metadata drifting from the class. No code path populates it. |
ModifiedById | Modified By | Lookup → UserAccount | Yes | |
Name | Name | Text | Yes | |
OrderQuantity | Order Quantity | Number | | The demand quantity this pegging row would have carried. |
OwnerId | Owner | Lookup → UserAccount | Yes | |
PendingQuantity | Pending Quantity | Calculated (calculated) | | Declared here as a calculated field (order quantity minus purchase-order quantity) whereas the domain type stores it as a plain column - a genuine mismatch between the metadata and the class. Because nothing ever writes this table, neither definition is exercised. |
PurchaseOrderQuantity | Purchase Order Quantity | Number | | |
RecordTypeId | Record Type | Guid, hidden | | |
SuggestedQuantity | Suggested Quantity | Number | | |
UIProps | UI Props | Text | | |
UnitCost | Unit Cost | Currency | | |
UpdatedDateTime | Modified Date | DateAndTime | Yes | |
Actions
| Action | Label | Type | What it does |
|---|
BulkDelete | Delete | Delete | Delete |
Clone | Clone | ServerAction (Clone) | Create a copy of this record |
Delete | Delete | Delete | Delete |
DeleteInList | Delete | Delete | Delete |
Edit | Edit | Edit | Edit |
EditInLine | Edit | Edit | Edit |
New | New | New | New |
