Function documentationConfigure Enrollment

 

You can configure the Enrollment application to suit your business needs.

Features

Personalized Screens

Employees can use implicit personalization options supported by Web Dynpro ABAP, such as hiding fields and setting default values to the input fields. These personalization changes are stored in the system until the administrator or the employee clears the personalization.

Changing the Layout

Administrators can change the application using the following:

  • Configuration Change

    Configure the application’s component configurations to add or remove steps from the guided activity floorplan (GAF), user interface building blocks (UIBBs), and fields in the UIBB. This layout change is applicable to all users of the system and all clients.

  • Customization

    Run the application in administration mode and customize the application to hide fields or steps in the GAF. These changes are applicable to all users at client level.

Configure Enrollment to Verify Eligibility

You can restrict employees from editing specific subtype(s) in the Personal Profile and Dependent and Beneficiaries steps of the Enrollment GAF, as follows:

  1. Configure the edit settings for the specific subtype in Specify Use Case and Active Subtypes (V_T7XSSPERSUBTY) view.

    Note Note

    You can use the HCM Processes and Forms process for employees updating their dependents and beneficiary data. For more information, see HCM Processes and Forms.

    End of the note.

  2. Provide the HCM Processes and Forms process group, containing the processes with which employees can update their personal data using the PERSDATA_PROCESS_GROUP application parameter. When a process group is provided as application parameter, the Request Profile Update button displays in the Personal Profile application. Employees choose this button to launch the HCM Processes and Forms application.

  3. Provide the HCM Processes and Forms process group, containing the processes with which employees can update their dependents and beneficiaries information using the FAM_DEP_PROCESS_GROUPapplication parameter. When a process group is provided as application parameter, the Request Profile Update button displays in the Dependents and Beneficiaries application. Employees choose this button to launch the HCM Processes and Forms application.

    Note Note

    You can hide the Personal Profile and the Dependents and Beneficiaries steps of the GAF by setting the HIDE_PERSONAL_DATA_STEP application parameter .

    End of the note.
Concurrent Employment (CE) Scenario

If an employee has multiple personnel assignments and accesses the Enrollment application, they must select the relevant personnel assignment with which they want to enroll for benefits. The employee can view or maintain data for their selected assignment. If an employee has only one assignment, it is automatically selected by the system.

Note Note

Assignments are determined by, and displayed from the Web Dynpro component, Central Service: Concurrent Employment Selection (HRESS_C_PERNR_SELECTION).

End of the note.

You must register the application as a CE application using the table view, Group definition settings for ESS CE applications (V_T7XSSCE_GRP). For more information, see Customizing for Employee Self-Service (Web Dynpro ABAP) under Start of the navigation path General Settings Next navigation step Concurrent Employment (CE) / Global Employment (GE) Next navigation step Assign CE / GE Group Definition Settings to ESS Applications End of the navigation path.

Application Title Handling

The application title is determined by the BEN_EVENT application parameter. This parameter is verified with the benefits adjustment reason configured in the system. The adjustment reason text is used as the application title in the AppCC for Benefits Enrollment (HRESS_C_BEN_ENRL_CONFIG) application configuration controller (AppCC) component.

Example Example

If the BEN_EVENT application parameter value is set to “HIRE” at runtime and if the adjustment reason text is “New Hire Enrollment”, the application title appears as “New Hire Enrollment”.

End of the example.

Note Note

In concurrent employment (CE) scenarios, the application title is concatenated with the grouping text of the selected personal assignment for the employee on the CE dialog box on the initial screen.

End of the note.
Terms and Conditions Agreement Text

You can create new text or change the standard text for the Terms and Conditions dialog box. The standard text is retrieved from the HRESS_BENF_TERMS_CONDITIONS general text (document class TX). The HRESS_BENF_TERMS_CONDITIONS general text identifier (ID) is set as the value for the AGR_DOCUMENT_OBJECT application parameter.

Track Employee Response to Terms and Conditions

You can track whether employees accept or decline the terms and conditions of the Enrollment process, by implementing BAdI: Saving of Terms and Conditions Agreement (HRESS_B_TERMS_AND_CONDITION). For more information, see the BAdI documentation from the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Select Variants

There are two variants defined in the application’s component configuration. Depending on the COUNTRYGROUPING application parameter, the appropriate variant displays country-specific or international screens. If the application parameter is 10, variant 10 loads and US-specific screens display in the application. If the application parameter is other than 10, variant 99 loads and international screens display.

Track Data

As an administrator, you can track applications for their usage and you can use SAP NetWeaver Business Warehouse (BI) to gather reports on this data. For more information, see BTracking.

Configure Additional Documents for the Plan Category Steps

If you configure applications in the following launchpads, as detailed in the following table, the Additional Documents button displays in the toolbar for the corresponding GAF step. Employees can choose this button to navigate to all the applications configured in the corresponding launchpads.

Role

Instance

Description

HRESS_BEN

CREDIT_PLANS

Credit Plans step Additional Document

HRESS_BEN

FSA_PLANS

Flexible Spending Account step Additional Document

HRESS_BEN

HEALTH_PLANS

Health Plans step Additional Documents

HRESS_BEN

INSURANCE_PLANS

Insurance Plans step additional Documents

HRESS_BEN

MISCELLANEOUS_PLANS

Miscellaneous Plans step Additional Documents

HRESS_BEN

SAVINGS_PLANS

Savings Plans step Additional Documents

HRESS_BEN

STOCK_PURCHASE_PLANS

Stock Plans step Additional Documents
Configure the Evidence of Insurability Form

If an employee enrolls in plans which require evidence of insurability (EOI), the system displays a dialog box with a warning message stating that EOI is required. The dialog box also links to applications configured in the following launchpad:

Role: HRESS_BEN

Instance: EOI_FORM

Configure the Link on the Confirmation Screen

You can configure the What do you want to do next? link on the confirmation screen in the following launchpad:

Role: HRESS_BEN

Instance: LPD_CONFIRMATION_STEP

Configure the Plan Name

If you configure an application in the following launchpad with the Application Alias Plan Name (BPLAN), the plan name displays as a hyperlink in the plan details dialog box. When an employee clicks the hyperlink the configured application displays.

Role: HRESS_BEN

Instance: NAVIGATION

More Information

For more information, see Application Composition and Concept Introduction for Enrollment.