Bookshelf Home | Contents | Index | Search | PDF

Siebel Marketing Guide > External Data Mapping >

Mapping Tables to Customer Hierarchies

---

Siebel Marketing constrains access to tables and fields using the following rules:

The first (primary) targeting level in a customer hierarchy can map to any table in the data source (provided it has the customer key for the primary level).
Successive targeting levels of the hierarchy can only map to tables that were also included in the level above it.

See sample customer hierarchy in Table 19.

Table 19. Sample Customer Hierarchy Design

Customer Hierarchy Name	Levels	Tables	Fields
Account hierarchy	Account (primary level)	ACCOUNT	ACCOUNT_ID
		TRANSACTIONS	ACCOUNT_ID
		DEMOGRAPHICS	SSN
		SUMMARY	ACCOUNT_ID
SSN/Account hierarchy	SSN (primary level)	ACCOUNT	SSN
		DEMOGRAPHICS	SSN
		TRANSACTIONS	SSN
		SUMMARY	SSN
	Account (secondary level)	ACCOUNT	ACCOUNT_ID
		TRANSACTIONS	ACCOUNT_ID
		SUMMARY	ACCOUNT_ID

Use the following guidelines when selecting tables to map to each level of the customer hierarchy:

Locate each table that holds the identifier for the primary level (Key 1), and map those tables to the primary level. In Table 19, these tables include Account, Demographics, Transactions and Summary.
Determine which of the tables also contain the second level identifier (Key 2) and map those tables to the second level.
Continue this process for lower levels of the hierarchy if required, making sure that any tables mapped to a level consist only of tables included in the level immediately above it.

CAUTION:  You must create the appropriate caching settings for the joins between fields that you map to the customer hierarchy. If settings are incorrect, some tasks will fail. For additional information, see Guidelines for Caching.

To map tables to customer hierarchies, perform the following tasks:

Mapping an Existing Table to Customer Hierarchies
Mapping a New Table to Customer Hierarchies

Bookshelf Home | Contents | Index | Search | PDF