Setting Up Products

Generally, every product consists of components, each of which may also consist of subcomponents. You use the Component Type page to break down products into component and subcomponent levels.

You can then combine components and subcomponents in a hierarchical relationship on the Component Definitions page. As changes are made in the combination of components and subcomponents, a different component definition of the product is created and distinguished from all others by a unique version definition. When you select a specific product version while creating a defect record, you can drill down to the correct components and subcomponents that you used to build that particular version.

For example, here is a simple breakdown of a laptop computer's components:

This example illustrates the fields and controls on the Example of laptop component hierarchy.

At the least, a laptop computer is made up of a bottom casing and a top casing. One of the bottom casing's subcomponents is the keyboard, which is made up of several individual keys. The top casing has a liquid crystal display (LCD) screen as one of the subcomponents. As you can see, this breakdown could go on for many levels.

Suppose that you manufacture laptops, and you want to offer an improved LCD screen. The laptops that include the improved screen are a new version. As you create the version's component definition, the only change is the LCD screen, but that change means that the hierarchy of components is different. By attaching the new component definition to a new and unique component version, you are assured that the correct LCD screen is available as you drill down on the product components.

Use the Component Types page (RQ_UD_COMP_TYPE) to define general component types.

Navigation:

Set Up CRM > Product Related > Quality Management > Component Types > Component Types

This example illustrates the fields and controls on the Component Types page.

The component type is the most basic definition of a component. This general description can be used in multiple component definitions. For example, you might define a component type that represents all keyboards, or you might narrow the definition to only keyboards for laptops.

Use the Component Definition page (RQ_COMP_DEFN) to define product components.

Navigation:

Set Up CRM > Product Related > Quality Management > Component Definitions > Component Definition

This example illustrates the fields and controls on the Component Definition page.

The component definition is a more specific description of a particular component. For example, you might have a laptop keyboard with gray keys and another with black keys. The component definition enables you to distinguish between the two keyboards.

The component definitions also show the level at which subcomponents are linked to other components in a child-to-parent relationship, creating a hierarchy that culminates in the product component definition.

Use the Component Definitions - Relationships page (RQ_COMP_PAR_LNK) to define parent-child relationships between product components.

Navigation:

Set Up CRM > Product Related > Quality Management > Component Definitions > Relationships

This example illustrates the fields and controls on the Relationships page.

Component relationships define the component hierarchy. In the example of the laptop computer, the bottom casing includes the keyboard assembly, which is made up of individual keys. Thus, the bottom casing is the parent to the keyboard assembly, which, in turn, is the parent to the keys.

To view the component relationship, return to the Component Definition page. Click the Component Hierarchy link to access the Component Hierarchy page. Click the Refresh button to display newly added components.

Use the Version page (RQ_PROD_VERS) to define distinct component versions.

Navigation:

Set Up CRM > Product Related > Quality Management > Component Versions > Version

This example illustrates the fields and controls on the Version page.

Products consist of components. When one or more of these components changes, you refer to the changed product as a new version. PeopleSoft Quality Management enables you to uniquely identify different product versions by defining different component versions. Each version represents a unique product component definition.

Use the Environments page (RQ_PROD_VERS_ENV) to define version environment details.

Navigation:

Set Up CRM > Product Related > Quality Management > Component Versions > Environments

This example illustrates the fields and controls on the Environments page.

Component version environments relate only to software products and describe technical details needed to identify problems and fixes. Environment information entered here automatically transfers to the Defect page when the corresponding version is selected. This page is needed for software products only.