PROFILE PARAMETERS NEED TO SET

[Former Member]

Hi Experts,

Our Auditor suggested us that below profile parameters are weak and need to set in production server.

The Profile Parameters are

1.login/failed_user_auto_unlock is not set (Need to set 1)

2.login/min_password_diff set is not adequate (Need to set 2-3)

3.login/min_password_digits is not defined.(Need to set 1 or more)

4.login/min_password_letters is not defined(Need to set morethan 3)

5.login/min_password_specials is not defined(Need to set 1)

6.login/disable_multi_gui_login is not defined(Need to set morethan3)

7.rec/client is set to OFF(Need to set OFF)

As per the given profile parameters i can set the valuues using t-code RZ10, after setting these parameters and i can also restart the server to activate these parameters

But here I need some clarification that after restaring the server, system will accept the old password (which iam using before setting the parameters) or it will ask the new password or can i able to logon using my old password

Please give me your valuable suggestions.

Regards,

Reddy

[Former Member]

Hi Reddy,

After setting the parameters you will still be able to logon to the system using the current password. Once the password has expired (based on profile parameter login/password_expiration_time), newly entered passwords must adhere to your parameter settings.

Gary

[Former Member]

Hi Gary,

Sorry.......for late response.

Thank you for your valuable information. I have activated all profile parameters except 7.rec/client parameter.

I am unable to understand the description of this parameter from sap(rz10 using f1 help)

Please could you tell me the impacts and list of major tables for this profile parameter.

Regards,

Reddy V.

[former_member185954]

Hi Reddy,

The rec/client parameter indicates wheter table logging should be enabled or disabled in particular or ALL clients.

Check the following link for detailed explanation.

http://help.sap.com/saphelp_47x200/helpdata/en/18/4363d5ffc40a47a0263d4774cfab6d/frameset.htm

Also check SAP Note 1916 - Logging table changes in R/3

Regards,

Siddhesh

[Former Member]

Hi Siddhesh,

Thank you for your valuable information.

I have activate table logging in our production system using the rec/client=ALL system profile parameter but I would like to know about the impact on performance.

At the same time i would like to know which tables should be logged.

Please let me know which tables should be logged in the system.

Regards,

Reddy V.

[vincentlim826]

Hi Reddy,

The following are some SAP Notes that you should read regarding table logging and the rec/client parameter.

#163694 R3trans: Logging table changes

#485879 Incomplete evaluation of table change logs

#608835 Performance problems due to table logging?

In fact, I think that setting the rec/client parameter to "All" can seriously impair SAP system performance. I recommend you do not use the value All. You should limit automatic logging to one client.

Note 608835 mentioned above should answer your query on performance/ impact.

You can use transaction SCU3 to view the change/activity logs.

As far as I know, there is no official recommendation of tables that must be logged. Maybe those important tables that you think, how about you take a look at Note 112388, which mentioned about tables like:

T000

T001*

T003*

T004*

T007*

T008*

T012*

T030

T033*

T042*

T044A

T044Z

T074

T077*

T078*

T079*

T169*

TACTZ

TADIR

TASYS

TBAER

TBRG

TCUR*

TDDAT

TDEVC

TSTC

TSYST

cheers,

Vincent

[Former Member]

Dear Mr. Vincent,

Thankyou for your valuable information.

Thanks & Regards,

Reddy V