LSA++ Simplified
Vložit
- čas přidán 27. 06. 2020
- LSA++ Simplified
A lucid, brief and consolidated video explaining LSA++ for BW4HANA.
There are umpteen PDFs, Blogs and videos on LSA++ already but just the sheer volume of material and the different terminologies used in those blogs, there's still a lot of confusion in terms of what are the different layers, which Infoproviders fit into which layer and how to effectively model with LSA++.
This video dispels all the doubts and gives you clear and easy to follow steps for LSA++. - Věda a technologie
This is how the explanation should be precise and very clear.I have seen so many videos but most of the presenters present in a confusion manner whereas this video is very clear and very simple. Great work and all the best.
So simply explained but yet so informative.. You are Lionel Messi of bw4hana..
Very well explained sir.Hope to see more videos on SAP BW4 HANA concepts.
Beautifully explained and simple.., thanks
Well done on explaining this! Superb. So much insight on this now -thanks!
Such a clear information. Thank you so much!!
Excellent job! Thank you for sharing Debanshu .
Thank u sir .. for that such great explaination ....
Thank you!
Well explained sir. Thanks for ur time and this video
Very good explanation!
Very well explained sir. Hope to see more videos on SAP BW4 HANA concepts.
Actually sir, I am looking for SAp BW on HANA, SAp BI ABAP, SQL using in BW.. Plz if possible upload all these videos thank you
Good explanation.. Thank you sir.
Great explanations 👍🏽 thanks
Perfect!! Loved it :) Thanks alot
Why do we need to load data twice from source..even if we load from staging layer to next level ADSO, it still serves the purpose of corporate layer, rebuilding the data in future if needed...this also avoids loading from source..loading from transactional system may not be the better option when compared to loading from staging to reporting layer ADSO..pls clarify..and thank you very much for all your videos..very much helpful😊
If that "dotted" line is not used in daily flow, you should have two seperate delta mechanism running with two DTPs. Even if it's a full load, why bother to get the same data from source two times?
This is the modification that I am using in the design. We should avoid extracting the same data twice from the source to reduce load on source. Before ODP, since we have PSA, it make sense to extract data into PSA first and then do a parallel load to corporate memory and data propagation layer. If we are using ODP we can first load to staging to fetch data from source once and then to propagation layer.
Another way to think if we want to fetch same data twice from the source, only pro I see is reducing batch time.
We need to check both options based on our requirements.
@@balakrishnakatha8000 I've never seen a requirement for loading the same data twice. Even there's a case, that should be very very rare. I think SAP designed this concept as two options. Either from Source->CM->DWH or from Source->DWH. Not simultaneously Source->CM & Source->DWH.
@@ErdemPekcan The parallel load to staging ADSO is to store data in the source format 1:1 without any transformations. This staging ADSO is not used in daily flow but rather to support rebuilding scenarios meaning when there's an issue in the data consistency which requires us to load an entire year data or entire plant/material group data from source, now you don't need to put any burden on source but rather get the data from the staging layer ADSO. That's the main purpose of the staging ADSO. And yes, although data is stored twice but plz keep in mind that granularity is not usually the same meaning in staging ADSO, it'll be same grain as source but in Stnd or Datamart ADSO the grain is higher and matches the requirement. Additionally, please keep in mind that ADSO tables are column tables meaning huge compression takes place (~80%) so that too helps to keep memory in check.
@@DebanshuMukherjee sorry but my point and explanation was not about the purpose of CM and DWH layers. It was all about data loading concept.