I'm beginning to think this warrants a technical support track, but you could also look at the info in this SAS Note: http://support.sas.com/kb/55/831.html   It's specifically about retrieving data, but that doesn't mean it wouldn't help with inserts. It's worth checking to see if the hotfix is relevant to your environment, anyway, and installing it if it isn't already. ... View more

Does this happen frequently or only once? If it's frequent, I would suggest opening a track with technical support so they can look into the root cause. Also don't forget that the business context code settings can be overridden in the communication definition, so have a look at the actual communication with the duplicated code to see if it is in fact editable or not. ... View more

This feels like a timezone issue, perhaps. What timezone is your RTDM server using? What timezone is the database using? ... View more

SunnyM -    I think there are probably some clarifying questions that might help get you an answer (either from me or from someone else), so let me ask a few and see what we can do...    When you say "SAS CRM", which product are you talking about - Marketing Automation? Real-Time Decision Manager? something else? For integration, what's the use case? Calling the CMS at the end of a campaign to stage the list of customers and what offer they should get? Or having the CMS somehow call SAS Customer Intelligence? Are there volume or performance considerations we should know about? Thanks, and hope we can get you some feedback based on a little more detail. ... View more

I agree that 2GB is probably not enough, but do be a little cautious with increasing the max heap size too much, as you might experience some intermittent performance hits when garbage collection occurs. We try to keep it to no more then 8GB, and only go that high if 6GB isn't sufficient. You might also want to increase -Xms at the same time so you don't have performance issues when new memory needs to be allocated.   The other thing that can cause seemingly simple things to intermittently take a long time is if you don't have enough load balanced connections defined on the Stored Process Server that's supporting MA (if you have just one, it's SASApp, but depending on your installation, you might have more than one and could have a "SASCI" or "SASAMA", etc. server context). The out-of-the-box configuration includes 3 that are configured to handle multiple concurrent jobs, but we like to re-configure that to have ~20-30 that handle just one job at a time, which avoids short jobs getting queued up behind longer-running ones. Check out http://support.sas.com/kb/40/567.html for more details, and contact support@sas.com if you have questions about this. ... View more

I have to admit I saw this post yesterday and have been thinking over why it would improve campaign execution times... do you have selection criteria that uses history? If so, having a partition on CONTACT_DT and always using a date range could be of considerable benefit. As far as best practices go, this is more of an organization-by-organization decision based on campaign requirements (selection criteria use cases, as I mentioned above) and reporting and/or analytical requirements. Moving old records off to a data warehouse would allow you to develop historical reports (different from what I would consider your operational campaign reports that are run against the CDM). Creating some DI Studio jobs (or other ETL) to schedule this kind of housekeeping is probably your next task. ... View more

I know for sure that PROC INFOMAPS lets you create information maps programmatically. I use it in combination with an Excel Spreadsheet to help consultants create initial information maps quickly (by using VBA in Excel to generate the PROC INFOMAPS code), but I'm not sure what capabilities it has for updating existing maps. Might be worth a look, though.   You'll also need some additional SAS code to register those new views in SMC and update their metadata if you want to automate this end-to-end. I don't have an example handy of registering new tables, but for updating metadata I used this recently:   proc metalib; omr (libid="&libid"); /* get this from SMC - it's the second half of the full object ID */ select (campaign communication); report; run;   ... View more

Generally speaking, if you want to load custom data, you'll need to write your own ETL process to create the LASR staging data. The out-of-the-box macros are available to drive the out-of-the-box reports, and there are some macros outlined in the Guide as you mentioned that you might be able to leverage; you can find the code ("ci2lasr.sas") under sashome/SASFoundation/9.4/sasautos (unix) or sashome\SASFoundation\9.4\ma\sasmacro (Windows) for reference - though please don't modify that one, as any changes could be overwritten by hotfixes, upgrades, or maintenance release, ... View more

@janezou wrote: If we can create the report in VA and put back to MA as a template for users to review, as you mentioned, that would be a great feature to have.   Here is what I did: 1) Created a report in VA in "Data Exploration", saved the report (campaign_Report, as type of "Visual Exploration") in a folder. 2) Opened SMC, saw the campaign_Report in the right folder 3) However, when I right click the report, only saw "General" and "Authorization" in "Property". Cannot see "Extended Attributes".   Are there settings to be changed in order to see "Extended Attributes"?   Thanks, Shill! I'm not sure why you woudln't be seeing that. I suggest you open a track with Technical Support (support@sas.com). Sorry! ... View more