Do you have any question about this error?
Message type: E = Error
Message class: SECAUDIT - Message class for security audit
Message number: 085
Message text: Profile parameter &1 (current value &2) was set dynamically
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
SECAUDIT085
- Profile parameter &1 (current value &2) was set dynamically ?The SAP error message SECAUDIT085 indicates that a profile parameter has been set dynamically at runtime, which may not be in line with the security policies or best practices of your SAP system. This message is part of the security audit log and is intended to alert administrators about changes to system parameters that could affect system behavior or security.
Cause:
The cause of this error message is that a profile parameter (denoted as
&1
in the message) has been changed dynamically (i.e., at runtime) to a new value (denoted as&2
). This can happen for various reasons, such as:
- Manual Changes: An administrator or user with sufficient privileges may have changed the parameter using transaction codes like RZ10 or RZ11.
- Programmatic Changes: A program or script running in the background may have modified the parameter.
- System Configuration: Certain configurations or installations may require dynamic changes to parameters.
Solution:
To address this issue, consider the following steps:
- Review the Change: Check the system logs to identify who made the change and why. This can help determine if the change was authorized and necessary.
- Revert if Necessary: If the change is not in line with your security policies, revert the parameter to its original value using transaction RZ11 or RZ10.
- Document Changes: Ensure that any changes made to profile parameters are documented, including the reason for the change and who authorized it.
- Implement Controls: If dynamic changes are not allowed in your environment, consider implementing controls to prevent unauthorized changes. This may include restricting access to certain transactions or implementing monitoring tools.
- Consult SAP Notes: Check for any relevant SAP Notes that may provide additional context or solutions related to this error message.
Related Information:
By following these steps and understanding the implications of dynamic parameter changes, you can better manage your SAP system's security and configuration.
Get instant SAP help. Start your 7-day free trial now.
SECAUDIT084
Kernel default used as current value for parameter &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SECAUDIT081
Parameter combination &1 and &2 is not valid
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SECAUDIT086
Profile parameter &1 (current value &2) is obsolete
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SECAUDIT087
Kernel parameter &1 = &2 does not match the current SHM value &3
What causes this issue? The value saved for the kernel parameter is different to the value that is currently in effect. The kernel parameter change w...
Click on this link to search all SAP messages.