APPS.HZ_REGISTRY_VALIDATE_V2PUB dependencies on HZ_RELATIONSHIP_TYPE_V2PUB

Line 11827: p_relationship_type_rec IN HZ_RELATIONSHIP_TYPE_V2PUB.RELATIONSHIP_TYPE_REC_TYPE,

11823: */
11824:
11825: PROCEDURE validate_relationship_type(
11826: p_create_update_flag IN VARCHAR2,
11827: p_relationship_type_rec IN HZ_RELATIONSHIP_TYPE_V2PUB.RELATIONSHIP_TYPE_REC_TYPE,
11828: p_rowid IN ROWID ,
11829: x_return_status IN OUT NOCOPY VARCHAR2
11830: ) IS
11831:

Line 13040: THE do_relationship_type IN HZ_RELATIONSHIP_TYPE_V2PUB WHICH

13036: SRANGARA AND RPITTS, THE CONCLUSION OF WHICH IS THAT
13037: NON_HIERARCHICAL RELATIONSHIPS DO NOT NEED ANY VALUE
13038: FOR MULTIPLE_PARENT_ALLOWED,SINCE EVEN A SINGLE PARENT
13039: DOES NOT MAKE SENSE FOR A NON_HIERARCHICAL RELATIONSHIP TYPE.
13040: THE do_relationship_type IN HZ_RELATIONSHIP_TYPE_V2PUB WHICH
13041: DEFAULTS THE VALUE OF THIS FLAG TO "Y" FOR NON_HIERARCHICAL
13042: REL TYPES SHOULD ALSO BE CHANGED IN THE FUTURE.
13043:
13044: ----- VJN

Line 13653: l_in := hz_relationship_type_v2pub.in_instance_sets (

13649: IF p_relationship_rec.subject_id IS NOT NULL
13650: AND p_relationship_rec.subject_id <> fnd_api.g_miss_num
13651: AND p_create_update_flag = 'C'
13652: THEN
13653: l_in := hz_relationship_type_v2pub.in_instance_sets (
13654: p_relationship_rec.subject_type,
13655: p_relationship_rec.subject_id
13656: );
13657:

Line 13907: l_in := hz_relationship_type_v2pub.in_instance_sets (

13903: IF p_relationship_rec.object_id IS NOT NULL
13904: AND p_relationship_rec.object_id <> fnd_api.g_miss_num
13905: AND p_create_update_flag = 'C'
13906: THEN
13907: l_in := hz_relationship_type_v2pub.in_instance_sets (
13908: p_relationship_rec.object_type,
13909: p_relationship_rec.object_id
13910: );
13911: