Using transaction RZ11 (Maintain Profile Parameters)
Using the ABAP Config Tool
Using transaction RZ10 (Edit Profiles)
Using transaction RZ03 (CCMS Control Panel) 2.
Transaction RZ10 (Edit Profiles)
The Config Tool
The SDM remote GUI
The UME administration console
SAP Business One
Yes – changing the respective database entry by using the Config Tool is recommended.
Yes – changing the secure store content by using the Config Tool is recommended.
No – changing the administrator’s password is sufficient.
Yes – changing the secure store content by using the command line „icmon -a“ is recommended.
Only Update work processes can update table content.
Table content has to be updated via „Asynchronous Update“
Dialog and background processes can update table content.
„Update (UPD)“ and „Update 2 (UP2)“ work processes can update table content.
You can set the minimum password length.
You can set an expiration time for passwords.
You can generally deactivate authorization checks in the complete SAP system (for example, in Sandbox systems)
You can enable an emergency „master user“, named „SAP_ALL“.
ICF services replace the remote function call (RFC).
Business Server Pages (BSP) are accessed via ICF.
ICF services can only be created by SAP. It is not possible for customers to create new ICF services.
ICF services provide HTTP-based access to selected functions within AS ABAP.
One or more authorization profiles can be assigned to a user master record.
One or more roles can be assigned to a user master record.
A single authorization value can be assigned to a user master record.
An authorization object can be assigned to a user master record.
Operation mode is switched to „night“
Missing user authorization
The network connection to the SAP system is broken
Mistyped user name
Full authorization is not allowed in this area.
Maintenance of authorizations for the corresponding area has not yet been completed. Additional work is needed.
You have full authorization for this area.
You do not have the necessary authorizations to maintain the objects underneath the yellow symbol.
My SAP SCM
Database lock that lasts too long can cause a sap system standstill.
After an SAP enqueue has been placed, the corresponding database table can still be changed by an update request coming from programs such as customer developed ABAP reports.
A database lock usually released at the end of transaction step, while an SAP enqueue is usually released at the end of an SAP transaction.
Many App servers and one database server
One app server and one database server
No app server and one database server
One app server and many database servers
You can change the font size (within limits) in the SAP GUI
You can have system messages displayed in a dialog box
You can change the size of input fields
You can suppress the display of pictures in the SAP GUI
Every user can display a picture of his or her choice on the SAP Easy Access screen
You can use a personal input history on your front end
An SAP transaction can bundle several database transactions. It is only as a result of all of these bundled database transactions that the data is consistent in business terms.
Due to work process multiplexing, each work process starts a separate database transaction within each dialog step.
This is because less resources are utilized in the system by following this strategy
Using the SAP transaction as a structural level above the database transaction significantly improves the performance of your SAP system.
Performing program syntax checks
Assigning users to work process
Distributing transaction load
As many as possible
/usr/sap//sys/profile or \usr\sap\\sys\profile
/usr/sap/trans/profile or \usr\sap\trans\profile
/etc or \winnt\system32\drivers\etc
/oracle//dbs or \oracle\/dbs