SAP Basis SM35 Batch input: session overview

Direkt zum Seiteninhalt
SM35 Batch input: session overview
SP02 Output control: Overview of spool requests
Technical developments are progressing at high speed. Thus, the term "blockchain" is not unique to digital currencies. Instead, there is talk of a technology that will disrupt existing products, services, and even business models. In order to better assess the potential and impact of blockchain technology, various companies from different technologies and, in particular, financial sectors have joined forces in consortia in recent years: The R3 Consortium, which is primarily a consortium of about 80 financial sector companies (UBS, Credit Suisse, Deutsche Bank, Commerzbank, ...). The IoT Consortium, which includes Bosch Ltd, Cisco Systems Inc, is investigating how blockchain technology can be used to secure and improve IoT networks. More than 120 financial, banking, IoT and industrial companies have joined the Hyperledger (Enterprise Ethereum Alliance) consortium. Enterprise Ethereum Alliance with about 500 startups, companies and academic institutions from a wide range of fields. Read more in my next blog post ....

SAP Basis is responsible for the smooth operation of programs in the SAP system. It acts like an operating system for R/3 and subsequent releases including S/4HANA. Every operating system provides an environment in which programs can run, such as MS Office on Microsoft Windows. In the same way, the SAP Basis system with the NetWeaver and HANA platforms provides an environment in which SAP programs can run. In this context, the NetWeaver platform itself relies on server operating systems such as Windows and Linux.
SE37 Function Builder
SAP HANA base administrators can master the database in a way that wasn't possible back then. The SAP database is much more self-healing. Errors do less damage, are easier to detect and fix, and are less likely to impact system performance and availability before they are fixed. Monitoring tools can automatically scan the application logs, identify potential errors, and even suggest fixes, making it much easier to get to the root of the problem.

In order for Fiori applications to be displayed according to the calling users, appropriate Fiori permissions must be maintained in the PFCG. There are several points to consider. This article discusses the permissions required to launch a Fiori application. In addition, a short explanation is given, how the displayed tiles can be configured in the Fiori launchpad via reels. To run Fiori applications from the launchpad and the permission queries defined in the OData services, the corresponding Fiori permission objects must also be maintained in the PFCG. Here the start permissions for the application's OData service in the backend system as well as permission objects are relevant for the business logic of the OData services used in the application. In general, it is important to know that if Fiori is implemented correctly, permissions must be maintained in the front-end server (call Launchpad, start the tile, etc.) as well as permissions in the back-end server (call the OData services from the backend). This article explains this in more detail.

"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.

This must be evaluated and decided jointly.

Why? Confidential information in print jobs is not protected against unauthorised disclosure.
SAP Corner
Zurück zum Seiteninhalt