Understanding the Oracle HCM Fusion Cloud Interface

The PeopleSoft HCM Payroll for North America to Oracle HCM Fusion Cloud integration enables customers who have migrated from PeopleSoft HCM to Fusion HCM Cloud to continue using PeopleSoft Payroll for North America for payroll purposes (for US and Canada employees only). When set up properly, the integration runs payroll successfully with minimal user intervention.

Note: This topic provides a high-level overview of the integration. For detailed information on setting up and implementing the integration, consult both the HCM Cloud to PeopleSoft Payroll Solution Implementation Guide and Integration Cookbook documents, which are provided by Oracle Fusion on the My Oracle Support (MOS) web site.

The Integration Process

The PeopleSoft Payroll-to-Fusion Cloud integration enables Oracle Fusion HCM customers to integrate employee personal, job, and absences data in Fusion with payroll setup data in PeopleSoft and thereby use the PeopleSoft Payroll for North America system for payroll purposes.

The Application Engine (AE) integration batch process program performs the integration between PeopleSoft and Fusion. The AE process extracts from Fusion all the data required to run payroll in PeopleSoft (setup entities, person, job, bonus, and absence information), places the data in the appropriate Fusion (worker structure, worker, or bonus) extract file in the specified configuration folder, and pushes the data to the PeopleSoft staging table. Then, using domain value maps (DVMs) to transform the data into a PeopleSoft-recognized format, the process inserts the transformed data into the respective PeopleSoft transaction tables.

The AE integration batch process extracts are:

  • Work Structure Extract: Extracts PeopleSoft foundation data elements (except SetID), which in Fusion are setup entities (business unit, company, department, location, job code, and position).

  • Worker Extract: Extracts employee person, job, and absence information.

  • Bonus Extract: Extracts employee bonus pay information.

For setup entities and transactions, Component Interface (CI) performs all validations that would happen for an online transaction.

Extracted absence and bonus information is populated to the Payroll for North America Paysheet Transaction Table (PSHUP_TXN).

The AE integration batch process also provides screens and error logs to monitor the integration progress:

  • The process issues a warning message if the folder to be processed contains multiple files of the same type of extract.

  • The process issues a warning message if the folder contains files that have already been processed.

  • The process logs any row that fails to an Error table with error codes and details to identify the reason for the failure.

  • If email notifications are configured in the PeopleSoft system, when the process is complete, the system sends an email notification to the designated integration specialist with a link to the Process Scheduler Status Monitor.

Integration Considerations

Once implemented, the following considerations are true for the PeopleSoft Payroll for North America to Oracle Fusion HCM Cloud integration:

  • PeopleSoft HCM is the source system (owner) for all data required for payroll setup.

  • Oracle Fusion HCM Cloud is the source system (owner) for all employee personal, job, and absence-related data.

  • PeopleSoft Payroll for North America is the payroll system for all persons entered in Fusion.

  • All setup options that are configured in the Installation Table component for Payroll for North America remain intact and continue to apply after the integration.

  • Existing PeopleSoft General Ledger setup, if any, remains intact and continues to apply in the integration as configured in the existing Payroll for North America system. The General Ledger setup is also in the HCM shared component setup.

  • Some adjustments are required for Absence processing, including but not limited to adjusting unit of measure (UOM), creating new translate values of a specific configuration, and customizing code to cause absence balances to appear on paychecks if desired.

  • The Benefit Administration flag must be selected in the PeopleSoft Installation Table component. When selected, the system uses PeopleSoft HCM Base Benefits as the default in the Job component. If you use a third-party benefits system, you must create a new Benefit Program ID in PeopleSoft and configure it for usage in the integration so that the system can use the correct Benefit Program ID on Job Data.

Prerequisites

For successful integration, certain conditions must exist or be met prior to implementation.

PeopleSoft Prerequisites

Before setting up or using the integration, the following conditions must be true or completed on the PeopleSoft Payroll for North America side:

  • PeopleSoft must exist with PeopleTools release 8.53.20 or higher.

  • All PeopleSoft HR and Absence data (both setup and transactional data) must exist and have been migrated into the HCM Fusion Cloud application. (Your integration manager must do this; the AE integration process does not include functionality to do this.)

  • The date on which Oracle Fusion will become the system of record for HR must be identified, and data must be in sync between PeopleSoft Payroll for North America and Oracle HCM Fusion Cloud by this date. Note that PeopleSoft production may need to be in read-only mode for a short duration after this date.

Fusion Prerequisites

Before setting up or using the integration, the following conditions must be true or completed on the Oracle HCM Fusion Cloud side:

  • Fusion must exist on release 9 with patch2, or higher.

  • Fusion flex fields must mapped and populated appropriately.