vijay

• Nov 10th, 2005

 

hi

in case  a sys admin responsibility is disabled,.,log in to any other user,,likeOPERATIONS,WELCOME. so go to sysadmin responsiblity here,,query for ur user,,and in the listed responsiblities,,u must have a sys admin responsiblity woth an TO AND FROM EFFECTIVE DATE.so there remove the TO dateand save it,.now when u login to ur respon ,u must see ur sys admin .

regards

vijay

devesh

• Nov 12th, 2005

 

sir,

thanx for the answer. but,when i have given the end date in system responsibility then he is not seeing from any user and i have seen that some people used the backhand and updated the some column.

so, i know that how i use the backhand for this problem?

ravi

• Dec 28th, 2005

 

What happened if a user set end date to system administrator user ?

Vivek

• Apr 12th, 2006

 

The start date and end date signifies the period for which a particular user

can access a responsibility. So When u populate the end date in the responsibility you no longer can access the responsibility after the end date

arun

• Apr 25th, 2006

 

Are you sure what you want from others??? Well you can not add any user if you are not having system administrator responsibility. Whatever user you are using must have this responsibility.Switch to this respo and enable or disable the user.

Hope this will help you.

Dwaipayan.Mojumder

 Profile Answers by Dwaipayan.Mojumder 

• Jan 11th, 2007

 

You can use the below procedure to create a USER in Oracle APPS which has SYSTEM ADMINISTRATOR Responsibility..Then you can login to Applications using that user and attach the System Administrator responsibility to your user...

Fire this proc in APPS Schema...Input Parameters - Login Name, Password

CREATE OR REPLACE PROCEDURE CREATE_APPLICATION_USER
(
 P_LOGIN_NAME IN VARCHAR2 DEFAULT NULL, 
 P_PASSWORD   IN VARCHAR2 DEFAULT NULL
)
AS
 LN_USER_ID                     NUMBER;
 LN_RESP_ID                     NUMBER;
 LN_APP_ID                      NUMBER; 
BEGIN

      FND_USER_PKG.CREATEUSER( P_LOGIN_NAME,'',P_PASSWORD); 

      SELECT USER_ID
      INTO  LN_USER_ID
      FROM FND_USER WHERE USER_NAME =   UPPER(P_LOGIN_NAME);

      SELECT  RESPONSIBILITY_ID,
              APPLICATION_ID
      INTO    LN_RESP_ID,
              LN_APP_ID
      FROM  FND_RESPONSIBILITY 
      WHERE RESPONSIBILITY_KEY = 'SYSTEM_ADMINISTRATOR';
 
   FND_USER_RESP_GROUPS_API.INSERT_ASSIGNMENT
                                                     ( LN_USER_ID
                                                      ,LN_RESP_ID
                                                      ,LN_APP_ID
                                                      ,NULL
                                                      ,SYSDATE
                                                      ,NULL
                                                      ,NULL   );
         COMMIT;
END;

imranbinyousuf

• Jul 26th, 2007

 

I think the only way to solve the issue is to update the table through SQL and change the effective date

kothariketan

 Profile Answers by kothariketan 

• Aug 16th, 2007

 

The system administrator responsibility got disabled. We can still use application developer responsibility and add "Define Responsibility" function / screen to existing any responsibility.

Once the menu under existing responsibility is rebuilt properly. Open Define Responsibility screen / function and reverse the end date.

Another option is through back end, update the respective record by making end Date NULL.

- Ketan Kothari

Bonthu Nagi Reddy

• Mar 5th, 2012

 

1) Log on to System Administrator.

2) Go to Security > User > Query the User Name.

3) Remove the Date Effective To( i.e which is end dated as open).

You can be able to view the System Administrator Responsibility.