Return to Navigation

Running the Basics AE Process

These topics provide an overview of the Basics AE process (BO_BASICS) and discuss how to:

Page Name

Definition Name

Usage

Application Engine Request Page

AE_REQUEST

Submit the Basics AE (BO_BASICS) process.

The Basics AE process reduces the complex tables and relationships contained in the BORM to two flat tables, BO_BASIC_IND (for data that is related to individuals) and BO_BASIC_ORG (for data that is related to organizations). For every customer business object that is enabled for Basics by role or relationship, the Basics AE finds all related business objects and writes the information to the relevant tables for use by the PeopleSoft Online Marketing and Marketing products.

For example, a customer company has four sites, each site has four contacts, and each contact has four contact methods. The process locates 64 (4 times 4 times 4) business objects to get contact information for the customer and organizes this information into a single BO_BASIC_IND record per role and relationship type keyed by the customer's business object identifier (BO_ID), role, and relationship ID. Rows for both the company and the site are populated in the BO_BASIC_ORG table.

On a large database, for example seven million rows, this process might run for several hours. You can significantly improve the performance of this process by enlisting the services of qualified implementation consultants or a database administrator (DBA). Working with these persons, you can tailor the Basics AE process to meet specific requirements and improve process performance.

The contact methods displayed in the Audience result grid are taken directly from the Basic Data tables. To show values for all the contact methods in the Audience result grid, Contact/Consumer contact methods must be set up to follow the corresponding mapping logic for Basic Data.

Step 1: When adding a person, you should ignore the description field, and concentrate on the Type fields. After doing that, remember that the first data entry you make by default becomes the primary contact information for all roles.

Step 2: Go to the Advanced Options section of the Address Book, and manually define the primary address, phone, and email info for each role.

The Basics AE process dynamically reads all enabled roles, relationships, and mappings. To tailor the process for your particular requirements and improve process performance, you can disable or remove the following information:

  • Basic data for roles.

    You are not required to implement all delivered roles for an installation, or copy all implemented roles to basic data. To disable a role for basic data, deselect the Enabled for Basic Data option for the role on the Role Type page.

    The roles that are enabled for basic data as delivered are:

    • Company

    • Site

    • Worker

    • Contact

    • Individual Consumer

  • Basic data for relationships.

    You can also disable relationships for basic data if they are not used. Disable a relationship by deselecting the Enabled for Basic Data check box on the Relationship Type page. The relationships that are enabled for basic data as delivered are:

    • Primary Contact / Company

    • Contact / Company

  • Remove basic data mappings for contact method purposes that are not needed. You can add or clone these mappings if they are needed in the future.

    The basic data mappings are delivered with multiple contact method purpose types associated with each role and relationship. These are the contact method purpose types that are mapped as delivered, and they vary by role:

    • Phone - Business

    • Phone - FAX

    • Phone - Home

    • Email - Business

    • Email - Home

    • Address - Business

    • Address - Home

    To remove a contact method purpose from a role or relationship, display the role or relationship on the Basic Data Mappings page, scroll to the contact method purpose row, and use the Delete Row button.

The DBA might perform some or all of the following actions:

Stripe the Disks on Which Data Resides

Striping is the process of dividing data into blocks and locating the blocks on different physical disks, which enables parallel database processing and speeds up the run.

Run SQL to Detect Problematic Data

The following data conditions can cause the Basics AE program to run inefficiently and can be detected and addressed prior to running the process:

  • Duplicate primary contact methods.

    Use this sample SQL to detect duplicates in the Phone table. You must run the same SQL for the Address and Email tables. To do so, replace each occurrence of the table name PS_BO_SRCH_PHN with PS_BO_SRCH_ADD (for address) and PS_BO_SRCH_EML (for email) before running.

    SELECT BO_ID, ROLE_TYPE_ID, BO_REL_ID, COUNT(*) FROM PS_BO_SRCH_PHN BO_CM_VW  WHERE BO_CM_VW.ROLE_TYPE_ID IN (2, 3, 4, 8, 9, 11) AND BO_CM_VW.BO_CM_START_DT <= { fn CURDATE() }  AND BO_CM_VW.BO_CM_END_DT > { fn CURDATE() }  AND BO_CM_VW.CM_USE_START_DT <= { fn CURDATE() }  AND BO_CM_VW.CM_USE_END_DT > { fn CURDATE() }  AND BO_CM_VW.PRIMARY_IND = 'Y'  AND BO_CM_VW.PROFILE_CM_SEQ = (SELECT MAX(G2.PROFILE_CM_SEQ)  FROM PS_BO_SRCH_PHN G2  WHERE G2.BO_ID = BO_CM_VW.BO_ID  AND G2.BO_CM_START_DT = BO_CM_VW.BO_CM_START_DT  AND G2.CM_USE_START_DT = BO_CM_VW.CM_USE_START_DT  AND G2.CM_USE_ID = BO_CM_VW.CM_USE_ID  AND G2.ROLE_TYPE_ID = BO_CM_VW.ROLE_TYPE_ID  AND G2.BO_REL_ID = BO_CM_VW.BO_REL_ID  AND G2.BO_REL_POSITION = BO_CM_VW.BO_REL_POSITION) GROUP BY BO_ID, ROLE_TYPE_ID, BO_REL_ID HAVING COUNT(*) > 1

  • Duplicate BO_ID in the Person table.

    Run this SQL to detect duplicates in the Person table.

    SELECT BO_ID, COUNT(*) FROM PS_RD_PERSON GROUP BY BO_ID HAVING COUNT(*) > 1

Gather Runtime Statistics

The Basics AE process step CDMXSTAT gathers and updates runtime statistics that are used by the relational database engine to optimize queries and find free space. This provides information to the engine about the distribution of data and improves the chances of index usage. This step is recommended after large numbers of rows are inserted or tables are reorganized, or when indexes are added or removed.

The DBA can disable this step (by making it Inactive in Application Designer) prior to a run if the statistics are already updated.

Drop and Rebuild Indexes

Drop table indexes and re-create them manually after the Basics AE process runs successfully. This is especially helpful on DB2UNIX or DB2 platforms. You can drop the indexes manually or enable the Basics AE process step CDMXDROP to drop indexes

This is the list of indexes to drop and re-create:

  • PS0BO_BASIC_IND

  • PS1BO_BASIC_IND

  • PSABO_BASIC_IND

  • PSBBO_BASIC_IND

  • PSCBO_BASIC_IND

  • PSDBO_BASIC_IND

  • PSEBO_BASIC_IND

  • PS0BO_BASIC_TMP1

  • PS1BO_BASIC_TMP1

  • PS0BO_BASIC_TMP2

  • PS1BO_BASIC_TMP2

  • PSABO_BASIC_ORG_TMP2

  • PSABO_BASIC_ORG

  • PSBBO_BASIC_ORG

  • PSCBO_BASIC_ORG

Inactivate Scheduled Jobs That Can Conflict with the Basics Process

The jobs CM_FLTM (for 8.9 and prior releases) and CM_MAINT (for release 9) are regularly scheduled to synchronize the normalized BORM tables to the flattened contact method tables. This improves access to contact methods for online processing, but can cause performance issues when run concurrently with the Basics AE.

To inactivate these jobs and any others that might cause data conflicts, use the PeopleTools Schedule JobSet Definitions page located under PeopleTools, Process Scheduler. Search for the job name and select Inactive in the Status field. Save the job definition.

When the Basics process ends, reactivate this job.

Use the Application Engine Request page (AE_REQUEST) to submit the Basics AE (BO_BASICS) process.

Navigation

select PeopleTools, then select Application Engine, then select Request AE, then select Application Engine Request

See the documentation for PeopleTools: Application Engine.