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 80: FROM hz_parties pp

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

Line 97: hz_parties party

93: SELECT party.party_id,
94: party.party_type,
95: party.status
96: FROM hz_contact_points cp,
97: hz_parties party
98: WHERE upper(cp.email_address) = UPPER(l_email_address)
99: AND cp.owner_table_name = 'HZ_PARTIES'
100: AND party.party_id = cp.owner_table_id
101: AND party.party_type = 'PERSON'

Line 99: AND cp.owner_table_name = 'HZ_PARTIES'

95: party.status
96: FROM hz_contact_points cp,
97: hz_parties party
98: WHERE upper(cp.email_address) = UPPER(l_email_address)
99: AND cp.owner_table_name = 'HZ_PARTIES'
100: AND party.party_id = cp.owner_table_id
101: AND party.party_type = 'PERSON'
102: AND party.status NOT IN ('M','D','I');
103:

Line 115: hz_parties per

111: per.party_type,
112: per.status
113: FROM hz_contact_points cp,
114: hz_relationships rel,
115: hz_parties per
116: WHERE upper(cp.email_address) = UPPER(l_email_address)
117: AND rel.party_id = cp.owner_table_id
118: AND cp.owner_table_name = 'HZ_PARTIES'
119: AND rel.subject_id = per.party_id

Line 118: AND cp.owner_table_name = 'HZ_PARTIES'

114: hz_relationships rel,
115: hz_parties per
116: WHERE upper(cp.email_address) = UPPER(l_email_address)
117: AND rel.party_id = cp.owner_table_id
118: AND cp.owner_table_name = 'HZ_PARTIES'
119: AND rel.subject_id = per.party_id
120: AND per.party_type = 'PERSON'
121: AND rel.directional_flag = 'F'
122: AND rel.subject_table_name = 'HZ_PARTIES'

Line 122: AND rel.subject_table_name = 'HZ_PARTIES'

118: AND cp.owner_table_name = 'HZ_PARTIES'
119: AND rel.subject_id = per.party_id
120: AND per.party_type = 'PERSON'
121: AND rel.directional_flag = 'F'
122: AND rel.subject_table_name = 'HZ_PARTIES'
123: AND rel.object_table_name = 'HZ_PARTIES'
124: AND rel.status NOT IN ('M','D','I');
125:
126: user_rec user_cur%ROWTYPE;

Line 123: AND rel.object_table_name = 'HZ_PARTIES'

119: AND rel.subject_id = per.party_id
120: AND per.party_type = 'PERSON'
121: AND rel.directional_flag = 'F'
122: AND rel.subject_table_name = 'HZ_PARTIES'
123: AND rel.object_table_name = 'HZ_PARTIES'
124: AND rel.status NOT IN ('M','D','I');
125:
126: user_rec user_cur%ROWTYPE;
127: per_person_party_rec per_person_party_cur%ROWTYPE;

Line 136: lv_subject_party_number hz_parties.party_number%TYPE;

132: par_rec hz_party_v2pub.party_rec_type;
133: cpoint_rec hz_contact_point_v2pub.contact_point_rec_type;
134: email_rec hz_contact_point_v2pub.email_rec_type;
135:
136: lv_subject_party_number hz_parties.party_number%TYPE;
137: ln_subject_party_id hz_parties.party_id%TYPE;
138: ln_contact_point_id hz_contact_points.contact_point_id%TYPE;
139:
140: ln_profile_id NUMBER;

Line 137: ln_subject_party_id hz_parties.party_id%TYPE;

133: cpoint_rec hz_contact_point_v2pub.contact_point_rec_type;
134: email_rec hz_contact_point_v2pub.email_rec_type;
135:
136: lv_subject_party_number hz_parties.party_number%TYPE;
137: ln_subject_party_id hz_parties.party_id%TYPE;
138: ln_contact_point_id hz_contact_points.contact_point_id%TYPE;
139:
140: ln_profile_id NUMBER;
141: ln_party_id NUMBER;

Line 195: | HZ_PARTIES to link to PER_ALL_PEOPLE_F |

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

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

347: AND pv_email_address IS NOT NULL) THEN
348:
349: cpoint_rec.contact_point_type := 'EMAIL';
350: cpoint_rec.status := 'A';
351: cpoint_rec.owner_table_name := 'HZ_PARTIES';
352: cpoint_rec.owner_table_id := ln_subject_party_id;
353: cpoint_rec.primary_flag := 'Y';
354: email_rec.email_address := pv_email_address;
355:

Line 484: l_party_number hz_parties.party_number%TYPE;

480: l_return_status VARCHAR2(1) := FND_API.G_RET_STS_SUCCESS;
481: l_msg_count NUMBER;
482: l_msg_data VARCHAR2(2000);
483: l_person_party_id NUMBER;
484: l_party_number hz_parties.party_number%TYPE;
485: l_person_profile_id NUMBER;
486: l_contact_point_id NUMBER;
487: l_generate_party_number VARCHAR2(1);
488:

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

553: IS NOT NULL) THEN
554:
555: cpoint_rec.contact_point_type := 'EMAIL';
556: cpoint_rec.status := 'A';
557: cpoint_rec.owner_table_name := 'HZ_PARTIES';
558: cpoint_rec.owner_table_id := l_person_party_id;
559: cpoint_rec.primary_flag := 'Y';
560: email_rec.email_address := per_person_rec.email_address;
561: