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.HZ_USER_PARTY_UTILS dependencies on HZ_PARTIES

Line 83: FROM hz_parties pp

79: +-----------------------------------------------------*/
80: CURSOR per_person_party_cur(l_per_person_id
81: per_all_people_f.person_id%TYPE) IS
82: /* SELECT pp.party_id
83: FROM hz_parties pp
84: , per_all_people_f per
85: WHERE pp.orig_system_reference = 'PER:'||per.person_id
86: AND per.person_id = l_per_person_id;
87: */

Line 96: FROM hz_parties pp,

92: WHERE person_id = l_per_person_id
93: AND party_id IS NOT NULL
94: UNION ALL
95: SELECT pp.party_id , '2-TCA' ORDER_BY_SOURCE , pp.last_update_date EFFECTIVE_DATE
96: FROM hz_parties pp,
97: per_all_people_f per
98: WHERE pp.orig_system_reference = 'PER:'||per.person_id
99: AND per.person_id = l_per_person_id
100: AND per.party_id IS NULL

Line 117: hz_parties party

113: SELECT party.party_id,
114: party.party_type,
115: party.status
116: FROM hz_contact_points cp,
117: hz_parties party
118: WHERE upper(cp.email_address) = UPPER(l_email_address)
119: AND cp.owner_table_name = 'HZ_PARTIES'
120: AND party.party_id = cp.owner_table_id
121: AND party.party_type = 'PERSON'

Line 119: AND cp.owner_table_name = 'HZ_PARTIES'

115: party.status
116: FROM hz_contact_points cp,
117: hz_parties party
118: WHERE upper(cp.email_address) = UPPER(l_email_address)
119: AND cp.owner_table_name = 'HZ_PARTIES'
120: AND party.party_id = cp.owner_table_id
121: AND party.party_type = 'PERSON'
122: AND party.status NOT IN ('M','D','I');
123:

Line 135: hz_parties per

131: per.party_type,
132: per.status
133: FROM hz_contact_points cp,
134: hz_relationships rel,
135: hz_parties per
136: WHERE upper(cp.email_address) = UPPER(l_email_address)
137: AND rel.party_id = cp.owner_table_id
138: AND cp.owner_table_name = 'HZ_PARTIES'
139: AND rel.subject_id = per.party_id

Line 138: AND cp.owner_table_name = 'HZ_PARTIES'

134: hz_relationships rel,
135: hz_parties per
136: WHERE upper(cp.email_address) = UPPER(l_email_address)
137: AND rel.party_id = cp.owner_table_id
138: AND cp.owner_table_name = 'HZ_PARTIES'
139: AND rel.subject_id = per.party_id
140: AND per.party_type = 'PERSON'
141: AND rel.directional_flag = 'F'
142: AND rel.subject_table_name = 'HZ_PARTIES'

Line 142: AND rel.subject_table_name = 'HZ_PARTIES'

138: AND cp.owner_table_name = 'HZ_PARTIES'
139: AND rel.subject_id = per.party_id
140: AND per.party_type = 'PERSON'
141: AND rel.directional_flag = 'F'
142: AND rel.subject_table_name = 'HZ_PARTIES'
143: AND rel.object_table_name = 'HZ_PARTIES'
144: AND rel.status NOT IN ('M','D','I');
145:
146: user_rec user_cur%ROWTYPE;

Line 143: AND rel.object_table_name = 'HZ_PARTIES'

139: AND rel.subject_id = per.party_id
140: AND per.party_type = 'PERSON'
141: AND rel.directional_flag = 'F'
142: AND rel.subject_table_name = 'HZ_PARTIES'
143: AND rel.object_table_name = 'HZ_PARTIES'
144: AND rel.status NOT IN ('M','D','I');
145:
146: user_rec user_cur%ROWTYPE;
147: per_person_party_rec per_person_party_cur%ROWTYPE;

Line 156: lv_subject_party_number hz_parties.party_number%TYPE;

152: par_rec hz_party_v2pub.party_rec_type;
153: cpoint_rec hz_contact_point_v2pub.contact_point_rec_type;
154: email_rec hz_contact_point_v2pub.email_rec_type;
155:
156: lv_subject_party_number hz_parties.party_number%TYPE;
157: ln_subject_party_id hz_parties.party_id%TYPE;
158: ln_contact_point_id hz_contact_points.contact_point_id%TYPE;
159:
160: ln_profile_id NUMBER;

Line 157: ln_subject_party_id hz_parties.party_id%TYPE;

153: cpoint_rec hz_contact_point_v2pub.contact_point_rec_type;
154: email_rec hz_contact_point_v2pub.email_rec_type;
155:
156: lv_subject_party_number hz_parties.party_number%TYPE;
157: ln_subject_party_id hz_parties.party_id%TYPE;
158: ln_contact_point_id hz_contact_points.contact_point_id%TYPE;
159:
160: ln_profile_id NUMBER;
161: ln_party_id NUMBER;

Line 215: | HZ_PARTIES to link to PER_ALL_PEOPLE_F |

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: | |
217: | After HR Merge into TCA, we should use the PARTY_ID |
218: | in PER_ALL_PEOPLE_F. Creating a Person Party |
219: | for a HR Person can be obsolete since a party will |

Line 371: cpoint_rec.owner_table_name := 'HZ_PARTIES';

367: AND pv_email_address IS NOT NULL) THEN
368:
369: cpoint_rec.contact_point_type := 'EMAIL';
370: cpoint_rec.status := 'A';
371: cpoint_rec.owner_table_name := 'HZ_PARTIES';
372: cpoint_rec.owner_table_id := ln_subject_party_id;
373: cpoint_rec.primary_flag := 'Y';
374: email_rec.email_address := pv_email_address;
375:

Line 504: l_party_number hz_parties.party_number%TYPE;

500: l_return_status VARCHAR2(1) := FND_API.G_RET_STS_SUCCESS;
501: l_msg_count NUMBER;
502: l_msg_data VARCHAR2(2000);
503: l_person_party_id NUMBER;
504: l_party_number hz_parties.party_number%TYPE;
505: l_person_profile_id NUMBER;
506: l_contact_point_id NUMBER;
507: l_generate_party_number VARCHAR2(1);
508:

Line 577: cpoint_rec.owner_table_name := 'HZ_PARTIES';

573: IS NOT NULL) THEN
574:
575: cpoint_rec.contact_point_type := 'EMAIL';
576: cpoint_rec.status := 'A';
577: cpoint_rec.owner_table_name := 'HZ_PARTIES';
578: cpoint_rec.owner_table_id := l_person_party_id;
579: cpoint_rec.primary_flag := 'Y';
580: email_rec.email_address := per_person_rec.email_address;
581: