This chapter provides an overview of product definitions in PeopleSoft Enterprise Customer Relationship Management (PeopleSoft CRM) and discusses how to:
Define products.
Assign product units of measurement (UOMs).
Define product package components.
Establish product prices.
Manage product relationships.
Enter product notes.
This section discusses:
Product definitions in PeopleSoft CRM.
Integrations with PeopleSoft Supply Chain Management (PeopleSoft SCM) and PeopleSoft Proposal Management.
PeopleSoft CRM uses a product definition to represent each product. The product definition—which is keyed by product ID—stores all of the product information that company representatives require to sell or support the product. PeopleSoft CRM also uses product definitions for:
Pricing product orders.
Generating product catalogs.
Storing product advisor scripts for use by sales and support personnel.
There are five types of product definitions in PeopleSoft CRM:
Standard product.
Package product.
Service agreement.
Service product.
Engagement service.
See Understanding Products and Items in PeopleSoft CRM.
Follow these steps to define products in PeopleSoft CRM:
Analyze how the various parts of the CRM system use product definitions.
For example, the catalog generation process and the ordering process can both use product definitions.
Create definitional elements to associate with products.
Definitional elements are attributes such as product brands, product categories, and competency codes. You associate definitional elements with product IDs to create unique product and product package definitions.
Select a product type and create a product definition.
After you define a product, the product ID becomes available on product search lists so that you can access the product definition from other CRM pages.
Important! In PeopleSoft CRM, you can define a product when you define an item, or you can create a product and associate it with existing items. Typically, you begin by defining an item and having the system copy the item's product ID, description, and standard UOM to the product definition table.
See Defining Items.
Associate definitional elements and other product attributes with the product ID.
Select package components (if the product definition is for a product package).
Establish product prices.
Define relationships between products.
Associate notes with products.
Product information is integrated with PeopleSoft SCM (and third-party SCM systems) and PeopleSoft Proposal Management, which is part of the PeopleSoft Enterprise Services Automation product suite, by using enterprise integration points (EIPs). These are the considerations for using EIPs:
SCM systems use product definitions to manage products and product components throughout the manufacturing process. PeopleSoft CRM delivers several EIPs that maintain data integrity between PeopleSoft CRM and SCM systems—including PeopleSoft SCM and third-party systems—by synchronizing product data.
You integrate product data by using the PeopleTools Integration Broker. This technology enables both synchronous and asynchronous messages to be transmitted using one technology.
These EIPs are used for both publishing and subscribing:
Note. If the PRODUCT_SYNC message is active, an add, change, or delete action in the Product Definition components automatically executes the product sync publish logic.
PeopleSoft CRM publishes the PRODUCT_SYNC message whenever product data is added, changed, or deleted using the Product Definition - Definition page, the Package Components page, the Product Price page, the Package Component Pricing page, the Notes page, the Relationships component (PROD_RELATIONS_CMP), and the Product Unit of Measure page. PeopleTools Integration Broker processes the message and applies a transformation to remove the PRODKIT_HEADER. Any package components that are themselves packages are also stripped from the message. Because PeopleSoft SCM does not permit packages within packages, package components that are themselves packages are also stripped from the message.
PeopleSoft CRM subscribes asynchronously to the PRODUCT_SYNC message that comes from the SCM system. This data is processed directly into the PeopleSoft CRM product tables using component interfaces. A product package header record is added for any kit components that are received from SCM. When a PRODUCT_SYNC or PRODUCT FULL_SYNC message is received, the system runs the subscription logic, which calls one of these component interfaces depending on the content of the message:
PRODKIT_CI
PRODKIT_COMPS_PRC_CI
PROD_DEFN_CI
PROD_NOTE_CI
PROD_PRICE_CI
PROD_RELATIONS_CI
PROD_UOM_CI
This table shows how an order represents packages to the PeopleSoft SCM system:
Type |
Line Display |
Line Data Model/EIP |
0-Static Package (1-level static quantity) PROD_ITEM.PROD_KIT=Y PROD_KIT_HEADER.LT_CONFIG_FLAG=N |
Display all components of the package as multiple lines. |
Store and publish parent line. |
1-Package (Kit) (multilevel dynamic quantity) PROT_ITEM.PROD_KIT=Y PROD_KIT_HEADER.LT_CONFIG_FLAG=Y |
Display all components of the package as multiple lines. |
Store all components as multiple lines, and publish as multiple lines. |
2-Configured Package(Kit) PROD_ITEM.PROD_KIT=Y PROD_ITEM.CFG_KIT=Y |
Display all components of the package as multiple lines. |
Store all components as multiple lines, and publish as multiple lines. |
3-Configured Product MASTER_ITEM_TBL.DIST_CFG_FLG=Y |
Display high-level parent line. |
Store and publish parent line plus configuration. |
Proposal Management Integrations
PeopleSoft CRM can send information to PeopleSoft Proposal Management. This occurs when a quote that originates from a PeopleSoft Sales lead or opportunity or is entered using PeopleSoft Order Capture includes an engagement service product. PeopleSoft Proposal Management prices the engagement and sends pricing information back to PeopleSoft CRM.
This integration consists of these application messages:
This message is sent to PeopleSoft Proposal Management when a quote is submitted for an engagement-type service in PeopleSoft Order Capture.
This message returns the capture ID, proposal ID, and version ID from PeopleSoft Proposal Management to PeopleSoft Order Capture.
When PeopleSoft Proposal Management completes pricing the engagement, pricing information is sent back to PeopleSoft Order Capture.
This sends the status of a proposal (for example, draft or negotiated) to PeopleSoft Proposal Management.
Important! Before you can integrate with PeopleSoft Proposal Management, you must first define the Engagement Services product.
See PeopleSoft Enterprise CRM 8.9 Order Capture Applications PeopleBook.
To define products, use the Product Definition (PROD_DEFN) component.
This section discusses how to:
Define product information.
Define external product descriptions.
Define actions for a product.
Define product attributes.
Attach files to product definitions.
Define installed product rules.
Attach images to product definitions.
Associate branch scripts with products.
Add products to product groups.
Define product availability for regions.
Track competing products.
Page Name |
Object Name |
Navigation |
Usage |
Products CRM, Product Definition, Definition |
Define product information. |
||
Products CRM, Product Definition, External Description |
Define a product's external description. |
||
Products CRM, Product Definition, Actions |
Define actions that occur during the life cycle of a product. |
||
Products CRM, Product Definition, Attributes |
Define product attributes such as dimensions, materials used in manufacturing, and color. |
||
Products CRM, Product Definition, Attachments |
Attach files to a product. |
||
Products CRM, Product Definition, Installed Product |
Define rule sets for processing installed products. |
||
Products CRM, Product Definition, Product Groups |
Add products to product groups. |
||
Products CRM, Product Definition, Images |
Attach images of different sizes to a product. |
||
Products CRM, Product Definition, Branch Scripts |
Associate a branch script with a product. |
||
Products CRM, Product Definition, Regions |
Define sales regions for products. |
||
Products CRM, Product Definition, Competitors |
Track competitors' products. |
Access the Product Definition - Definition page.
Note. Slightly different views of this page appear depending on the product type that you select when you add the product definition. The display template that you associate with the product type controls how the page appears.
See Product Definitions in PeopleSoft CRM, Configuring Display Templates.
Product Details
This is information that identifies the product, and appears for all product types. The specific fields that appear vary depending on the requirements of the product type. For example, engagement services do not have a catalog number, model number, brand, or category.
Model Number and Catalog Number |
Enter the product catalog number and model number if a product appears in another vendor catalog. |
This group box appears for all product types.
Business |
Select if the product is available as a standalone product (not part of a package) to businesses. |
Consumer |
Select if the product is available as a standalone product to consumers. |
Note. If you do not select either of these options, the system treats the product as one that is available only as a package component.
For packages, indicate the pricing method. This information appears for standard products and for package products.
at Top Level |
Select to use the price that is defined on the Product Price page for the package price. |
at Component Level |
Select to calculate the package price as the sum of the prices for each component in the package. Note. When you select the at Component Level option, define the price for each component of the package using the Package Component
Pricing page. |
If the implementation includes PeopleSoft Advanced Configurator, the check boxes in the Configured Packages group box define the configuration attributes for the product. This group box appears for products of type Standard and Package.
Select if the product is a fully configured package. A fully configured package uses the product configurator at runtime and creates a package based on the selections for the configurator model. |
|
Enter the configuration model, user interface, output, and pricing that are used to configure the package. |
|
Template |
Enter the name of the agreement template that is used to record the service agreements for a service product. Examples of service product agreements include maintenance and repair agreements, product support agreements, cleaning service agreements, and replacement warranties. |
See Product Modeling with a Component Model.
Inventory
This group box appears only for products of type Standard.
This group box appears only for products of type Service Agreement.
Template ID |
Enter the name of the agreement template that defines the service agreement. |
This group box appears for products of type Service and Service Agreement. The information that you enter in this group box determines how the service is classified for tax purposes.
This group box appears for products of type Service and enables you to enter the duration and frequency of the service.
See Also
Creating Product Definitional Elements
Access the Product Definition - External Description page.
External Description and Long External Description |
Enter short and long external descriptions for the product. The text can include any HTML tags except:
These main structure tags are unnecessary because they are included in the standard PeopleSoft-generated page. Note. Be sure that the HTML code follows proper HTML formatting rules. |
Preview |
Click to preview the short and long descriptions. |
Access the Product Definition - Actions page.
This page enables you to add actions to a product and view the actions for the product. The actions that are available are determined by setID and if the action is performed by an application method, the Application Method and Application Name fields show the relevant information.
Access the Product Definition - Attributes page.
Choose an option for processing of order capture line attributes. The PeopleSoft Order Capture application uses these options to determine how it processes line attributes. Setting either the Never has Attributes or the Always has Attributes option increases performance because the attributes engine does not need to check for attributes when these options are set. This field is not required. If left blank, Conditionally has Attributes is assumed to provide backward compatibility with existing functionality. Possible values are:
|
Note. The specific attributes that you can enter on this page are defined at system installation.
Access the Product Definition - Attachments page.
File Name |
Click to view the contents of the attachment. |
Type |
Select the attachment type. Options areProspectus, Disclosure, Literature, and White Paper. |
Required |
Select to indicate if the user must view the attachment before ordering the product or if the information is supplemental. |
Warning! For product images uploaded to a DB2 platform, the maximum image size is 32K.
See Also
Access the Product Definition - Installed Product page.
See Defining Creation and Update Rules for Installed Products, Setting Up Product Registration.
Access the Product Definition - Images page.
Image Size |
Select the size of the image that you want to associate with the product. Options are Large Image, Medium Image, Small Image, and Zoom Image. You can attach one image of each size. |
Browse |
Click to locate, upload, and attach an image. Note. You can upload and view only JPEG type images. The maximum size of the JPEG file depends on the database platform that you are using. Most systems can handle images up to 32 kilobytes. |
Access the Product Definition - Branch Scripts page.
See Also
Access the Product Definition - Product Groups page.
See Also
Access the Product Definition - Regions page.
All Regions |
Select if the product is available to customers in all regions. Note. If you select this option, the system disregards the regions that are associated with particular products. |
Only in Regions below |
Select to make the product unavailable in all regions except those that you specify. |
All except Regions below |
Select to make the product available in all regions except those that you specify. |
Region ID |
Enter one or more region codes if you select either the Only in Regions below option or the All except Regions below options. |
See Also
Access the Product Definition - Competitors page.
Competitor Code |
Enter a competitor code. You can create reports to perform analysis using competitor product information. |
See Also
Defining Creation and Update Rules for Installed Products
To assign product UOMs, use the Product Unit of Measure (PROD_UOM) component.
This section discusses how to assign UOMs.
Page Name |
Object Name |
Navigation |
Usage |
PROD_UOM |
Products CRM, Product Unit of Measure, Product Unit of Measure |
Select the UOMs that apply to the product. Define minimum and maximum order quantities, valid order increments, and minimum selling prices for the product when sold by that UOM. |
Access the Product Unit of Measure page.
UOM
UOM |
Enter a UOM that applies to sales order units for the product. |
Minimum Quantity and Maximum Quantity |
Enter minimum and maximum order quantity fields. The order entry and quotation entry systems place the order line on hold if these limits are violated. |
Enter a value if a product can be sold only in specific increments. |
See Also
Defining Creation and Update Rules for Installed Products
To define product package components, use the Package Components (PRODKIT) component.
This section lists prerequisites and discusses how to define product package components.
Before you can define product package components, you must specify a package level in the product definition.
See Also
Page Name |
Object Name |
Navigation |
Usage |
PRODKIT_SUMMARY |
Products CRM, Package Components, Package Components |
Define the components of a product package, specify the maximum and minimum number of optional or required components that a customer can select, and specify (for each component) the maximum and minimum quantity that a customer can order. |
Access the Package Components page.
Minimum Total Components and Maximum Total Components |
Enter the minimum and maximum number of components that a customer must purchase to complete an order. |
Package Hierarchy |
Displays the components of primary and nested packages using a tree diagram. |
Package Components
Component |
Enter the ID for each product or package that you want to add to the primary package. A package can consist of a number of individual products and secondary packages. Note. You cannot add a configured product to a package. Configured products within packages are not supported. |
Default Quantity |
Enter the default quantity for the component. This number must be between the minimum and maximum quantity for the component. |
Select whether the component quantity is per package (assembly) or per order. For example, suppose that you need to deliver a manual with a computer package and the customer orders several packages. To send one manual with each ordered package, select Assembly. To send one manual with the entire order (regardless of the number of packages in the order), select Order. |
|
Minimum and Maximum |
Enter the minimum and maximum quantity that a customer can order per component. For example, if a particular component of a package is required but you can only order one, enter 1 in the Minimum field and 1 in the Maximum field. If a component is an optional part of a package, but you can order a maximum of two, enter 0 in the Minimum field and 2 in the Maximum field. Note. A minimum quantity of 0 means that the component is optional. |
OK to Ship Without |
Select to ship the available product package components without waiting for this component. |
To establish product prices, use the Product Price (PROD_PRICE) and the Package Component Pricing (PRODKIT_COMPS_PRC) components
This section provides an overview of product pricing and discusses how to:
Set prices for individual products or product packages by using top-level pricing.
View prices for package components.
The sources and definitions of product prices vary depending on how you define products. Note these differences:
Prices for products that are created in PeopleSoft SCM or a third-party SCM system are defined by inventory business units unless the product is nonstockable (for example, a service such as installation).
When you synchronize with a SCM system, you must enter the inventory business units into the Business Unit table in the PeopleSoft CRM system.
Product definitions created in PeopleSoft CRM do not require the inventory business unit field.
In PeopleSoft CRM, the inventory business unit is unknown when a product is ordered, and the system uses the lowest price from any inventory business unit associated with the product.
See Also
Understanding Item Definition in PeopleSoft CRM
PeopleSoft Inventory 8.8 PeopleBook
Page Name |
Object Name |
Navigation |
Usage |
Products CRM, Price, Product Price |
Set prices for standalone products and for product packages by using top-level pricing. |
||
Products CRM, Package Component Pricing, Package Component Pricing |
View prices for each package component for product packages that uses component-level pricing. |
Access the Product Price page.
Ship From Business Unit
Access the Package Component Pricing page.
This page lists the components of the package, the dates on which the component became part of the package, and the date it became obsolete in the package.
See Also
Defining Product Package Components
This section provides an overview of product relationships, lists prerequisites, and discusses how to define product relationships.
PeopleSoft CRM comes with a number of predefined relationship types that enable you to define relationships between products:
Complement
A complement is an accessory to another product. For example, a headset or carrying case might be a complement to a cell phone.
Cross-sell
A cross-sell is a product that enhances or extends the capabilities of another product. For example, a DVD player might be a cross-sell for a television.
Up-sell
An up-sell is a product that is superior to the product that the customer inquires about or orders.
Product alternate
A product alternate is offered in place of another. For example, suppose that the delivery time for a product does not meet the customer's needs. In that case, you might offer a product alternate.
Prerequisite
A prerequisite is a product that is required for another product to function properly.
Replacement product
A replacement product is offered in place of another product that a customer orders if the original product is no longer available.
Service feature
A service feature for a product enhances the main product or service. For example, related service features for wireless service might include caller ID and call waiting.
Agreement
Relates products to all the service agreements that cover that product.
Before you define relationships between products, you must:
Review the available relationships that are delivered with the system.
Define additional relationships that are required by the business.
Specify optional relationship attributes.
See Also
Setting Up Product Relationship Codes
Page Name |
Object Name |
Navigation |
Usage |
PROD_RELATIONS |
Products CRM, Relationships, Product Relationships |
Define relationships between products. |
|
PROD_REL_OVERVIEW |
|
View effective relationships between products. |
Access the Product Relationships page.
Product Relationship |
Select the relationship between the product in the Product field and the product in the Product ID field. |
Product ID |
Enter the ID of the product that you are relating to the product in the Product field. |
Start Date and End Date |
Enter the start and end dates of the relationship. |
This section lists prerequisites and discusses how to enter product notes.
Before you can associate a standard note with a product, you must define the note on the Standard Notes page.
See Working with Notes and Attachments.
Page Name |
Object Name |
Navigation |
Usage |
Products CRM, Product Notes, Notes |
Enter standard or custom product notes. |
Access the Notes page.
Sequence |
Enter a sequence number to specify the order in which notes appear on documents. |
Classification |
Select Standard or Custom. |
Standard Note Code |
Enter the code of a standard note to associate with the product. |
Note Type |
Enter the note type for a custom note associated with the product. |
Text |
Enter the note text for a custom note. If you use a standard note, this field displays the predefined note text. |
See Also
Creating Standard Notes and Product Notes