Benefit Plan Import

You can import a program, plan not in program, or eligibility profile exported from one environment into other environments. You can also import them to different enterprises in the same environment.

Use the Import Plan Configuration task in either the Setup and Maintenance or Plan Configuration work area.

During the import, you can:

• Create objects or reuse objects that exist in both the source and destination environments.

• Map third-party objects, such as HR and payroll objects, between environments.

Importing plans from a source environment with a newer application version than that of the destination environment is unsupported.

The basic process for importing plan configurations is:

1. Set up the destination environment.

2. Import the plan configuration using one of these methods:

   • Creating all destination named objects

   • Reusing existing destination named objects

3. Map source and destination HR, payroll, and compensation objects.

4. Review imported plan configuration.

5. Finalize imported plan configuration.

6. Validate imported plan configuration.

Setting up the Destination Environment

Before you import a plan configuration, you must set up:

• All of the relevant HR, payroll, and compensation structures and objects:

  • HR objects include legal employer, locations, jobs, and organizations

  • Payroll objects include payroll definition and payroll elements

  • Compensation objects include salary basis

• Any criteria that you used in the eligibility profiles associated with the import object. You can still import any associated eligibility profiles without criteria set up. But if the underlying criteria for an eligibility profile aren't present in the environment, the eligibility profile doesn't work.

Importing by Creating All Named Destination Objects

You can create, rather than reuse, all named objects when importing a plan configuration.

• Enter a prefix, suffix, or both that the import process adds to the start or end of all source named objects during the import.

• Ensure that the Reuse existing named objects check box is clear.

Importing by Reusing Existing Destination Objects

You can reuse destination named objects that match the source objects that you are importing, as long as the existing destination objects are available as of the import date.

The import process:

• Doesn't reuse existing named destination objects that match the source objects if they are available as of a future date

• Prompts you to enter a prefix or suffix if it finds future-dated destination objects

The following table identifies the existing named objects that the import process always reuses, and the condition for that reuse:

Condition	Reused Objects
When you select Reuse existing named objects	Plan, plan type, options, reporting groups, regulations, eligibility profiles, and user-defined life events
Regardless of whether you select Reuse existing named objects	Year periods, predefined life events, action items, and formulas

Mapping HR, Payroll, and Compensation Objects

You must map any source workforce structure (HR), payroll, and compensation setup objects that you are importing to corresponding destination objects.

Source objects that you must map include:

• Legal employer, organization, location, department, person type, job, assignment status, grade, position, performance rating, qualification, and competency

• Formulas, payroll definition, and salary basis

To perform mapping during the import process, you must have data access privileges for the destination objects.

Importing Only Rates

If you frequently update just the rates, you can choose to import only those changes. When you import the zip file in the Plan Configuration work area, you need to select Rates from the list named Import Specific Objects to import only the rate data. This drop-down list is visible only when you import programs and plans.

The import process fails if these dependent objects aren’t present in the destination environment:

• Program
• Plan
• Option
• Compensation Level Factor
• User Value
• Formula
• Flex Shell Plan
• Eligibility Profile

Reviewing Imported Objects

On the Review Imported Plan Configuration page, use the graph to identify visually any discrepancies between the number of source and destination objects. Click the relevant bar to:

• View details about the source and destination objects

• Identify which source objects were imported

Source and destination objects that are covered in this review are: age and service factor, age factor, benefit balances, benefit groups, compensation factor, coverage across plan types, coverage, eligibility profiles, full-time equivalent factor, hours worked factor, length of service factor, life events, options, plan types, plans, regulations, reporting groups, service areas, standard rates, user-defined criteria, and variable rate profiles.

Finalizing Imported Objects

Change the status for the imported program or plan not in program from Pending to Active in preparation for validating it. The import process:

• Always reuses fast formulas if they exist in the destination environment

• Creates fast formulas that don't already exist at the global level, even though the source formula is defined at LDG level

• Creates formulas using the same names as the source formulas, ignoring any entered prefix or suffix

You must validate the logic for the imported and created formulas, and then compile them individually or in bulk. Compile formulas by running the Compile Formula process on the Submit a Process or Report page.

Validating Imported Objects

You can compare the results of the following destination validation and evaluation with the results for those of the source environment.

• On the Import Benefits Plan Configuration page, search for your import request and click the name in the Search Results section. Open the Validate Imported Plan Configuration page to validate the imported program or plan not in program.

• On the Evaluation and Reporting work area, Processes tab, run the Evaluate Life Event Participation process for a sample person.