Materials management: in typical item master data, which code most directly distinguishes purchased items from manufactured items?

Introduction / Context:
Enterprise resource planning (ERP) and materials management systems maintain a master record for each item. Among the attributes are fields that classify whether an item is bought, made, or subcontracted. This classification drives planning logic (MRP), lead times, costing, and workflow routing.

Given Data / Assumptions:

• We need the field that explicitly categorizes the item’s supply type.
• “Purchased” vs. “manufactured” is a sourcing classification, not an identifier.
• Other fields (location, item number, drawing) serve different purposes.

Concept / Approach:
A product type or procurement type code (sometimes called “Make/Buy code”) flags whether the system should plan for internal production or external procurement. Planning engines read this flag to explode bills of materials (for made items) or generate purchase requisitions (for bought items). Stock location identifies where items are stored; item number is a unique identifier; drawing number links to engineering documents but does not dictate sourcing.

Step-by-Step Solution:

Verification / Alternative check:
Standard ERP configuration (e.g., MRP views) includes a Make/Buy or procurement type field specifically for this distinction.

Why Other Options Are Wrong:

• Stock location: storage detail, not sourcing.
• Item number: identifier common to all items.
• Drawing number: engineering reference; does not imply make/buy status.
• None: incorrect because a standard code exists for this classification.

Common Pitfalls:
Assuming identifiers or drawings determine sourcing; these support documentation and tracking, while the product/procurement type drives planning behavior.

Final Answer:
product type code