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

Return to: 02 — Business Capability Map — topic detail

order entry

Capability: order entry

The order-add journey validates or obtains a customer, collects order-header information, accepts multiple line items with stock lookups, calculates totals, and commits the order and its items. The source identifies this flow in D4_Orders.add_order and its supporting item and total routines. Customer validation and creation within this journey cannot be independently confirmed because the supplied evidence contains the customer interface but no D4_Cust implementation. E0011 E0012

Order creation has an explicit transaction structure. D4_Orders.add_order begins a transaction, inserts the order header, invokes item insertion, and commits only after the required operations succeed. An explicit rollback is shown when the order-header operation reports a negative error status or when insert_items returns false. The broad exception handler instead calls the framework exception handler, and the supplied source does not show an accompanying database rollback. Framework or exception-handler behavior could provide additional protection, but that behavior is not evidenced. E0012

The order total is calculated by summing line totals and applying a 1.1 multiplier. The invoice path separately calculates sales tax at 0.065 and shipping at 0.035, which also totals ten percent. The figures therefore suggest intended numerical equivalence, but exact equality is not established because the interactive calculation uses the binary floating-point literal 1.1 while the invoice calculates separate components. The rounding and precision behavior of Money is unavailable, so cent-level differences remain possible. E0012