The Product table defines any physical object that is to be processed, refined, or treated in a production or service workflow. This may include tools, mechanical components, or other customer-supplied parts.

Products serve as key input items in the JOP extension and play a central role in defining routings, pricing, documentation, and quality control processes.

Typical Examples

Precision tools (e.g., cutting tools, molds, dies)
Engine or machine components
Custom mechanical assemblies

Product Characteristics

In addition to basic identification, products can also include metadata that describes physical and technical characteristics. These properties are essential for process decisions, routing conditions, and quality controls.

Note: Product-specific metadata (properties) are set up and managed using the Key-Property table. This table allows flexible definition of attributes that can be reused across services, materials, and products.

Typical Examples

Length — Overall length of the part or component.
Diameter — Inner or outer diameter, relevant for cylindrical items or tools.
Other dimensions — Depending on the product type, further dimensional or geometric attributes may be maintained.

These metadata attributes are typically used in conjunction with service rules, pricing brackets, or inspection requirements.

Product Card Fields

The Product Card contains the following fields:

Code — The unique identifier for the product. Used internally for lookups, references, and transactions.
Description — A clear and recognizable name for the product, shown in documents and user interfaces.
Product Group Code — Links the product to a group that shares common routing or pricing logic. This supports structured setup and rule-based processing.
Blocked — When enabled, this field prevents the product from being used in new orders or routings. Useful for phasing out obsolete products.

Product and Group Structure

Each Product is assigned to a Product Group. This hierarchical design supports business logic that is applied across multiple related products.

Product Groups can be used to define:

Standard routing rules based on product type or complexity
Pricing structures and conditions shared across similar product lines
Process folder grouping and documentation templates

Best practice suggests using the Product Group to reflect internal classification logic, while the individual Product record captures customer-specific terminology.

Product Usage in the JOP Flow

In the JOP production flow, Products are combined with Services and Materials to generate structured work orders. This includes:

Creating routings for specific products based on predefined group rules
Applying price lists per product or group for cost calculations
Managing quality inspections or certifications per product type