SAP Basis Active monitoring - SAP Stuff

Direkt zum Seiteninhalt
Active monitoring
IDOC IDoc and EDI Basis: Repair and Check Programs
After installing the GUI, the GUI patches should be applied as far as available. This includes the hotfixes after the patches, which are necessarily installed after the patches. BI Addon Patch A new service package and patch may need to be installed. It may also be that can be patched directly if another SP exists. The process takes about 30 minutes. The progress of the installation pauses at a certain percentage, as already mentioned above, so you do not have to cancel the installation prematurely. If the installation is not possible, the latest version will be included in another setup. Installation of the Precalculation Server The Precalculation Server is installed. You can also install any patches here. Service The installations create a service. This can be called under Services. Set the Startup Type of the service to "Automatic" (Standard Manual) Enter Login Credentials Recovery for First and Second Failure to "Restart the Service" Start Service Logon SAP Login to the SAP system with the appropriate client from the Precalculation Server. You can use the SAP system's own login. Warning: There must be permissions for the transaction RSPRECALCADMIN and SM51. The transaction SM51 will then be called. Before creating the instances, it must be ensured that the correct application server is selected, otherwise problems with the instances in the user's application may occur later. The transaction RSPRECALCADMIN is then called. A certain number of instances are displayed. They should all be marked and deleted until the view is empty again. They are then re-created with a continuous numbering in order to distinguish them later. Only the ID and description must be entered. The rest will be awarded automatically. The service will now restart and all instances should be green. This may take 2-3 minutes. Important: In the end, all instances must be green. This completes the creation and configuration.

The Log function displays logs for SPAM steps using the tp transport control programme. After successfully inserting the queue, you should always check these logs. Associating the SPAM steps with log files Step Log file DISASSEMBLE_PATCH Generate Cofile TEST_IMPORT Testimport IMPORT_OBJECT_LIST Commandfile Import DDIC-IMPORT DD-Import IMPORT_PROPER DD-Activation Import ADO-Import Verification Versions Method Execution ABAP/Dynpro Generation Procedure To get to the log display, select Image Jump Log Queue. Importance of Return Codes Return-Code Meaning 0 or 4 System information and warnings Warnings are generally uncritical for the system. However, you should check them anyway, as in rare cases follow-up errors may occur. Larger 4 Serious errors that must be fixed before you can successfully complete the commit. Confirm Queue Usage Confirm the successful insertion of the Queue in your system. This ensures that additional support packages can be used in the future. Without this confirmation, it is not possible to insert additional support packages. If you have not yet confirmed successful support packages, you will be prompted to confirm these support packages when upgrading your system. Prerequisites You have successfully imported one or more Support Packages. Procedure Confirm successful insertion of the Support Packages into your system with the Support Package.
You wanted to rush to release a transport order in the quality system of your SAP landscape and accidentally clicked on "Reject" instead of "Approve"? Now the order cannot be transported any further and will soon be cleared by job from the queue? Don't despair: In this blog post, I'm going to tell you a simple way to get rejected transportation to the production system anyway. As a reader of our blog, you are certainly interested in tricks and tricks that will make your SAP system easier to handle. You may be aware of the situation where you want to approve a transport order quickly after the test has been completed and you have clicked in the system when the order was released. The problem now is that the transport order in the system now has a status of "rejected" and can therefore no longer be transported. In total, a transport order may receive important changes that you would have liked to have transported to the production system. Approach to release rejected transport orders The screenshot below shows the situation in the STMS transaction where a transport order in the quality assurance area was rejected. Therefore, an import into the production system is no longer possible. The transport job can be removed either manually or through a job. The question here, however, is how the amendments which were wrongly rejected can be transferred to the subsequent system. Rejected Transport Order Tip: Leave the status on Rejected, remove the rejected transport order from the import queue, if necessary, and follow the next steps. Switch to the import queue in your quality system. Go there via Additions -> More Orders -> Attach to the modal window where you can perform further steps.

Regular maintenance tasks or the standard procedures must be described and defined to build checklists based on them and to control compliance with this standard. The SAPSolution-Manager can also support this as a tool of SAP e.g. through the Guided Procedures. In this context, it is also necessary to document the functionality of an underlying application and thereby determine what testing and monitoring activities are necessary. This is a reconciliation process between the SAP basis, other IT departments and, if necessary, the business areas concerned. The defined standard and the system's IST situation must be fully documented and regularly checked for compliance. This can be done through automated monitoring, validation using tools such as SAP-LVM (Landscape Virtualisation Management) or SAP Solution Manager, as well as manual checklists. Only the regular review of the standards guarantees their compliance. It can also support the regular use of SAP services such as Go-live Checks or Early Watch. Examples of how to standardise procedures are listed here: ・ Naming of system instances and logical hosts, or at least one central registry in a directory service, or LVM or SAP customer portal ・ Centrally starting and stopping systems, such as via the LVM ・ Categorising SAP instances by T-shirt size to define profile standards and cost them.

"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP basis.

In addition, this scenario is also possible for poorly maintained access control lists.

SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis:

Likewise, these can only be offered as simple and comprehensible product bundles if technical standards are established.
SAP Stuff
Zurück zum Seiteninhalt