Database export / import
Advanced Memory Parameters
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.
In these cases, you will quickly get the problem under control with a manual user synchronization. This is because the user synchronization checks which roles are assigned to a user and then assigns the current, matching profile. You can run this user synchronization either manually or (my recommendation!) automatically as a background job:
Some useful tips about SAP basis can be found on www.sap-corner.de.
Decentralized, cross-site monitoring and alerting
Let me show you how EasyReCert can simplify this process. Automatic representation of employees & role assignment Each user of the application automatically receives the employees assigned to him. In the first step, the user verifies the assignment of the employees assigned to him. In the second step, the user is shown the roles of his employees. It is now possible to mark the assignment of the role as correct or incorrect. Understandable explanation of the roles Often roles have no talking names and for the decider it is not clear which specific permissions are behind a role. The tool offers the possibility to provide a description for each role, which is available by pop-in. Looking up which role has which permissions and which is meant for which is completely omitted. Flags & Criticality The tool offers in its options the possibility to set flags for critical roles and highlight them in particular. At a glance, the decision-makers see that one of their employees has a critical role and can examine it carefully. Since roles are classified differently in each company, you are completely free to decide which roles you want to consider critical. Roll Whitelist Do you want to exclude certain roles from the audit? Or do you want to test only critical roles? The tool offers you a whitelist function for this. This whitelist allows you to include roles that you do not want to check in the recertification process. So you completely decide which roles the tool should take into account. Logging of the results The results of the tests are logged via the application log and can be viewed both by SAP standard means and directly by the tool. It is also possible to export the audit logs or add optional comments to the logs later.
It should be mentioned here that it only makes sense to access the tables by reading the SELECT statement to get a quick view of the results. Using the DBACOCKPIT, it is not possible to create entire table structures using Create Table. For such applications, SAP provides other, better options. Another important point is that once a user has the necessary permissions to use the transaction DBACOCKPIT, it can potentially (with appropriate permissions on the tables) access the entire SAP system. For example, a query can be used to read the entire user table. Therefore, the transaction should always be treated with caution and only awarded to administrators. DBACOCKPIT handles the call control permissions similar to the SE16 / SE16N transaction. When the table is called, the S_TABU_DIS or S_TABU_NAM permission object is checked with a specific activity. This means that only the tables or table permission groups for which the corresponding values in the aforementioned permission objects are assigned can be accessed. You can read more about assigning permissions to individual tables here. In addition, you can save SQL statements that you run once, and run them again at any time to recognise changes in the result set without having to reformulate the SQL statement each time. The editor also allows you to start the query for SQL statements in the background. The result is obtained by calling the transaction SM37, in which the result is output in a spool file.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
QUEUE_NOT_EMPTY: There are incomplete OCS jobs in the tp buffer.
A note box in which data of all kinds can be quickly filed and retrieved. This is what Scribble Papers promises. At first, the program looks very spartan. But once a small structure is in place, you realise the great flexibility of this little helper.
This data exchange is known as Electronic Data Interchange (EDI).