Comments
-
The inability to alter an existing job with regards to a customized pvo seems to be a severe limitation on the usefulness of this api functionality. If I want to customize a base pvo, I put it in a job. If i want to schedule an extract of a pvo, it goes into a job. however, if I want to use the rest api to alter the filter…
-
This would have saved us a number of hours spent re-customizing the pvo's after we split the jobs up.
-
it would allow better programmatic access to handling jobs in the BICC. while the bicc is good, its not ideal for large job setups.
-
BIP has limits as well, but I don't know the tool you referenced. One major limit of BIP reports is a hard 2 million row max limit that Oracle seems to not want to lift.
-
The primary reason we are moving to extract from the OTBI PVO's is fewer issues with things like determining primary keys, duplicate data, etc. The Extracts have fewer issues in our experience. As for changes to the extracts, they add columns, but removal of columns isn't a big issue (at least for us right now). The bigger…
-
Columns get added all the time, the depreciation document lists additions to the VO's as well, and some of them are selected on the VO by default, but to my knowledge, it will never alter a job already setup. So if you already have a configured VO, it will stay that way until you alter it.