The RZ10 transaction code in SAP Basis is used to open the parameter profile maintenance window. This window allows you to view and maintain the profiles that are used to configure the SAP system. For example, you can set parameters like system default settings, startup programs and background jobs, memory and spool settings, and access control.
On this page, you will find links to SAP Documentation, Wiki & Help Pages, Q&A, similar/related TCodes, Source Tables, and Authorization Objects for RZ10.
- BC-CCM-CNF (Use Subcomponents)
- BC-CCM-CNF-PFL (Profile Maintenance)
- RZ10 - Maintain Profile Parameters
- BC-CCM-CNF-PFL (Profile Maintenance)
SAP Help, Wiki, Q&A and other resources for RZ10
Click the above link for the full list of resources and help pages, only the first few are posted below
-
Importing Profile Files After Installation - SAP Help Portal
During an initial installation of an SAP system, an upgrade to a new SAP release, or the addition of a new application server instance, the system automatically generates or updates the profile files at operating system level. The installation program does not save profile files directly in the database.
"Since the profile maintenance (transaction RZ10) works with profile data from the database, you have to manually import the profile files from the file directory of the operating system into the database."
https://help.sap.com/docs/SAP_NETWEAVER_740/b17bd20044a44edb9aa7830ee52ffac3/92bcaaa397f848a999dfa0c71188c058.html
-
Profile Maintenance - SAP Help Portal
During an initial installation of an SAP system, an upgrade to a new SAP release, or the addition of a new application server instance, the system automatically generates or updates the profile files at operating system level. The installation program does not save profile files directly in the database. These profiles must be manually imported into the database.
"Changes are made to profiles at database level using transaction RZ10 (edit profiles). To save these changes at operating system level too, they must be activated."
https://help.sap.com/docs/SAP_NETWEAVER_740/b17bd20044a44edb9aa7830ee52ffac3/5a860a509ece466ce10000000a423f68.html
-
Determining a Change to a Profile | SAP Help Portal
If a profile was changed, it is saved as a separate version in the database. The old versions of the profile are not lost and can be used again at any time by copying them. Only when changes are activated is the the new version saved at operating system level too. The latest version of a profile in the database can be compared with the active version at operating system level.
https://help.sap.com/docs/ABAP_PLATFORM_NEW/b17bd20044a44edb9aa7830ee52ffac3/588d0a509ece466ce10000000a423f68.html
-
Changing Profile Files - SAP Help Portal
During an initial installation of an SAP system, an upgrade to a new SAP release, or the addition of a new application server instance, the system automatically generates or updates the profile files at operating system level. These profile files must be manually imported to the database. If there is already a version in the database, this can be edited in profile maintenance (transaction RZ10).
https://help.sap.com/docs/SAP_NETWEAVER_740/b17bd20044a44edb9aa7830ee52ffac3/c1bf434761a8493381631db50e41a3bb.html
-
Changing Profile Files | SAP Help Portal
During an initial installation of an SAP system, an upgrade to a new SAP release, or the addition of a new application server instance, the system automatically generates or updates the profile files at operating system level. These profile files must be manually imported to the database. If there is already a version in the database, this can be edited in profile maintenance (transaction RZ10).
https://help.sap.com/docs/ABAP_PLATFORM_NEW/b17bd20044a44edb9aa7830ee52ffac3/c1bf434761a8493381631db50e41a3bb.html
-
Profile Maintenance | SAP Help Portal
During an initial installation of an SAP system, an upgrade to a new SAP release, or the addition of a new application server instance, the system automatically generates or updates the profile files at operating system level. The installation program does not save profile files directly in the database. These profiles must be manually imported into the database.
"Changes are made to profiles at database level using transaction RZ10 (edit profiles). To save these changes at operating system level too, they must be activated."
https://help.sap.com/docs/ABAP_PLATFORM_NEW/b17bd20044a44edb9aa7830ee52ffac3/5a860a509ece466ce10000000a423f68.html
-
Authorization Checks - SAP Help Portal
To ensure that a user has the relevant authorizations when he or she performs an action, users are subject to authorization checks.
https://help.sap.com/docs/SAP_NETWEAVER_740/c6e6d078ab99452db94ed7b3b7bbcccf/4ca0ac7a68243b9ee10000000a42189b.html
-
Configure Principal Propagation for HTTPS - SAP Help Portal
Find step-by-step instructions to configure principal propagation to an ABAP server for HTTPS.
https://help.sap.com/docs/CP_CONNECTIVITY/cca91383641e40ffbe03bdc78f00f681/a8bb87a72d094e0d981d2b1f67df7bc3.html
-
Nach der Installation Profil-Dateien importieren - SAP Help Portal
Bei der Erstinstallation eines SAP-Systems, dem Upgrade auf ein neues SAP-Release und dem Hinzufügen einer neuen Applikationsserver-Instanz generiert bzw. aktualisiert das System automatisch die Profildateien im Dateiverzeichnis auf Betriebssystemebene. Das Installationsprogramm speichert Profil-Dateien allerdings nicht direkt in der Datenbank.
"Da die Profilpflege (Transaktion RZ10) allerdings mit Profildaten aus der Datenbank arbeitet, mssen Sie die Profildateien manuell aus dem Dateiverzeichnis des Betriebssystems in die Datenbank importieren."
https://help.sap.com/docs/SAP_NETWEAVER_740/b17bd20044a44edb9aa7830ee52ffac3/92bcaaa397f848a999dfa0c71188c058.html?locale=de-DE
-
Configuring the Workload Monitor - SAP Help Portal
You use the workload monitor to analyze statistical data from the SAP kernel. When doing so, there are many ways in which you can influence the type and scope of both the data collection and the data storage. This process presents these influence methods.
https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/9f46232c95d9411fbdd98858b31f4c2f/af59f23a4453c316e10000000a114084.html
-
View the full list of resources, SAP Help/Wiki pages and Q&A for RZ10
Related Transaction Codes
TCODE | Description | Functional Area |
---|---|---|
RZ11 | Profile Parameter Maintenance | Basis - Profile Maintenance |
SMICM | ICM Monitor | Basis - Internet Communication Manager |
SU01 | User Maintenance | Basis - User and Authorization Management |
SM59 | RFC Destinations (Display/Maintain) | Basis - RFC |
SE80 | Object Navigator | Basis - Repository Browser |
Tables for SAP Transaction Code RZ10
TABLE | Description | Functional Area |
---|---|---|
SMLG | Standard milestone group | Project Systems - Network and Activity |
TSTC | SAP Transaction Codes | Basis - ABAP Runtime Environment |
MONI | Monitor table MONI | Basis - Performance Monitors (TCC) |
USR02 | Logon Data (Kernel-Side Use) | Basis - Authentication and SSO |
TSTCA | Values for transaction code authorizations | Basis - ABAP Runtime Environment |
TCOLL | Configuration: Data collection for performance monitoring | BC - Workload Monitoring Tool |
Authorization Objects for SAP Transaction Code RZ10
AUTHORIZATION OBJECT | Description | Functional Area |
---|---|---|
S_TCODE | Transaction Code Check at Transaction Start | |
S_RFC | Authorization Check for RFC Access | |
S_TABU_DIS | Table Maintenance (via standard tools such as SM30) | |
S_PROGRAM | ABAP: Program Flow Checks | |
S_DATASET | Authorization for file access | |
S_ADMI_FCD | System Authorizations |
Most searched SAP Basis Components TCodes
- Idoc TCodes
- User TCodes
- Spool TCodes
- Se16 TCodes
- Table View TCodes
- Transport TCodes
- Display Authorization Object TCodes
- Display TCodes
- Display User Roles TCodes
- Authorization TCodes
- Sapscript TCodes
- Rfc TCodes
- Work Order TCodes
- Smartform TCodes
- Workflow TCodes
- Query TCodes
- Bapi TCodes
- Enhancement TCodes
- Idoc Monitoring TCodes
- Error Log TCodes
- Web Service TCodes
- Change Document TCodes