Egress Ltd: Data Migration without the headache

LoadPay

LoadPay provides an efficient and accurate means for loading data directly into Oracle HRMS databases.

It can be used for either large scale data migration projects, or simply to load subsets of data to an already live Oracle HRMS system.

LoadPay can be run in simulation only mode that validates the load without committing any changes to the database. From this a report is produced detailing any data items that would fail to load. This allows an organisation to address any data cleansing issues and prevents any corrupt data entering Oracle HRMS.

It utilises the Oracle provided Application Program Interfaces (APIs) to ensure that all mandatory field validation is correctly verified, and to also fulfil Oracle’s loading standards. Using the standard load APIs ensures that the integrity of the system is maintained. 

As well as Data Migration projects, LoadPay can be used within an organisation’s test team to load consistent test data across various test environments. It is critical to a test team to ensure that the test case data is the same across multiple environments and LoadPay is used to ensure that this is the case.

Egress recognises that many organisations customise the Oracle application and may even build their own APIs to load data.  Where this situation exists, Egress has a team of technical developers, who will configure LoadPay to accommodate any variations that an organisation has made, ensuring that target system requirements are satisfied.

LoadPay has been proven on the world’s largest Oracle HRMS system, where it has been used to load an entire organisation’s HR/Payroll data and also to load subsets of data (such as OLM and Competency data) for already live organisations. It is the preferred data load mechanism for this system and will remain so throughout the benefits realisation work taking place well into the next decade.

Typical applications

  • Loading an organisation, or number of organisations, onto a new instance of Oracle HRMS.
  • Populating a test version of Oracle HRMS with data to allow testing of a new software release.
  • Populating a new component of Oracle HRMS that an organisation has decided to implement.
  • Validating the integrity of data against Oracle HRMS without actually loading it into the database through the use of the simulation mode.