Deleting versions
Context-dependent authorizations
If the security advice change affects normal programme flow, you should schedule application tests. If only exceptional treatments are adjusted, you can omit or severely limit the test.
The customising parameters in the table PRGN_CUST control the password generator in the transactions SU01 and SU10. The values of the profile parameters override the customising parameter entries to prevent invalid passwords from being generated. If the value of a customising parameter is less than the value of the corresponding profile parameter, the default value of the customising parameter is drawn instead. The same is true if no value is maintained. You can exclude certain words or special characters as passwords by entering them in the USR40 table. In this table you can enter both specific passwords (e.g. your company's name) and patterns for passwords (e.g. 1234*). '*' stands for any number of additional characters (wild card) and '?' for any character. However, when maintaining the USR40 table, note that the number and type of entries affect performance.
Create order through role-based permissions
Call the SIMGH transaction and create your own IMG structure, such as company name Customising. You will then add node outline to this tree. Often it makes sense to break down into SAP components such as finance, controlling and sales. Now add the tree as your favourite to make it easier to find it quickly. Then call the transaction S_IMG_EXTENSION and look for the IMG structure SAP Customising Introduction Guide. This is the default IMG structure in which you must include your structure. To expand, you must specify an extension ID. If there is no extension, you must create an extension ID. Position the cursor under My Favourites on the entry SAP Customising Intro Guide, and then click the Expand Structure button.
Once you have logged in, the permissions associated with your user (via the user account) will be available. Each of your actions leads to the use of runtime versions of the corresponding objects. This also applies to every privilege and role. Runtime versions of rolls are not transportable in SAP HANA. However, in order to achieve a high quality in the development of your applications, you should use a system landscape with development system (DEV), quality assurance system (QAS) and productive system (PRD). To enable you to translate development results to QAD and PRD, SAP HANA Studio provides you with the opportunity to create objects in a (freely definable) Design Time Repository that you can provide and transport via Delivery Units to other systems.
If you get into the situation that authorizations are required that were not considered in the role concept, "Shortcut for SAP systems" allows you to assign the complete authorization for the respective authorization object.
You can use the BAdI SMIME_EMAIL of the SMIME extension spot and implement the CERTIFICATE_RETRIEVAL and CERTIFICATE_SELECTION methods according to your requirements.
You can also find some useful tips from practice on the subject of SAP authorizations on the page www.sap-corner.de.
After rolling the profiles do not match your last changes? With the new features in the transport management of rolls, you can avoid such inconsistencies and connect role maintenance to the customising setting.