(PDF) SAP Fiori Packaging.pdf - PDFSLIDE.NET (2023)

  • 7/24/2019 SAP Fiori Packaging.pdf

    1/15

    SAP Fiori Packaging

    Version 1.1, January 2015

    SAP

  • 7/24/2019 SAP Fiori Packaging.pdf

    2/15

    Page 2of 14

    Table of Contents

    Introduction...............................................................................................................................................3

    Packaging principle: Singletransactional apps on all back-endreleases with launch page................ 4

    Packaging principle: Transactional apps on all back-end releaseswith SAP Fiori launchpad, also

    known as principalapps.........................................................................................................................5

    Packaging principle: Transactional apps on most recentSuiteback-end release................................ 7

    Packaging principle: Transactional apps on earlier/lowerback-endreleases with option to upgradeto latest Business Suiterelease................................................................................................................9

    AppendixA...............................................................................................................................................12

    AppendixB...............................................................................................................................................14

  • 7/24/2019 SAP Fiori Packaging.pdf

    3/15

    Page 3of 14

    Introduction

    This document describes the different packaging (assembly)principles used for SAP Fiori transactional apps,

    including some architecture background. The target group forthis document is SAP Fiori consultants and

    other Fiori experts, in particular those involved inimplementing Fiori-related system components. The

    following graphic gives an overview of the different Fiori apptypes.

    You can find a list of all apps including a link to thetechnical requirements per app in the App Catalog on the

    SAP Help Portal athttp://help.sap.com/fiori. There you can alsofind additional information on Fiori and

    Fiori products.

    Transactional Fiori apps consist of software artefacts to bedeployed both on the front-end server and the

    back-end server. These objects are delivered as productversions, software components (within product

    versions) and their support packages/stacks. By default, thereis one shipment each quarter.

    The assembly of these software components is not identical forall apps.

    The following sections describe the different principles inpackaging the artefacts.

    http://help.sap.com/fiorihttp://help.sap.com/fiorihttp://help.sap.com/fiorihttp://help.sap.com/fiori
  • 7/24/2019 SAP Fiori Packaging.pdf

    4/15

    Page 4of 14

    Packaging principle: Singletransactional apps on all back-endreleases

    with launch page

    The launch page version of the apps will not be developedfurther. SAP still provides maintenance to

    customers but it is no longer possible to download installationfiles. 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 aguide how to migrate to the launchpad versionofthose apps: Guide [insert link here,

    not in the sentence]

    There is one integration component and one UI component for eachapp (total of 25 apps). The

    reason for 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 patchableindependent of other apps, and thus

    minimizing the effort for upgrading the apps.

    The required minimum SP in the back end is low to address abroad installed base and make it as

    easy as possible for customers to install the integrationcomponents.

    In case of back-end upgrades, the integration component remainsthe same.

    Product versions contain integration component instances andfront-end server instances.

    Launch page runs on NetWeaver 7.00 (whereas SAP Fiori launchpadrequires NetWeaver 7.31 or

    higher).

    Maintenance and enhancements of the existing apps are shippedvia SPs of the software

    components.

    For a list of product versions, see Appendix A.

    http://scn.sap.com/docs/DOC-55889http://scn.sap.com/docs/DOC-55889http://scn.sap.com/docs/DOC-55889http://scn.sap.com/docs/DOC-55889
  • 7/24/2019 SAP Fiori Packaging.pdf

    5/15

    Page 5of 14

    Packaging principle: Transactional apps on all back-end releaseswith

    SAP Fiori launchpad, also known as principal apps

    Back end

    Software component SAP IW BEP 200 (latest SP) has to beinstalled in back-end releases based on

    NetWeaver lower than NW 7.40 as a technical prerequisite to runOData services.

    OData services are delivered via integration components on allreleases including NW 7.40.

    Integration components are modification-free add-ons for theback end.

    There is one integration component per app (same components aslisted in the table in appendix A

    for the Single transactional apps on all back-end releases withlaunch page) for the first 3 product

    versions listed below. For these product versions, there is noclustering of apps to ensure that

    customers can migrate smoothly. Duplication of code has alsobeen avoided.

    For SAP FIORI FOR SAP ERP HCM 1.0, there is one integrationcomponent for all apps and for allbackend releases to coverfunctionality available in all backend releases. To exploitadditional

    backend features available as of Ehp5, a second integrationcomponent can be installed .

    In case of back-end upgrades, the integration component remainsunchanged.

    Front end

    There are UI components for clusters of apps that correspond toinstances in the back end. The

    reason for this change of the packaging principle compared tothe version with the launch page was

    to avoid an ever increasing number of product versions byaggregating apps into fewer product

    versions and UI software components (at that time, Fiori hadbeen accepted as UI paradigm and the

    expectation was to build hundreds of apps).

    The following related product versions contain integrationcomponent instances and front-end server

    instances:

    SAP Fiori principal apps for ERP 1.0 (FIORI ERP APPLICATIONSX1)

    SAP Fiori principal apps for SRM 1.0 (FIORI SRM APPLICATIONSX1)

    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 ofQ1/2015 delivery)

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

    http://help.sap.com/saphelp_fiorierpx1_100/helpdata/en/f5/5590533e73cc26e10000000a4450e5/frameset.htmhttp://help.sap.com/saphelp_fiorierpx1_100/helpdata/en/f5/5590533e73cc26e10000000a4450e5/frameset.htmhttp://help.sap.com/saphelp_fiorisrmx1_100/helpdata/en/94/369053bb64d56ce10000000a4450e5/frameset.htmhttp://help.sap.com/saphelp_fiorisrmx1_100/helpdata/en/94/369053bb64d56ce10000000a4450e5/frameset.htmhttps://service.sap.com/sap/support/pam?hash=s%3DSAP%2520Fiori%2520for%2520Request%2520Approvals%25201.0%2520%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007313%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3DSAP%2520Fiori%2520for%2520Request%2520Approvals%25201.0%2520%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007313%26pt%3Dg%257Cdhttp://help.sap.com/saphelp_fiorisrmx1_100/helpdata/en/94/369053bb64d56ce10000000a4450e5/frameset.htmhttp://help.sap.com/saphelp_fiorierpx1_100/helpdata/en/f5/5590533e73cc26e10000000a4450e5/frameset.htm
  • 7/24/2019 SAP Fiori Packaging.pdf

    6/15

    Page 6of 14

    ABAP Backend Server

    (ECC 600 or higher, SRM 7.00 or higher

    ABAP Frontend Server

    Product-specific UI Add-Ons

    UI for SAP Business Suite

    ERP

    MM, SD, LE, FIN Tr avel HCM

    UI Infrastructure

    SAP Netweaver Gateway 2.0

    Stable Business Suite Backend Core Component

    RUNTIMEDESIGN TIME

    HANA/ANY DB

    OData Integration Add-Ons (NON-MODIFYING)

    SRM Approve Req.

    Appro

    valSRM

    Netweaver (7.00 or higher)

    plus

    SAP IW BEP 200 (for NW b elow NW 7.40)

    Product versions/UI software components are as follows:

    SAP Fiori principal apps for SAP ERP 1.0, technical name: FIORIERP 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: FIORISRM APPLICATIONS X1 1.0

    SRM with UI software component UIX01SRM 100

    SAP Fiori for Request Approvals 1.0, technical name: FIORIAPPROVE REQUESTS X1 1.0

    Approve Request with UI software component UIX01CA1 100

    per App aus Schaubildentfernen, UI-SWcomponent fr HCMherausnehmen,

    https://service.sap.com/sap/support/pam?hash=s%3DSAP%2520Fiori%2520principal%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007315%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3Dprincipal%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007314%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3Dprincipal%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007314%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3DSAP%2520Fiori%2520principal%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007315%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3DSAP%2520Fiori%2520principal%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007315%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3DSAP%2520Fiori%2520for%2520Request%2520Approvals%25201.0%2520%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007313%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3DSAP%2520Fiori%2520for%2520Request%2520Approvals%25201.0%2520%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007313%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3DSAP%2520Fiori%2520for%2520Request%2520Approvals%25201.0%2520%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007313%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3DSAP%2520Fiori%2520principal%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007315%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3Dprincipal%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007314%26pt%3Dg%257Cd
  • 7/24/2019 SAP Fiori Packaging.pdf

    7/15

    Page 7of 14

    Documentation for each product is available underSAP FioriProductson 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 recentSuiteback-end

    release

    Backend

    The most recent back-end release of the Business Suite runs onNetWeaver 7.40. As part of the Suite

    back-end support package stack, the NW 7.40 Support PackageStack including software component

    Gateway Foundation SAP_GWFND is installed in the back end. Thissoftware component is a

    prerequisite to run OData services.

    OData services are delivered as part of back-end SPs. There areno integration components. The

    reason for this architecture was to allow the option of HANAoptimization and the goal of minimizing

    the number of packages to be installed.

    Frontend

    There are UI components for clusters of apps that correspond toinstances on the back end (as

    described above in the section Transactional apps on allback-end releases with SAP Fiori launchpad,

    also known as principal apps).

    Product versions: The product versions for ERP, SCM, SRM, and soon contain UI artefacts only and no

    back-end objects (these are shipped via SPs in the backend).

    Please note that the UI product versions have a logicaldependency to a particular SP stack of the back-

    end product version. This dependency is not modelled in PPMS andtherefore is not considered by

    installation tools like MOPZ.The dependency is described in theRIN of the UI product version and is modelled in thecross-product

    solution consumed by the landscape planner.

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

    http://help.sap.com/fiori_productshttp://help.sap.com/fiori_productshttp://help.sap.com/fiori_productshttp://help.sap.com/saphelp_fiorierpx1_100/helpdata/en/f5/5590533e73cc26e10000000a4450e5/content.htm?current_toc=/en/c5/5690533e73cc26e10000000a4450e5/plain.htm&show_children=truehttp://help.sap.com/saphelp_fiorisrmx1_100/helpdata/en/94/369053bb64d56ce10000000a4450e5/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/dd/b564520e2a725fe10000000a441470/content.htm?frameset=/en/ba/954353a531e647e10000000a441470/frameset.htm&current_toc=/en/ba/954353a531e647e10000000a441470/plain.htm&node_id=4&show_children=falsehttp://help.sap.com/fiori_bs2013/helpdata/en/dd/b564520e2a725fe10000000a441470/content.htm?frameset=/en/ba/954353a531e647e10000000a441470/frameset.htm&current_toc=/en/ba/954353a531e647e10000000a441470/plain.htm&node_id=4&show_children=falsehttp://help.sap.com/saphelp_fiorisrmx1_100/helpdata/en/94/369053bb64d56ce10000000a4450e5/frameset.htmhttp://help.sap.com/saphelp_fiorierpx1_100/helpdata/en/f5/5590533e73cc26e10000000a4450e5/content.htm?current_toc=/en/c5/5690533e73cc26e10000000a4450e5/plain.htm&show_children=truehttp://help.sap.com/fiori_products
  • 7/24/2019 SAP Fiori Packaging.pdf

    8/15

    Page 8of 14

    New apps are shipped as follows:

    o With SPs of existing software components if the app fits intothe existing SWC (for example, an

    additional MM app will be shipped in the same software componentas the existing MM apps)

    o With new software components in existing product versions (forexample, the first app for

    Insurance is shipped in a new software component as part of anew instance in the existing ERP

    UI product version)

    o With new product versions (for example, the first app for SLCwill be shipped as a new product

    version for SLC).

    ABAP Backend Server (AT1)

    SAP Business Suite 7i2013

    ABAP Frontend Server

    Product-specific UI Add-Ons

    UI for SAP Business Suite (AT1)

    ERP

    FIN SD PP PS MM QM

    CRM SRM SCM

    UI Infrastructure

    SAP Netweaver Gateway 2.0

    ERP

    FIN SD PP PS MM QM

    CRM SRM SCM

    RUNTIMEDESIGN TIME

    HANA / ANY DB

    Netweaver 7.40

    (including SAP_GWFND)

    Documentation for each product is available on the SAP HelpPortal 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

    http://help.sap.com/fiori_bs2013/helpdata/en/bd/4c615240e1745fe10000000a441470/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/3b/b24f52f10a5c64e10000000a423f68/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/3b/b24f52f10a5c64e10000000a423f68/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/f3/3b3252d40a6401e10000000a441470/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/f3/3b3252d40a6401e10000000a441470/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/bd/4c615240e1745fe10000000a441470/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/bd/4c615240e1745fe10000000a441470/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/66/83605307864d75e10000000a44538d/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/66/83605307864d75e10000000a44538d/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/66/83605307864d75e10000000a44538d/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/bd/4c615240e1745fe10000000a441470/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/f3/3b3252d40a6401e10000000a441470/frameset.htmhttp://help.sap.com/fiori_bs2013/helpdata/en/3b/b24f52f10a5c64e10000000a423f68/frameset.htm
  • 7/24/2019 SAP Fiori Packaging.pdf

    9/15

    Page 9of 14

    Packaging principle: Transactional apps onearlier/lowerback-end

    releases with option to upgrade to latest Business Suiterelease

    Selected transactional apps from ERP and CRM that were initiallydeveloped and shipped only for the

    latest Business Suite release (for example, ERP EhP7) have beenmade available on lower backend

    releases as well (downport)and are shipped as SAP Fioritransactional apps for ERP/CRM 1.0.

    Back end

    Since OData services can only be shipped on lower back-endreleases via integration components,

    new integration components were introduced. One integrationcomponent supports all back-end

    releases (for example, ECC 6.00 up to EhP6).

    When the back end is upgraded to the latest Suite release (forexample, ERP EhP7), these integration

    components are merged into the standard back-end SP.

    Frontend

    For the UI artefacts, UI components were built for clusters ofapps that correspond to instances on

    the back end.

    During an upgrade, these UI components are merged into the UIcomponents delivered with the

    latest Business Suite release.

    The product versions contain both UI components and integrationcomponents.

    Maintenance and enhancements of the existing apps are shippedvia 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 intothe existing SWC (for example, an

    additional PS app will be shipped in the same software componentas the existing PS apps)

    o With new software components in existing product versions (forexample, the first app for Retail

    is shipped in a new software component as part of a new instancein the existing ERP UI product

    version)

  • 7/24/2019 SAP Fiori Packaging.pdf

    10/15

    Page 10of 14

    ABAP Backend Server

    (ECC 600 up to EHP6, CRM 7.00 up to EhP2

    ABAP Frontend Server

    Product-specific UI Add-Ons

    UI for SAP Business Suite

    ERP

    PP, PS, QM, MM SD Retail

    UI Infrastructure

    SAP Netweaver Gateway 2.0

    Stable Business Suite Backend Core Component

    RUNTIMEDESIGN TIME

    HANA/ANY DB

    OData Integration Add-Ons (NON-MODIFYING) per cluster ofApps

    CRM

    CRM

    Netweaver (7.00 up to 7.31)

    plus

    SAP IW BEP 200

    Product versions/UI software components are as follows (fromleft 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 HelpPortal 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

    https://service.sap.com/sap/support/pam?hash=s%3Dfiori%2520x2%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007284%26pt%3Dg%257Cdhttp://help.sap.com/fiori_productshttp://help.sap.com/saphelp_fioricrmx2_100/helpdata/en/24/0da852588a3258e10000000a423f68/frameset.htmhttp://help.sap.com/saphelp_fioricrmx2_100/helpdata/en/24/0da852588a3258e10000000a423f68/frameset.htmhttps://service.sap.com/sap/support/pam?hash=s%3Dfiori%2520x2%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007273%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3Dfiori%2520x2%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007273%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3Dfiori%2520x2%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007284%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3Dfiori%2520x2%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007284%26pt%3Dg%257Cdhttp://help.sap.com/fiori_productshttp://help.sap.com/fiori_productshttp://help.sap.com/saphelp_fiorierpx2_100/helpdata/en/bf/1f8b52722d7454e10000000a44176d/frameset.htmhttp://help.sap.com/saphelp_fiorierpx2_100/helpdata/en/bf/1f8b52722d7454e10000000a44176d/frameset.htmhttp://help.sap.com/saphelp_fioricrmx2_100/helpdata/en/24/0da852588a3258e10000000a423f68/frameset.htmhttp://help.sap.com/saphelp_fioricrmx2_100/helpdata/en/24/0da852588a3258e10000000a423f68/frameset.htmhttp://help.sap.com/saphelp_fioricrmx2_100/helpdata/en/24/0da852588a3258e10000000a423f68/frameset.htmhttp://help.sap.com/saphelp_fiorierpx2_100/helpdata/en/bf/1f8b52722d7454e10000000a44176d/frameset.htmhttp://help.sap.com/fiori_productshttps://service.sap.com/sap/support/pam?hash=s%3Dfiori%2520x2%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007284%26pt%3Dg%257Cdhttps://service.sap.com/sap/support/pam?hash=s%3Dfiori%2520x2%26o%3Dmost_viewed%257Cdesc%26st%3Dl%26rpp%3D20%26page%3D1%26pvnr%3D67838200100900007273%26pt%3Dg%257Cd
  • 7/24/2019 SAP Fiori Packaging.pdf

    11/15

    Page 11of 14

    Please note that the term transactional appsmay be misleading.In this context, it refers to the apps of

    ERP and CRM downported from SAP Business Suite 7 Innovations2013to lower releases, whereas the

    term transactional apps is usually(e.g. in the chapterIntroduction of this document)used to

    distinguish apps that engage back-end transactionsfromanalytical apps (Smart Business apps) and from

    fact sheets.

    For product versions/software components, please see AppendixB.

  • 7/24/2019 SAP Fiori Packaging.pdf

    12/15

    Page 12of 14

    Appendix A

    List of apps (total 25) shipped in May 2013 (SAP Fiori 1.0, onLaunch Page), and also shipped a s principal

    apps (on SAP Fiori Launchpad) in Nov 2013.

    App Name Product Version, DeliveryMay 2013 (SAP Fiori 1.0)

    Product Version(Delivery since Nov2013)

    IntegrationComponent(for AllDeliveries)

    UI Comp.Delivery May2013 (SAPFiori 1.0)

    UI Component(Delivery sinceNov 2013)

    ApproveRequests

    FIORI GENERICINBX 1.0 FIORI APPROVEREQUESTS X1

    SAP IW PGW UIGIB001 UIX01CA1 100

    CustomerInvoices

    FIORI INVOICEBILL 1.0 FIORI ERPAPPLICATIONS X1

    SRA021 UISRA021 UIX01EAP 100

    ApproveLeaveRequests

    FIORI LEAVEREQAPPR 1.0 FIORI ERPAPPLICATIONS X1

    GBHCM003 UIHCM003 UIX01HCM 100

    My LeaveRequests

    FIORI LEAVEREQCRE 1.0 FIORI ERPAPPLICATIONS X1

    GBHCM002 UIHCM002 UIX01HCM 100

    My Benefits FIORI MYBENENRO 1.0 FIORI ERPAPPLICATIONS X1

    SRA007 UISRA007 UIX01HCM 100

    My Spend FIORI MYDEPTSPEND 1.0 FIORI ERPAPPLICATIONS X1

    SRA012 UISRA012 UIX01EAP 100

    ChangeSales Orders

    FIORI ORDERCHG 1.0 FIORI ERPAPPLICATIONS X1

    SRA003 andSRA018

    UISRA003andUISRA018

    UIX01EAP 100

    Create SalesOrders

    FIORI ORDERCRE 1.0 FIORI ERPAPPLICATIONS X1

    SRA017 UISRA017 UIX01EAP 100

    Order fromRequisitions

    FIORI ORDERPOREQ 1.0 FIORI ERPAPPLICATIONS X1

    SRA013 UISRA013 UIX01EAP 100

    Track SalesOrders

    FIORI ORDERSTSTRK 1.0 FIORI ERPAPPLICATIONS X1

    SRA018 UISRA018 UIX01EAP 100

    My Paystubs FIORI PAYSLIPLOOK 1.0 FIORI ERPAPPLICATIONS X1

    SRA006 UISRA006 UIX01HCM 100

    Check PriceandAvailability

    FIORI PRICECHECK 1.0 FIORI ERPAPPLICATIONS X1

    SRA016 UISRA016 UIX01EAP 100

  • 7/24/2019 SAP Fiori Packaging.pdf

    13/15

    Page 13of 14

    App Name Product Version, DeliveryMay 2013 (SAP Fiori 1.0)

    Product Version(Delivery since Nov2013)

    IntegrationComponent(for AllDeliveries)

    UI Comp.Delivery May2013 (SAPFiori 1.0)

    UI Component(Delivery sinceNov 2013)

    ApprovePurchaseContracts

    FIORIPURCHASECONTAPPR 1.0

    FIORI ERPAPPLICATIONS X1

    SRA001 UISRA001 UIX01EAP 100

    ApprovePurchaseOrders

    FIORIPURCHASEORDAPPR 1.0

    FIORI ERPAPPLICATIONS X1

    GBAPP002 UIAPP002 UIX01EAP 100

    ApproveRequisitions

    FIORIPURCHASEREQAPPR 1.0

    FIORI ERPAPPLICATIONS X1

    GBAPP002 UIAPP001 UIX01EAP 100

    Track

    Shipments

    FIORI SHIPTRK 1.0 FIORI ERP

    APPLICATIONS X1

    SRA019 UISRA019 UIX01EAP 100

    ApproveShoppingCarts

    FIORI SHOPCARTAPPR 1.0 FIORI SRMAPPLICATIONS X1

    GBSRM001 UISRM001 UIX01SRM 100

    My ShoppingCart

    FIORI SHOPCARTCRE 1.0 FIORI SRMAPPLICATIONS X1

    SRMNXP01100

    UISRA011andUISRA014

    UIX01SRM 100

    TrackShopping

    Carts

    FIORI SHOPCARTTRK 1.0 FIORI SRMAPPLICATIONS X1

    SRMNXP01100

    UISRA011 UIX01SRM 100

    MyTimesheet

    FIORI TIMERECORDING 1.0 FIORI ERPAPPLICATIONS X1

    SRA002 UISRA002 UIX01HCM 100

    ApproveTimesheets

    FIORI TIMESHTAPPR 1.0 FIORI ERPAPPLICATIONS X1

    SRA010 UISRA010 UIX01HCM 100

    TrackPurchaseOrders

    FIORI TRACKPO 1.0 FIORI ERPAPPLICATIONS X1

    SRA020 UISRA020 UIX01EAP 100

    ApproveTravelExpenses

    FIORI TRAVELEXPAPPR 1.0 FIORI ERPAPPLICATIONS X1

    SRA008 UISRA008 UIX01TRV 100

    ApproveTravelRequests

    FIORI TRAVELREQAPPR1.0

    FIORI ERPAPPLICATIONS X1

    SRA009 UISRA009 UIX01TRV 100

    My TravelRequests

    FIORI TRAVELREQCRE 1.0 FIORI ERPAPPLICATIONS X1

    SRA004 UISRA004 UIX01TRV 100

  • 7/24/2019 SAP Fiori Packaging.pdf

    14/15

    Page 14of 14

    Appendix B

    List of apps that have been downported from the latest BusinessSuite release:

    Fiori App Name Product Version IntegrationComponent

    UI Component

    My Accounts FIORI CRM APPLICATIONS X2 1.0 GBX02CRM 700 UIX02CRM100

    My Tasks FIORI CRM APPLICATIONS X2 1.0 GBX02CRM 700 UIX02CRM100

    My Contacts FIORI CRM APPLICATIONS X2 1.0 GBX02CRM 700 UIX02CRM100

    My Appointments FIORI CRM APPLICATIONS X2 1.0 GBX02CRM 700UIX02CRM 100

    My Notes FIORI CRM APPLICATIONS X2 1.0 GBX02CRM 700 UIX02CRM100

    My Opportunities FIORI CRM APPLICATIONS X2 1.0 GBX02CRM 700UIX02CRM 100

    Simulate Sales Pipeline FIORI CRM APPLICATIONS X2 1.0 GBX02CRM700 UIX02CRM 100

    My Leads FIORI CRM APPLICATIONS X2 1.0 GBX02CRM 700 UIX02CRM100

    Track Sales Pipeline FIORI CRM APPLICATIONS X2 1.0 GBX02CRM 700UIX02CRM 100

    My Contacts FIORI ERP APPLICATIONS X2 1.0 GBX02SA4 604 UIX02EA4100

    Release Production Orders FIORI ERP APPLICATIONS X2 1.0 GBX02SAP600 UIX02EAP 100

    Confirm Production Orders FIORI ERP APPLICATIONS X2 1.0 GBX02SAP600 UIX02EAP 100

    Confirm Production Operations FIORI ERP APPLICATIONS X2 1.0GBX02SAP 600 UIX02EAP 100

    Release Production OrderOperations

    FIORI ERP APPLICATIONS X2 1.0 GBX02SAP 600 UIX02EAP 100

    Change WBS Element Status FIORI ERP APPLICATIONS X2 1.0 GBX02SAP600 UIX02EAP 100

    Confirm Project Milestone FIORI ERP APPLICATIONS X2 1.0 GBX02SAP600 UIX02EAP 100

    Confirm Network Activity FIORI ERP APPLICATIONS X2 1.0 GBX02SAP600 UIX02EAP 100

    Report Quality Issue FIORI ERP APPLICATIONS X2 1.0 GBX02EAP 600UIX02EAP 100

    My Quality Tasks FIORI ERP APPLICATIONS X2 1.0 GBX02EAP 600UIX02EAP 100

    Look Up Retail Products FIORI ERP APPLICATIONS X2 1.0 GBX02RT4604 UIX02RT4 100

    Change Network Activity Status FIORI ERP APPLICATIONS X2 1.0GBX02SAP 600 UIX02EAP 100

    Approve Service Entry Sheet FIORI ERP APPLICATIONS X2 1.0GBX02SAP 600 UIX02EAP 100

    Approve Supplier Invoices FIORI ERP APPLICATIONS X2 1.0 GBX02SAP600 UIX02EAP 100

    Adjust Stock FIORI ERP APPLICATIONS X2 1.0 GBX02RT4 604 UIX02RT4100

    Official names of product versions:

    FIORI CRM APPLICATIONS X2 1.0: SAP Fiori transactional apps forSAP CRM 1.0

    FIORI ERP APPLICATIONS X2 1.0: SAP Fiori transactional apps forSAP ERP 1.0

  • 7/24/2019 SAP Fiori Packaging.pdf

    15/15

    Copyright 2015SAP 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 inGermany and inseveral 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 SAPGroupproducts 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 of 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, orconsequential

    damages that may result from the use of these materials.SAP doesnot 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 thosefeaturesand 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 SAPs Support Services and may not be

    modified or altered in any way.

Top Articles
Latest Posts
Article information

Author: Prof. An Powlowski

Last Updated: 02/20/2023

Views: 5716

Rating: 4.3 / 5 (44 voted)

Reviews: 91% of readers found this page helpful

Author information

Name: Prof. An Powlowski

Birthday: 1992-09-29

Address: Apt. 994 8891 Orval Hill, Brittnyburgh, AZ 41023-0398

Phone: +26417467956738

Job: District Marketing Strategist

Hobby: Embroidery, Bodybuilding, Motor sports, Amateur radio, Wood carving, Whittling, Air sports

Introduction: My name is Prof. An Powlowski, I am a charming, helpful, attractive, good, graceful, thoughtful, vast person who loves writing and wants to share my knowledge and understanding with you.