Locking user DDIC in productive client

Hi all,
We have a requirement to lock DDIC account in our productive client. (not 000, 001).
a) Does SAP expect the DDIC user to remain unlocked during day-to-day operations?
b) What will be effects if we do lock it in the productive client?
c) I noticed there is one client dependent RDDIMPDP job being run as DDIC.
Can any other user run the job which has similar authorisations as DDIC or
only DDIC need to run?
Any help or informational link will be greatly appreciated.
Thanks a lot
Kumar

Hi Kumar,
Lock the users SAP, DDIC, EARLYWATCH and your remote support user. Unlock them only when necessary. (Note that it should never be necessary to use SAP!)
Locking an user will restrict unauthorized logon. by locking DDIC ,the background jobs are not affected.
more on this..refer the following link
http://help.sap.com/saphelp_nw70/helpdata/en/3e/cdaccbedc411d3a6510000e835363f/frameset.htm
with regards,
Rajesh.
plz, reward points!!

Similar Messages

SRM supplier user synchronization between SUS and productive client

Dear Sirs, in our SRM environement the contact persons (and relative system users) created by suppliers in the auto-registration procedure, should be synchronized between SUS and productive client.
(in our implementation client 150 and 330) .
This sync mechanism should be valid also for lock-unlock status of the user and reset of the password,
but in both cases it does not works (a locked user, manually unlocked from client 150 via SU01, is again locked in client 330, the same from 330 client).
Could you suggest a solution or some checkpoints ?
Could you provide some links for the configuration of this mechanism ? (we have seen only the SPRO node " Maintain Systems for Synchronization of User Data") ?
I am not shure if XI is implicated or not.
Best regards,
Riccardo Galli

HI
Maintain Systems for Synchronization of User Data
In this IMG activity, you specify the RFC destinations to which user data from SUS User Management is replicated.
In the Logical System field, you should enter the backend destination with which the user data should be synchronized when they are entered in SUS. On the basis of this information, the system determines the relevant RFC destination automatically.
Specify the function modules for creating, changing, or deleting a user in the external system for each logical system:
Function Module for Creating User: Function module that is called to create a user in the external system
Function Module for Changing User: Function module that is called to change the user in the external system
Function Module for Deleting User: Function module that is called to delete the user in the external system
If this data exists, you can set the indicator Use Purchasing BP ID to use the business partner ID from the procurement system instead of the business partner ID from SUS.
What are the settings maintained here ?
external system and roles in external system
br
Muthu

Reseting User ddic uflag parameter in Client 00 On Iseries as400 v5r4m0

Hi
I am busy doing a homogenous system copy from my prd system to a new 4th system (for Migration possibilities). I know that at the end of my db copy it will prompt ,me to provide the ddic password. My source system ddic user id (prd) at the moment is locked. I intend backuping up the prd sytem tonight, but i need to reset user ddic first, as whatever gets backed up will come across.
Does anyone know how to reset the uflag paramter of ddic in client 000.
I have only two users in client 000 i.e ddic and sap* and i cant do anythign with sap* as it has no profiles attached to it.(security issue) I know how to do the unlock of the user in oracle i.e
Oracle
Update USR02 set UFLAG=0 where BNAME='DDIC' and MANDT=000.
Can anyone help on the as400 side.

Hi Morga,
If I understand correctly, you just need help how to issue SQL commands natively on the iSeries, is that right?
If so, that's how you'd proceed:
Sign on to the machine via green screen as user <sid>OFR and then type STRSQL. You'll then get as screen that allows you to enter the SQL statement like you suggested it for Oracle.
STRSQL is a product which does not come for free. So, if you do not have that installed, you could use SQLUTIL. SQLUTIL is free, but not per default on the system. (Search for library QGPTOOLS.)
In case you don't have it, read SAP note 68732 for more information of how to get it.
Hope that helps.
Best regards,
Dorothea

Forgot password for client 000 user DDIC

We forgot password for client 000 user DDIC & SAP*
please suggest any one how to recover the password
Thanks in advance

Hi,
Pls refer below link explaining step by step details of activating SAP* user login.
[http://forums.sdn.sap.com/thread.jspa?threadID=1497131]
[http://www.sap-img.com/basis/changing-the-default-password-for-sap-user.htm]
Regards,

While Filling-up setup tables how to lock users & Suspend user

Hi Friends & Experts,
I am going to Run Set-up tables in my BI Production servers as Application wise for example..SD, MM, PP, QM, & Invetary.
So I want to tell to client kindly lock users & suspend users to stop document postings.
How to tell this to clients this situation. pls do suggest on this.
Siri

Hi Friends thank you for your quick response...
Is there any Particular T.Codes as Application wise..E.g: PP, MM, SD, QM. Inventary.. to Lock instead of Lock SM01.
Because if we lock SM01 All T.codes are going to Lock. I think It's not advisable.
Pls Suggest me as soon as possible.
Siri

How to reset ddic password for client 000 in MSSQL 2005 database

SAP = ECC6
DB = MSSQL 2005
client = 000
1. SAP* account was removed from the DB, can't be found in USR02 table.
2. Only left ddic account and was locked. How can i reset ddic password?
3. How can i unlock and reset my own password from the MSSQL database?

You can unlock and reset passwords for DDIC and for your own user id in the following way:
Please execute the below queries at your database level:
To unlock user ids:
SQL>update SAP<SID>.usr02 set flag=0 where bname="*user id*" and mandt=client number;
SQL>commit;
To reset the passwords:
SQL>update SAP<SID>.usr02 set bcode="encrypted password" where bname="*user id*" and mandt=client number;
SQL>commit;
Then log into the system and execute /$sync
hope this will help you.
Regards,
FAisal

Profile for Production Client in production server.

Dear Tech Masters,
I have installed SAP ECC 6.0 (Production server). Now I want to create client ( First client after installation), which would be the production client. I am not sure about the profile for client copy from 000. After a lot googling ...I am confuse whether SAP_ALL or SAP_CUST which one I use for client copy from 000 for production client.
Please help me asap.
Edited by: RABI PAL on Jan 2, 2009 7:44 PM

go with SAP_ALL
you are using 000 client and ur going to create new client XXX for XXX client you try to use SAP_ALL then you can you DDIC with full authorizations for XXX Client.

Help me: I have locked user cn=orcladmin in oid

Hello.
Pleas help me, I have locked user cn=orcladmin in oid production environment
I have tried to unlock with this procedure, but It doesn´t work:
[oracle@appamucm01pro admin]$ /opt/oracle/mw/mw_idm/Oracle_IDM/ldap/bin/oidpasswd connect=OIDDB unlock_su_acct=true
OID DB user password:
ERROR * gsldpuUnlockSuAccount * ORA-28000:ORA-28000: the account is locked
encountered
Error in unlocking OID super user account.
[oracle@appamucm01pro admin]$
This is my oid version:
[oracle@appamucm01pro admin]$ $ORACLE_HOME/bin/oidldapd -version
oidldapd: Release 11.1.1.5.0 - Production on fri mar 1 14:38:56 2013
Copyright (c) 1982, 2011 Oracle. All rights reserved.
[oracle@appamucm01pro admin]$
[oracle@appamucm01pro admin]$

Hi ,
First get your OID schema name for example suppose it's ODS the follow the following steps
1- sqlplus / as sysdba
2- alter user ODS account unlock;
it should unlock you OID user .
thanks
Amar

Maintaining Posting Periods on productive client.

hi all.
Is there any way of maintaining posting periods "OB52" (IMG activity) without changing the status of productive client to modifiable. I know one way is to maintain the posting periods in dev and then transport. Is there any other way? (directly in production) and also what is the recommended method for doing this.

Hello Rizwan,
You can maintan OB52 in productive client by keeping the client as productive.The settings in SCC4 have to be like this :
Client Role: Production
Changes and Transport for client specific objects: Not allowed.
Client Independent object changes: No changes to Repository and cross client authorization objects allowed.
These settings will allow users to maintain OB52 in production clients but won't allow them access to maintain general customizing.
Further you would need to assign authorizations for S_TABU_DIS as mentioned by Barry.
OB52 is nothing but a view of table T001B. The authorization group for T001B table in table maintainence generator is FC31.
So whosever needs to maintain OB52 needs to have proper authorization for this table via S_TABU_DIS.
The values assigned have to be :
Activity 02,03
Authorization Group: FC31.
Also you can check whether OB52 is allowed for maintainence in production.
For this go to transaction SOBJ. Then check the check box against enter conditions and click on display. A pop up would come up. here you can give the view name V_T001B. In the resulting screen check for the check box against Current Settings. If it is checked then OB52 is open for maintainence in production client.
There is one more method:
Go to SPRO. Then to SAP Reference IMG. Go to the node for opening and closing posting periods. You can also search for this using Control+F option. Use the search string " Open and Close Posting Periods".
Once there click on it. Then in menu bar go to EDIT and then to display IMG activity. In the next screen to go tab Maint. objects under the selection block Assigned objects. Here you will find an entry for table V_T001B. Double click on it a new screen appears. Here just check if the check box against current settings is checked. If it is then OB52 can be maitained in production clients.
Please award points if the answer was helpful to you.
With Regards.
Ruchit

Erros SSC4 - Already at least one production client

Hello,
I need to set up a second client to productive.
When trying to setup SCC4 in the following error occurs:
Error: You specified client 100 as production client, but there is already at least one production client in the system (e.g. 200).
I have this need in GRC and PI.
tks!
Jônatas.

Dúvidas neste fórum devem seguir o idioma Português.
Thread Locked.

Unable to access user DDIC and SAP*

+Hi GURUS,+
+I installed solutionmanager 4.0 and i loggen in the system(000) with DDIC user and check the TCODE SICK.+
++When i restarted the server it was not allow me to login awith user DDIC and SAP in 000 client.++*
+It's giving error message:+
+Password log on nolonger possible too many times failed attempts.+
++Could you please help me out is there any way to set DDIC and SAP from windows level(i mean sap inst directry..usr/sap/<sid>/sys/profile)*
Regards
JAn

Hi,
Unlock it at Database level
UPDATE usr02 SET uflag = 0 WHERE bname = "SAP*" AND mandt = <client number>
Or
Run the sql query at sql prompt and then login to sap with sap* and password "pass".
SQL> delete from usr02 where mandt=<your login client> and banme='SAP*';
Rakesh

Program to lock users

Dear Pros,
As a security admin. I would appreciate if someone could help me program to lock users vis following requiremnt:
1) Has logged onto the system in the past, but has not logged on in the last 90 days.
2) Has never logged onto the system in the past 30 days.
3) Does NOT belong to User Group SUPER.
4) Dialog Users ONLY.
Thanks for any help or suggestion

Hi,
 Try with this program or you can modify:
Selection Text
001 Program Parameter
002 User Lockeds
003 User Erased
004 Report of User Lokeds and Erased
005 User
006 Last Access Date
007 Creation Date
008 Result
009 Full Name
010 Exception (Not to erase these users)
CHECK_T Test ejecution
CLASS Users Group
MESBL Months to Lock
MESBO Months to Delete
S_EXCEP Users
REPORT ZBAR0009 NO STANDARD PAGE HEADING LINE-SIZE 155 LINE-COUNT 60.
TABLES: USR02, "Datos logon
 USR21, "Asignación nombre usuario - clave dirección
 ADRP. "Personas (gestión de direcciones central)
DATA: BEGIN OF IT_USBOR OCCURS 0,
 BNAME LIKE USR02-BNAME, "Nombre de usuario según maestro de us
 ERDAT LIKE USR02-ERDAT, "Fecha de creación del maestro de usua
 TRDAT LIKE USR02-TRDAT. "Fecha del último acceso al sistema
DATA END OF IT_USBOR.
DATA: BEGIN OF IT_USBLO OCCURS 0,
 BNAME LIKE USR02-BNAME, "Nombre de usuario según maestro de us
 ERDAT LIKE USR02-ERDAT, "Fecha de creación del maestro de usua
 TRDAT LIKE USR02-TRDAT. "Fecha del último acceso al sistema
DATA END OF IT_USBLO.
DATA: BEGIN OF BDCDATAC OCCURS 5.
 INCLUDE STRUCTURE BDCDATA.
DATA: END OF BDCDATAC. "Estructura Batch Input
Tablas de mensajes generados por el batch input de modificación.
DATA: BEGIN OF BDCMSGCOLLM OCCURS 5.
 INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF BDCMSGCOLLM.
DATA: FECHA1 LIKE USR02-TRDAT,
 FECHA2 LIKE USR02-TRDAT,
 FECHA3 LIKE USR02-TRDAT,
 TR_MS(30),
 I TYPE I,
 P TYPE I,
 CONT TYPE I.
SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
 PARAMETERS: MESBL(2) DEFAULT '03',
 MESBO(2) DEFAULT '06',
 CLASS LIKE USR02-CLASS DEFAULT 'UPSTREAM',
 CHECK_T AS CHECKBOX DEFAULT 'X'.
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN: BEGIN OF BLOCK C1 WITH FRAME TITLE TEXT-010.
 SELECT-OPTIONS: S_EXCEP FOR USR02-BNAME.
SELECTION-SCREEN END OF BLOCK C1.
START-OF-SELECTION.
Armado de Fechas
MOVE SY-DATUM TO FECHA1.
FECHA2 = FECHA1 - ( 30 * MESBL ).
FECHA3 = FECHA1 - ( 30 * MESBO ).
PERFORM EXTRACCIÓN_US_BLOQUEAR.
PERFORM EXTRACCIÓN_US_BORRAR.
PERFORM VALIDAR_EXCEPCIONES.
PERFORM EJECUTAR_TRANS.
TOP-OF-PAGE.
 FORMAT COLOR 4 ON.
 SKIP.
 WRITE: /57 TEXT-004, 134 'Fecha: ', SY-DATUM.
 WRITE: /134 'Página: ', SY-PAGNO, 151 ' '.
 SKIP.
END-OF-PAGE.
*& Form EXTRACCIÓN_US_BORRAR
 text
--> p1 text
<-- p2 text
FORM EXTRACCIÓN_US_BORRAR.
Selección de los Usuarios a Borrar que han entrado alguna vez
 SELECT BNAME ERDAT TRDAT APPENDING CORRESPONDING FIELDS OF TABLE
 IT_USBOR FROM USR02 WHERE TRDAT LT FECHA3 AND
 TRDAT NE '00000000' AND
 CLASS EQ CLASS.
Selección de los Usuarios a Borrar que aún no han entrado
 SELECT BNAME ERDAT TRDAT APPENDING CORRESPONDING FIELDS OF TABLE
 IT_USBOR FROM USR02 WHERE ERDAT LT FECHA3 AND
 TRDAT EQ '00000000' AND
 CLASS EQ CLASS.
ENDFORM. " EXTRACCIÓN_US_BORRAR
*& Form EXTRACCIÓN_US_BLOQUEAR
 text
--> p1 text
<-- p2 text
FORM EXTRACCIÓN_US_BLOQUEAR.
Selección de los Usuarios a Bloquear que han entrado alguna vez
 SELECT BNAME ERDAT TRDAT APPENDING CORRESPONDING FIELDS OF TABLE
 IT_USBLO FROM USR02 WHERE TRDAT LT FECHA2 AND
 TRDAT GE FECHA3 AND
 CLASS EQ CLASS.
Selección de los Usuarios a Bloquear que aún no han entrado
 SELECT BNAME ERDAT TRDAT APPENDING CORRESPONDING FIELDS OF TABLE
 IT_USBLO FROM USR02 WHERE ERDAT LT FECHA2 AND
 ERDAT GE FECHA3 AND
 TRDAT EQ '00000000' AND
 CLASS EQ CLASS.
ENDFORM. " EXTRACCIÓN_US_BLOQUEAR
*& Form VALIDAR_EXCEPCIONES
 text
--> p1 text
<-- p2 text
FORM VALIDAR_EXCEPCIONES.
 IF S_EXCEP NE SPACE.
 DELETE IT_USBLO WHERE BNAME EQ 'SAP*' OR
 BNAME EQ 'DDIC' OR
 BNAME EQ 'MAILADM' OR
 BNAME EQ 'SAPGUEST' OR
 BNAME EQ 'WF-BATCH' OR
 BNAME IN S_EXCEP.
 DELETE IT_USBOR WHERE BNAME EQ 'SAP*' OR
 BNAME EQ 'DDIC' OR
 BNAME EQ 'MAILADM' OR
 BNAME EQ 'SAPGUEST' OR
 BNAME EQ 'WF-BATCH' OR
 BNAME IN S_EXCEP.
 ELSE.
 DELETE IT_USBLO WHERE BNAME EQ 'SAP*' OR
 BNAME EQ 'DDIC' OR
 BNAME EQ 'MAILADM' OR
 BNAME EQ 'SAPGUEST' OR
 BNAME EQ 'WF-BATCH'.
 DELETE IT_USBOR WHERE BNAME EQ 'SAP*' OR
 BNAME EQ 'DDIC' OR
 BNAME EQ 'MAILADM' OR
 BNAME EQ 'SAPGUEST' OR
 BNAME EQ 'WF-BATCH'.
 ENDIF.
ENDFORM. " VALIDAR_EXCEPCIONES
*& Form EJECUTAR_TRANS
 text
--> p1 text
<-- p2 text
FORM EJECUTAR_TRANS.
DATA: L TYPE I.
 DESCRIBE TABLE IT_USBLO LINES L.
 IF L GT 0.
 LOOP AT IT_USBLO.
 ADD 1 TO CONT.
 IF CHECK_T EQ SPACE.
 PERFORM EJECUTAR_US01 USING 'LOCK' IT_USBLO-BNAME.
 ENDIF.
 PERFORM LISTAR USING IT_USBLO-BNAME IT_USBLO-ERDAT
 IT_USBLO-TRDAT TR_MS 'LOCK'.
 AT LAST.
 ULINE /1(152).
 ENDAT.
 ENDLOOP.
 ENDIF.
 DESCRIBE TABLE IT_USBOR LINES L.
 IF L GT 0.
 CLEAR CONT.
 LOOP AT IT_USBOR.
 ADD 1 TO CONT.
 IF CHECK_T EQ SPACE.
 PERFORM EJECUTAR_US01 USING 'DELE' IT_USBOR-BNAME.
 ENDIF.
 PERFORM LISTAR USING IT_USBOR-BNAME IT_USBOR-ERDAT
 IT_USBOR-TRDAT TR_MS 'DELE'.
 AT LAST.
 ULINE /1(152).
 ENDAT.
 ENDLOOP.
 ENDIF.
ENDFORM. " EJECUTAR_TRANS
*& Form EJECUTAR_US01
 text
 -->P_0154 text *
FORM EJECUTAR_US01 USING VALCODE USUARIO.
REFRESH BDCDATAC.
MOVE: 'SAPLSUU5' TO BDCDATAC-PROGRAM,
 '0050' TO BDCDATAC-DYNPRO,
 'X' TO BDCDATAC-DYNBEGIN.
APPEND BDCDATAC.
CLEAR BDCDATAC.
MOVE: 'USR02-BNAME' TO BDCDATAC-FNAM, "Usuario SAP
 USUARIO TO BDCDATAC-FVAL.
APPEND BDCDATAC.
CLEAR BDCDATAC.
IF VALCODE EQ 'LOCK'.
MOVE: 'BDC_OKCODE' TO BDCDATAC-FNAM, "OK_CODE
 '=LOCK' TO BDCDATAC-FVAL.
APPEND BDCDATAC.
CLEAR BDCDATAC.
MOVE: 'SAPLSUU5' TO BDCDATAC-PROGRAM,
 '0500' TO BDCDATAC-DYNPRO,
 'X' TO BDCDATAC-DYNBEGIN.
APPEND BDCDATAC.
CLEAR BDCDATAC.
MOVE: 'BDC_OKCODE' TO BDCDATAC-FNAM, "OK_CODE
 '=LOCK' TO BDCDATAC-FVAL.
APPEND BDCDATAC.
CLEAR BDCDATAC.
ELSEIF VALCODE EQ 'DELE'.
MOVE: 'BDC_OKCODE' TO BDCDATAC-FNAM, "OK_CODE
 '=DELE' TO BDCDATAC-FVAL.
APPEND BDCDATAC.
CLEAR BDCDATAC.
MOVE: 'SAPLSPO1' TO BDCDATAC-PROGRAM,
 '0300' TO BDCDATAC-DYNPRO,
 'X' TO BDCDATAC-DYNBEGIN.
APPEND BDCDATAC.
CLEAR BDCDATAC.
MOVE: 'BDC_OKCODE' TO BDCDATAC-FNAM, "OK_CODE
 '=YES' TO BDCDATAC-FVAL.
APPEND BDCDATAC.
CLEAR BDCDATAC.
ENDIF.
CALL TRANSACTION 'SU01' USING BDCDATAC
 MODE 'N'
 UPDATE 'S'
 MESSAGES INTO BDCMSGCOLLM.
REFRESH BDCDATAC.
 MOVE BDCMSGCOLLM-MSGV1(30) TO TR_MS.
 CLEAR BDCMSGCOLLM.
 REFRESH BDCMSGCOLLM.
ENDFORM. " EJECUTAR_US01
*& Form LISTAR
 text
 -->P_IT_USBLO_USUARIO text *
FORM LISTAR USING CODUS FECHA1 FECHA2 MENSAGE ACC.
DATA: NOMBRE(50), LOCKSTATE LIKE USLOCK . "RM 06-04-05
Búsqueda del Nombre Completo del Usuario
 CLEAR NOMBRE.
 SELECT PERSNUMBER INTO USR21-PERSNUMBER FROM USR21
 WHERE BNAME EQ CODUS.
 ENDSELECT.
 SELECT NAME_FIRST NAME_LAST INTO (ADRP-NAME_FIRST, ADRP-NAME_LAST)
 FROM ADRP
 WHERE PERSNUMBER EQ USR21-PERSNUMBER.
 ENDSELECT.
 CONCATENATE ADRP-NAME_FIRST ADRP-NAME_LAST INTO NOMBRE
 SEPARATED BY SPACE.
 IF ACC EQ 'LOCK'.
 ADD 1 TO I.
 IF I EQ 1.
 ULINE /1(30).
 WRITE: / SY-VLINE, 2 TEXT-002, 30 SY-VLINE.
 ULINE /1(152).
 WRITE: / SY-VLINE, 2 TEXT-005, 15 SY-VLINE, 17 TEXT-009,
 68 SY-VLINE, 70 TEXT-007, 93 SY-VLINE, 95 TEXT-006,
 118 SY-VLINE, 120 TEXT-008, 152 SY-VLINE.
 ULINE /1(152).
 ENDIF.
 IF CONT EQ 1.
 FORMAT COLOR 2 INTENSIFIED ON.
 ELSEIF CONT EQ 2.
 CLEAR CONT.
 FORMAT COLOR 2 INTENSIFIED OFF.
 ENDIF.
 Búsqueda del Status de Bloqueo del Usuario
 CALL FUNCTION 'SUSR_USER_LOCKSTATE_GET'
 EXPORTING
 USER_NAME = CODUS
 IMPORTING
 LOCKSTATE = LOCKSTATE
 EXCEPTIONS
 USER_NAME_NOT_EXIST = 1
 OTHERS = 2.
 IF LOCKSTATE-LOCAL_LOCK EQ 'X'. "RM 06-04-05
 MOVE 'BLOQUEADO' TO MENSAGE.
 ELSE.
 CLEAR MENSAGE.
 ENDIF.
 WRITE: / SY-VLINE, 2 CODUS, 15 SY-VLINE, 17 NOMBRE,
 68 SY-VLINE, 70 FECHA1, 93 SY-VLINE, 95 FECHA2,
 118 SY-VLINE, 120 MENSAGE, 152 SY-VLINE.
 ELSEIF ACC EQ 'DELE'.
 ADD 1 TO P.
 IF P EQ 1.
 ULINE /1(30).
 WRITE: / SY-VLINE, 2 TEXT-003, 30 SY-VLINE.
 ULINE /1(152).
 WRITE: / SY-VLINE, 2 TEXT-005, 15 SY-VLINE, 17 TEXT-009,
 68 SY-VLINE, 70 TEXT-007, 93 SY-VLINE, 95 TEXT-006,
 118 SY-VLINE, 120 TEXT-008, 152 SY-VLINE.
 ULINE /1(152).
 ENDIF.
 IF CONT EQ 1.
 FORMAT COLOR 2 INTENSIFIED ON.
 ELSEIF CONT EQ 2.
 CLEAR CONT.
 FORMAT COLOR 2 INTENSIFIED OFF.
 ENDIF.
 WRITE: / SY-VLINE, 2 CODUS, 15 SY-VLINE, 17 NOMBRE,
 68 SY-VLINE, 70 FECHA1, 93 SY-VLINE, 95 FECHA2,
 118 SY-VLINE, 120 MENSAGE, 152 SY-VLINE.
 ENDIF.
ENDFORM. " LISTAR

Running solman_setup again in productive client?

Hello,
my colleague fully completed solman_setup initial configuration in client 000.
He also started basic configuration but stopped at step 7 (Automatic Configuration: Activate BC Sets).
In productive client 100 I would like to start the complete setup with initial / basic configuration again.
We have MOPZ / EWA / service level reporting, documentation, project management in productive use.
Are there any risks or side effects to be expected?
Thanks and Regards,
bcAS

Hello,
If you just installed it SAP* should still be enabled
Are you sure you can't logon
Client: 000 or 001
User: SAP*
Password: 06071992
This should remain active until you perform this procedure: Defining a New Superuser and Deactivating SAP*
Described in this link
http://help.sap.com/saphelp_nw70/helpdata/en/3e/cdacecedc411d3a6510000e835363f/content.htm
Deactivating the Hard-Coded SAP* User
You can also deactivate the hard-coded user SAP* by activating the profile parameter login/no_automatic_user_sapstar. For more information, see SAP Note 68048.
So if you have not yet de-activated SAP*, then the following should still be valid
Client: 000 or 001
User: SAP*
Password: 06071992
Regards,
Paul

Lock user locally in CUA

Hi,
I want to lock user locally in CUA system .
If I use bapi BAPI_LOCK_USER it locks the user globally .
I need one function module or BAPI which locks the users locally in the client not considering the CUA .
Which FM/ BAPi can be used ? Pls advice .
Thanks,
Suman

Hi,
I used FM SUSR_BAPI_USER_LOCK with LOCK_LOCAL = 'X' and LOCK_GLOBAL=' ' . The new problem I am facing is it locally locks the user in CUA source system but unlocks the user in all target systems .
Please advice how to solve this .
Thanks,
Suman

Initial user to login to client 100

I have installed a demo version of SAP NW.
I have created client 100 in client 000.
My question is how do i login to client 100??
I tried SAP* with PASS but coudld not get into..
Any ideas??

Hi ,
If all the users are locked, they can be unlocked by
a)Try this command at ur sql plus query level
Go to cmd prompt.
Sqlplus /nolog
conn /as sysdba
this will take you to the sqlprompt.
Just execute the earlier commands there.
sqlplus>UPDATE SAP<schema>.usr02 set uflag=0 where mandt=<CLNT NO> and uflag=64;
this statement actually unlocks the users of that particular client. So, try for every client in that sap system.
b) You can delete sap* user
Go to cmd prompt.
Sqlplus /nolog
conn /as sysdba
sqlplus>DELETE SAP<SID>.usr02 where mandt='CLIENT.NO' and bname=SAP*;
Note:-
After doing this restart the system. So, that a new user with the name "sap" gets generated with password "pass". Provided the parameter is set login/no_automatic_user_sapstar= 0 (Automatic user SAP is permitted).
regards,
kanthi

Locking user DDIC in productive client

Similar Messages

Maybe you are looking for