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

Return to: 08. Integration Catalogue — topic detail

Order forms

Interface: Order forms

ordcur.per defines an ORDER FORM with fields mapped to orders.order_num, order_date, customer_num, ship_instruct, backlog, po_num, ship_date, ship_weight, ship_charge, and paid_date. p_ordcur.per adds form-only MONEY field t_price for total price while retaining the order mappings. Both form definitions declare the stores7 database and list customer and orders as tables. E0009

order.per maps customer fields to customer number, name, address, city, state, ZIP code, and telephone; maps order number, date, and ship date to the order header; and displays four repeated item rows. Item number, description, unit price, and total price are marked NOENTRY, while stock number, manufacturer code, and quantity are entered or associated with item data. E0009

orderform.per similarly defines customer and order metadata, including company, contact name, purchase-order number, instructions, and an order date defaulting to today. Its manufacturer code field has UPSHIFT, its telephone field uses the picture ###-###-#### XXXXX, and its four repeated item records contain item number, stock number, manufacturer code, stock description, quantity, unit price, and item total. E0009