Background documentationConcept Introduction

 

The Flexible Spending Account (FSA) Claims application uses the following classes:

  • Feeder Classes

    This application uses feeder classes from package PAOC_ESS_BENEFITS_WDA to supply data to the generic user-interface building block (GUIBB) and to supply a screen structure. The main feeder classes for this application are as follows:

    • Feeder Class for FSA Claims Form (CL_HRESS_BEN_FSA_OVR_FORM)

      This feeder class uses the FSA_OVERVIEW query object to create the application overview screen and to read the overview data for the plan selected by the employee.

    • Feeder Class for Lists in FSA Claims (CL_HRESS_BEN_FSA_OVR_LIST)

    • Feeder Class for the FSA Claims Detail Screen (CL_HRESS_BEN_FSA_DETAIL_FORM)

For more information, see the class documentation in the Class Builder, using transaction SE24.

  • Connector Classes

    This application uses the following connector classes to transfer data across user-interface building blocks (UIBBs) in the floorplan manager (FPM) overview page (OVP):

    • Connector class for list GUIBB (CL_HRESS_BEN_FSA_CONN_LIST_OVR)

    • Connector Class for the BOL Participation Overview Query (CL_HRESS_BEN_CONNECTOR_QUERY)

    • BOL Identity Mapping (CL_HRESS_CONNECTOR_IDENTITY)

    For more information, see the class documentation in the Class Builder, using transaction SE24.

  • Transaction Classes

    This application’s transaction behavior is determined by the BOL Transaction Handler (CL_FPM_BOL_TRANSACTION) class, which is retrieved by the OVP application for create, read, update, and delete activities in the FPM.

This application also consists of a business object layer (BOL), a generic interaction layer (genIL), and a self-service (XSS) adapter. For more information, see Business Object Layer (BOL), Generic Interaction Layer (GenIL), and XSS Adapter.

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