Migration to SAP HANA
Own development testing is very common in the quality system. Therefore, the customising/workbench developments must be transported to the appropriate system. It is highly recommended to use the order type "Transport of copies". This post explains why you should use this type of order and what you need to consider. Transporting copies - Why? All objects on the original transport order remain locked. Only the copies of the objects are transported to the next SAP system. If something goes wrong during transport, objects can easily be recollected or added. In addition, when copies are transported to the test system, no import is created in the production system. The import queue remains clean and clear. The problem with overtaking transports is eliminated. Transporting Copies - Creation To create a transport of copies, call the Transport Organiser through the transaction SE01. Check the Order Type "Transfers of Copies" and click View Create a new order (using the Document icon or F6 key). Then select the order type "Transport of copies". Then define a description and the destination system of the transport. Transport of copies - Add objects The transport order of the type "Transports of copies" was created. Now we want to add the objects of the original to be transported. Unfortunately, not all objects of an order can be copied directly. Therefore, it is important to take the objects task by task. A transport order can contain multiple tasks. Press CTRL+Y to highlight the task ID and then copy it by CTRL+C. Right-click on your order of the type "Transport of Copies" and select the Include objects option. Select the object list of an order and copy in the ID of the task that contains the objects to be transported. Confirm your input. All objects of the order are transferred to the transport of copies. You can then transport the objects to the test system using the normal transport procedure.
Especially after security incidents it may be necessary to find out which (technical) users have logged in at which time. The USR02 table provides a first entry point. In the TRDAT column you can find the last login date for the user you want. However, a history of previous applications is not found in this table. In such cases, the Security Auditlog or SAL helps. Preparation In order to access the desired data, it must also have been saved previously. In the Security Auditlog, you can use various filters to determine which users are logged on which client and which information. The Security Auditlog stores, depending on configuration, logins, RFC calls, and other actions for specific users. You can make these settings in the SM19 transaction. Note: Logging user activity must be aware of the users concerned! Configure the SAL only for technical users or in consultation with users / works council / etc. It can be seen there among other things when the SAL was activated and last edited (1). You can also select the various filters (2), activate the filters individually (3), specify clients and users (4) and specify which activities are logged (5). Static configuration in the SM19 Under the Dynamic Configuration you can also see if SAL is currently active for the system. Determine the status of the SAL Evaluation of the SAL If the Security Audit Log is active, switch to the SM20 evaluation of the Security Audit Log. Select the desired user and client and the appropriate time window. The option Dialogues login is sufficient for the login. Then, restart the AuditLog analysis. Start evaluation You will get an overview of the user's login to the selected client of the system.
SE38 ABAP Editor
Costs: 75% savings on subsequent corrections. Significant reduction in development and maintenance costs. ABAP code: 84% faster and more fail-safe programs. Improved performance reduces runtime and hardware utilization. Targeted corrections minimize system errors and downtime.
In the case of distributed or local SAP systems, it can also be helpful if departments or decentralized IT units can schedule their own jobs themselves. It is important that the associated approval processes can also be mapped and easily tracked. This brings convenience, flexibility and a degree of freedom without neglecting operational security. The integration of the business departments can relieve the IT administrator and turn background processing into an end-to-end process integrated into the organization.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
By being involved in projects in a timely manner, project success will be promoted and will contribute to company success in the medium and long term.
The goal of these conventional programs is usually to either crash the program (buffer overflow) or to artificially execute the program's own code (code injection).