APPS.HZ_USER_PARTY_UTILS dependencies on FND_USER

Line 65: | user name passed in as parameter. FND_USER |

61: pv_return_status OUT NOCOPY VARCHAR2) IS
62:
63: /*--------------------------------------------------+
64: | Cursor for fetching the user record based on |
65: | user name passed in as parameter. FND_USER |
66: | stores user names all capital letters. |
67: +--------------------------------------------------*/
68: CURSOR user_cur(l_user_name fnd_user.user_name%TYPE) IS
69: SELECT customer_id,

Line 68: CURSOR user_cur(l_user_name fnd_user.user_name%TYPE) IS

64: | Cursor for fetching the user record based on |
65: | user name passed in as parameter. FND_USER |
66: | stores user names all capital letters. |
67: +--------------------------------------------------*/
68: CURSOR user_cur(l_user_name fnd_user.user_name%TYPE) IS
69: SELECT customer_id,
70: employee_id
71: FROM fnd_user
72: WHERE user_name = UPPER(l_user_name);

Line 71: FROM fnd_user

67: +--------------------------------------------------*/
68: CURSOR user_cur(l_user_name fnd_user.user_name%TYPE) IS
69: SELECT customer_id,
70: employee_id
71: FROM fnd_user
72: WHERE user_name = UPPER(l_user_name);
73:
74: /*-----------------------------------------------------+
75: | Cursor for finding a person party from person_id |

Line 173: | 1) Find a party from FND_USER |

169:
170: BEGIN
171:
172: /*--------------------------------------------------+
173: | 1) Find a party from FND_USER |
174: | |
175: | If username was passed in, fetch it and check |
176: | whether party id is already defined for the user |
177: | |

Line 179: | fnd user since the calling program may call this |

175: | If username was passed in, fetch it and check |
176: | whether party id is already defined for the user |
177: | |
178: | It is possible that pv_user_name is not a valid |
179: | fnd user since the calling program may call this |
180: | API to get a party before it creates a fnd user. |
181: | We just ignore this case because the purpose of |
182: | this is returning a party_id which should be |
183: | stampled to fnd user. |

Line 180: | API to get a party before it creates a fnd user. |

176: | whether party id is already defined for the user |
177: | |
178: | It is possible that pv_user_name is not a valid |
179: | fnd user since the calling program may call this |
180: | API to get a party before it creates a fnd user. |
181: | We just ignore this case because the purpose of |
182: | this is returning a party_id which should be |
183: | stampled to fnd user. |
184: +--------------------------------------------------*/

Line 183: | stampled to fnd user. |

179: | fnd user since the calling program may call this |
180: | API to get a party before it creates a fnd user. |
181: | We just ignore this case because the purpose of |
182: | this is returning a party_id which should be |
183: | stampled to fnd user. |
184: +--------------------------------------------------*/
185: IF pv_user_name IS NOT NULL THEN
186:
187: OPEN user_cur(pv_user_name);

Line 208: | 2) Find a party from the per person_id in FND_USER |

204:
205: END IF;
206:
207: /*-----------------------------------------------------+
208: | 2) Find a party from the per person_id in FND_USER |
209: | |
210: | A party may be already created for the person |
211: | since a per person is allowed to have multiple |
212: | fnd users. |

Line 212: | fnd users. |

208: | 2) Find a party from the per person_id in FND_USER |
209: | |
210: | A party may be already created for the person |
211: | since a per person is allowed to have multiple |
212: | fnd users. |
213: | |
214: | For now we rely on the ORIG_SYSTEM_REFERENCE in |
215: | HZ_PARTIES to link to PER_ALL_PEOPLE_F |
216: | |

Line 446: | the fnd users that are already assigned a per_all_people.

442: | DESCRIPTION
443: | Create a party for a per_all_people_f person if it has not
444: | already created. The concept here is that we believe that
445: | HR person is more reliable resource than email_address for
446: | the fnd users that are already assigned a per_all_people.
447: |
448: | We will use the first name and last name from the HR table,
449: | and use 'PER:' + person_id as orig system reference
450: | so we can use Party Merge to merge this party created from