Database Changes for Siebel Marketing and population of Load Number
Following the upgrade process from Siebel 7.5 (included Marketing with Segmentation Bridge to Analytics 7.7) to 8.1 in our development and test environments, we noticed that Load Number was not populated as had to be.
In more detail, as clearly mentioned in Siebel Database Upgrade Guide (Version 8.1 Rev B, October 2011), in the paragraph titled “Summary of Database Changes for Siebel Marketing” (table 24), records are imported in S_DD_CAMP_WAVE and S_CAMP_LD_WAVE tables and a Load record is created for each campaign occurrence. Then it is mentioned that Load numbers are assigned based on date of execution. Attached to SR you may find a screenshot (Not Sequential Load Number.jpg) that illustrates the issue. Unfortunately, Load Numbers do not follow the date that campaigns were Loaded and Launched.
In more detail, as clearly mentioned in Siebel Database Upgrade Guide (Version 8.1 Rev B, October 2011), in the paragraph titled “Summary of Database Changes for Siebel Marketing” (table 24), records are imported in S_DD_CAMP_WAVE and S_CAMP_LD_WAVE tables and a Load record is created for each campaign occurrence. Then it is mentioned that Load numbers are assigned based on date of execution. Attached to SR you may find a screenshot (Not Sequential Load Number.jpg) that illustrates the issue. Unfortunately, Load Numbers do not follow the date that campaigns were Loaded and Launched.
0