Transaction Apps are only apps that don’t have to run on Hana system. They can run on any Database. All factsheets, Analytical apps and Small Business Apps run on SAP Hana. Only Fact sheet requires Search Models. Only Analytical Apps requires Hana XS Engine and KPI Framework is needed for Smarts Business Apps.
Posted Date:- 2021-11-05 07:20:22
Configure access to KPI data (SAP Smart Business only) includes – enables user access to KPI data, KPI modeler, Configure navigation targets for KPI’s.
Posted Date:- 2021-11-05 07:18:24
By implementing SAP Single Sign-On, your apps become automatically available after just one initial user authentication at the user’s Windows desktop, with no need for further log-on procedures.
Kerberos technology is the method of choice in intranet scenarios for SSO. It simply re-uses your Windows domain authentication for single sign-on.
X.509 certificates provide a viable option for creating a secure SSO infrastructure if you’re considering extending single sign-on to extranet or cross-company scenarios.
Posted Date:- 2021-11-05 07:11:01
The important skill sets for the SAP Fiori application are around SAPUI5 (JavaScript), OData and some awareness of the web development. Other skills, which are helpful to aware, are JavaScript, HTML5, CSS and general web development.
Posted Date:- 2021-11-05 07:07:37
For Analytical apps you need SAP Hana as underlying database, no exceptions. SAP Fiori leverages.
XS engine by using virtual data models. Within XS engine there are 2 components: the HANA Live App content for respective business suite and Smart business component with the KPI modeler. Within the HANA live content the VDM reuse content exists which can be modified.
In below Pic, you have ABAP front end server which contains the UI Add-Ons for respective products used, NetWeaver Gateway with OData enablement, the central UI add-on and the KPI framework. These front end components have read access to the backend data via a trusted RFC connection.
Posted Date:- 2021-11-05 07:06:29
For fact sheets with integrated geographical maps, geographical coordinates and address data are transferred from the ABAP back-end server to the map provider using HTTP or HTTPS.
To ensure confidentiality and integrity of data, we strongly recommend protecting HTTP connections by using Transport Layer Security (TLS) or Secure Sockets Layer (SSL).
Posted Date:- 2021-11-05 07:05:26
If a Customization doesn’t run properly, all customization can be disabled by providing a single configuration. In support situation, this can be done by setting a breakpoint early in sap-ui-core.js and then executing the following code in the Console –
-window[“sap-ui-configâ€]= window[“sap-ui-configâ€]||{};
-window[“sap-ui-configâ€][“xx-disableCustomizingâ€] = true;
For security reason this setting is not possible using a URL parameter.
To dump the complete extensibility data, use the following command in the browser Console:
sap.ui.core.CustomizingConfiguration.log()
As a result, an object is returned in the Console which contains the customizing configuration, structured by type of customization and view name.
Posted Date:- 2021-11-05 07:04:41
The configuration is stored in the component.js file of the custom application. The component of the custom application needs to inherit from the main component of the original application. To make the location of the original application or component known to SAPUI5, it may be necessary to use register Module Path. The configuration in the customizing section contains the extension metadata and describes the objects that are replaced or extended.
Posted Date:- 2021-11-05 07:02:56
SAP Web Dispatcher (Reverse proxy) is entry point for HTTP(s) request in SAP Fiori Architecture. It can accept or reject connections as per user request.
Posted Date:- 2021-11-05 07:01:28
Transaction Apps are only apps that don’t have to run on Hana system. They can run on any Database. All factsheets, Analytical apps and Small Business Apps run on SAP Hana. Only Fact sheet requires Search Models. Only Analytical Apps requires Hana XS Engine and KPI Framework is needed for Smarts Business Apps.
Posted Date:- 2021-11-05 07:00:44
In Embedded Hub Deployment: NetWeaver gateway is deployed on same server as the Business Suite. So multiple Business Suite systems requires Gateway to be configured multiple times. It is not recommended by SAP especially for customers with multiple back ends.
No additional separate NetWeaver Gateway system is required. It is usually used for sandbox purposes only.
Posted Date:- 2021-11-05 06:59:51
Configure access to KPI data (SAP Smart Business only) includes – enables user access to KPI data, KPI modeler, Configure navigation targets for KPI’s.
Posted Date:- 2021-11-05 06:59:18
Configure ABAP Front-end server includes- Configure SAP NetWeaver Gateway, Configure the Central UI Add-On, Configure SAP Fiori Launchpad.
Posted Date:- 2021-11-05 06:58:19
By implementing SAP Single Sign-On, your apps become automatically available after just one initial user authentication at the users Windows desktop, with no need for further log-on procedures.
Kerberos technology is the method of choice in intranet scenarios for SSO. It simply re-uses your Windows domain authentication for single sign-on.
X.509 certificates provide a viable option for creating a secure SSO infrastructure if you’re considering extending single sign-on to extranet or cross-company scenarios.
Posted Date:- 2021-11-05 06:57:44
To configure Enterprise search in back end, we must have Embedded Search Technology setup.
Posted Date:- 2021-11-05 06:56:14
To define a trust relationship between SAP system and SAP NetWeaver gateway host by configuring SAP system to be trusting system and NetWeaver gateway host to be the trusted system. It enables remote logon for users who use the same user data in both SAP NetWeaver Gateway host and SAP system.
To configure SAP system as the trusting system:
* Create an RFC destination for use in the trust configuration.
* Define system to be trusting system using transaction SMT1.
* Configure the system to create and accept assertion tickets from SAP NetWeaver Gateway host using SSO2 wizard.
To configure SAP NetWeaver Gateway host as trusted system:
* Create an RFC destination for communicating with the trusting SAP system.
Posted Date:- 2021-11-05 06:55:45
Analytical apps and the SAP Smart Business apps share the setup of HANA XS engine and KPI Framework only (in Smart Business Apps). After setup of SAP Fiori System Landscape with SAP Hana XS engine we need to be following the KPI modeler on front-end server and respective SAP Smart Business Products on SAP Hana server.
Posted Date:- 2021-11-05 06:55:00
Step 1 Configure SAP Web Dispatcher:
Needs to be configured to specify routing rules stating which URL is forwarded to which request
Step 2
Configuring authentication and SSO needs to be done in the HANA database.
Step 3 configuring the front-end server:
* Configuring NetWeaver Gateway
* Central UI add-Ons
* Product specific add-Ons
Step 4 (Only needed for Smart business apps):
* Enable user access to KPI data
* Model KPIs
* Configure navigational targets for KPI catalogs
Posted Date:- 2021-11-05 06:54:07
Step 1 Configuring SAP Web Dispatcher specifies routing rules to define which URL is forwarded to which system is done for both Transactional Apps and Factsheets.
Step 2 only needs to be configured for Factsheets. If we just have to configure Transactional Apps we can skip
Step 3 is configuring the front-end server and this is done for both Transactional Apps and Factsheets.
At high level we need to configure:
* SAP NetWeaver Gateway
* The Central UI Add-Ons (Launchpad Configuration)
* Product Specific Add-Ons
Step 4 is configuring the back-end server and this is done for both Transactional Apps and Factsheets.
Viewing from a high level – Roles, Users and Authorizations.
Note: Transactional Apps can run on any DB whereas the Factsheets must run on SAP Hana.
Posted Date:- 2021-11-05 06:53:24
Configurations of SAP Fiori Apps are divided into two parts:
* Configuration of Transaction Apps and Fact sheets,
* Configuration of Analytical Apps.
Before configuring anything, the complete infrastructure for SAP Fiori apps must be installed. Once that is completed there will be activities to configure on back-end and front-end servers.
Posted Date:- 2021-11-05 06:51:47
The Launchpad administrator must have the PFCG role SAP_UI2_ADMIN assigned.
SAP_UI2_ADMIN is a composite role containing the following release-dependent roles −
SAP_UI2_ADMIN_700 for SAP NetWeaver 7.0
SAP_UI2_ADMIN_702 for SAP NetWeaver 7.0 enhancement package 2
SAP_UI2_ADMIN_731 for SAP NetWeaver 7.0 enhancement package 3 and SAP NetWeaver 7.3 enhancement package 1
Posted Date:- 2021-11-05 06:50:00
Three routing rules need to be defined in SAP NWG system −
* Default_host/sap/public
* Default_host/sap/bc
* Default_host/sap/opu
Two routing rules need to be defined in the HANA studio −
* Content/sap/hana
* Content/sap/hba
Posted Date:- 2021-11-05 06:49:20
A virtual data model (VDM) is a structured representation of HANA database views used in SAP HANA Live for SAP Business Suite and follows consistent modeling rules.
It provides direct access to SAP business data using standard SQL or OData requests. Business data is exposed through well-defined database views, operating directly on the tables of the SAP Business Suite systems and transforming them into consistent and easily understandable views.
VDMs allow you to access data in one component and use it in another without having to persist the data a second time.
A Virtual data model consists of the following types of views −
Query views are designed for direct consumption by an analytical application (based on HTML5, for instance) or a generic analytical tool (for example, BusinessObjects tools). They are always the top view in a hierarchy of views and are not designed for reuse in other views. However, the virtual data model also includes query views to support (showcase) applications based on the virtual data model.The interface of the query views is kept stable. The name of a query view ends with Query and provides output fields in a format consumable by UIs.
Reuse views are the hearts of the virtual data model. They expose the business data in a well-structured, consistent and comprehensible way, covering all relevant business data in SAP Business Suite systems. They are designed for reuse by other views and must not be consumed directly by analytical tools.
Private views encapsulate certain SQL transformations on one or several database tables or even other views. They are not classified as reuse views, as they might not carry clear business semantics, but are rather intended to be reused in other views. They are comparable to subroutines or (private) methods in programming languages. A private view may be based on database tables, other private views, or on reuse views.
Value help views (VHVs) provide the value list for a specific business entity that is used in a value help in a query view. Relevant business entities are specified by an identifier or code. A maximum of one VHV is defined for each business entity per package. A VHV is included either in an underlying package to the business query views that make use of it, or in the same package. In SAP HANA, for each main package a specific VHV exists for a specific business entity.
Posted Date:- 2021-11-05 06:48:40
For Analytical apps you need SAP Hana as underlying database, no exceptions. SAP Fiori leverages.
XS engine by using virtual data models. Within XS engine there are 2 components: the HANA Live App content for respective business suite and Smart business component with the KPI modeler. Within the HANA live content the VDM reuse content exists which can be modified.
In below Pic, you have ABAP front end server which contains the UI Add-Ons for respective products used, NetWeaver Gateway with OData enablement, the central UI add-on and the KPI framework. These front end components have read access to the backend data via a trusted RFC connection.
Posted Date:- 2021-11-05 06:48:17
For fact sheets with integrated geographical maps, geographical coordinates and address data are transferred from the ABAP back-end server to the map provider using HTTP or HTTPS.
To ensure confidentiality and integrity of data, we strongly recommend protecting HTTP connections by using Transport Layer Security (TLS) or Secure Sockets Layer (SSL).
Posted Date:- 2021-11-05 06:47:17
If a Customization doesn’t run properly, all customization can be disabled by providing a single configuration. In support situation, this can be done by setting a breakpoint early in sap-ui-core.js and then executing the following code in the Console −
-window[“sap-ui-configâ€]= window[“sap-ui-configâ€]||{};
-window[“sap-ui-configâ€][“xx-disableCustomizingâ€] = true;
For security reason this setting is not possible using a URL parameter.
To dump the complete extensibility data, use the following command in the browser Console −
sap.ui.core.CustomizingConfiguration.log()
As a result, an object is returned in the Console which contains the customizing configuration, structured by type of customization and view name.
Posted Date:- 2021-11-05 06:46:59
Fragments are pieces of a UI without their own controller. The name of each view of fragment is important. A fragment must be named as <NAME>.fragment.xml and a view <NAME>.view.xml
SAPUI5 Views − Views are nothing but the application pages. We define our user interface by creating Views. Views is formed or created by using one or more Controls in it say Page,SimpleForm,Dialog,Label,Input etc. Every view has its own controller.
SAPUI5 Fragments − Fragments are the pieces of UI just like SAPUI5 Views. Whenever we need to use some similar UI parts many times in our application/views we create Fragments of those UI parts because Fragments are reusable and are light weight compared to VIews and Controls. Fragments are stored with in the application itself and can be used by that application only. Fragments are defined as View only and calling Views controller is shared with Fragment as Fragments are not having their own controllers.
Posted Date:- 2021-11-05 06:46:40
Fragments are pieces of a UI without their own controller. The name of each view of fragment is important. A fragment must be named as <NAME>.fragment.xml and a view <NAME>.view.xml
SAPUI5 Views − Views are nothing but the application pages. We define our user interface by creating Views. Views is formed or created by using one or more Controls in it say Page,SimpleForm,Dialog,Label,Input etc. Every view has its own controller.
SAPUI5 Fragments − Fragments are the pieces of UI just like SAPUI5 Views. Whenever we need to use some similar UI parts many times in our application/views we create Fragments of those UI parts because Fragments are reusable and are light weight compared to VIews and Controls. Fragments are stored with in the application itself and can be used by that application only. Fragments are defined as View only and calling Views controller is shared with Fragment as Fragments are not having their own controllers.
Posted Date:- 2021-11-05 06:46:16
The configuration is stored in the component.js file of the custom application. The component of the custom application needs to inherit from the main component of the original application. To make the location of the original application or component known to SAPUI5, it may be necessary to use register Module Path. The configuration in the customizing section contains the extension metadata and describes the objects that are replaced or extended.
Posted Date:- 2021-11-05 06:45:51
IW_BEP on Business Suite
IW_FND on Gateway Layer
Posted Date:- 2021-11-05 06:45:27
Transaction code SE11 is ABAP dictionary. By using this transaction code, you can create, change and display table entries and structures. At the initial screen, you can put any tables or structures to view, edit or even create a new one. Transaction code SE11 is normally used a ABAP programmer.
SAP Gateway Service Builder (transaction SEGW)) is a design-time environment, which provides developers an easy-to-use set of tools for creating services. The Code-based OData Channel consumes it and supports developers throughout the development life cycle of a service.
SE80 - Object Navigator
SE 80 is a tool to develop and navigate programs and dd-obj.
SE80 Object Navigator → means all the objects will be available there. In se80 in addition to viewing the objects related to programming and classes, there are more privileges to view such as some other repositories such as mime, object repository, object browser and all.
Posted Date:- 2021-11-05 06:45:13
You can use transaction /UI5/THEME_TOOL to download newly created theme and you will find css in one of those folders.
You can also transport themes from one system to another (Eg: from Test to Production system) using the tool for Customer Themes Maintenance.
Start the tool using transaction: /UI5/THEME_TOOL
Navigate to the theme you want to transport.
Select Transport and choose.
Posted Date:- 2021-11-05 06:44:56
To be able to use the UI Theme Designer, Activate the following Internet Communication Framework (ICF) service nodes −
>> /sap/public/bc/themes
>> /sap/bc/theming
To be able to use SAP UI5 and NWBC preview pages, following ICF services must be activated −
>> /sap/bc/ui5_demokit
>> /sap/public/bc/ui2
Posted Date:- 2021-11-05 06:44:41
SAP Solution Manager is the standard platform for Application Lifecycle Management (ALM), and plays a decisive role within the ALM tools. Besides providing SAP functionality itself, SAP Solution Manager integrates the other tools to ensure a comprehensive approach
Posted Date:- 2021-11-05 06:43:25