OLE Example: OLE Processing
Point-in-Time Recovery
With simple job programming, you can start in clear environments with few dependencies. If the number of jobs and the complexity increases, an automatic job control is a good choice. Honico Batchman is such a solution, a 100% SAP integrated AddOn, which is quickly and easily installed via normal transports. The advantage here is that no additional infrastructure is required; instead, the existing SAP system landscape is used for the entire control and execution without incurring a loss in performance. This also ensures full audit and operational security (compliance). Since pure SAP systems are rather the exception, non-SAP systems can also be controlled and monitored. As a third option, high-end solutions are available that additionally monitor the infrastructure and legacy. Widely used products in this segment are UC4 and Arvato Streamworks. These three solution options differ significantly in terms of price and scope of services. IT departments in companies must therefore evaluate which solution is best suited to their own requirements.
Only one transaction code can be entered here, otherwise a single role would always be searched, which includes all transactions searched for and is assigned to the respective user. However, since the transactions can also be assigned to the user via different roles, this would not be useful. If you use the above Input variants are also only considered transactions that have been maintained in the role menu. If it is not certain whether the transaction was entered in the menu or in the S_TCODE privilege object of the role, up to four transactions can also be checked by searching through the S_TCODE permission object. Important is the attention and appropriate use of the AND/OR relationship. After the query is executed, the roles that contain the requested transaction and are associated with the user are now displayed. If you use the search through the S_TCODE permission object, the following result page appears. When looking at the result, in addition to limiting the number of transactions that can be entered, another drawback of this variant becomes apparent: Although both associated roles are displayed, at first glance it is not possible to see which transaction is contained in which role. To do this, the roles would have to be considered individually. If more transactions with user assignment are to be identified at the same time and the role assignment is to be seen directly, the use of the transaction SE16N is recommended.
WLF_IDOC IDoc Monitor
The presentation layer is based on the software components, collectively called "SAP GUI". This includes several possible implementation variants: for example, SAP GUI for HTML (Web GUI) and Web Dynpro for ABAP (WDA). Since the respective GUI depends entirely on the concrete application, the presentation layer looks very different in practice.
The website www.sap-corner.de offers many useful information about SAP basis.
With the function module SWNC_COLLECTOR_GET_AGGREGATES one can determine the most important SAP Basis transactions. After all, each SAP Basis expert sees different transactions as important.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
Especially during a migration HANA runs in a parallel system, therefore at least one new system comes to your landscape.
The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.
Here, the data is graphically prepared for the user on the end device by means of software components from the application programs of the application layer.