Skip to main content

Type_ReceiptLoadIn

Type_ReceiptLoadIn = 4

Example​

procedure ScriptEvent(var Value: variant);
begin
  Value := GetOrderTypeCode(Type_ReceiptLoadIn); // 'ReceiptLoadIn'
end;

Usage​

Type_ReceiptLoadIn identifies Velox ReceiptLoadIn order type 4 for scripts, tags and VxData transaction records.

Value

PropertyValue
Script typeLongInt
Numeric value4
Paired textType_ReceiptLoadIn_String = ReceiptLoadIn
Deprecated numeric aliasOrder_Type_ReceiptLoadIn = 4
Database domainOrder_Type.Num; Order_Hdr.TypeNum
Tag-map entryYes: <!Type_ReceiptLoadIn!> expands to 4

Additional Technical Info​

Type_ReceiptLoadIn is the canonical numeric identifier for the ReceiptLoadIn member of the Velox order-type vocabulary. Its fixed LongInt value is 4, paired with Type_ReceiptLoadIn_String.

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 fixed value 4. GetOrderTypeCode maps it to ReceiptLoadIn; GetOrderTypeNum performs the reverse mapping. The numeric name is in the Velox tag map, so <!Type_ReceiptLoadIn!> expands to 4.

No reviewed invoice-to-order or ASN-to-order bridge helper returns ReceiptLoadIn. Those helpers cover only the sales/purchase direction pair; scripts must select this warehouse-operation type explicitly when the flow contract requires it.

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 ReceiptLoadIn 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: receiptloadin is recognised and ReceiptLoadIn is not. Unsupported text returns Null. Number-to-text conversion returns Null for Null or an unsupported number.

The 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

  • The database description is Receipt / Load In, while the canonical code has no spaces or slash: ReceiptLoadIn.
  • This is an order-type identity, not proof that goods were received, checked, put away or incremented.
  • 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, comparing or tag-expanding Type_ReceiptLoadIn 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