DBA Data[Home] [Help]

APPS.IGS_AD_IMP_008 dependencies on FND_LOOKUP_VALUES

Line 31: asbala 15-APR-2004 3349171: Incorrect usage of fnd_lookup_values view

27: gmaheswa 10-NOV-2003 Bug 3223043 HZ.K Impact changes
28: pkpatel 11-DEC-2003 Bug 3311720 (Added the Date validations in Relation Address processing)
29: gmaheswa 15-DEC-2003 Bug 3316838 Removed code related to date overlap under same employer or employer party number.
30: asbala 10-MAR-2004 Bug 3484532 (Removed the check for person already exists in HR. All check will happen from TCA)
31: asbala 15-APR-2004 3349171: Incorrect usage of fnd_lookup_values view
32: akadam.in 21-SEP-2004 Academic History LOV Build
33: skpandey 21-OCT-2004 Bug: 4691121
34: Description: Sync the changes made in version 115.124 from 115.123 which was mistakenly overridden by 115.125 version
35: pkpatel 17-Jan-2006 Bug 4937960 (R12: SWS Performance repository violation deliverables)

Line 112: || asbala 15-APR-2004 3349171: Incorrect usage of fnd_lookup_values view

108: || skpandey 21-SEP-2005 Bug: 3663505
109: || Description: Added ATTRIBUTES 21 TO 24 TO STORE ADDITIONAL INFORMATION
110: || pkpatel 15-APR-2002 Bug no.1834307 : Modified the Relationship_Type_C cursor to validate both Relationship_code and relationship_type
111: || asbala 12-nov-03 3227107: address changes - signature of igs_pe_person_addr_pkg.insert_row and update_row changed
112: || asbala 15-APR-2004 3349171: Incorrect usage of fnd_lookup_values view
113: || (reverse chronological order - newest change first)
114: */
115:
116: --1. Validate the RELATIONSHIP_TYPE and RELATIONSHIP_CODE -- ssawhney PE CCR 2203778

Line 119: CURSOR Relationship_Type_C(cp_lookup_type fnd_lookup_values.lookup_type%TYPE,

115:
116: --1. Validate the RELATIONSHIP_TYPE and RELATIONSHIP_CODE -- ssawhney PE CCR 2203778
117: -- OSS will not allow creation of relations between org and person through import process at this moment.
118:
119: CURSOR Relationship_Type_C(cp_lookup_type fnd_lookup_values.lookup_type%TYPE,
120: cp_subject_type hz_relationship_types.subject_type%TYPE,
121: cp_object_type hz_relationship_types.object_type%TYPE,
122: cp_appl_id fnd_lookup_values.view_application_id%TYPE,
123: cp_relationship_code P_Relations_Rec.Relationship_code%TYPE,

Line 122: cp_appl_id fnd_lookup_values.view_application_id%TYPE,

118:
119: CURSOR Relationship_Type_C(cp_lookup_type fnd_lookup_values.lookup_type%TYPE,
120: cp_subject_type hz_relationship_types.subject_type%TYPE,
121: cp_object_type hz_relationship_types.object_type%TYPE,
122: cp_appl_id fnd_lookup_values.view_application_id%TYPE,
123: cp_relationship_code P_Relations_Rec.Relationship_code%TYPE,
124: cp_relationship_type P_Relations_Rec.Relationship_type%TYPE,
125: cp_security_group_id fnd_lookup_values.security_group_id%TYPE) IS
126: SELECT COUNT(1)

Line 125: cp_security_group_id fnd_lookup_values.security_group_id%TYPE) IS

121: cp_object_type hz_relationship_types.object_type%TYPE,
122: cp_appl_id fnd_lookup_values.view_application_id%TYPE,
123: cp_relationship_code P_Relations_Rec.Relationship_code%TYPE,
124: cp_relationship_type P_Relations_Rec.Relationship_type%TYPE,
125: cp_security_group_id fnd_lookup_values.security_group_id%TYPE) IS
126: SELECT COUNT(1)
127: FROM FND_LOOKUP_VALUES lk, hz_relationship_types hz
128: WHERE hz.forward_rel_code= cp_relationship_code AND
129: hz.relationship_type = cp_relationship_type AND

Line 127: FROM FND_LOOKUP_VALUES lk, hz_relationship_types hz

123: cp_relationship_code P_Relations_Rec.Relationship_code%TYPE,
124: cp_relationship_type P_Relations_Rec.Relationship_type%TYPE,
125: cp_security_group_id fnd_lookup_values.security_group_id%TYPE) IS
126: SELECT COUNT(1)
127: FROM FND_LOOKUP_VALUES lk, hz_relationship_types hz
128: WHERE hz.forward_rel_code= cp_relationship_code AND
129: hz.relationship_type = cp_relationship_type AND
130: lk.LOOKUP_TYPE = cp_lookup_type AND
131: lk.lookup_code = hz.forward_rel_code AND