Let's Reconnect, thank you for making 2022 our best year yet.

Look Back
BI Publisher Report as Cloud Data Extract engine — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

BI Publisher Report as Cloud Data Extract engine

edited Nov 14, 2017 4:09PM in General Transactional Reporting (OTBI) 2 comments


Use of Report as Cloud Data Extract engine and keep track of extracted data/ record


Cloud Integration process where data is extracted and sent via FTP to other partner applications.

If this process is performed on a scheduled basis (or manual run) then it becomes difficult to find out which records were extracted earlier and where are NOT? Other mechanisms are used to remove already extracted records from being sent twice. 

Could we perform the following steps: 

#01: BIP Report is given the capability (similar to EBS) to update some DFF fields (not other fields) from the source tables (data being pulled) to update and store them so that next run could validate and exclude these records. This should be kept as datatime field so that it can keep track of when the data was pulled. In addition, if the record was updated then the record should be pulled second time in BIP. This could be performed on Datatime and "Last_Update_date" comparison. 

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!