App Implementation: Analyze Archiving Variants Distribution

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:

Database	SAP Fiori System Landscape Setup	Prerequisites
ABAP environment	Setup of SAP Fiori System Landscape for SAP Business Suite with ABAP Environment	Installation Requirements (Transactional Apps)
HANA database	Setup of SAP Fiori System Landscape for SAP Business Suite with SAP HANA Database	Installation Requirements (Fact Sheets)

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
1967530 1982196	ILM Data Archiving Write Variant Distribution Analysis Release Information Note for ILM Distribution & Optimization Analysis of Archiving

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

SAP Note Number	Description
1982196 2012336	Release Information Note for ILM Distribution & Optimization Analysis of Archiving UIILM001 - Analyze Archiving Variant Distribution Fiori App

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=F0627

Front-End Server : Activate OData Services

Component	Technical Name
OData Service (Version Number)	ILM_ARCH_VARIANT_DIST_SERVICE (0001 )

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	ILM_DISTANALY

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
ILM_ARCH_VARIANT_DIST_SERVICE (0001 )	In addition, this role contains authorizations to display the related business data. N/A Note In addition, this role contains authorizations to display the related business data.	OData service authorization must be assigned.

OData Service (Version Number)

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

Front-End Server : Assignment to Authorization Role

ILM_ARCH_VARIANT_DIST_SERVICE (0001 )

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

N/A

Note

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

OData service authorization must be assigned.

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 SAP Gateway Service Enablement Backend Odata Channel Service Development for backend OData Channel Maintain Models .

In this configuration, enter the following:
- Technical Model Name: ILM_ARCH_VARIANT_DIST_SERVICE
- Model Version: 0001
- Model Provider Class: Cl_ILM_ARCH_DISTRIBUTION_MPC
- Description: ILM_ARCH_VARIANT_DIST_SERVICE
- Choose Save.
Maintain Services

In Customizing for SAP NetWeaver under SAP Gateway Service Enablement Backend Odata Channel Service Development for backend OData Channel Maintain Services .

In this configuration, enter the following:
- Technical Service Name: ILM_ARCH_VARIANT_DIST_SERVICE
- Service Version: 0001
- Data Provider Class: Cl_ILM_ARCH_DISTRIBUTION_DPC
- Description: ILM_ARCH_VARIANT_DIST_SERVICE
- After saving the configuration, choose Assign Models and assign the Technical Model Name as ILM_ARCH_VARIANT_DIST_SERVICE form the list of values.
  
  Note
  ILM_ARCH_VARIANT_DIST_SERVICE is the technical model created in the Maintain Models configuration step.
- Choose Save.
Activate and Maintain Services

In Customizing for SAP NetWeaver under SAP Gateway OData Channel Administration General Settings Activate and Maintain Services .

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

Note

This step is required once for the backend for the Analyze Archiving Variant Distribution 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 Gateway OData Channel Administration General Settings Activate and Maintain Services .

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

Note
This step is required once for the frontend for the Analyze Archiving Variant Distribution 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 .