How Corporate Campaign selections are stored

You should design the list selection flowchart that is associated with a Corporate Campaign so that when it runs in Campaign the selected customers are stored in the Distributed Marketing system database, in the uacc_corporate_lists table.

Generating and storing the list through the flowchart

Note: Before the flowchart can store the list selections in the uacc_corporate_lists table, the table must be mapped in Campaign.

List selections are made through a Select process in the flowchart. You define the SQL statements to select desired customers for the Corporate Campaign. For example, the Select process might select all customers with a savings account within a specific range.

You can use one or more Select processes to select the target customers for the Corporate Campaign list.

Following the Select processes, you add a Snapshot or Extract process. When you configure the Snapshot or Extract process, ensure that you:

Export the selections to the uacc_corporate_lists table.
Select the Append to Existing Data radio button.
Note: The uacc_corporate_lists table contains the history of all the generated lists. If you select either Replace All Records or Update Records, the contents of the table are overwritten or updated and all the lists are deleted or updated.

Mapping database fields to the uacc_corporate_lists table

In the list selection flowchart, you must map fields in your customer database to the following fields in the uacc_corporate_lists table:


Field	Field Type	Saved Value
ListId	Campaign Generated Field	`CampaignCode`. Generated field `CampaignCode` should be mapped against `ListId` field.
AudienceLevel	Derived Field	The audience levels configured in the List Manager module must be hardcoded with the values configured in the listmanager_tables.xml file (for example, "P" for People Table or "P/C" for People Table/Contract Table).
UserBranch	N/A	Not required.
UserID	`<Customer_User>`	The user name of the field marketer or corporate marketer that is running the flowchart. Note: Internally, all flowcharts are run by the same Campaign user. The flowchart uses the UserName variable to store in the UserID field the user name of the field marketer or corporate marketer who ran this flowchart.
GenerationDate	`<Generate_Date>`	Date on which the records are generated. This can be a specific date, a formula, or a date indicated in the campaign.
Status	Derived Field	All records are initially set to T, for To Accept, which corresponds to Waiting in the user interface. List records can have one of four status values, depending on the actions of field marketers during validation: T: To Accept V: Accepted A: Added D: Deleted
Audience Level ID	`<CustomerID>` or `<AccountID>`	The unique ID for the target of the campaign, typically a Customer ID Or Account ID.

You may need to map additional fields for filtering purposes. For example, if the region_id column was added for Data Level Filtering, you need to map it as well.