Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: C06 — Conceptual Information Model — topic detail
Order, item, stock, and invoice records
In this document
Data: Order, item, stock, and invoice records
Generated record artifacts provide schema-like field evidence. P_Items.java.svn-base includes item_num, stock_num, manu_code, description, quantity, unit_price, and total_price. X_Invoice.java.svn-base combines order, item, stock, and manufacturer-related fields. Other identified artifacts include P_Orders.java.svn-base, P_Stock.java.svn-base, R.java.svn-base, and SQLCA.java.svn-base. These names and Java-side types support a generated data model, but do not prove a live database schema or persistence. E0006
The manu_code naming is not fully consistent across the evidence. One help example uses p_items[pa].menu_code in a stock predicate, while surrounding naming and interface material suggest manu_code or manufacturer code. This may be a source typo or example artifact and remains unresolved. E0004
items__manu_code__fld.setShiftState(TextFieldAdapter.UPSHIFT) and related field settings suggest uppercase input or display behavior. Without the custom framework implementation, they do not establish validation, normalization, or database-storage semantics. E0006
Harten documentation of the Informix 4GL and Java source repository, from the retained 17 October 2026 export. The exact upstream revision analysed is not established. Source findings do not establish runtime behaviour or equivalence between the implementations.
Evidence identifiers are retained for traceability. The underlying analysis records are not included in this public edition; credential values are redacted. About this case study.