Data Extracts for everybody A SAS Customer Intelligence Studio implementation

Transcription

1 Data Extracts for everybody A SAS Customer Intelligence Studio implementation

2 1. Preparing for SAS - C.I.S. Building the infrastructure

3 Purpose Drag-and-drop environment for business to create their own data pulls; Design once, deploy multiple times same DB structure, same workflow, different connection strings (database and user); Assign coding to the data on the fly; Write back to the database; Keep implementation under change management; Solution SAS Customer Intelligence 5.4 on SQL Server 2008 R2 databases

4 SAS Metadata Folder Structure Libraries all libraries and tables Information Maps all information maps Business Contexts all business contexts Stored processes all stored processes Scheduler jobs all jobs that will be schedule to execute different tasks Use folders to setup security!

5 Configure access to external database (SQL Server 2008) SQL Server login with appropriate access to the database: DEMO_SAS_User SAS Authentication Domain Set the login on a group that contains the users who will access the database SASUSERS group - all registered users PUBLIC group - all users (including users who do not have an individual SAS identity)

6 Server definition

7 Libraries

8 Information Map Presents the data to the user in a familiar manner Hides database implementation details, like actual tables and columns names or tables relationships Can include calculated fields or/and filters Built around one or more SUBJECT different points of view for your analysis ex. Customer, Household, Account Behaviour controlled by Custom Properties Built using: SAS Information Map Studio PROC INFOMAPS

9 Information Map Data Sources and Relationships

10 Information Map Custom Properties

11 Information Map Folders and Data Items Folders in IMAP = Categories in CIS one folder: fields from one or more tables and/or calculated fields Data Items in IMAP = Data Items in CIS

12 Information Map Folders and Data Items: Custom Properties Folder Numeric Data Item Character Data Items

13 Information Map Metadata definition

14 Business Context Is based on an Information Map Holds Resources for Customer Intelligence Set BC security to control access to Customer Intelligence resources

15 Stored Processes for use with CIS Process Nodes Must use keyword MAUser Must deliver result as Package only

16 Stored Processes for use with CIS Process Nodes One code, multiple connection strings: hidden parameter (prompt) that takes connection parameters from a file.

17 Customer Intelligence Studio We needed global variables to transmit values across the entire CIS flow : use Campaign s Brief. A campaign definition is a template to start from. Created in SAS Management Console, under Customer Intelligence Plug-In. A campaign definition is a resource in a business context, and by that is associated with an Information Map. The required variables define the uniqueness of the data pull.

18 2. Working with SAS - C.I.S. Creating a data extract

19 SAS CIS campaign Everything in CIS is under a SAS Business Context. New Campaign select the definition you want to use. The parameters in Brief are already available; If there were parameters with default values, they would be displayed too. Must fill at least the required parameters; Save the campaign.

20 SAS CIS campaign - Counts All numbers represent DISTINCT Subject IDs!

21 SAS CIS campaign - &MATableForMacro

22 SAS CIS campaign level

23 SAS CIS campaign level with duplicates

24 SAS CIS campaign level without duplicates Cannot pick which records (package code) to keep in the export when duplicates are dropped!

25 SAS CIS campaign ExportRecords level Surrogate subject for Export define it at Information Map level

26 SAS CIS campaign ExportRecords level

27 SAS CIS campaign ExportRecords level 5, , ,870 = 15,026 = 15,020 (non-seeds) + 2 (SEEDs) x 3 (packages)

28 Subject must be ExportRecords Export definition must be of ExportRecords type

29 Gabriela Nanau CORNERSTONE Web: