Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.

Return to: 02 — Business Capability Map — topic detail

Reports

Capability: Reports

The reports menu provides mailing labels, accounts receivable, backlog, stock-list, options, and exit. Each report command generally leaves the menu before invoking its function and re-enters afterward. Mailing labels uses customer query-by-example, orders selected customers by ZIP code, and iterates over the results. Output can go to a file, printer, or screen according to print_option. File output asks for a filename and defaults to labels.out when the response is NULL; printer output targets PRINTER; screen output starts without a destination and clears the screen. E0007

The mailing-label report prints customer name, company, address, optional second address line, city, state, and ZIP code. With screen output selected, it pauses after each row for RETURN. Accounts receivable selects orders whose paid_date is NULL by joining customer, orders, and items, ordered by customer number and order number. Its output supports the same file, printer, and screen destinations, defaults to ar.out for a NULL filename, and prints company heading, report title, current date, customer identity, column headings, order details, and grouped customer and order totals. E0007

The report-options menu sets print_option to f for file, p for printer, or s for screen. Exit leaves the existing option unchanged. Backlog and stock-list display errors stating that the selected options have not been implemented. The help documentation identifies mailing labels and accounts receivable as available reports, while backlog and stock-list are not implemented; terminal output is the default and can be redirected for the current session. E0007

Both mailing-label and accounts-receivable processing check int_flag while producing rows. The reported pattern resets int_flag to FALSE before leaving the loop, then checks it again afterward before displaying an abort message. On the supplied evidence, this creates a strong source-level indication that an interrupted report may be treated as normally completed. The exact runtime result remains uncertain because the event that sets int_flag and the relevant Informix-4GL control-flow behavior are not fully established. E0007 E0008