Hi Prabhjeet,

The latency is determined by the non functional supplemental requirements you have gathered from your consumers regards how out of date the data can be before it impact the business process. You can schedule as often as choose as a trade of between what your data extract consumers need versus what all the other users need to carry on doing their day to day data entry business process.

If you use the scheduler in BICC the values in the list of values for recurrence are immediate, hourly, daily, day of month, year. But you can also schedule as often as you wish by for example calling API to run the Enterprise Scheduler Service job definition for an extract schedule in BICC.

Each view object is a sql query. So you can read the sql in the view object to understand the impact it will have on the application database in terms of tables and views selected. And you can do data analysis on your data volumes over time to know how much data to expect to be extracted each period of time. Your extract will also put a load on the middleware not just the database.