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 153: | 1) Find a party from FND_USER |

149:
150: BEGIN
151:
152: /*--------------------------------------------------+
153: | 1) Find a party from FND_USER |
154: | |
155: | If username was passed in, fetch it and check |
156: | whether party id is already defined for the user |
157: | |

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

155: | If username was passed in, fetch it and check |
156: | whether party id is already defined for the user |
157: | |
158: | It is possible that pv_user_name is not a valid |
159: | fnd user since the calling program may call this |
160: | API to get a party before it creates a fnd user. |
161: | We just ignore this case because the purpose of |
162: | this is returning a party_id which should be |
163: | stampled to fnd user. |

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

156: | whether party id is already defined for the user |
157: | |
158: | It is possible that pv_user_name is not a valid |
159: | fnd user since the calling program may call this |
160: | API to get a party before it creates a fnd user. |
161: | We just ignore this case because the purpose of |
162: | this is returning a party_id which should be |
163: | stampled to fnd user. |
164: +--------------------------------------------------*/

Line 163: | stampled to fnd user. |

159: | fnd user since the calling program may call this |
160: | API to get a party before it creates a fnd user. |
161: | We just ignore this case because the purpose of |
162: | this is returning a party_id which should be |
163: | stampled to fnd user. |
164: +--------------------------------------------------*/
165: IF pv_user_name IS NOT NULL THEN
166:
167: OPEN user_cur(pv_user_name);

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

184:
185: END IF;
186:
187: /*-----------------------------------------------------+
188: | 2) Find a party from the per person_id in FND_USER |
189: | |
190: | A party may be already created for the person |
191: | since a per person is allowed to have multiple |
192: | fnd users. |

Line 192: | fnd users. |

188: | 2) Find a party from the per person_id in FND_USER |
189: | |
190: | A party may be already created for the person |
191: | since a per person is allowed to have multiple |
192: | fnd users. |
193: | |
194: | For now we rely on the ORIG_SYSTEM_REFERENCE in |
195: | HZ_PARTIES to link to PER_ALL_PEOPLE_F |
196: | |

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

422: | DESCRIPTION
423: | Create a party for a per_all_people_f person if it has not
424: | already created. The concept here is that we believe that
425: | HR person is more reliable resource than email_address for
426: | the fnd users that are already assigned a per_all_people.
427: |
428: | We will use the first name and last name from the HR table,
429: | and use 'PER:' + person_id as orig system reference
430: | so we can use Party Merge to merge this party created from