How to lock (SU01) and unlock (SU10) an SAP user
Installing, maintaining and servicing other software that is not an SAP system but also provides important functions such as SAP Router, SAP Cloud Connector, TREX, SAP ETD and many more
The Advanced Memory thus contains mainly user contexts of different work processes, if these cannot be loaded completely into the roll area. Since the storage area is accessible for all work processes, the work processes can also access external user contexts that lie here. In addition, the Advanced Memory contains a global area where data can be stored independently of user contexts. The extended memory size is determined by the values of em/initial_size_MB and em/global_area_MB. The first parameter determines the size of the storage area in which user contexts can be stored, and the second determines the size of the global area. Parameters for Private Storage Last but not least, there is the private storage, which is only used when the user context of a work process has used up all the other storage areas available to it, i.e. its share of the extended memory and its rolling area. In this case, the workprocess goes into PRIV mode. A workprocess in private mode is bound to its current user context and will not become free for other tasks until the current request is completed. If it has used up all the private memory allocated to it, the workprocess will then be restarted and the memory released. This behaviour is controlled with the abap/heaplimit parameter. At times, the user context may exceed the value of abap/heaplimit. The parameters abap/heap_area_total, abap/heap_area_dia and abap/heap_area_nondia define an upper limit for private storage. The abap/heap_area_total parameter defines how much private storage all workprocesses can use in total. The parameters abap/heap_area_dia and abap/heap_area_nondia, on the other hand, determine how much private storage a single (non-)dialogue workprocess can use.
In order to explain the relationship between TREX and SAP Solution Manager, I would like to ask you a question first. Can you remember when you last used the search help (F4) in SAP, what you were looking for and above all what the search string looked like? Now, the entitlement admin might have looked like this. Any role for a new key-user in the HCM area, but how exactly was that called? Would you Google the same way? - Not much. The Enterprise Search in Solution Manager 7.2 In the SAP Solution Manager, the SAP Enterprise Search provides a comprehensive full-text search. With only one keyword, you can search centrally for all types of documents in the ITSM and ChaRM, such as incidents or changes, via the Fiori Launchpad. If you have added attachments, they will also be searched for the keyword. At a technical level, a special BOL query object is passed to the Enterprise Search, which passes the HANA database and performs a search. What if you don't use the Solution Manager on SAP HANA? Enterprise Search with TREX 7.1 SAP offers the possibility to use Solution Manager 7.2 on another database (AnyDB), for example DB2 or Oracle. In order to use Enterprise Search (also embedded search) in this case, you need the TREX admin tool. This stands for Text Receival and Information Extraction, which basically describes the functionality of the software. The TREXEngine takes the search text in the form of the Query object and provides an intelligent search of keywords and long texts in previously classified documents. Installation and Usage Tips Run the TREX configuration after the basic configuration of the Solution Manager. In SOLMAN_SETUP you will find the Embedded Search scenario, which is the guide for the configuration. In the Process Management scenario, configure the embedded search using the description. Here the object connectors are created and the indexing jobs are started. Both are required to use the solution documentation in conjunction with other components. If you are installing UNIX, make sure that the shared libraries are up-to-date or that they are initially available.
OAC2 Change document types
Within this step, a pricing strategy is chosen. The strategy chosen must be based on the value for money. The selection shall also be justified. The price of the service will continue to be determined, as will formal decisions on clearing models and discounts. This step is less important for the SAP basis. While it is necessary to set a price for the IT products to be defined in terms of appreciation and offsetting, it does not require an elaborate pricing system. STEP 8: MARKET COMMUNICATION The step of market communication describes the way in which the respective service is advertised and how it is to be communicated with customers in this regard. It's about the communication tools that are planned, which describe the place of communication, the communication tools that describe what to advertise, and the content. These are usually derived from the target group to be applied for. For the SAP basis, the content is an essential feature of the market communication. That is, depending on the target group, information must be created and communicated. STEP 9: INTERNAL COMMUNICATION Internal communication describes how the above-mentioned aspects can also be successfully communicated internally, i.e. in the direction of one's employees.
SAP HANA base administrators can master the database in a way that wasn't possible back then. The SAP database is much more self-healing. Errors do less damage, are easier to detect and fix, and are less likely to impact system performance and availability before they are fixed. Monitoring tools can automatically scan application logs, identify potential errors and even suggest fixes, making it much easier to get to the root of the problem.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
IMPORT_OBJECT_LIST In this step, the object lists for the support packages in the queue are fed into the system.
Encryption of the data of a HANA system is disabled by default.