aic

Currently im working on cmm productinzed :

 

ill move current logic to prod there might be some adjustments that we need to slightly adjust this doesn’t have any dependency on any of tables so we can move separately to prod nothing will get impacted. So once all goes in . we create sep folder for emdm separately and us separately.

 

On brand res kantar data for that currently nothing is in production and for that data did we do explicit additional logic or its just dbt and 365 injestion for us. We are using similar thing its coming from 365 only no new mechanism. Everything that we are doing is in dbt only.

 

Brand health gold layer implementation :

 

for all stories I have pr links in comments. This will have 3 gold tables we have in in pr files in brand res we have brand res models.yml bgs emdm brand health funnel fatc sql bgs emdm brand health key attritutes fact sql bgs emdm brand health mds fact sql. All 3 logics are fixed one problem w key attributes in line 12-21 we have entry for whcihc dat level granularity we are sendin g maks mentioned this is based on week level but in logic we have yr level grand at line 93. But other 2 tables are yr level granularity. Either he shd have missed in that case he shd update week to year he. If he asking to make changes to week level only we shd get from where we shd get. We don’t have week level granularity. This is the only thing missing. We have created ct product id and cal id for all 3 tables like 53 since only for key attributes fact sql contractdict since calender id never matches. In line 62 source it was already there. So In this pr only if you want to move media reach we can simple bring it to brnd resonance foler also right. Maybe we can send it to prod and seggretage us and emdm separately. Brand res is purely based on brand health right yes

 

 

 

cmm gold layer implementation :

pr link opens to net sales value roas for bgs emdm

in files bgs emdm mmm roi fact sql

if you see us we use mm roi line 34 there is one more story that I assigned to you that is for moving us table also to same logic. Replace it w approved fact and do some testing like check w country code and see if we’re getting the same data or not. So this logic also we have made all changes this one also ill try to move prs to prod. We will add scheduled ones separately. We have kpi thing at line 175 all these things available so for these scenairios we will push that to schedule. We already have a scheduled job we will just make this job also part of it. As mmm roi is just a view so we just have to run it once it comes under market effectiveness view. That runs only once if there are any code changes we trigger it manually. Nav said other pre commit ill push you can make dag changes also us model thing it has to be changed and tested if were getting the crt data or not. So Satwik pls login to this branch work on this and add this mmm roi changes also. Satwik if you see here we will have dags at line 82 market effectiveness so I just checked w us model and added if there is any change you can add it. U better add new user story which bgs mm roi fact also you just make changes do testing and add in same pr so that itll be easy for checking also.

 

 

Add logic to generalize are and exper:

Small change ope pr link files emdm brand health image profile fact .sql we made small change like 19 for brand image attribute but this is what maks said was to add this logic Arvind said he has to check but for meta data also we added this line 19 thing this is one thing we need to check w Arvind whether we have to move this or not. Even if we push theres no impact. For now try to push pr and add changes Arvind will be approver if he comments anything you guys can remove like 19 logic for this pr this is the only change. We are waiting for this.

 

Media spend table for ds team:

Go to pr files

They are ok to move it to prob we have no other issues w this thing so this is bgs media spend fact sql. For their dashboards they have certain logic we have made some changes on existing logic and created this table like 60. This is for US. Let says if we have changes we can add on top of this at line 5 we have loop doc for this. This table almost it will go to prod. Getting the approvals might be the only thing

 

 

So main are productinalization of cmm and brand res and some small cgane are an expert smtg these 3 are major ones. So he said cmm one is net sales values roas for bgs emdm expansion. and brand health funnel gold layer. Brand res one cmm one are an expert are 3 prs if theyre coming up any changes.

 

 

 

Implementation of share of search story you have one attachement. .txt this is the model better you connect w him babis regarding this before starting the implementation he wil lhve loop doc also this is just the compiled logic. Create all required for dbt model. I think

 

Mm roi fact to approved fact you can just make change sin same tract this is the cmm model.

 

Media spend table: into prod. Ill do it and prod and share you pr if there is any change just make changes.

 

regarding 1020 had a meet w nav so there are comments pr is not yet published. So fix documentation issue not much impacted if you feel not relevant direct resolve. If sql issue if its valid check it first then make changes and push it. Or if there logic change don’t do that will change data. Example if 10 col are there 5 col are used 2 are not used then you can remove. Or if youre using max min and its suggestion smtg else do it its fine. But if youre taking current yr data so itll give current. But lets say if it suggests here from fiscal calender functionally don’t change anything only logical change if suggest then do. Take this branch do change push it to that branch only.

For prod and pack. Every model will have dbt tetss. Either you need to update whole test cases or just create new yest cases. If they say instead of that test case you need this you shd add it. Add productionization and add 2 story points. Just whatever prs assigned take comments fix those and push it. Fiscal quarter ai comment. I asked shd we derive from khc fiscal calender dim? Said no if you try to pick it from fiscal itll have multiple yr columns. This is like month level granularity. That’s y we are talking cal week as yr month that’s 202606 so we cannot go for week level granularity. Taking sysdate and current yr same we do for current querter also. For this one we can mention current yr we are picking not based on week start and end bu ton current date alone mention that and resoleve this comment. Documentation issue change the comment line.

Cal weeks is just for picking and calculating just to get that start and end data of particular week alone. Inner join, this is already published. Resolve it push changes add comments click resolve build will run again once it succeeds these ppl will approve the pr

 

 

Babis : so you can comipile sndbox table w that script and send it to me for validation

 

Shweta:

He literally gave you everything just go ahead and create sandbox table for him. You can have this one placed in a model give it a run and in line 6 its pointing to raw source table instead of that use ref table for production and run through dbt model. Create model in omni exc folder. Then place this one there. Config materialization as table . once table is created you can adjust as per dbt standarnds and as per that you can push it in particular feature branchbut as it is straight forward. You just need cal date int and I think you do not need calender id coz cal id will be created in the gold model so you need cal date int

 

 

You need to bring max month and data as cal date int just add that and get this model created.