Type_CustomerRemittance
Type_CustomerRemittance = 1
Example
procedure ScriptEvent(var Value: variant);
begin
Value := Type_CustomerRemittance; // 1
end;
Usage
Type_CustomerRemittance identifies Velox CustomerRemittance remittance type 1 for scripts, tags and VxData transaction records.
Value
| Property | Value |
|---|---|
| Script type | LongInt |
| Numeric value | 1 |
| Paired text | Type_CustomerRemittance_String = CustomerRemittance |
| Deprecated alias | None exposed in the reviewed source |
| Database domain | Remittance_Type.Num; Remittance_Hdr.TypeNum |
| Tag-map entry | Yes: <!Type_CustomerRemittance!> expands to 1 |
Additional Technical Info
Type_CustomerRemittance is the canonical numeric identifier for the CustomerRemittance member of the Velox remittance-type vocabulary. Its fixed LongInt value is 1, paired with Type_CustomerRemittance_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 1. The numeric name is in the Velox tag map, so <!Type_CustomerRemittance!> expands to 1. The reviewed implementation exposes no remittance-type converter.
The reviewed source exposes no GetRemittanceTypeNum or GetRemittanceTypeCode function. Numeric and String remittance constants are registered independently, so callers must compare them directly or use the owning data/configuration contract.
Database alignment
Fresh-build VxData seeds this exact row in Remittance_Type, and nullable Remittance_Hdr.TypeNum references that table. The reviewed fresh-build remittance script has no per-remittance-type event-routing table analogous to Invoice_Event_Type or Order_Event_Type.
The seed-table code is CustomerRemittance 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
Reading the constant returns its compiled value exactly. Because no remittance converter exists, there is no built-in case-insensitive text normalisation, whitespace trimming or unknown-value-to-Null conversion for this family.
The numeric value has meaning only inside its remittance-type domain. Identical integers in party, source, status, shipment or other vocabularies are not interchangeable.
Edge cases and quirks
CustomerRemittanceidentifies the customer-direction remittance domain. It does not prove who paid whom, that funds settled, or that invoice allocation/reconciliation succeeded.- No converter normalises case or rejects whitespace for remittance text. Direct String comparison follows the comparison operation chosen by the script.
- Numeric PascalScript constants do not retain a domain type after evaluation; validate the target field/table contract before assignment.
- The remittance family has no deprecated alias or converter in the reviewed source.
- A nullable header
TypeNummay containNulleven 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_CustomerRemittance 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. Callers own direct comparison and validation because no remittance converter supplies an unknown-value fallback. 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
Type_CustomerRemittance_Stringis the paired canonical text.