Hi Srinivas, if we want complete full load -- ( historic data ) , setup table filling is required right ,in that case once setup table is filled, is it possible to extract data through only ODP (DTP -- without PSA )? or through info package only we can able to do full load?
Hi Srinivas, thank you for the valuable videos. We are seeing delta extractions running in foreground in ECC instaed of background jobs. Due to the custom exit coding on these datasources the jobs cancelled with timeout. Is there a way to have background jobs?
Hi Anil, If your requirement is fetch historical data too then setup table filling is mandatory. But in general its good to initialise delta first to capture regular delta. And bring historical data by filling setup tables and extract to bw using full dtp. I hope this clears your question.. Happy Learning 🎓
Hi Anil, Multiple options here, 1. Enable error stack and correct there 2. Sometimes it’s possible to change at New table or inbound table using debugging 3. At source table level with help of respective team, b/w the time we can exclude the error record’s from load by applying dtp filter. Happy Learning 🎓
Hi Bro, I am getting error messages "Message not found(in main memory)" and "Drop cube failed in Data Target ZDSOXXX" in step Delete Target contents of DSO. Can you pls help me to solve this issue
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
Great explanation sir, please continue the Interview series.
Thanks Srinivas. Step by step doc presentation would be helpful and avoid confusion.
Hi Srinav, I have one doubt "ODQMON" hold only new delta requests? or it store DTP(ODP) request also whose data already moved to BW side
Hi Srinivas, if we want complete full load -- ( historic data ) , setup table filling is required right ,in that case once setup table is filled, is it possible to extract data through only ODP (DTP -- without PSA )? or through info package only we can able to do full load?
Hi Srinivas, thank you for the valuable videos. We are seeing delta extractions running in foreground in ECC instaed of background jobs. Due to the custom exit coding on these datasources the jobs cancelled with timeout. Is there a way to have background jobs?
Hi Srinivas, as per this tutorial I understand that no need to fill setup tables for initialization. is that correct?
Hi Anil,
If your requirement is fetch historical data too then setup table filling is mandatory. But in general its good to initialise delta first to capture regular delta. And bring historical data by filling setup tables and extract to bw using full dtp. I hope this clears your question..
Happy Learning 🎓
Got it, thank you so much Srinivas!
You are welcome.
Happy Learning🎓.
Hi Srinivas, if we get ADSo activation failed where can we correct data? If there is PSA we can correct there. So this case how can we correct data
Hi Anil,
Multiple options here,
1. Enable error stack and correct there
2. Sometimes it’s possible to change at New table or inbound table using debugging
3. At source table level with help of respective team, b/w the time we can exclude the error record’s from load by applying dtp filter.
Happy Learning 🎓
Thank you Srinivas!
Hi Bro,
I am getting error messages "Message not found(in main memory)" and "Drop cube failed in Data Target ZDSOXXX" in step Delete Target contents of DSO.
Can you pls help me to solve this issue
Hi Anil,
You can reach out to me on my WhatsApp number or via email at srinivasm.sapbw@gmail.com.
Happy Learning 🎓