Integrating Master Business Objects

This chapter lists prerequisites and discusses how to:

• Integrate items.

• Integrate customers.

• Integrate price lists.

Important! Start all gateways as explained in the CRM Process Integration Pack Installation Guide.

Prerequisites

Before you integrate master business objects, you need to:

• Map PeopleSoft CRM setIDs to sales areas in SAP and item operating units and master organizations in Oracle.

• Map unit of measure values between Oracle or SAP and PeopleSoft CRM.

• Map required storage locations in SAP and subinventories in Oracle applications as inventory locations in PeopleSoft CRM.

Integrating Items

This section provides an overview of item integration, lists prerequisites, and discusses how to:

• Create items in Oracle applications.

• Create items in SAP.

• Check for items in PeopleSoft CRM.

• Check for products in PeopleSoft CRM.

Understanding Item Integration

Items are created in Oracle or SAP and propagated to PeopleSoft CRM, which creates new items as well as corresponding products. This process goes one way only: from Oracle or SAP to PeopleSoft. This integration supports the following scenarios:

• Item created in Oracle or SAP is propagated to PeopleSoft CRM.

• Item updated in Oracle or SAP is propagated to PeopleSoft CRM.

  Saving the item definition in Oracle or SAP automatically initiates the process to propagate items to PeopleSoft CRM.

  Because items in PeopleSoft CRM can be attached to multiple products, only create items in Oracle or SAP. New products created in PeopleSoft CRM will not have a corresponding cross-reference key.

  Item Full Sync is not supported. Configured items (configurators and packages) are not supported.

  Item substitutions are not integrated from Oracle or SAP to PeopleSoft CRM.

Prerequisites

Before you can integrate items, you need to:

• Define values in Oracle for:

  • Item status.

  • Serial number control.

• Define values in SAP for:

  • Material types.

  • Serial number profiles (for serialized materials).

    If the serial number profile is attached to a material, a serialized flag is marked in PeopleSoft.

• Define values in PeopleSoft CRM for:

  • Item number and product ID control values (autonumbering).

  • Item groups and product groups.

  • Item status.

  • Stock types.

  • Installed product default status settings.

Pages Used to Integrate Items

Creating Items in Oracle Applications

Access the Master Items screen.

To create items:

1. Select an item master organization.

2. For integrating items, specify details for:

   • Item ID.

     Keep item IDs to 18 characters or less. Although item IDs in Oracle can be up to 30 characters long, PeopleSoft item IDs can only be 18 characters. If an item ID created in Oracle has more than 18 characters, the corresponding PeopleSoft item ID will contain only the first 18 characters of the Oracle ID.

   • Short and long description.

   • Unit of measure.

   • Current status.

   • Inventory organization to which the item is assigned.

   • Item group and category definition.

   • Item type. For example, indicate if the item is finished goods or a serviceable item.

3. Assign the item to organizations.

4. Save the record.

See Also

Oracle applications 11.5.5 documentation

Creating Items in SAP

Access the Create Material Screen.

To create items:

1. Enter the material name.

2. Select the industry sector to which the material belongs.

3. Select the material type.

4. Click Enter

5. Click Organization levels.

6. Select the plant, sales organization, and distribution channel, and click Enter.

7. On the screen that appears, specify details for:

   • Unit of measure.

   • Material group.

   • General item category group.

8. Enter all other mandatory data and save the record.

9. To trigger the material creation, enter the transaction code BD21 in the command field.

10. Select the message type as MATMAS.

    An outbound intermediate document for that material is created.

See Also

SAP R/3 release 4.6C documentation

Checking for Items in PeopleSoft CRM

Access the Item Definition page.

Check if the information that you transferred from Oracle or SAP is reflected in PeopleSoft CRM.

See Also

Defining Items

Checking for Products in PeopleSoft CRM

Access the Product Definition page.

Check if the information that you transferred from Oracle or SAP is reflected in PeopleSoft CRM.

See Also

Setting Up Product Definitional Elements

Integrating Customers

This section provides an overview of customer integration, lists prerequisites, and discusses how to:

• Create customers in PeopleSoft CRM.

• Update customers in PeopleSoft CRM.

• Check for customers in Oracle applications.

Understanding Customer Integration

You can integrate customer and contacts data between PeopleSoft CRM and Oracle or SAP. This integration supports the following scenarios:

• The customers and contacts created in PeopleSoft CRM are propagated to Oracle or SAP.

• The customers and contacts updated in PeopleSoft CRM are propagated to Oracle or SAP.

• Customers and contacts updated in Oracle or SAP are propagated to PeopleSoft CRM.

  Although PeopleSoft CRM supports multiple bill-to and ship-to addresses, multiple bill-to and ship-to addresses are not supported in the integration with SAP. Use a single bill-to and ship-to address only. The primary address specified is used by the system.

  Consumer and Site Sync not supported. Contacts are not populated from SAP to PeopleSoft CRM.

  Currently, one-time ship-to and bill-to address and contacts are not handled.

  Save the customers in PeopleSoft CRM to automatically integrate to Oracle or SAP.

  Important! A customer or contact record is only ready to be transferred after entering key data elements (such as bill-to and ship-to addresses, contact details, and correct status).

Prerequisites

Before you can integrate customers, you need to:

• Define values in Oracle for:

  • Customer and site numbering.

  • Operating units.

  • Profile classes.

• Define values in SAP for:

  • Organization unit settings.

  • Customer account group settings.

• Define values in PeopleSoft CRM for:

  • Customers and contact autonumbering.

  • Customer types.

  • Location types.

  • Country and address formats.

  • State codes.

  • Site types.

  • Time zones.

  • Business object roles.

  • Industry types.

  • Payment terms and payment methods.

  • Name type defaults.

  • User roles.

Pages Used to Integrate Customers

Creating Customers in PeopleSoft CRM

Access the Company page.

To create customers:

1. Specify the details for:

   • Company name, name type, purchasing options, currency code, and currency type.

   • Ship-to, bill-to, and sold-to addresses and start and end date.

   • Phone number and effective dates.

   • Contact name type, first name, last name, and purchasing options.

   • Company site, site contacts, and relationships.

2. Save the record.

   Important! The county and postal codes are mandatory for integrating customers to Oracle, and the postal code should be valid for the county.

Checking for Customers in Oracle Applications

Access the Customer Addresses screen.

Check the customer details on this screen.

Important! For all customers propagated from PeopleSoft CRM, the sold-to, bill-to, and ship-to check boxes should be selected at the header level.

See Also

Oracle applications 11.5.5 documentation

Checking for Customers in SAP

Access the Customer Display screen.

The customer general details are displayed.

See Also

SAP R/3 release 4.6C documentation

Integrating Price Lists

This section provides an overview of price list integration, lists prerequisites, and discusses how to:

• Create price lists in Oracle applications.

• Create price lists in SAP.

• Check for price lists in PeopleSoft CRM.

Understanding Price List Integration

The list price is the base price used for the item. Master price lists are created in Oracle or SAP for pricing a product or service. Price list integration is one way from Oracle or SAP to PeopleSoft CRM. The integration supports these scenarios:

• Price list created in Oracle or SAP is propagated to PeopleSoft CRM.

• Price list updated in Oracle or SAP is propagated to PeopleSoft CRM.

  Saving the price lists in Oracle or SAP to automatically creates a message in PeopleSoft CRM.

  Price lists can be created in SAP using one of these options:

• Material price list: Create price list for materials.

• Price list: Create price list for a group of customers, based on price list type and currency.

• Individual price list: Create price list for a specific customer.

Prerequisites

Before integrating price lists, you need to:

• Map business units in PeopleSoft CRM to operating units in Oracle.

• Define values in SAP for:

  • Condition types.

  • Price list types.

  • Sales organizations.

  • Distribution channels.

  • Divisions.

• Define values in PeopleSoft CRM for:

  • Pricing key fields.

  • Pricing rule sequences.

  • Price rules.

  • Price sets.

  • Exclusive pricing.

  • Price lists.

  • Services.

  • Service activities.

  • Purchase options.

  • Transaction types.

Pages Used to Integrate Price Lists

Creating Price Lists in Oracle Applications

Access the Advanced Pricing - Price Lists screen.

To create price lists:

1. Enter the price list name and description.

2. Select Active.

3. Select the currency code and enter effective dates.

4. Specify the product context as Item.

5. Select the product attribute.

6. Enter the product value, unit of measure, line type, and item value.

7. Save the price list.

Creating Price Lists in SAP

Access the Create Condition Records screen.

To create price lists:

1. Select Prices, Price List.

2. Select the sales organization, distribution channel, price list type, and currency.

3. Enter values for the following:

   • Condition type.

   • Material.

   • Rate.

   • Valid on and valid to dates.

4. Save the record.

   If the price list created in SAP is purely based on material, the Name field is populated with the sales organization concatenated with distribution channel and condition type. For each material in a SAP price list, for the particular pricing condition, equivalent price list line items are created in PeopleSoft CRM.

   If the SAP price list is based on price list type and currency, the Name field in the header of the PeopleSoft Price List page is populated with the sales organization concatenated with the distribution channel and price list type.

   If the SAP price list created is based on a customer, the Name field in the header of the PeopleSoft Price List page is populated with the sales organization concatenated with the distribution channel and the first four letters of the customer name.

5. To trigger the price list creation, enter the transaction code BD21in the command field.

6. Select the message type as COND_A.

   The outbound intermediate document is triggered, which guarantees that the price list has been created.

Checking Price Lists in PeopleSoft CRM

Access the Price List page.

Check for the following price list details in PeopleSoft CRM.

• Price list ID.

• Description.

• Status.

See Setting Up Price Lists.