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:38:44
The Launchpad user must have the PFCG role SAP_UI2_USER_700 assigned. With this role the user can run the SAP Fiori Launchpad on the Personalization level and has authorization to execute the following OData services −
/UI2/PAGE_BUILDER_PERS
/UI2/INTEROP
/UI2/LAUNCHPAD
Posted Date:- 2021-11-05 06:37:35
Configuration Layer − Contains all content as delivered to customers including translation.
Customization Layer − Customers adjust content for all users in the system. We can use CUST layer for testing or other reasons. Content is transportable through customizing requests by customers. After customization, content is decoupled from configuration layer and no automatic synchronization after changes to delivered layer.
Posted Date:- 2021-11-05 06:36:40
Static − It shows predefined static content (text, icon).
Dynamic − It shows numbers that can be read dynamically.
News Tile − Flips through news messages according to the configuration of the tile.
KPI Tile − It displays KPI’s in real time.
Posted Date:- 2021-11-05 06:35:53
We need to perform certain configuration tasks on front end server which are specific to app type. We need to Activate OData Services for transactional apps and Factsheets but not for Analytical apps. For analytical apps we need to configure access to SAP HANA data.
Posted Date:- 2021-11-05 06:34:37
We can use SAP Fiori Launchpad designer for configuring and creating groups and catalogs which can then be accessed from SAP Fiori Lauchpad which is a single entry point to all apps. We can search recently launched apps via search capability of Launchpad. Tiles which are available on Fiori Launchpad home page are configured using Launchpad Designer Tool.
Posted Date:- 2021-11-05 06:33:24
You need to know the system alias of the ABAP system in which you developed and configured the Gateway Service. There are two possibilities here −
>> If the GW_CORE and IW_BEP components are installed on the same ABAP system, then the system alias will probably be “LOCALâ€.
>> If they are installed on different systems, then although system aliases can be any name you like, they generally follow the naming convention of <SID>_<Client> So the system alias for connecting to client 200 of system C11 would generally be C11_200.
However this is only a convention, not a rule.
Posted Date:- 2021-11-05 06:32:43
Authorization Object S_RFCACL
Definition
Authorization check for RFC users, particularly for trusted systems
Defined Fields
This authorization object contains the following fields −
RFC_SYSID − ID of the calling system or the domain of the satellite system.
RFC_CLIENT − Client of the calling system.
RFC_USER − ID of the calling user.
RFC_EQUSER − Flag that indicates whether the user can be called by a user with the same ID (Y = Yes, N = No)
RFC_TCODE − Calling transaction code.
RFC_INFO − Additional information from the calling system (currently inactive).
ACTVT − Activity
Posted Date:- 2021-11-05 06:30:57
In order to expose our Gateway service to outside world, we must create an entry in the Service Catalogue on which ever server is acting as the Gateway hub.
Posted Date:- 2021-11-05 06:30:13
Sequence of steps −
LPD_CUST
Launchpad Designer – Add a catalog, add a group
Target mapping – semantic object, action
Static/Dynamic Launcher
PFCG – Catalog, group
Posted Date:- 2021-11-05 06:29:33
Workflow scenario aggregates one or more workflow tasks in workflow engine and is represented by a single entry in the consumer application. The service /IWPGW/TASKPROOCESSING is provided in the standard.
Posted Date:- 2021-11-05 06:28:29
SWI2_DIAG → to diagnose workflow errors.
Posted Date:- 2021-11-05 06:27:44
Embedded hub Deployment — Development in SAP Business Suite Backend System
Advantages
Easy reuse of content in SAP Business Suite backend system. We can reuse structures from the backend system and access local business logic.
Reduced total cost of ownership (TCO) as we do not require a separate SAP NetWeaver Gateway system.
Considerations
The life cycle of SAP NetWeaver Gateway content is dictated by the frequency of updates in the SAP Business Suite backend system.
We must integrate the consuming application or infrastructure with the SAP Business Suite system on a point-by-point basis. Cross-system composition is not advisable.
Central SAP NetWeaver Gateway content is not available. Backend-specific content is used in the SAP Business Suite backend system.
Cons
If multiple SAP Business Suite systems are used Gateway would have to be configured multiple times.
Posted Date:- 2021-11-05 06:25:48
OData is a protocol used to exchange data on web and was originally developed by Microsoft.It is based on Atom Publishing and Atom Syndication standards, which in turn, are based on XML and HTTPS(S).
The Atom publishing format doesn’t specify how Data should be encoded with in a feed therefore it fails to provide self-describing messages and fails to be fully RESTful. OData extends Atom by providing a metadata description of message.
OData provides definition for −
* Simple types
* Complex Types
* Association as well as Navigation path between entries.
* Custom behavior
* OData also adds an alternative representation of data in the format of JSON.
Posted Date:- 2021-11-05 06:24:07
UI5 data binding supports three different model implementations −
JSON Model supports data in a JavaScript Object Notation format and It supports two-way binding.
XML model supports XML data and it supports two-way binding.
OData model supports OData compliant data. It creates OData requests and handles responses. It includes the open source library dataJS to handle OData requests and data. It supports two-way experimental binding.
Posted Date:- 2021-11-05 06:23:09
The Model-view-controller pattern defines domain modeling, GUI of application and input and actions based on devices. MVC approach defines in SAP UI5 has following points −
Model
A bridge between view and data of the apps and it accepts the request from view and responds accordingly. It doesn’t depend on any of classes.
View
It manages the display of information (GUI of the application) and it depends on Model.
Controller
It concludes the input given by devices and communicates to model/view to take proper action. It also depends on model. View and Controller have 1:1 relationship. Controller entertains user requests received from View.
Posted Date:- 2021-11-05 06:22:04
SAP Hana XS engine contains 2 components-Hana Live App Content and SMART Business components with KPI modeler. Within Hana Live App Content VDM reuse content exist.
Posted Date:- 2021-11-05 06:21:23
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 06:19:06
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 06:18:32
Trusted RFC provides data from backend Business suite to the apps. SAP Business suite is present in ABAP back-end server with all its modules- ERP, CRM, SRM, SCM. Fiori Apps are available in ABAP frontend server in Fiori Launchpad.
Posted Date:- 2021-11-05 06:17:34
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:17:01
In NetWeaver Gateway Central Hub deployment − UI layer and SAP NetWeaver gateway is contained in ABAP Front-end server. The ABAP back end server contains business logic and back end data. Separating business logic and back end data from UI layer has below advantages −
* Single Point of maintenance for UI issues- such as browser support and updated version of SAP UI5 libraries.
* Central place for theming and branding SAP Fiori Apps.
* Routing and composition of multiple backend systems is supported.
* Single Point of access to backend systems and enhanced security because of no direct access to backend system.
* SAP recommends Central Hub deployment especially for Productive environment. Separate NetWeaver Gateway system is required.
Posted Date:- 2021-11-05 06:16:12
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:14:01
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:11:55
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:10:31
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:09:52
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:09:25
To configure Enterprise search in back end, we must have Embedded Search Technology setup.
Posted Date:- 2021-11-05 06:08:45
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:05:46
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:04:34
Following are some of the service metadata annotations which are common and a front end developer must know these in order to understand the service and integrate it:
-edm:EntityContainer
-edm:EntitySet
-edm:EntityType
-edm:Property
-edm:NavigationProperty
-edm:AssociationSet
Posted Date:- 2021-11-05 06:03:18
The service metadata document describes the structure of all resources in the service. This structural metadata makes it easy to understand a service. We can explore service metadata at the address “$metadata†relative to the service root.
Posted Date:- 2021-11-05 06:02:27
SAPUI5 Bootstrapping means loading and initializing SAPUI5 in any HTML page. The most important library or resource loaded in SAPUI5 bootstrap is “sap-ui- core.jsâ€. Apart from this theme for the application, SAPUI5 libraries etc are declared in the bootstrapping.
Posted Date:- 2021-11-05 06:02:00
We can bind data to any controls using three methods, Property, Element and Aggregation binding.
Posted Date:- 2021-11-05 06:01:38
Fragments are created without controllers, they don’t have their own controllers they share controller of the view which is invoking it.
Posted Date:- 2021-11-05 06:01:15
Fragments are very light weight UI controls and part of another UI. Fragments are not completely like views but they act like a view. Fragments are defined similar like views and are names like “myFragment.fragment.xml“.
Posted Date:- 2021-11-05 06:00:37
The JSON model is a client-side model and, therefore, intended for small datasets, which are completely available on the client. The OData model is a server-side model: the dataset is only available on the server and the client only knows the currently visible rows and fields.
Posted Date:- 2021-11-05 06:00:08
There 4 four Lifecycle methods available in every SAPUI5 views controller. These are onInit(), onExit(), onAfterRendering(), onBeforeRendering().
onInit is called when a view is instantiated and its controls (if available) have already been created;
onExit is called when the view is destroyed; used to free resources and finalize activities;
onAfterRendering when the view has been rendered and, therefore, its HTML is part of the document;
onBeforeRendering is called before the controller view is re-rendered and not before the first rendering.
Posted Date:- 2021-11-05 05:59:11
Following are the predefined three types of view available in SAPUI5:
* JSON view
* JavaScript View(JS View)
* HTML View
Posted Date:- 2021-11-05 05:58:40
As SAPUI5 follows MVC(Model-View- Controller) there model plays crucial role in the framwork.
SAPUI5 has following predefined four data models available:
* JSON Model – Client-side model, supports two way binding.
* XML Model – Client-side model and intended for small data sets this is very rarely used model.
* Resource Model – This is also client side model used to maintain resource bundles, specially texts.
* ODATA Model – This is most important model of the four provided. This is server side model, supports two way binding ODATA model currently supports ODATA version 2.0.
Posted Date:- 2021-11-05 05:58:09
SAP recommends following application design patterns keeping in mind design consistency of the applications:
* Master – Detail
* Master-Master- Detail
* Full Screen
* Full Screen-Full Screen-MasterDetail (Multi Flow)
Posted Date:- 2021-11-05 05:57:21
We need to use formatter when we need to perform some changes on the back end property data on the front end.
we can use formatter while data binding to a property like as follows:
oControl = new sap.ui.commons.TextField({
value : {path : “/pathâ€, formatter : function(oEvent){
return “Value:â€+oEvent;
}}});
Posted Date:- 2021-11-05 05:56:52
Component or Component.js is the first point of our application or we can say that it serves as index which encapsulates all our applications details i.e. view names, routing details, main view, applications type(Full Screen or SplitApp), application service configuration etc..
Posted Date:- 2021-11-05 05:56:37
SAPUI5 uses two mechanism for navigation in applications those are EventBus and Routing where latter supersedes since SAPUI5 1.16. sap.ui.core.routing is the class used for the routing. We define routing in components metadata in “routing†key.
Posted Date:- 2021-11-05 05:56:03
There are 5 design principles we need to keep in mind while designing SAP Fiori applications. Role-Based, Delightful, Simple, Responsive, and Coherent.
Posted Date:- 2021-11-05 05:54:30
SAPUI5 library provides a special API “sap.ui.Device“which can be used for the device and its feature detection. This API provides flags like “chromeâ€, “firefoxâ€, “mozillaâ€, “edge†etc. in “sap.ui.Device.browser†API which returns boolean values.
Posted Date:- 2021-11-05 05:54:05
SAPUI5 library provides a special API “sap.ui.Device“which can be used for the device and its feature detection. This API has a flag “sap.ui.Device.touch†which returns true if device is a touch screen otherwise false.
Posted Date:- 2021-11-05 05:51:15
As we know there are more than 500 FIORI applications, SAP has provided a Shell or single point place from where we can access all the applications. This serves as a home page for all the FIORI applications provided. This shows a tile-based UI where every UI redirects to the assigned FIORI application. This Launchpad is fully customizable according to your needs like theming and all.
Posted Date:- 2021-11-05 05:50:57
SAP FIORI is a collection of standard applications based on the SAPUI5 library provided by SAP. SAP FIORI applications share some standard design guidelines and the way in which these applications are developed. Currently, more than 500 FIORI applications are available freely.
Posted Date:- 2021-11-05 05:50:32
SAPUI5 is a client-side HTML5 rendering framework or library and SAP FIORI is a collection of and released as waves of applications that are completely based on the SAPUI5 framework. It means we can create applications using the SAPUI5 framework and SAP FIORI is the final product i.e. application.
Posted Date:- 2021-11-05 05:50:14