eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.JTF_UM_PASSWORD_PVT dependencies on FND_USER

Line 197: * user is not a valid user in fnd_user (user_name does not exist or is enddated).

193: * param x_msg_data
194: * param x_msg_count
195: * Errors : Expected Errors
196: * requester_user_name or password is null
197: * user is not a valid user in fnd_user (user_name does not exist or is enddated).
198: * user does not have an email in fnd_user table.
199: * Other Comments :
200: * DEFAULTING LOGIC
201: * For the default workflow (JTAUMPSW) that is called by this API the following are valid:

Line 198: * user does not have an email in fnd_user table.

194: * param x_msg_count
195: * Errors : Expected Errors
196: * requester_user_name or password is null
197: * user is not a valid user in fnd_user (user_name does not exist or is enddated).
198: * user does not have an email in fnd_user table.
199: * Other Comments :
200: * DEFAULTING LOGIC
201: * For the default workflow (JTAUMPSW) that is called by this API the following are valid:
202: * 1. Whether or not approval is needed is determined by the usertype_id.

Line 258: from fnd_user

254: CURSOR c_item_key IS SELECT JTF_UM_PSW_WF_S.nextval FROM dual;
255:
256: CURSOR c_user(l_user_name in varchar2) IS
257: select email_address
258: from fnd_user
259: where user_name = l_user_name
260: and (nvl(end_date, sysdate+1) > sysdate OR
261: to_char(END_DATE) = to_char(FND_API.G_MISS_DATE));
262:

Line 1035: * FND_USER update : The update of fnd_user table is done using fnd_user_pkg

1031: * requester_user_name and email is null
1032: * requester_user_name is not a valid user
1033: * requester_email does not correspond to a valid user
1034: * Other Comments :
1035: * FND_USER update : The update of fnd_user table is done using fnd_user_pkg
1036: * procedure as recommended by fnd (bug 1713101)
1037: * DEFAULTING LOGIC
1038: * If only the user name is passed then the email is defaulted using the following logic
1039: * 1. Email address from fnd_users where user_name = p_requester_user_name

Line 1039: * 1. Email address from fnd_users where user_name = p_requester_user_name

1035: * FND_USER update : The update of fnd_user table is done using fnd_user_pkg
1036: * procedure as recommended by fnd (bug 1713101)
1037: * DEFAULTING LOGIC
1038: * If only the user name is passed then the email is defaulted using the following logic
1039: * 1. Email address from fnd_users where user_name = p_requester_user_name
1040: * 2. Email from per_all_people_F where person_id = employee_id
1041: * (retrieved from fnd_users using the user_name)
1042: * 3. Email from hz_contact_points where owner_type_id = party_id and
1043: * owner_table = 'HZ_PARTIES' and contact_point_type = 'EMAIL'.

Line 1041: * (retrieved from fnd_users using the user_name)

1037: * DEFAULTING LOGIC
1038: * If only the user name is passed then the email is defaulted using the following logic
1039: * 1. Email address from fnd_users where user_name = p_requester_user_name
1040: * 2. Email from per_all_people_F where person_id = employee_id
1041: * (retrieved from fnd_users using the user_name)
1042: * 3. Email from hz_contact_points where owner_type_id = party_id and
1043: * owner_table = 'HZ_PARTIES' and contact_point_type = 'EMAIL'.
1044: * Party_id here is obtained from the customer id stored in fnd_user
1045: * where user_name = p_requester_user_name.

Line 1044: * Party_id here is obtained from the customer id stored in fnd_user

1040: * 2. Email from per_all_people_F where person_id = employee_id
1041: * (retrieved from fnd_users using the user_name)
1042: * 3. Email from hz_contact_points where owner_type_id = party_id and
1043: * owner_table = 'HZ_PARTIES' and contact_point_type = 'EMAIL'.
1044: * Party_id here is obtained from the customer id stored in fnd_user
1045: * where user_name = p_requester_user_name.
1046: * In all the above cases the user, employee, party etc. have to be valid.
1047: *
1048: * If only the email address is specified, the user name is determined using a similar logic

Line 1049: * 1. User_name from fnd_user where email_address = p_requester_email_Address

1045: * where user_name = p_requester_user_name.
1046: * In all the above cases the user, employee, party etc. have to be valid.
1047: *
1048: * If only the email address is specified, the user name is determined using a similar logic
1049: * 1. User_name from fnd_user where email_address = p_requester_email_Address
1050: * 2. User_name from fnd_user where employee_id = person_id (retrieved from per_all_people_f
1051: * using the email_address)
1052: * 3. User_name from fnd_user where customer_id = hz_contact_points.owner_type_id and
1053: * owner_table = 'HZ_PARTIES' and contact_point_type = 'EMAIL' and

Line 1050: * 2. User_name from fnd_user where employee_id = person_id (retrieved from per_all_people_f

1046: * In all the above cases the user, employee, party etc. have to be valid.
1047: *
1048: * If only the email address is specified, the user name is determined using a similar logic
1049: * 1. User_name from fnd_user where email_address = p_requester_email_Address
1050: * 2. User_name from fnd_user where employee_id = person_id (retrieved from per_all_people_f
1051: * using the email_address)
1052: * 3. User_name from fnd_user where customer_id = hz_contact_points.owner_type_id and
1053: * owner_table = 'HZ_PARTIES' and contact_point_type = 'EMAIL' and
1054: * contact_point = p_requester_email_Address

Line 1052: * 3. User_name from fnd_user where customer_id = hz_contact_points.owner_type_id and

1048: * If only the email address is specified, the user name is determined using a similar logic
1049: * 1. User_name from fnd_user where email_address = p_requester_email_Address
1050: * 2. User_name from fnd_user where employee_id = person_id (retrieved from per_all_people_f
1051: * using the email_address)
1052: * 3. User_name from fnd_user where customer_id = hz_contact_points.owner_type_id and
1053: * owner_table = 'HZ_PARTIES' and contact_point_type = 'EMAIL' and
1054: * contact_point = p_requester_email_Address
1055: *
1056: * If both email and user name are passed, the combination is validated using the above logic.

Line 1203: if not fnd_user_pkg.changePassword(username => l_requester_user_name,

1199: if x_return_status <> FND_API.G_RET_STS_SUCCESS then
1200: RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
1201: end if;
1202:
1203: if not fnd_user_pkg.changePassword(username => l_requester_user_name,
1204: newpassword => l_password) then
1205: RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
1206: end if;
1207:

Line 1210: fnd_user_pkg.UpdateUser (

1206: end if;
1207:
1208: -- update the password date to null to force user to change psswd upon
1209: -- first login
1210: fnd_user_pkg.UpdateUser (
1211: x_user_name => l_requester_user_name,
1212: x_owner => 'CUST',
1213: x_unencrypted_password => l_password,
1214: x_password_date => null);

Line 1223: update fnd_user set

1219: -- password upon first logon
1220: -- not needed now as FND API allows setting the password date to null
1221: /*
1222: --begin
1223: update fnd_user set
1224: password_date = null
1225: where user_name = l_requester_user_name;
1226: */
1227: /* exception