Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: 02 — Business Capability Map — topic detail
stock management
In this document
Capability: stock management
The stock business object contains a stock number, manufacturer code, manufacturer name, description, unit price, and unit description. Stock-selection form evidence also exists, and order-entry flows use stock lookups. These records support inventory selection and invoice enrichment, but the source does not establish complete stock maintenance behavior. E0013 E0012
D4_Stock exposes add, find, update, and delete menu operations, but each corresponding method only reports that the option has not been implemented. The system therefore exposes stock-management UI without source evidence of stock CRUD behavior in this range. A stock-list report option is similarly present but is stubbed rather than functional. E0012
Startup loading retains stock data in a bounded in-memory array with capacity thirty. The loader stops when the capacity is exceeded and resets the retained counter to the maximum retained count. Records beyond thirty stock rows are therefore not retained by the visible loader. The code sets error-handler status to zero before breaking, but the meaning of that status and whether users receive an overflow warning are unresolved. E0012
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.