Loyalty: Reporting v. 60
Released 07th of July 2020
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.
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.
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. |
Loyalty: Reporting v.59.1-8
Released 25th of June 2020
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 bonuspoints = 300, only 200 points will be subtracted.
New bonus rule for Bonus campaigns
(TFS: 177551)
New Bonus Rule "Ignore items with campaign bonus" has been added. Under "Loyalty Programs" --> "Bonus" a new checkbox is added under bonus rules. If the new bonus rule is checked, members will not get any bonus points when purchasing items that gives member specific campaign bonus.
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).
Improvements
Description | |
|---|---|
Loyalty | Fetching coupons from Chain Web (TFS: 178764) When we get coupons linked to unknown member in Reporting, we create this member. This is done to secure that package will not fail if member is not updated in Reporting yet. |
Loyalty: Reporting v.58
Released 23rd of March 2020
Import of stamps
(TFS: 168533)
To keep track of stamp card campaigns we now import stamp cards from Chain Web.
Stamps are imported by RT-job with the following two packages, these must be enabled first:
DimStampCard - Imports stamp card headers.
FactStampCard- Contains latest transactiondate and stamp card balance per member and campaign.
Two new views related to stamp card:
pub.vStampCards - One row per member and campaign.
CampaignReference - Campaign reference from DimCampaign.
MemberNumber - Member number
StampCardKey - Id for stamp card in Chain Web.
StampCardBalance - Current balance for stamp cards.
TransactionDate - Timestamp for latest stamp card transaction.
pub.vStampCardLines - One row per member, campaign and stamp card transaction.
CampaignReference - Campaign reference from DimCampaign.
MemberNumber - Member number
StampCardKey - Id for stamp card in Chain Web.
TransactionDate - Timestamp for stamp card transacton
StampCardTransactionTypeName - Type of stamp card transaction.
Value - Number of stamps used in transaction.
InstanceNumber - Which instance. E.g. Every 5. item for free. First 5 items had instance 1, next 5 items has instance 2.
ReceiptID - Receipt id from cash register, if available.
Comment - Comment on transaction, if available.
Coupon information from Chain Web
(TFS: 168541)
When fetching coupon information from Chain Web we now also include TransactionID from used coupons when available.
New view is created to see all coupons:
pub.vCoupon - One row per coupon.
CouponNumber - Coupon number
ValidFrom - Campaign valid from date
ValidTo - Campaign valid to date
MemberID - Member number
Used - If coupon is used (1 = Used, 0 = Not used).
TransactionID - Receipt number where coupon is used.
CampaignReference - Campaign reference
OfferNumber - Offer number.
Note: Upgrade script will delete all existing coupons, they will be imported again next time N-job runs.
Campaign detail
(TFS: 169114)
To show more detail from campaigns, we now fetch price rules and offer details from Chain Web.
New package must be enabled: Offerdetails.
New views are created for this data:
pub.vPriceRule with following columns:
PriceRuleKey - Price rule key
PriceRuleName - Price rule name
ItemId - EAN / item group number
ItemType - If price rule is for Article (item), ItemGroup (item group), Model eller Color (color).
DiscountGroupItemType - Type discount group (Condition, Effect, Exept).
CampaignReference - Campaign reference
OfferNumber - Offer number.
New view to show offer details, pub.vCampaignOffer:
CampaignReference - Campaign reference
OfferNumber - Offer number
Name - Offer name
OfferStart - Start date on offer
OfferStop - Stop date on offer
New view for member sales data
(TFS: 171445)
3rd party is able to use this view to fetch data on members who have recently made a purchase in a store and can use this data to conduct a customer survey.
Description of view pub.vMemberSurveyFollowUp, one row per member / receipt
StoreNumber - Store where receipt is created.
ReceipID - Receipt number
TransactionDateTime - Timestamp from receipt.
ReceiptAmountIncVAT - Sum of receipt with VAT, except excluded items.
ReceiptNumberOfItems - Quantity of items in receipt, except excluded items.
MemberReceiptLastYear - Number of receipt for this member last year.
MemberNumber - Member number
MemberFirstName - Member first name
MemberLastName - Member last name
Email - Members e-mail
Mobile - Member mobile number
AllowContactOnMobile - If member has agreed to be contacted on mobile.
AllowContactOnEmail - If member has agreed to be contacted on e-mail.
AllowContactByOrdinaryMail - If member has agreed to be contacted on regular mail.
Sex - Sex of member
YearOfBirth - Which year member is born.
PostalNo - Postal number for member.
CashierFirstName - First name of cashier for this receipt
CashierLastName - Last name of cashier for this receipt.
OperatorKey - Cashier number for this receipt.
To create comma separated list of items which should be excluded from Sum and quantity of items. Alter view and edit this line:
AND da.EAN NOT IN ('EAN1','EAN2','EAN3') -- List of EANs for plastic bags to be excluded from amount/qty
Improvements
Modules | Description |
|---|---|
Member | Lookup member from POSLog (TFS: 158811) We have made improvements when doing lookup on members from POSLog. If LoyaltyNumber is available we always use this for lookup before checking identificators. |
Member Campaigns | Import of coupons (TFS: 164210) The performance of importing coupons from Chain Web has been significantly improved. |