APPS.HZ_REGISTRY_VALIDATE_V2PUB dependencies on HZ_RELATIONSHIP_TYPE_V2PUB

Line 11817: p_relationship_type_rec IN HZ_RELATIONSHIP_TYPE_V2PUB.RELATIONSHIP_TYPE_REC_TYPE,

11813: */
11814:
11815: PROCEDURE validate_relationship_type(
11816: p_create_update_flag IN VARCHAR2,
11817: p_relationship_type_rec IN HZ_RELATIONSHIP_TYPE_V2PUB.RELATIONSHIP_TYPE_REC_TYPE,
11818: p_rowid IN ROWID ,
11819: x_return_status IN OUT NOCOPY VARCHAR2
11820: ) IS
11821:

Line 13030: THE do_relationship_type IN HZ_RELATIONSHIP_TYPE_V2PUB WHICH

13026: SRANGARA AND RPITTS, THE CONCLUSION OF WHICH IS THAT
13027: NON_HIERARCHICAL RELATIONSHIPS DO NOT NEED ANY VALUE
13028: FOR MULTIPLE_PARENT_ALLOWED,SINCE EVEN A SINGLE PARENT
13029: DOES NOT MAKE SENSE FOR A NON_HIERARCHICAL RELATIONSHIP TYPE.
13030: THE do_relationship_type IN HZ_RELATIONSHIP_TYPE_V2PUB WHICH
13031: DEFAULTS THE VALUE OF THIS FLAG TO "Y" FOR NON_HIERARCHICAL
13032: REL TYPES SHOULD ALSO BE CHANGED IN THE FUTURE.
13033:
13034: ----- VJN

Line 13643: l_in := hz_relationship_type_v2pub.in_instance_sets (

13639: IF p_relationship_rec.subject_id IS NOT NULL
13640: AND p_relationship_rec.subject_id <> fnd_api.g_miss_num
13641: AND p_create_update_flag = 'C'
13642: THEN
13643: l_in := hz_relationship_type_v2pub.in_instance_sets (
13644: p_relationship_rec.subject_type,
13645: p_relationship_rec.subject_id
13646: );
13647:

Line 13897: l_in := hz_relationship_type_v2pub.in_instance_sets (

13893: IF p_relationship_rec.object_id IS NOT NULL
13894: AND p_relationship_rec.object_id <> fnd_api.g_miss_num
13895: AND p_create_update_flag = 'C'
13896: THEN
13897: l_in := hz_relationship_type_v2pub.in_instance_sets (
13898: p_relationship_rec.object_type,
13899: p_relationship_rec.object_id
13900: );
13901: