Data Extractor

Oracle Revenue Management and Billing provides you with a facility to extract the system data in the Comma Separated Values (CSV) format. You can extract transactional data (such as, bills, payments, adjustments, and so on) as well as non-transactional data (i.e., master data, such as persons, accounts, adjustment types, bill segment types, and so on) from the system. You can extract the data in either batch or online mode. The extracted data can then be used by the downstream system for various purposes, such as accounting, financial analysis, payment processing, streamlining operations, reporting, and so on.

The Data Extractor module provides the following features:

  • Supports data extraction from each table associated with the respective maintenance object.

  • Facilitates full data extraction at the first instance and incremental data extraction in the subsequent instances.

  • Provision to setup full or incremental data extraction in the subsequent instances.

  • Separate CSV file created for each table from where the data is extracted.

  • Facilitates the customers to configure the data extraction at required intervals.

  • Enables you to define data masking rules for sensitive data.

  • Supports conditional filters to extract selective data.

You can also use an OUAF feature named Generalized Data Export (GDE). It facilitates you to extract the system data in the JavaScript Object Notation (JSON) format. For more information, see the Generalized Data Export section in the Oracle Utilities Application Framework Administrative Guide. There is one problem with GDE incremental data loading. It does not work as expected for the old legacy or Cobol entities (such as person, account, contract). To handle this issue, while configuring a data export control for a maintenance object for incremental data capture in the Generalized Export Dashboard screen, you must do the following:

  • Remove the F1-MO-REGCHN algorithm attached to the Audit system event of the respective maintenance object.

  • Attach the C1-MO-REGCHN algorithm to the Post-Processing system event of the respective business object.