You can update user information on the A.20.05 Users screen.
The arguments of the UPDATE_USER function are listed below.
Argument Name |
Type |
In/Out |
---|---|---|
P_USER |
Record, user_upd_rec |
IN |
P_PROJ_ID |
VARCHAR2(10), m_projects.proj_id |
IN |
P_COMMIT |
VARCHAR2 |
IN |
P_RESULT |
NUMBER |
OUT |
P_MESSAGE |
VARCHAR2 |
OUT |
The function returns m_users.m_usr_id.
The next table shows the values that can be transferred with P_USER in the UPDATE_USER function.
Column Name |
Mandatory |
Description |
---|---|---|
user_id |
Yes |
Username (VARCHAR2(10), m_users.m_usr_id) |
first_name |
No |
First Name (VARCHAR2(30), m_users.first_name) |
last_name |
No |
Last Name (VARCHAR2(40), m_users.last_name) |
company |
No |
Company Name (VARCHAR2(60), m_users.company) |
department |
No |
Department Name (VARCHAR2(20), m_users.department) |
telephone |
No |
Telephone (VARCHAR2(40), m_users.telephone) |
fax |
No |
Fax (VARCHAR2(40), m_users.fax) |
|
No |
Email Address (VARCHAR2(50), m_users.email) |
managed_by |
No |
Managed by (VARCHAR2(10), m_users.managed_by) |
notify_login |
No |
Notify on Login (VARCHAR2(1), m_users.notify_on_login_ind) |
pw_change_days |
No |
Password Change Interval (NUMBER(6), m_users.pw_change_days) |
pw_history |
No |
Password History Size (NUMBER(6), m_users.pw_history) |
complex_pw_enforced |
No |
Complex Password? (VARCHAR2(1), m_users.complex_pw_enforced) |
super_user_ind |
No |
Global Access (VARCHAR2(1), m_users.super_user_ind) |
osuser |
No |
OS User (VARCHAR2(60), m_users.osuser) |
mail_password |
No |
Password via Email (VARCHAR2(1), default ‘N’) |
amount |
No |
Allowed Amount (NUMBER(24), m_users.amount) |
currency |
No |
Currency (VARCHAR2(10), m_units.unit_code) |