SAP Fiori Packaging.pdf

SAP Fiori Packaging

Version 1.1, January 2015

©SAP

Table of Contents Introduction ............................................................................................................................................... 3

Packaging principle: ‘ Single transactional apps on all back- end releases with launch page’ ................ 4 Packaging principle: ‘Transactional apps on all back -end releases with SAP Fiori launchpad’, also known as ‘principal apps’ ......................................................................................................................... 5 Packaging principle: ‘Transactional apps on most recent Suite back-end release’ ................................ 7 Packaging principle: ‘Transactional apps on earlier/lower back-end releases with option to upgrade to latest Business Suite release’ ................................................................................................................ 9 Appendix A ............................................................................................................................................... 12 Appendix B ............................................................................................................................................... 14

Page 2 of 14

Introduction This document describes the different packaging (assembly) principles used for SAP Fiori transactional apps, including some architecture background. The target group for this document is SAP Fiori consultants and other Fiori experts, in particular those involved in implementing Fiori-related system components. The following graphic gives an overview of the different Fiori app types.

You can find a list of all apps including a link to the technical requirements per app in the App Catalog on the SAP Help Portal at http://help.sap.com/fiori . There you can also find additional information on Fiori and Fiori products. Transactional Fiori apps consist of software artefacts to be deployed both on the front-end server and the back-end server. These objects are delivered as product versions, software components (within product versions) and their support packages/stacks. By default, there is one shipment each quarter. The assembly of these software components is not identical for all apps.

The following sections describe the different principles in packaging the artefacts.

Page 3 of 14

Packaging principle: ‘ Single transactional apps on all back-end releases with launch page’ The launch page version of the apps will not be developed further. SAP still provides maintenance to customers but it is no longer possible to download installation files. The same set of 25 apps has been redeveloped based on the SAP Fiori launchpad (see next section) and is shipped as SAP Fiori principal apps for ERP/SRM 1.0. SAP published a guide how to migrate to the launchpad version of those apps: Guide [insert link here, not in the sentence] 

There is one integration component and one UI component for each app (total of 25 apps). The reason f or designing the ‘old’ SAP Fiori 1.0 (launch page version) as having just one component per app was that each app should be installable and patchable independent of other apps, and thus minimizing the effort for upgrading the apps. The required minimum SP in the back end is low to address a broad installed base and make it as easy as possible for customers to install the integration components.



In case of back-end upgrades, the i ntegration component remains the same.



Product versions contain integration component instances and front -end server instances.



Launch page runs on NetWeaver 7.00 (whereas SAP Fiori launchpad requires NetWeaver 7.31 or higher).



Maintenance and enhancements of the existing apps are shipped via SPs of the software components.



For a list of product versions, see Appendix A.

Page 4 of 14

Packaging principle: ‘Transactional apps on all back-end releases with SAP Fiori launchpad’, also known as ‘principal apps’ Back end 

Software component SAP IW BEP 200 (latest SP) has to be installed in back-end releases based on NetWeaver lower than NW 7.40 as a technical prerequisite to run OData services.



OData services are delivered via integration components on all releases including NW 7.40. Integration components are modification-free add-ons for the back end.



There is one integration component per app (same components as listed in the table in appendix A for the ‘Single transactional apps on all back-end releases with launch page ’ ) for the first 3 product versions listed below. For these product versions, there is no clustering of apps to ensure that customers can migrate smoothly. Duplication of code has also been avoided.





For SAP FIORI FOR SAP ERP HCM 1.0, there is one integration component for all apps and for all backend releases to cover functionality available in all backend releases. To exploit additional backend features available as of Ehp5, a second integration component can be installed . In case of back-end upgrades, the i ntegration component remains unchanged.

Front end 

There are UI components for clusters of apps that correspond to instances in the back end. The reason for this change of the packaging principle compared to the version with the launch page was to avoid an ever increasing number of product versions by aggregating apps into fewer product versions and UI software components (at that time, Fiori had been accepted as UI paradigm and the expectation was to build hundreds of apps).

The following related product versions contain integration component instances and front-end server instances: 

SAP Fiori principal apps for ERP 1.0 (FIORI ERP APPLICATIONS X1)



SAP Fiori principal apps for SRM 1.0 (FIORI SRM APPLICATIONS X1)



SAP Fiori for Request Approvals 1.0 (FIORI APPROVE REQUESTS X1) “Pam links einbauen”



SAP FIORI FOR SAP ERP HCM 1.0 “Pam links einbauen” (available as of Q1/2015 delivery)

Maintenance and enhancements of the existing apps are shipped via SPs of the software components.

Page 5 of 14

ABAP Frontend Server Product-specific UI Add-Ons UI for SAP Business Suite ERP

SRM

MM, SD, LE, FIN

Tr avel

HCM

Approve Req. Appro val

SRM

UI Infrastructure DESIGN TIME

RUNTIME

SAP Netweaver Gateway 2.0

ABAP Backend Server (ECC 600 or higher, SRM 7.00 or higher

OData Integration Add-Ons (NON-MODIFYING)

Stable Business Suite Backend Core Component

Netweaver (7.00 or higher) plus SAP IW BEP 200 (for NW b elow NW 7.40)

HANA/ANY DB Product versions/UI software components are as follows: 

SAP Fiori principal apps for SAP ERP 1.0, technical name: FIORI ERP APPLICATIONS X1 1.0 covering ERP, Travel and HCM with the following UI software components:



o

UIX01EAP 100

o

UIX01TRV 100

o

UIX01HCM 100

SAP Fiori principal apps for SAP SRM 1.0, technical name: FIORI SRM APPLICATIONS X1 1.0 SRM with UI software component UIX01SRM 100



SAP Fiori for Request Approvals 1.0, technical name: FIORI APPROVE REQUESTS X1 1.0 Approve Request with UI software component UIX01CA1 100



‘per App’ aus Schaubildentfernen, UI -SWcomponent für HCM herausnehmen,

Page 6 of 14

Documentation for each product is available under SAP Fiori Products on the Help Portal. See also the following direct links: 

SAP Fiori principal apps for SAP ERP 1.0



SAP Fiori principal apps for SAP SRM 1.0



SAP Fiori for Request Approvals 1.0



Docu link HCM… einbauen

Packaging principle: ‘Transactional apps on most recent Suite back-end release’

Backend 

The most recent back-end release of the Business Suite runs on NetWeaver 7.40. As part of the Suite back-end support package stack, the NW 7.40 Support Package Stack including software component Gateway Foundation SAP_GWFND is installed in the back end. This software component is a prerequisite to run OData services.



OData services are delivered as part of back-end SPs. There are no integration components. The reason for this architecture was to allow the option of HANA optimization and the goal of minimizing the number of packages to be installed.

Frontend 

There are UI components for clusters of apps that correspond to instances on the back end (as described above in the section Transactional apps on all back-end releases with SAP Fiori launchpad, also known as ‘principal apps’ ).

Product versions: The product versions for ERP, SCM, SRM, and so on contain UI artefacts only and no back-end objects (these are shipped via SPs in the back end). Please note that the UI product versions have a logical dependency to a particular SP stack of the backend product version. This dependency is not modelled in PPMS and therefore is not considered by installation tools like MOPZ. The dependency is described in the RIN of the UI product version and is modelled in the cross-product solution consumed by the landscape planner. Maintenance and enhancements of the existing apps are shipped via SPs of the software components.

Page 7 of 14

New apps are shipped as follows: o

With SPs of existing software components if the app fits into the existing SWC (for example, an additional MM app will be shipped in the same software component as the existing MM apps)

o

With new software components in existing product versions (for example, the first app for Insurance is shipped in a new software component as part of a new instance in the existing ERP UI product version)

o

With new product versions (for example, the first app for SLC will be shipped as a new product version for SLC).

ABAP Frontend Server Product-specific UI Add-Ons UI for SAP Business Suite (AT1) ERP FIN

CRM SD

PP

PS

MM

SRM

SCM

QM


RUNTIME


ABAP Backend Server (AT1) SAP Business Suite 7i2013 ERP FIN

CRM SD

PP

PS

MM

SRM

SCM

QM

Netweaver 7.40 (including SAP_GWFND)

HANA / ANY DB

Documentation for each product is available on the SAP Help Portal at http://help.sap.com/fiori_products. For example: 

SAP Fiori for SAP ERP 1.0



SAP Fiori for SAP CRM 1.0



SAP Fiori for SRM 1.0



SAP Fiori for GRC

Page 8 of 14

Packaging principle: ‘Transactional apps on earlier/lower back-end releases with option to upgrade to latest Business Suite release’ Selected transactional apps from ERP and CRM that were initially developed and shipped only for the latest Business Suite release (for example, ERP EhP7) have been made available on lo wer backend releases as well (“downport”) and are shipped as SAP Fiori transactional apps for ERP/CRM 1.0. Back end 

Since OData services can only be shipped on lower back-end releases via integration components, new integration components were introduced. One integration component supports all back-end releases (for example, ECC 6.00 up to EhP6).



When the back end is upgraded to the latest Suite release (for example, ERP EhP7), these integration components are merged into the standard back-end SP.

Frontend 

For the UI artefacts, UI components were built for clusters of apps that correspond to instances on the back end.



During an upgrade, these UI components are merged into the UI components delivered with the latest Business Suite release.

The product versions contain both UI components and integration components. Maintenance and enhancements of the existing apps are shipped via SPs of the software components. New apps that are downported are shipped as follows: o

With SPs of existing software components if the app fits into the existing SWC (for example, an additional PS app will be shipped in the same software component as the existing PS apps)

o

With new software components in existing product versions (for example, the first app for Retail is shipped in a new software component as part of a new instance in the existing ERP UI product version)

Page 9 of 14

ABAP Frontend Server Product-specific UI Add-Ons UI for SAP Business Suite ERP

CRM

PP, PS, QM, MM

SD

Retail

CRM


RUNTIME


ABAP Backend Server (ECC 600 up to EHP6, CRM 7.00 up to EhP2

OData Integration Add-Ons (NON-MODIFYING) per cluster of Apps

Stable Business Suite Backend Core Component

Netweaver (7.00 up to 7.31) plus SAP IW BEP 200

HANA/ANY DB

Product versions/UI software components are as follows (from left to right): 

SAP Fiori transactional apps for SAP ERP 1.0, technical name: FIORI ERP APPLICATIONS X2 1.0 covering ERP (PP, PS, QM, and MM), SD and Retail with the following UI software components:



o

UIX02EA4 100 (SD, starting with EhP4)

o

UIX02EAP 100 (PP, PS, MM, QM)

o

UIX02RT4 100 (Retail)

SAP Fiori transactional apps for SAP CRM 1.0, technical name: FIORI CRM APPLICATIONS X2 1.0 covering CRM with UI software component UIX02CRM 100.

Documentation for these products is available on the SAP Help Portal at http://help.sap.com/fiori_products : 

SAP Fiori transaction apps for SAP ERP 1.0



SAP Fiori transactional apps for SAP CRM 1.0

Page 10 of 14

Please note that the term transactional apps may be misleading. In this context, it refers to the apps of ERP and CRM downported from SAP Business Suite 7 Innovations 2013 to lower releases, whereas the term transactional apps is usually (e.g. in the chapter ‘Introduction’ of this document) used to distinguish apps that engage back-end transactions from analytical apps (Smart Business apps) and from fact sheets.

For product versions/software components, please see Appendix B.

Page 11 of 14

Appendix A List of apps (total 25) shipped in May 2013 (SAP Fiori 1.0, on Launch Page), and also shipped a s ‘principal apps’ (on SAP Fiori Launchpad) in Nov 2013.

App Name

Product Version, Delivery May 2013 (SAP Fiori 1.0)

Product Version (Delivery since Nov 2013)

Integration Component (for All Deliveries)

UI Comp. Delivery May 2013 (SAP Fiori 1.0)

UI Component (Delivery since Nov 2013)

Approve Requests

FIORI GENERICINBX 1.0

FIORI APPROVE REQUESTS X1

SAP IW PGW

UIGIB001

UIX01CA1 100

Customer Invoices

FIORI INVOICEBILL 1.0

FIORI ERP APPLICATIONS X1

SRA021

UISRA021

UIX01EAP 100

Approve Leave Requests

FIORI LEAVEREQAPPR 1.0


GBHCM003

UIHCM003

UIX01HCM 100

My Leave Requests

FIORI LEAVEREQCRE 1.0


GBHCM002

UIHCM002

UIX01HCM 100

My Benefits

FIORI MYBENENRO 1.0


SRA007

UISRA007

UIX01HCM 100

My Spend

FIORI MYDEPTSPEND 1.0


SRA012

UISRA012

UIX01EAP 100

Change Sales Orders

FIORI ORDERCHG 1.0


SRA003 and SRA018

UISRA003 and UISRA018

UIX01EAP 100

Create Sales Orders

FIORI ORDERCRE 1.0


SRA017

UISRA017

UIX01EAP 100

Order from Requisitions

FIORI ORDERPOREQ 1.0


SRA013

UISRA013

UIX01EAP 100

Track Sales Orders

FIORI ORDERSTSTRK 1.0


SRA018

UISRA018

UIX01EAP 100

My Paystubs

FIORI PAYSLIPLOOK 1.0


SRA006

UISRA006

UIX01HCM 100

Check Price and Availability

FIORI PRICECHECK 1.0


SRA016

UISRA016

UIX01EAP 100

Page 12 of 14

App Name

Product Version, Delivery May 2013 (SAP Fiori 1.0)

Product Version (Delivery since Nov 2013)

Integration Component (for All Deliveries)

UI Comp. Delivery May 2013 (SAP Fiori 1.0)

UI Component (Delivery since Nov 2013)

Approve Purchase Contracts

FIORI PURCHASECONTAPPR 1.0


SRA001

UISRA001

UIX01EAP 100

Approve Purchase Orders

FIORI PURCHASEORDAPPR 1.0


GBAPP002

UIAPP002

UIX01EAP 100

Approve Requisitions

FIORI PURCHASEREQAPPR 1.0


GBAPP002

UIAPP001

UIX01EAP 100

Track Shipments

FIORI SHIPTRK 1.0


SRA019

UISRA019

UIX01EAP 100

Approve Shopping Carts

FIORI SHOPCARTAPPR 1.0

FIORI SRM APPLICATIONS X1

GBSRM001

UISRM001

UIX01SRM 100

My Shopping Cart

FIORI SHOPCARTCRE 1.0


SRMNXP01 100

UISRA011 and UISRA014

UIX01SRM 100

Track Shopping Carts

FIORI SHOPCARTTRK 1.0


SRMNXP01 100

UISRA011

UIX01SRM 100

My Timesheet

FIORI TIMERECORDING 1.0


SRA002

UISRA002

UIX01HCM 100

Approve Timesheets

FIORI TIMESHTAPPR 1.0


SRA010

UISRA010

UIX01HCM 100

Track Purchase Orders

FIORI TRACKPO 1.0


SRA020

UISRA020

UIX01EAP 100

Approve Travel Expenses

FIORI TRAVELEXPAPPR 1.0


SRA008

UISRA008

UIX01TRV 100

Approve Travel Requests

FIORI TRAVELREQAPPR 1.0


SRA009

UISRA009

UIX01TRV 100

My Travel Requests

FIORI TRAVELREQCRE 1.0


SRA004

UISRA004

UIX01TRV 100

Page 13 of 14

Appendix B List of apps that have been downported from the latest Business Suite r elease: Fiori App Name

Product Version

Integration Component

UI Component

My Accounts

FIORI CRM APPLICATIONS X2 1.0

GBX02CRM 700

UIX02CRM 100

My Tasks


GBX02CRM 700

UIX02CRM 100

My Contacts


GBX02CRM 700

UIX02CRM 100

My Appointments


GBX02CRM 700

UIX02CRM 100

My Notes


GBX02CRM 700

UIX02CRM 100

My Opportunities


GBX02CRM 700

UIX02CRM 100

Simulate Sales Pipeline


GBX02CRM 700

UIX02CRM 100

My Leads


GBX02CRM 700

UIX02CRM 100

Track Sales Pipeline


GBX02CRM 700

UIX02CRM 100

My Contacts

FIORI ERP APPLICATIONS X2 1.0

GBX02SA4 604

UIX02EA4 100

Release Production Orders


GBX02SAP 600

UIX02EAP 100

Confirm Production Orders


GBX02SAP 600

UIX02EAP 100

Confirm Production Operations


GBX02SAP 600

UIX02EAP 100

Release Production Order Operations


GBX02SAP 600

UIX02EAP 100

Change WBS Element Status


GBX02SAP 600

UIX02EAP 100

Confirm Project Milestone


GBX02SAP 600

UIX02EAP 100

Confirm Network Activity


GBX02SAP 600

UIX02EAP 100

Report Quality Issue


GBX02EAP 600

UIX02EAP 100

My Quality Tasks


GBX02EAP 600

UIX02EAP 100

Look Up Retail Products


GBX02RT4 604

UIX02RT4 100

Change Network Activity Status


GBX02SAP 600

UIX02EAP 100

Approve Service Entry Sheet


GBX02SAP 600

UIX02EAP 100

Approve Supplier Invoices


GBX02SAP 600

UIX02EAP 100

Adjust Stock


GBX02RT4 604

UIX02RT4 100

Official names of product versions: FIORI CRM APPLICATIONS X2 1.0: SAP Fiori transactional apps for SAP CRM 1.0 FIORI ERP APPLICATIONS X2 1.0: SAP Fiori transactional apps for SAP ERP 1.0

Page 14 of 14

Copyright 2015 SAP SE. All rights reserved © No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties o f merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver “How-to” Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

SAP Fiori Packaging.pdf

Recommend Documents