SAP Basis CG3Y File download - SAP Basis

Direkt zum Seiteninhalt
CG3Y File download
SM36 Define job
The result table USERTCODE contains the transaction codes of the SAP users. Afterwards you simply have to output the complete list via "Object > Output complete list". Then save the list via "System > List > Save > Local file". The column Account contains the SAP user. This way you can see the used transactions grouped by SAP user.

Of course, the SAP consultant remains in the foreground as a person and is the figurehead for our services. However, where it makes sense, they are supported by customized tools.
STMS Transport Management System
To view the software components installed in your SAP system with their respective package levels, select Status Package Levels. A dialogue box appears listing the installed software components with additional information. For more information on this dialogue, please refer to the Online Manual. SPAM: ABAP/Dynpro Generation Usage For performance reasons, the SPAM is set by default to prevent ABAP/Dynpro generation from occurring during the commit. The corresponding programmes are not generated until they are called. However, you can set the SPAM so that the generation takes place during the recording. It is quite possible that the SPAM will report errors during generation because, for example, a self-written or modified report is syntactically wrong and refers to an object that is being played over the cue. Often it is desirable to ignore the generation errors for the time being and to fix them after inserting them. Prerequisites to play Support Packages.

Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page you will find useful information on this topic.

The 5 most common errors in SAP test management In this blog post I would like to discuss the 5 most common errors in SAP test management, which in my experience occur regularly in this area. I hope that with this I can give you some guidance so that you can avoid these mistakes. No test management Quite simple. You have complex SAP software in use or are just introducing a new module tailored to your company, but the test process plays a subordinate role and tests take place only sporadically and unstructured? Then you have already made the first mistake. To ensure high software quality, avoid hidden consequential error costs and consciously plan for a test period instead of the risk of time bottlenecks, a methodical approach should be planned. Too much testing If you have decided to introduce test management, you need to weigh up the resources required for this. A large amount of testing quickly pushes the cost-benefit ratio into the realm of inefficiency, because the time required for testing drives up costs. On the other hand, the test quality should of course be high. Therefore, a structured and comprehensive approach is of high importance. Basically, you should make sure that the costs for the test effort do not exceed the average of the consequential failure costs.

Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.

When creating and clicking on Save the "CWBDS" object, a message may appear prompting you to select an object from the permitted namespace.

For example, it is possible to allow a user to run the programme "BSP" on the host "XYZ", but not on the host "ABC".

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
Zurück zum Seiteninhalt