Configuration & operation of the SAP Solution Manager
Troubleshooting and support in case of occurring problems
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.
You will need to download the support package again. CANNOT_DETERMINE_DATA_FILES: The name of a data file could not be determined because a profile parameter was not configured correctly. Verify the settings using the RSPARAM report. CANNOT_DISASSEMBLE_R_DATA_FILE: Unable to extract an R3trans data file. A possible cause of error is that the appropriate OCS file was not found or the data file could not be opened for writing. An error occurred while transferring a 20K block from the EPS inbox to the /usr/sap/trans/data (UNIX) directory. CANNOT_DISASSEMBLE_D_DATA_FILE: Unable to extract an ADO data file. The reasons are the same as for CANNOT_DISASSEMBLE_R_DATA_FILE. CANNOT_CREATE_COFILE: The cofile could not be created from the corresponding data file. One of the possible causes of error is that adm does not have write permissions for the /usr/sap/trans/cofiles (UNIX) directory.
Some useful tips about SAP basis can be found on www.sap-corner.de.
Provision resources in minutes instead of weeks
Cross-client tables can be modified. The control system of another, productive client can thus be undermined and undermined. Quite a lot of power! Did you also know that the SAP system provides a feature that deletes table change protocols (DBTA BLOG table) and that it is effective across all clients? If the table change logs have not been additionally archived via the BC_DBLOGS archiving object, traceability is no longer available. That way, every criminal act within your company can be beautifully covered up. Similarly, full access to batch management allows you to manage all background jobs in all clients with the permission. This allows you to delete old background jobs that have gone unauthorised. There are also some points to consider when managing print jobs. Typically, the following two SAP access permissions are enabled to protect print jobs: S_SPO_DEV (spooler device permissions) S_SPO_ACT (spooler actions). Why? Confidential information in print jobs is not protected against unauthorised disclosure. (Strictly) sensitive print jobs can be read unauthorised or redirected to external printers and printed out. Print jobs are unprotected unless additional SAP access permissions are enabled to protect print output. The print jobs are multi-tenant, which means that the authorisation award should also be well thought through at the point.
Depending on whether the user should edit or display the table, either "UPDATE" or "SHOW" can be used here. Enter an X as the value. It is important to use either"'SHOW" or "UPDATE" because a combination will cause an error when calling the parameter transaction. In addition, the table must set the view to be called. Use the "VIEW" field. Finally, the parameter transaction can be created using the "Save" button. As usual, it must be assigned to a package and a workbench order to become available. If a person's role is now assigned permission for this parameter transaction, it can open the specified view above it and does not have the ability to enter all possible views in the SM30.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
If not, view the detailed status and log information for all support packages in the system.
The freeware Scribble Papers is a "note box" in which all kinds of data can be stored. It takes in typed texts as well as graphics and entire documents. The data is then organised in folders and pages.
The transaction looks like a piece of the puzzle.