SAP BASIS AND DATABASE SERVICE
The 5 most common errors in SAP test management In this blog post I would like to discuss the 5 most common errors in SAP test management, which in my experience occur regularly in this area. I hope that with this I can give you some guidance so that you can avoid these mistakes. No test management Quite simple. You have complex SAP software in use or are just introducing a new module tailored to your company, but the test process plays a subordinate role and tests take place only sporadically and unstructured? Then you have already made the first mistake. To ensure high software quality, avoid hidden consequential error costs and consciously plan for a test period instead of the risk of time bottlenecks, a methodical approach should be planned. Too much testing If you have decided to introduce test management, you need to weigh up the resources required for this. A large amount of testing quickly pushes the cost-benefit ratio into the realm of inefficiency, because the time required for testing drives up costs. On the other hand, the test quality should of course be high. Therefore, a structured and comprehensive approach is of high importance. Basically, you should make sure that the costs for the test effort do not exceed the average of the consequential failure costs.
What do RFC interfaces and RFC security have to do with the play "Hauptmann von Köpenick" and the science fiction film "Minority Report"? Probably more than you like! RFC security and theatre?! Germany, Berlin, 1906: The 46-year-old cobbler Wilhelm Voigt dreams of returning to a normal life. After various convictions and many prison stays, he lives on the margins of society. It's not just the money he lacks. Above all, the lack of access to his social system makes him. In view of his impasse, he opts for a drastic measure. The excluded shoemaker pulls off and grates off several junk dealers to assemble a military uniform gradually. A few days later, he slips into the same disguise, successfully changes his identity and then swings through Berlin as Captain von Köpenick. He commandeers soldiers, storms the town hall and even detains the mayor. There is no doubt about the commands and their execution, because their true identity is veiled: Because of a simple disguise. A disguise that gives him all the necessary permissions he needs for his scam. At the end of the day, Wilhelm Voigt successfully compromised the Berlin government. RFC Security and Science Fiction?! USA, Washington, DC, 2054: The Washington police have long since stopped investigating murders: It prevents the killings right in advance. For this purpose, so-called "precogs" are used, which use precognition to predict and report murders in visions before they happen. At the same time, the government uses a system of public scanners that can identify all citizens clearly at any time by iris detection. One day, when policeman John Anderton himself appears as the culprit in a vision of the "Precogs," he flees the police building and decides to find out why.
The administration of SAP Basis
SAP Basis Administration Batch Control Job Control A large proportion of batch jobs run at night, while IT systems are available for dialog and online applications during the day. Meanwhile, web applications demand computer capacity around the clock. Even dialog systems are no longer in operation only from 8 a.m. to 6 p.m., but between 7 a.m. and 10 p.m. or longer. The time window for administration tasks is increasingly shifting toward transaction processing. This leaves less and less time for mission-critical batches, which can lead to disruptions and terminations. Whereas batch processing used to be a mainframe domain, companies today usually have to control background processing in heterogeneous operating system environments and client-server applications. For this reason, cross-platform, integration-capable job schedulers that can respond to unplanned events are in demand.
Parameters in the SAP create a high degree of flexibility. Profiles can be used to configure the system for almost any purpose. But with such a large number of parameters one quickly loses an overview of the influence of each parameter. For storage management alone, there are 20 different parameters that can be changed at different points in the SAP system. This article brings order to the mess and explains the most important parameters. There are three types of memory in the SAP system for a work process: ・ Roll Area - Local Memory Area for a Work Process ・ Extended Memory - Global Memory Area for All Work Processes ・ Private Storage /Dynamic Memory (Private Memory/Heap Memory) - Private Memory Overview of SAP System Memory Regions Parameters for the Rolling Range When a user starts a programme, a role area is created for that programme instance through a workprocess. The user context is stored in this memory area. The size of the roll area for a work process is determined by the ztta/roll_first parameter. If the storage area is not sufficient, a portion of the Advanced Memory will be allocated for the user context, the size of which will be determined by ztta/roll_extension, ztta/roll_extension_dia, and ztta/roll_extension_nondia. The latter two override ztta/roll_extension if used and offer the possibility to set different quotas for dialogue and non-dialogue work processes.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
It then explains how the task can be solved by using the transaction SE16N.
Together with you, we create a catalog of measures to ensure the optimal operation of your SAP landscape.