Skip to main content

Type_PurchaseOrder_String

Type_PurchaseOrder_String = 'PurchaseOrder'

Example​

procedure ScriptEvent(var Value: variant);
begin
  Value := GetOrderTypeNum(Type_PurchaseOrder_String); // 2
end;

Usage​

Type_PurchaseOrder_String provides the exact PurchaseOrder text paired with Type_PurchaseOrder for the Velox order-type domain.

Value

PropertyValue
Script typeString
Text value'PurchaseOrder'
Paired numberType_PurchaseOrder = 2
Deprecated numeric aliasOrder_Type_PurchaseOrder = 2
Database domainOrder_Type.Num; Order_Hdr.TypeNum
Tag-map entryNo

Additional Technical Info​

Type_PurchaseOrder_String is the canonical text for the PurchaseOrder member of the Velox order-type vocabulary. Its fixed String value is 'PurchaseOrder', paired with Type_PurchaseOrder.

It selects a domain value; it does not create, load, validate, send, receive, post or change the status of a transaction.

Implementation

Velox declares and registers exact text PurchaseOrder. GetOrderTypeNum compares it with Delphi SameText and returns 2; GetOrderTypeCode performs the reverse mapping. The String identifier is not in the Velox tag map.

GetOrderTypeNumForInvoiceType maps both supplier invoice tokens to this value, and GetOrderTypeNumForASNType maps SupplierASN to this value. Their String-returning partners return PurchaseOrder.

Database alignment

Fresh-build VxData seeds this exact row in Order_Type. Order_Hdr.TypeNum is a nullable foreign key to that table; Order_Event_Type.TypeNum is a required foreign key used with order status to select event behaviour.

The seed-table code is PurchaseOrder and its display description is human-spaced. The code, number and description are separate representations; persist the numeric key in TypeNum and use the exact code only where a code contract calls for it.

Behaviour

Text-to-number conversion is case-insensitive because it uses SameText, but it does not trim: purchaseorder is recognised and PurchaseOrder is not. Unsupported text returns Null. Number-to-text conversion returns Null for Null or an unsupported number.

The paired numeric value has meaning only inside its order-type domain. Identical integers in party, source, status, shipment or other vocabularies are not interchangeable.

Edge cases and quirks

  • PurchaseOrder is a Velox transaction direction/type, not proof of party roles, commercial ownership, message standard or completion state.
  • A sales/purchase bridge result loses the source invoice-versus-credit or ASN distinction; retain that source domain separately if it matters.
  • Numeric PascalScript constants do not retain a domain type after evaluation; validate the target field/table contract before assignment.
  • The preferred name is numerically indistinguishable from its deprecated alias after evaluation.
  • A nullable header TypeNum may contain Null even though the seed vocabulary defines this value.
  • The constant does not enforce event configuration, party relationships, lifecycle transitions or business-document validity.

Side effects

Reading or comparing Type_PurchaseOrder_String has no database, file, network or shared-state side effect. Converter and bridge helpers, where present, are fixed in-memory mappings.

Errors

Reading the constant does not raise an error. Converter misses return Null; inputs outside the documented String/number contract can still encounter normal PascalScript Variant conversion behaviour. Persisting a value absent from the target type table can fail a database foreign key.

Performance and concurrency

This is immutable compiled metadata. Constant access, fixed converters and fixed bridge lookups are constant-time for practical purposes and do not carry mutable transaction state.

Remarks

Customer/supplier and sales/purchase naming expresses Velox's transaction vocabulary, not a universal accounting or EDI interpretation. Confirm the mapping contract, parties, signs and downstream process independently. The example is source-reviewed and non-destructive.

Related entries

Created 2026-07-15