Show TOC

App Implementation: Monitor Data Aging ObjectsLocate this document in the navigation structure

System Landscape Requirements

In order to be able to implement this app, your system landscape has to be enabled for SAP Fiori. Depending on the database type serving as the basis in your system landscape, it has to be set up for SAP Fiori and has to meet the respective prerequisites:

The SAP product version in the back-end system serving as the the basis for the app must be the following:

Required Back-End Product (Product Version Stack)

SAP NetWeaver 7.4 (12 (08/2015))

Each SAP Fiori app consists of front-end components and back-end components:
  • The front-end components of the app consist of the user interfaces and content required for launching the app on the SAP Fiori launchpad. These components have to be installed on your front-end server.

  • The back-end components of the app mainly consist of the OData services required for the app. These components have to be installed in your back-end system.

The front-end and back-end components of the app are delivered with the following SAP product versions as part of the listed software components. The required software components for the app are contained in the listed product instances:

App Component

Required SAP Product Version (Support Package Stack)

Available Instances Containing Software Component

Software Component Required for App (Support Package)

Front-End Components

SAP Fiori 1.0 for SAP Information Lifecycle Management ( 06 (10/2015) )
  • UI for ILM NW731
  • UI for ILM NW740

UIILM001 100 (0006 )

Back-End Components

SAP NetWeaver 7.4 (12 (08/2015))

Application Server ABAP

SAP_BASIS 740 (0012 )

For more information about the installation of front-end components, see http://help.sap.com/fiori_implementation.

The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your respective back-end system and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information about virus scanning and scan profiles for SAP Fiori apps, see Virus Scanning.

Required SAP Notes

On the back-end server, the following SAP notes must be implemented for this app:

SAP Note Number

Description

  • ILM Monitor Data Aging Objects and Manage Data Aging Groups oData Services

  • Release Information Note for the ILM Fiori application Monitor Data Aging Objects

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number

Description

  • ILM Fiori application Monitor Data Aging Objects

  • Release Information Note for the ILM Fiori application Monitor Data Aging Objects

Implementation Tasks

The following sections list tasks that have to be performed to implement the required components of the app. The tables contain the app-specific data required for these tasks.

You can find the data required to perform these tasks in the SAP Fiori apps reference library at:

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F0618

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

DAAG_MONOBJ (001 )

For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

Front-End Server: Activate SAP UI5 Application

Component

Technical Name

SAP UI5 Application

FND_DAGOBJ_MON

For more information about how to activate the SAP UI5 application (ICF service), see Front-End Server: Activate ICF Services.

Enable App for Access in SAP Fiori Launchpad

To define the access of single users to this app in the SAP Fiori launchpad, technical content is delivered, such as catalogs and example roles.

You can find an overview of the delivered technical content for this SAP Fiori app in the SAP Fiori apps reference library.

For more information about how to procede with this content, see Enable App for Access in SAP Fiori Launchpad.

Front-End Server and Back-End Server: Assign OData Service Authorizations to Users

You must assign OData service authorizations for the app to your users.

Note

Several authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server :
  • On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.

  • On the front-end server , you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.

OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server : Assignment to Authorization Role

DAAG_MONOBJ (001 )

In addition, this role contains authorizations to display the related business data.

  • SAP_FND_DAGOBJ_MON_APP

Note

In addition, this role contains authorizations to display the related business data.

OData service authorization must be assigned.

Prerequisites for Implementation

Before implementing the app, you must ensure the following:

  • You use a database that supports data aging.

  • You have switched on the Data Aging business function (DAAG_DATA_AGING).

    For more information about the Data Aging business function, see SAP ERP Library on SAP Help Portal at http://help.sap.com Start of the navigation path SAP ERP Next navigation step Application Help  Next navigation step Business Functions Next navigation step Business Functions in SAP NetWeaver Next navigation step  Data Aging  End of the navigation path.

  • You have installed the app to use the functionality to schedule jobs for data aging groups

  • You have implemented the social collaboration platform SAP JAM to use the collaboration function.

    Note

    For more information about how to configure SAP JAM, look for Social Media Integration in the documentation of SAP NetWeaver at http://help.sap.com.Information published on non-SAP site

    The e-mail address in the user’s back-end system profile has to be identical with the e-mail address they used for registration for SAP JAM. At least one SAP JAM group has to be assigned to the user. To discuss a certain object, users must be assigned to the same SAP JAM group.

  • You have set values for the alert threshold if you are using a SAP HANA database. You can set three alert thresholds. The app uses the lowest value to define data aging objects as critical ones. Depending on the support package stack of your SAP HANA system the value is stored as described below:

    • Statistics server based on SAP HANA SPS 7

      The value is stored in table STATISTICS_ALERT_THRESHOLDS in alert 27.

      For more information, see SAP HANA Administration Guide on SAP HELP Portal at http://help.sap.com Start of the navigation path SAP In-Memory Computing Next navigation step SAP HANA Next navigation step SAP HANA Platform Next navigation step System Administration and Maintenance Information End of the navigation path.

    • Statistics server based on SAP HANA with SPS < 7

      The value is stored in the INI-file statisticsserver.ini in section THRESHOLD_PARTITIONED_TABLE_RECORD_COUNT_WARNING_LEVEL.

    If you are using another database that supports data aging, the app uses an alert threshold with the value 1.4 billion data sets ( filling level 70%).

Configuration Tasks

To be able to implement the app, you must perform the following configuration tasks in the back-end system:

  • Maintain Models

    In Customizing for SAP NetWeaver under Start of the navigation path SAP Gateway Service Enablement Next navigation step Backend Odata Channel Next navigation step Service Development for backend OData Channel Next navigation step  Maintain Models End of the navigation path.

    In this configuration, enter the following:

    • Technical Model Name: DAAG_MONOBJ

    • Model Version: 0001

    • Model Provider Class: Cl_DAAG_MONOBJ_MPC_EXT

    • Description: DAAG_MONOBJ

    • Choose Save.

  • Maintain Services

    In Customizing for SAP NetWeaver under Start of the navigation path SAP Gateway Service Enablement Next navigation step Backend Odata Channel Next navigation step Service Development for backend OData Channel Next navigation step  Maintain Services End of the navigation path.

    In this configuration, enter the following:

    • Technical Service Name: DAAG_MONOBJ

    • Service Version: 0001

    • Data Provider Class: Cl_DAAG_MONOBJ_DPC_EXT

    • Description: DAAG_MONOBJ

    • After saving the configuration, choose Assign Models and assign the Technical Model Name as DAAG_MONOBJ form the list of values.

      Note

      DAAG_MONOBJ is the technical model created in the Maintain Models configuration step.

    • Choose Save.

  • Activate and Maintain Services

    In Customizing for SAP NetWeaver under Start of the navigation path SAP Gateway Next navigation step OData Channel Next navigation step Administration Next navigation step  General Settings Next navigation step Activate and Maintain Services End of the navigation path.

    In this configuration, add the technical service DAAG_MONOBJ and activate.

Note

This step is required once for the backend for the Monitor Data Aging Objects app.

To be able to implement the app, you must perform the following front end configuration tasks:

  • Activate and Maintain Services

    In Customizing for SAP NetWeaver under Start of the navigation path Gateway Next navigation step OData Channel Next navigation step Administration Next navigation step  General Settings Next navigation step Activate and Maintain Services End of the navigation path.

    In this configuration, add the technical service DAAG_MONOBJ and activate.

    Note

    This step is required once for the frontend for the Monitor Data Aging Objects app.

More Information

For more information about app implementation, see http://help.sap.com/fiori_implementation Start of the navigation path App Implementation Information for SAP Fiori End of the navigation path.