Order-entry data capture: which of the following data elements would typically <em>not</em> be keyed by a user into the order entry subsystem because it is automatically derived from master data?

Introduction / Context:
Effective order-entry systems minimize manual input to reduce errors and speed processing. Master data such as item prices and costs, customer terms, and product descriptions are stored centrally and pulled automatically. Users should only enter transactional specifics like item, quantity, and ship-to details, which vary per order.

Given Data / Assumptions:

• Order-entry UI retrieves master data for items and customers.
• Users enter variable transaction data (e.g., quantity).
• Pricing and costing rules are system-controlled for consistency.

Concept / Approach:
Item cost is derived from the item master or costing subsystem and should not be manually keyed at order entry. Manually entering costs risks inconsistency with inventory valuation and reporting. Conversely, item number, customer number, and quantity are typically provided by the user (often via lookup and validation) because they are contextual to the specific transaction and not implied by a default rule alone.

Step-by-Step Solution:

Verification / Alternative check:
ERP order-entry modules fetch cost and price from item master/price lists; user edits, if allowed, require special authorization and are logged.

Why Other Options Are Wrong:

• Item quantity: Must be entered for each order line.
• Customer number: Selected/entered to identify the account.
• Item number: Chosen for each line; not auto-derivable.
• None: Incorrect, since item cost is typically system-derived.

Common Pitfalls:
Allowing freeform cost entry, leading to valuation mismatches; not validating item and customer IDs against master data.

Final Answer:
item cost