We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.
Showing posts with label level. Show all posts
Showing posts with label level. Show all posts

SAP S_TABU_LIN set up as organizational level

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Question: Hello,

I have started to look at the use of S_TABU_LIN to restrict table record maintenance on BUKRS , KOKRS; WERKS and EKORG. What I want is to be able to set these restricitons as organizational levels as we are using template roles which by inheritance will be used at about 200 different companies.

Has anyone tried this ?

Is it possible or not ?



Answer:
You can create orglevels using the report SAP provides (PFCG_ORGFIELD_CREATE) . Note BUKRS already is an orglevel . SO test it before you go too far and read the results of the test results closely before you implement.

Answer:
This is not possible. It would mean 2 fields as OrgLevel:
First defining the field OrgCriteria definition as organzational level, and supplementary to that the needed values.
Both fields are in the object S_TABU_LIN. How would the system know which value belongs to whicht OrgCrit?



Keyword: BASIS
Title : SAP S_TABU_LIN set up as organizational level

Lock the user at Database level

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Login to the system database..then run a query to update the USR02 table.

To lock an user.

SQL> UPDATE USR02 SET UFLAG = '64' where BNAME='USERID' AND MANDT='CLIENT'
SQL> COMMIT

To unlock an user use

SQL> UPDATE USR02 SET UFLAG = '0' where BNAME='USERID' AND MANDT='CLIENT'
SQL> COMMIT

Here the different values of uflag have different meaning
UFLAG value

0 ------ Not locked

16 ------ Mystery values

32 ------ Locked by CUA admin

64 ------ Locked by system Administrator

128 ------ Locked due to incorrect logon attempts or too many failed attempts

192 ------ A combination of both. The user is locked by admin and user tries to logon with incorrect passwords and gets locked ( 192 = 64+128)



Keyword: BASIS
Title : Lock the user at Database level

Slow Response Times on the R/3 Application and Operating System Level

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Symptom

There is heavy operating system paging, especially page out, and high swap rates.

Corrective action

Increase the main memory or roll area.



Keyword: BASIS
Title : Slow Response Times on the R/3 Application and Operating System Level

T r a n s l a t e to your language