Background documentationConcept Introduction

 

The Enrollment application is based on the following concepts:

  • Business Object Layer (BOL)

    The business object layer (BOL) model is a programming concept that allows for uniform application development, decoupled from interface changes in the underlying business object-specific application programming interfaces (APIs). The Enrollment application uses the following BOL models, which you can access by using transaction GENIL_MODEL_BROWSER:

    • Model for ESS Benefits (HRBENF)

      Each plan category is represented as a dependent object and related to root object (PERNR_BEN) with cardinality 0…N. Plan categories are related to dependents such as, beneficiaries, investments, and dependents.

    • HRPAD

      For more information, see Business Object Layer (BOL).

    Note Note

    Each plan category is identified using the assigned key structure and attributes structure. The following table lists the key structures and attribute structures for all the plan categories in the application:

    End of the note.

    Plan Category/Dependent Object Name in the BOL Model

    Key Structure

    Attribute Structure

    Health Plan / HEALTH_PLANS

    HRESS_S_BEN_HEALTH_KEY

    RPBEN_OA

    Insurance Plan / INSURANCE_PLANS

    HRESS_S_BEN_INSURANCE_KEY

    RPBEN_OB

    Savings Plan / SAVINGS_PLANS

    HRESS_S_BEN_OTHERPLANS_KEY

    RPBEN_OC

    FSA Plan / FSA_PLANS

    HRESS_S_BEN_OTHERPLANS_KEY

    RPBEN_OD

    Miscellaneous Plan / MISCELLANEOUS_PLANS

    HRESS_S_BEN_MISCEL_KEY

    RPBEN_OE

    Stock Plan / STOCK_PURCHASE_PLANS

    HRESS_S_BEN_OTHERPLANS_KEY

    RPBEN_OF

    Credit Plan / CREDIT_PLANS

    HRESS_S_BEN_OTHERPLANS_KEY

    RPBEN_O1

    The dependencies between plan categories and other dependent objects are identified using the assigned key structure and attributes structure. The following table lists the key structures and attribute structures for all the dependent objects of plan categories in the application:

    Dependent Object

    Key Structure

    Attribute Structure

    Dependents

    HRESS_S_BEN_DEPENDENTS_KEY

    HRESS_S_BEN_DEPENDENTS

    Beneficiaries

    HRESS_S_BEN_BENEFICIARIES_KEY

    HRESS_S_BEN_BENEFICIARIES

    Investments

    HRESS_S_BEN_INVESTMENTS_KEY

    HRESS_S_BEN_INVESTMENTS

    The following table lists the dependent objects for each plan category:

    Plan Category/Dependent Object Name in the BOL Model

    Dependents

    Beneficiaries

    Investments

    Health Plan / HEALTH_PLANS

    Yes

    No

    No

    Insurance Plan / INSURANCE_PLANS

    No

    Yes

    No

    Savings Plan / SAVINGS_PLANS

    No

    Yes

    Yes

    FSA Plan / FSA_PLANS

    No

    No

    No

    Miscellaneous Plan / MISCELLANEOUS_PLANS

    Yes

    Yes

    Yes

    Stock Plan / STOCK_PURCHASE_PLANS

    No

    Yes

    No

    Credit Plan / CREDIT_PLANS

    No

    No

    No

  • Generic Interaction Layer (genIL)

    The generic interaction layer (genIL) connects the Model for ESS Benefits (HRBENF) BOL model to the HCM backend, business logic, or database.

    The Enrollment application uses the genIL class, GenIL Implementation for GenIL Object Model HRBENF (CL_HRESS_BEN_HRBENF_IL), which implements the BOL model. This class uses the handler class, Handler Class for Dependent Objects of GenIL Model HRBENF (CL_HRESS_BEN_GENIL_HANDLER) to perform all create, read, update, and delete activities on all of the enrollment objects in the database.

    You can modify the standard Enrollment application to suit your business needs, by doing the following:

    • Familiarize yourself with the Web Dynpro ABAP UI technology. For more information, see Web Dynpro for ABAP.

    • Expand your knowledge of the SAP Floorplan Manager. For more information, see Floorplan Manager for Web Dynpro ABAP.

    • Expand your knowledge of the main elements in the Enrollment application in Employee Self-Service (ESS) Web Dynpro ABAP. For more information, see Application Composition.

    • Execute the necessary configuration steps for the application. For more information, see Configure Enrollment.