Hi Suneel,
I think there is some confusion related to LIS extractors and others. So to clarify this I just want to let you know that Set Tables, Extraction Queues, V3 jobs deal only with LIS extractors not others.
So when we are talking about FI/CO datasources it extracts direclty from the base tables. Its other thing that the delta mechanism is based on timestamp tables but these do not have a concept of setup table fill up or extraction queues.
Now having clarified that, your query is ideally for datasources other than LIS/LO extractors Right!
You would require donwtime only for transport and not other than that. Below is how it will work for FI/CO datasources:
Here assumption is that you have already moved the required changes in BW prod system for related DSO/Cubes etc. for the additional field being added to underlying datasource.
1. Lock system for users - 10 Min. (done by basis)
2. Clear delta queues from RSA7 (run the infopackage atleast 2 times) - 10 Min (done by BW team)
3. Transport your datasource in Prod & verify transport- 10 Min (done by basis)
4. Replicate the datasource in BW system - 10 Min (done by bw)
5. Initialize the datasource from BW system - 5 Min (done by bw)
6. Unlock users for users - 10 Min. (done by basis)
7. If historical data (for new added field) is required perform historical load - could be many hours depending on volume of data
7.1. If historical data is loaded thn you will have to delete the historical data in cube too and reload again. Here you can do a selective deletion based on your requirement
8. Kick of delta load after historical data is complete
I suggest talk to business about the historical data load. Like how many years of data you need for new added field. If no historical data is required for new added field then you can skip step 7 from flow above.
Please let me know if there are any questions.
Thanks
Amit