SAP Basis SWF_APPL_DISPLAY Evaluate application log

Direkt zum Seiteninhalt
SWF_APPL_DISPLAY Evaluate application log
Our services
There are the following types of Support Packages: SPAM/SAINT Update A SPAM/SAINT update (PAT) contains updates and improvements to the SAP Patch Manager and the SAP Add-On Installation Tool. FCS Support Package An FCS Support Package (FFD) brings an FCS system to the generally available release level (GA level) before other support packages can be inserted. Component Support Package One such support package (COP) applies to one software component (SAP_BASIS, SAP_HR, SAP_APPL, etc) and contains corrections for errors in the repository and in the dictionary in exactly this software component. Support Packages for the component SAP_HR include adjustments due to legal changes in addition to these corrections. A BW Support Package (BWP) is a support package for the SAP Business Information Warehouse (SAP_BW) software component and contains corrections only. Add-On Support Package An Add-On Support Package (AOP) always applies to an add-on with a specific release and includes corrections for that add-on.

For the authorisation requirement of a user, the transactions with user assignment already awarded should be determined accordingly, in order to be able to exclude them when selecting a suitable role. How does this work? There are various ways to identify specific user-assigned transactions, with varying degrees of result. The following article presents two variants. The first section first describes how to use SUIM to address the problem and what problems are encountered. It then explains how the task can be solved by using the transaction SE16N. As in the previous blog post Identifying all transactions of multiple roles, the roles Test_Schmidt1 and Test_Schmidt2 are used for this. Two of the transactions MM01, MM02, MM03 and MM04 were assigned to these roles in different ways. In the Test_Schmidt1 role, the transactions MM01 and MM02 were entered in the Role menu. In the Test_Schmidt2 role, the transaction MM03 was maintained in the menu of the role, but the transaction MM04 was maintained only in the S_TCODE permission object of the role. Both roles have been assigned to the user SCHMIDT_TEST. Identification of certain transactions with user assignment using SUIM This option is useful if only one transaction is to be checked for its existing assignment to a particular user. The audit is carried out here by means of the transaction SUIM. For this purpose, the variant "Roles according to complex selection criteria" has to be executed in the SUIM. After activating the option "With valid assignment of", the corresponding user and the transaction to be checked will be entered here. It is also recommended to hide the display of the collection roles in the search results.
Interfaces
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 ....

INTRODUCTION A growing number of SAP-based departments are facing major changes and challenges within the SAP product portfolio as well as in their own task environment. These result from influences of digitalisation, digital transformation, new technologies such as cloud computing or big data, but also developments such as customer experience or the Internet of Things. In order to overcome the challenges and to transform the existing SAP basis, recommendations for action are grouped in seven thematic areas. These topics cover the areas of skills and roles (cloud and supplier management, strengthening of the technology architect, focus on project work), marketing and self-understanding (creation of a service catalogue, regular exchange with the CIO, renaming of the SAP basis), new technologies and innovation (test and innovation lab, proactive & regular training), organisation in change (development of the two subject areas close to structure and application-orientated , virtual teams of experts), standardisation and automation (automation of routine tasks, outtasking of rare tasks), "cloudability", outsourcing & outtasking (assessment of usefulness for the cloud, use of appropriate service forms) and IT roadmap (influence of own IT roadmap). By reflecting on the thematic areas, methods and possibilities for implementing the recommendations are presented.

With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.

If you would like to learn about the architecture of HANA, I recommend a contribution from our colleagues at erlebe Software.

Meanwhile, there are other ways to build consensus.
SAP Corner
Zurück zum Seiteninhalt