Process documentationConfiguring the Student Lifecycle Management My Request Application

 

My Request is a BSP application built on latest UI5 template which is available only from EHP08 as it ensures better performance for the application. The following document describes the steps required to define and configure the My Request application. Following are the notes to be applied along with EHP07 SP11 and EHP8 SP01 upgrade:

Note Note

If you are upgrading from EHP7 and if you are already using req_manager, you can continue using the same version.

End of the note.

Process

  1. Activate the ICF service of BSP Applications manually as follows:

    1. Run transaction Maintain Services (SICF) on the ABAP server

    2. Press F8

    3. Navigate Start of the navigation path Default_Host Next navigation step SAP Next navigation step BC Next navigation step UI5_UI5 Next navigation step SAP End of the navigation path.

    4. Under this node, navigate to the BSP applicationStart of the navigation path myrequest Next navigation step formdesigner End of the navigation path

    5. If it is not yet active, activate the ICF service for your app choosing Start of the navigation path Service/Host Next navigation step Activate End of the navigation path

  2. Enable virus check for attachments for security reasons:

    1. In SLCM system, enter the transaction /n/IWFND/VIRUS_SCAN

    2. Enable or disable the virus profile

      For more information about this topic, see:

      • Note 78179

      • SAP Help – Virus Scan for Gateway

      Note Note

      Due to security concerns, the attachment size which can be uploaded from the applicant UI or the Form Runtime is limited to 3MB at the UI layer.

      End of the note.

    3. Setup the ABAP Frontend System for Security. It is recommended to move UI Applications delivered as part of the SLCM Admission portal to the ABAP frontend server as the applications are exposed to the internet.

      For transactional BSP applications, the client can issue the following types of requests to the ABAP front-end server:

      • HTML requests

      • OData requests

      For communication between the client and the ABAP front-end server, a HTTPS connection is established. Data and services from the ABAP back-end server are provided to the ABAP front-end server by using OData services. To do so:

      1. Create and activate BSP Application, FORMRUNTIME in the ABAP Frontend Server

      2. You can activate the OData services (PIQ_ADM_PORTAL_SRV and GFD_CONFIG_SRV) individually, as follows:

        1. Run the transaction Activate and maintain the services (/IWFND/MAINT_SERVICE) on the front-end server.

        2. Select Add Service

        3. Enter the system alias of your backend system

        4. In the External Service Name field, enter the technical name of the OData service for your app without the version number.

        5. In the Version field, enter the version number.

        6. Select Get Services

        7. Select Add Selected Services

        8. Enter a technical name for the service in your customer namespace

        9. Assign a package or select a Local Object

        10. Select Execute to save the service

        11. In the Activate and Maintain Services screen, check if the system alias is correct. If not, delete the alias and add the correct one.

        For more information, see:

        • Setup of SAP Fiori Launchpad

        • Setup of SAP Fiori Search

        • Setup of ABAP Frontend Server

        • Front-End Server: Activate OData Services

    4. Activate ICF Nodes for Gateway Services:

      1. Enter transaction /IWFND/MAINT_SERVICE

      2. Search and select GFD_CONFIG_SRV in the Service Catalog

      3. Click Manage ICF Node and click Activate

      Note Note

      You must perform similar steps to activate the PIQ_ADM_PORTAL_SRV service.

      End of the note.

    5. You can use the RPT_GFD_INITIAL_DATA_SETUP report for initial configuration. Once the report is executed , the customizing activities are not required except Configure Supported Languages and My Request display. You can use the same if any additional use cases have to be configured. Select Form Designer Configuration and upload the excel.

    6. You can use theRPT_GFD_MAP_RECOMEND_SETUP report fill the data in field FORM_SUBMISSION_ID_MAP of table GFDDBCONFIGRATON along with table entries of GFDDB_CONFIG_MAP . Select the Context ID and execute in test and actual run for Insert, Update or Delete options. If your Context ID is not listed, then enter your Context ID.

      1. In IMG, enter the transaction SPRO

      2. Navigate to Start of the navigation path Student Lifecycle Management Next navigation step Role-Based Web UI Next navigation step Request manager for Student Lifecycle Management End of the navigation pathand configure the following as described in the implementation guide:

        • Configure Supported Languages

        • Configure UI Display

        • Configure Form Contexts

        • Configure GFD Intermediate Page

      1. In IMG, enter the transaction SPRO

      2. Navigate to Start of the navigation path Student Lifecycle Management Next navigation step Role-Based Web UI Next navigation step Admission UI End of the navigation pathand configure the following as described in the implementation guide:

        • Configure Actions Status

Result

You have successfully configured the My Request application.