Using BICC PVOs and need a method for identifying records that are deleted in Cloud Fusion

RFong at PSJH

Currently using BICC PVOs to extract Cloud Fusion data from different workstream areas (FSCM and HCM) to build a data store - used for reporting and analysis. We have noticed that the BICC PVOs identify updated and new records, but we are unable capture deleted records in the Fusion app without a full table load. Full table loads is not a sustainable solution as the data continues to grow. What methods and tools are available to help manage and keep our data synchronized from Oracle Fusion (FSCM and HCM) with our Data Store.

Dave Kekish

If you get a pecsv data set (which is just the primary keys identified for your PVO), that is the current valid set of active records for that pvo.

We handle it in this manner, we pull data rows (Delta or full depending on the pvo/day/situation, usually just Delta changes). these rows are bulk inserted into staging tables which then merge to our internal warehouse table. These are automatically considered "active" records.

We then pull the PECSV Key any row in the warehouse table that is not in this PECSV data is considered to have been deleted (we soft delete for 30 days, then perma delete). Any row that was previously soft deleted (i.e., we got a delta record, but it wasn't in the previous PECSV data set) is marked active if it is in the PECSV data set. This is primarily due to the scheduling differences of the data and PECSV data pulls on oracles side, i.e., they do not run at the same time despite being scheduled that way.