{"id":23712,"date":"2023-08-30T05:00:00","date_gmt":"2023-08-30T03:00:00","guid":{"rendered":"https:\/\/sii.pl\/blog\/?p=23712&category=hard-development"},"modified":"2026-05-07T13:42:11","modified_gmt":"2026-05-07T11:42:11","slug":"standard-fiori-apps-enhancements","status":"publish","type":"post","link":"https:\/\/sii.pl\/blog\/en\/standard-fiori-apps-enhancements\/","title":{"rendered":"Standard Fiori Apps enhancements"},"content":{"rendered":"\n

Standard SAP Fiori apps are a portfolio of applications where we receive a set of basic functionalities from the start. Very often, there are specific code fragments or configuring options that make customization possible in order to meet the business requirements. These places are called enhancements, and that is what this article is going to cover.<\/p>\n\n\n\n

When our requirement is to enhance the functionality of the standard SAP Fiori application, there are a couple of aspects that are worth examining before. If we need to add a new field, it is possible that it is already possible that the option to add it at the ODATA level already exists and is in the documentation. Let\u2019s try to systemize the places worth examining to ensure that the approach we have chosen is the most optimal. As an example, we will use the \u201cRevise Payment Proposals\u201d application and attempt to add a new field, \u201citem text\u201d, based on Roger Sainsbury\u2019s analysis.<\/p>\n\n\n\n

Enhancement types<\/strong><\/h2>\n\n\n\n

Personalization<\/strong><\/h3>\n\n\n\n

Sometimes, it is possible that the new field we are about to add is already available in the personalization options (view setting). It is enough to remember to verify it in the application\u2019s settings.<\/p>\n\n\n\n

\"Settings<\/a>
Fig. 1 Settings button of the SAP Fiori app<\/figcaption><\/figure>\n\n\n\n
\"List<\/a>
Fig. 2 List of available fields to show in the settings<\/figcaption><\/figure>\n\n\n\n

Customization<\/strong><\/h3>\n\n\n\n

Some Fiori apps are easy to customize in SPRO (enabling\/disabling fields) but how to enter the SPRO screen when we are in the Fiori Launchpad? There is a simple way to navigate there. To enter the \u2018ok_code\u2019 in the Fiori Launchpad app, it is enough to go to \u2018GUI Actions and Settings\u2019.<\/p>\n\n\n\n

\"Options<\/a>
Fig. 3 Options available from the \u201cmore\u201d tab<\/figcaption><\/figure>\n\n\n\n

From there, we can enable the \u201cshow OK Code Field\u201d option.<\/p>\n\n\n\n

\"Show<\/a>
Fig. 4 Show OK Code selection field<\/figcaption><\/figure>\n\n\n\n

This is how we can access SPRO without installing native SAPGUI frontend, without downloading new files, and without being limited by authorizations according to the corporation rules.<\/p>\n\n\n\n

\"SPRO<\/a>
Fig 5. SPRO selection screen<\/figcaption><\/figure>\n\n\n\n

Run-time adaption<\/strong> (RTA)<\/strong><\/h3>\n\n\n\n

RT adaptation is a functionality that enables the assignment of a super-user who can make basic changes to the Fiori app. These changes will apply to all users, unlike personalization where only one user is able to see the changes. To use RTA, the user must be assigned to the \u2018SAP_UI_FLEX_KEY_USER\u2019 role at the frontend Gateway. <\/p>\n\n\n\n

At the same time, the \u2018Adapt UI\u201d option will become available in the Fiori Launchpad. Unfortunately, this option is currently only available in apps that use \u2018SmartForms\u2019 and \u2018ObjectPage\u2019 controls, such as the \u2018Purchase Requisition Item Factsheet\u2019.<\/p>\n\n\n\n

\"RTA<\/a>
Fig. 6 RTA options available for the SAP Fiori app<\/figcaption><\/figure>\n\n\n\n

In the example above, we can use the Adapt IU mode to add or remove new fields without looking into the code.<\/p>\n\n\n\n

If none of the aforementioned solutions enable the necessary changes in the standard Fiori app, we still have one of the two more advanced methods \u2013 SAP WEB IDE for the front-end changes and ODATA service for the back-end changes.<\/p>\n\n\n\n

Fiori Enhancements using SAP WEB IDE<\/strong><\/h2>\n\n\n\n

To begin with, we should examine the documentation of the standard Fiori to find \u2018extension points\u2019 or \u2018hooks\u2019.<\/p>\n\n\n\n

\"Sekcja<\/a>
Fig. 7 The extensibility section of the \u2018Revise Payment Proposals\u2019 application\u2019s documentation<\/figcaption><\/figure>\n\n\n\n

If we decide to implement such changes, we can carry them out at the SAP WEB IDE level through view replacement.<\/p>\n\n\n\n

\"Widok<\/a>
Fig. 8 Extension selection screen for replacing the original view in SAP WEB IDE<\/figcaption><\/figure>\n\n\n\n

If we decide to replace the original view (for instance \u2018S3\u2019), it will create a new project with an \u2018Extension\u2019 ending, containing the copy of the standard view.<\/p>\n\n\n\n

\"List<\/a>
Fig. 9 List of files of the extension version of the app<\/figcaption><\/figure>\n\n\n\n

In the new project, within the \u2018manifest.json\u2019 file, a new fragment of code will appear, linking the old version of the app with the new version.<\/p>\n\n\n\n

\"Code<\/a>
Fig. 10 Code fragment inside the \u2018manifest.json\u2019 file in the extended app<\/figcaption><\/figure>\n\n\n\n

If we decide to delete this enhancement in the future, all we need to do is delete this code fragment and the app will revert to its original state.<\/p>\n\n\n\n

With the help of SAP WEB IDE we can also modify the translations of texts, including the newly created field. During the extension selection, there is an \u2018i18n Resource Text Customization\u2019 option.<\/p>\n\n\n\n

\"Extension<\/a>
Fig. 11 Extension selection screen for making changes in the \u2018i18n\u2019 file<\/figcaption><\/figure>\n\n\n\n

If we choose this option, the \u2018i18n\u2019 file from the standard version of the app will be copied to the app with the extension:<\/p>\n\n\n\n

\"A<\/a>
Fig. 12 A list of files with text translations within the SAP WEB IDE app<\/figcaption><\/figure>\n\n\n\n

In this file, we can add additional field for the newly added column.<\/p>\n\n\n\n

\"Code<\/a>
Fig. 13 Code fragment from \u2018i18n\u2019 file responsible for the text translation of newly added field<\/figcaption><\/figure>\n\n\n\n

After making those changes, remember to make a demployment (\u2018deploy as new app\u2019). This will ensure that the modified application will be displayed as a new BSP application.<\/p>\n\n\n\n

\"BSP<\/a>
Fig. 14 BSP application view after locating it in the SAP system<\/figcaption><\/figure>\n\n\n\n

To run the enhanced application, we also have to configure the tile and target mapping in the Fiori catalogue.<\/p>\n\n\n\n

\"A<\/a>
Fig. 15 A screen showing tile configuration in SAP Fiori Launchpad<\/figcaption><\/figure>\n\n\n\n

We should also remember that the name in the semantic object field must be different from the standard app:<\/p>\n\n\n\n

\"Miejce<\/a>
Fig. 16 The place of semantic object\u2019s configuration in the enhanced version of the app<\/figcaption><\/figure>\n\n\n\n

For the target mapping, the URL address contains the name of the new BSP application (which can also be found using the SICF transaction), and the component name can be found in the \u2018Component.js\u2019 file of the enhanced project:<\/p>\n\n\n\n

\"Fragment<\/a>
Fig. 17 Code fragment from the \u2018Component.js\u2019 file pointing to the name of the enhanced application<\/figcaption><\/figure>\n\n\n\n

To test the enhanced application, we should naturally remember about to launch the proper tile with the new app (not the original).<\/p>\n\n\n\n

Enhancing standard ODATA services<\/strong><\/h2>\n\n\n\n

According to Sebastian Gaer\u2019s methodology, adding a new field in the ODATA service consists of three steps:<\/p>\n\n\n\n

    \n
  1. First, we extend the appropriate ABAP Data Dictionary (DDIC) structure using the command APPEND STRUCTURE.<\/li>\n\n\n\n
  2. Secondly, we extend the ODATA entity in the Gateway Model Provider.<\/li>\n\n\n\n
  3. Finally, we populate the data of the newly added field in the Gateway Data Provider.<\/li>\n<\/ol>\n\n\n\n

    In the \u2018Revise Payment Proposals\u2019 application, there is an option to add custom fields:<\/p>\n\n\n\n

    \"Fragment<\/a>
    Fig. 18 \u2018Revise Payment Proposals\u2019 app\u2019s documentation fragment describing customer fields<\/figcaption><\/figure>\n\n\n\n

    First we create and activate the new field in the ABAP dictionary \u2013 ZZSGTXT.<\/p>\n\n\n\n

    \"Okienko
    Fig. 19 Selection screen of data element in the SAP system<\/figcaption><\/figure>\n\n\n\n

    Then, we add the new field to the standard application\u2019s structure:<\/p>\n\n\n\n

    \"Widok<\/a>
    Fig. 20 View of the structure pointing to the newly added field<\/figcaption><\/figure>\n\n\n\n

    In the second step, the package \u2018ODATA_REVISE_PAYMENT_PROPOSAL\u2019 contains both the Model Provider class and the Data Provider class for the specified ODATA service.<\/p>\n\n\n\n

    \"Widok<\/a>
    Fig. 21 Screen of the available classes in the \u2018Revise Payment Proposal\u2019 app<\/figcaption><\/figure>\n\n\n\n

    In the next step, we add a new field for the \u2018PaytProposalInvoice\u2019 entity.<\/p>\n\n\n\n

    \"Screen<\/a>
    Fig. 22 Screen of the available entity sets in the app<\/figcaption><\/figure>\n\n\n\n
    \"Screen
    Fig. 23 Screen of the newly added property for the given Entity Set \u2018PaytProposalInvoice\u2019<\/figcaption><\/figure>\n\n\n\n

    Re-generate the runtime objects by clicking the following button:<\/p>\n\n\n\n

    \"Fragment<\/a>
    Fig. 24 SEGW button for regenerating the ODATA service<\/figcaption><\/figure>\n\n\n\n

    As a result, a few new lines of code appear in the MPC class named CL_FAP_REVISE_PAYMENT.<\/p>\n\n\n\n

    \"Fig.<\/a>
    Fig. 25 Code fragment from the method \u2018DEFINE_PAYTPROSOALINVOICE\u2019 displaying new property<\/figcaption><\/figure>\n\n\n\n

    Then, if we want to populate the new field with data, we need to locate the method: CL_FAP_REVISE_PAYMENT_DPC_EXT->PAYTPROPOSALINVO_GET_ENTITYSET.<\/p>\n\n\n\n

    This method is already redefined and has an enhancement at the end, where we can add the code to retrieve data from the field BSEG-SGTXT and pass it to \u2018et_entityset\u2019 table (which holds the data for the entire entity set).<\/p>\n\n\n\n

    Finally, we should also remember to add a new column in the front-end view so that the data from newly created field displays correctly.<\/p>\n\n\n\n

    \"Fragment<\/a>
    Fig. 26 Code fragment from the view presenting newly added column to the table with enhanced field<\/figcaption><\/figure>\n\n\n
    \n \n \n \"\"\n <\/picture>\n
    \n
    \n

    Sii x SAP<\/h2>\n <\/div>\n

    \n As an SAP Silver Partner, we have many years of experience in implementing ERP solutions in companies of various scales and process complexities.\n <\/p>\n \n SAP offering<\/span>\n <\/a>\n <\/div>\n<\/div>\n\n\n\n

    Summary<\/strong><\/h2>\n\n\n\n

    The ODATA service can also be enhanced with BAdI (Business add-ins). However, these add-ins are not available for all of the standard SAP FIORI applications. Fiori views can also be created at the back-end level with help of \u2018CDS Views\u2019. Modifying them involves using SAP annotations on both the front and back-end levels, but this will be discussed in more detail in the next article.<\/p>\n\n\n\n

    In summary, there are numerous ways to enhance standard Fiori apps and they are limited by the options which were given by the SAP company. In the worst-case scenario, it is possible to enhance the entire application and rewrite the pieces that need improvement.<\/p>\n\n\n\n

    ***<\/p>\n\n\n\n

    If you are interested in SAP topics, also take a look at other articles by our experts<\/a>. <\/p>\n\n\n

    \n \n
    \n \n
    \n
    \n \n\n
    <\/div>\n <\/div>\n
    \n \n\n
    <\/div>\n <\/div>\n
    \n \n\n
    <\/div>\n <\/div>\n
    \n \n\n
    <\/div>\n <\/div>\n
    \n \n\n
    <\/div>\n <\/div>\n <\/div>\n \n
    \n
    \n \n\n
    <\/div>\n <\/div>\n
    \n \n\n
    <\/div>\n <\/div>\n
    \n \n\n
    <\/div>\n <\/div>\n
    \n \n\n
    <\/div>\n <\/div>\n
    \n \n\n
    <\/div>\n <\/div>\n <\/div>\n<\/div>\n \n\n
    \n 4\/5 <\/div>\n <\/div>\n","protected":false},"excerpt":{"rendered":"

    Standard SAP Fiori apps are a portfolio of applications where we receive a set of basic functionalities from the start. … Continued<\/a><\/p>\n","protected":false},"author":555,"featured_media":23705,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_editorskit_title_hidden":false,"_editorskit_reading_time":0,"_editorskit_is_block_options_detached":false,"_editorskit_block_options_position":"{}","inline_featured_image":false,"footnotes":""},"categories":[1319],"tags":[1775,1776,1683,1499],"class_list":["post-23712","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-soft-development","tag-aplikacja-en","tag-sap-fiori-en","tag-applications","tag-sap-en"],"acf":[],"aioseo_notices":[],"republish_history":[],"featured_media_url":"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2023\/08\/Rozszerzenia-standard-Fiori-Apps.jpg","category_names":["Soft development"],"_links":{"self":[{"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/posts\/23712"}],"collection":[{"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/users\/555"}],"replies":[{"embeddable":true,"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/comments?post=23712"}],"version-history":[{"count":3,"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/posts\/23712\/revisions"}],"predecessor-version":[{"id":33810,"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/posts\/23712\/revisions\/33810"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/media\/23705"}],"wp:attachment":[{"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/media?parent=23712"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/categories?post=23712"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sii.pl\/blog\/en\/wp-json\/wp\/v2\/tags?post=23712"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}