Document status: RELEASED
Date:
Version Requirements can be found in Reporting Release Documentation.
Bonus campaign
(TFS: 176377)
New view to show how much bonus amount member is given in a specific campaign.
View returns only data from member campaigns with campaign bonus as price rule.
New view: pub.vBonusCampaign
Columns:
CampaignNumber
CampaignName
TransactionDate
TransactionID
MemberNumber
EAN
OriginalFaceAmount
BonusAmount
Support for new bonus rule to exclude bonus points on campaign items
(TFS: 178520)
Bonus calculation in Reporting supports bonus ruletype 9. When this type is enabled, items which are included in campaigns will get 0 bonus points. BonusAmount is calculated as before.
Bonus rule must be enabled in Chain Web and transferred to Reporting by existing package "BonusRulesConfig.dtsx" (triggered by N-job).
Negative balance in bonus calculation
(TFS: 176950)
Bonus calculation will never calculate negative bonus points when doing e.g. returns. If balance = 200 and negative bonus points = 300, only 200 points will be subtracted.
View for member
(TFS: 175318)
New column "StreetAdress" added to existing view pub.vMember
Member associations in member view
(TFS: 175769)
Existing view pub.vMember is extended with a new column “MemberAssociationList”. The column shows comma separated lists of member associations related to member.
Improvements
Modules | Description |
|---|---|
Loyalty | Member associations (TFS: 175660) When fetching member associations from Loyalty, we create members that does not exist in Reporting, to prevent the package from failing. Fetching coupons from Chain Web (TFS: 178764) When we get coupons linked to unknown member in Reporting, the member is created. This is done to secure that the package will not fail if member is not updated in Reporting yet. Sale linked to member (TFS: 179365) When Reporting reads member number from POSLog we remove prefixes (e.g. 1:) before doing lookup. This is done to prevent the package to fail when reading data with poor quality. |