Reading Custom Details in C.I.S. - 5.4 vs. 6.1 - SAS · Details on the MATableForMacros can be...

Know your custom details!Reading Custom Details in C.I.S.

- 5.4 vs. 6.1 -

Use Custom Details as “global variables” – values available for all process (code/custom) nodes in the campaign.

The problem:

Previous presentation: http://www.torsas.ca/attachments/File/06072013/Nanau-CIStudio.pdf

SAS 9.2, C.I.S. 5.4 – values in campaign’s “Brief”:

Over-simplified code:

C.I.S. Code Node

Runs successfully !

SAS 9.2, Customer Intelligence Studio 5.4 – expected behaviour

C.I.S. Code Node

SAS 9.2, Customer Intelligence Studio 5.4 – expected behaviour

SAS Log shows there is an actual SAS dataset referred by the macro variable MATABLEFORMACRO,

Which is read, and the output table is created:

C.I.S. Code Node

SAS 9.2, Customer Intelligence Studio 5.4 – expected behaviour

PROC PRINT shows the content of the output table:

The Custom Details defined in “Brief” – Category = CAMPAIGNUDF

C.I.S. Process Node

SAS 9.2, Customer Intelligence Studio 5.4 – expected behaviour

Runs successfully !

C.I.S. Process Node

SAS 9.2, Customer Intelligence Studio 5.4 – expected behaviour

The log shows that MATABLEFORMACRO was read and the output table was successfully created.

The content of the output table shows the values in Custom Details.

SAS 9.3, Customer Intelligence Studio 6.1

When migrating a SAS 9.2 (MA 5.4) campaign to SAS 9.3 (MA 6.1) and there is a Briefsection in the source campaign, then all custom details in this Brief will be grouped in the destination campaign under one Custom Details page called “Brief Custom Details” by SAS.

For the purpose of this presentation a Custom Details page named “Brief Custom Details” was created to mimic a migrated campaign.

However, there is no need for the Custom Details Page to be called “Brief Custom Details”. You can have the Custom Details grouped in any number of pages – they should all be retrievable in the MACROVAR Table.

SAS 9.3, Customer Intelligence Studio 6.1

The definition:

Actual values for a campaign:

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Code Node

Runs successfully !or … Does it?

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Code Node

The MATABLEFORMACRO is materialized in MATableslibrary and the output data set is created.

… but a PROC PRINT will show no CAMPAIGNUDF category. So where are the Custom Details?

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Code Node

The problem was solved by applying hotfix K78006:

After applying the hotfix the custom details values were read from the MATables and stored in the output SAS dataset:

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Process Node

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Process Node

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Process Node

These are the same settings and code as in SAS 9.2, C.I.S. 5.4, and yet:

ERROR!

What does the log say?

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Process Node

C.I.S. 6.1 uses streams to gather additional information in a stored process!

Define the data stream macrovar in order for the MACROVAR table to be populated.

You refer to a stream by using %maspinit macro.

Can also define data stream neighbor to gather information regarding upstream and downstream nodes from the current Process node. However, neighbor stream is not required in order to access the MACROVAR table.

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Process Node

Define streams (in every single stored process that uses the MACROVAR table)

Data tab (SAS Management Console)

Data Sources and Targets (EG)

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Process Node

Call %maspinit to refer the streams (in every single stored process that uses the MACROVAR table)

Add this line after %STEPBEGIN

%maspinit(xmlstream=macrovar neighbor);

Use SAS Management Console(Execution -> Edit Source Code) if you want to have control on where the code is inserted !• No “Edit Source Code” for Type=Stored

Process (9.2) – must upgrade to see the new tab layout.

EG might remove the %maspinit line, depending on its position inside the code – EG generates additional code!• Will keep the line if after “* End EG

generated…”, but not if above.

Most of the setup info described above can be found in “SAS® Marketing Automation 6.1 User’s Guide”, at:

• Page 145-146 – Define Streams• Page 276-277 - Gather Additional Information

Details on the MATableForMacros can be found in “SAS® Marketing Automation 6.1 User’s Guide” in Appendix 3, “The MACROVAR Table,” on page 323.

Many thanks to SAS Support team for bringing everything together in a nice, brief e-mail!

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Process Node

Once the settings are done, use the stored process in campaign with Custom Details:

Runs successfully !

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Process Node

Once the settings are done, use the stored process in campaign with Custom Details:

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Process Node

Once the settings are done, use the stored process in campaign with Custom Details:

SAS 9.3, Customer Intelligence Studio 6.1

C.I.S. Process Node

Neighbor stream show info about the neighbouring nodes:

Gabriela Nanau

Email: gnanau@cstonecompanies.com

CORNERSTONE Web: www.cstonecompanies.com