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_DNB_HIERARCHY_PVT dependencies on HZ_RELATIONSHIP_V2PUB

Line 779: p_relationship_rec HZ_RELATIONSHIP_V2PUB.RELATIONSHIP_REC_TYPE;

775: (p_subject_id NUMBER, p_object_id NUMBER, p_relationship_code VARCHAR2, p_start_date DATE)
776: RETURN NUMBER
777: IS
778: /***** FOR CREATING RELATIONSHIPS **********/
779: p_relationship_rec HZ_RELATIONSHIP_V2PUB.RELATIONSHIP_REC_TYPE;
780: x_relationship_id NUMBER;
781: x_party_id NUMBER;
782: x_party_number VARCHAR2(2000);
783: x_return_status VARCHAR2(2000);

Line 808: hz_relationship_v2pub.create_relationship('T',p_relationship_rec,

804: -- TRYING TO CREATE, DOES NOT EXIST ALREADY UNDER THE 'DNB_HIERARCHY'
805: -- RELATIONSHIP TYPE
806: IF relationship_exists( p_subject_id, p_object_id, p_relationship_code, 'DNB_HIERARCHY' ) = 'N'
807: THEN
808: hz_relationship_v2pub.create_relationship('T',p_relationship_rec,
809: x_relationship_id,x_party_id,x_party_number,x_return_status,x_msg_count,x_msg_data,'');
810: END IF;
811: return 0 ;
812: END create_rel ;

Line 829: p_relationship_rec HZ_RELATIONSHIP_V2PUB.RELATIONSHIP_REC_TYPE;

825: (p_subject_id NUMBER, p_object_id NUMBER, p_relationship_code VARCHAR2, p_start_date DATE)
826: RETURN NUMBER
827: IS
828: /***** FOR CREATING RELATIONSHIPS **********/
829: p_relationship_rec HZ_RELATIONSHIP_V2PUB.RELATIONSHIP_REC_TYPE;
830: x_relationship_id NUMBER;
831: x_party_id NUMBER;
832: x_party_number VARCHAR2(2000);
833: x_return_status VARCHAR2(2000);

Line 871: hz_relationship_v2pub.create_relationship('T',p_relationship_rec,

867: -- TRYING TO CREATE, DOES NOT EXIST ALREADY UNDER THE 'DNB_HIERARCHY'
868: -- RELATIONSHIP TYPE
869: IF relationship_exists( p_subject_id, p_object_id, p_relationship_code, 'DNB_HIERARCHY' ) = 'N'
870: THEN
871: hz_relationship_v2pub.create_relationship('T',p_relationship_rec,
872: x_relationship_id,x_party_id,x_party_number,x_return_status,x_msg_count,x_msg_data,'');
873: END IF;
874:
875:

Line 900: x_relationship_rec HZ_RELATIONSHIP_V2PUB.RELATIONSHIP_REC_TYPE;

896: -- end date relationship between two parties, by calling the update relationship API
897: (p_subject_id NUMBER, p_object_id NUMBER, p_relationship_code VARCHAR2 )
898: RETURN NUMBER
899: IS
900: x_relationship_rec HZ_RELATIONSHIP_V2PUB.RELATIONSHIP_REC_TYPE;
901: x_relationship_id NUMBER;
902: x_directional_flag VARCHAR2(1);
903: x_object_version_number NUMBER;
904: x_party_object_version_number NUMBER;

Line 921: hz_relationship_v2pub.get_relationship_rec ('T', x_relationship_id, x_directional_flag, x_relationship_rec,

917: AND object_table_name = 'HZ_PARTIES'
918: AND directional_flag = 'F';
919:
920: -- CALL THE GET RELATIONSHIP API TO GET THE CORRESPONDING RELATIONSHIP RECORD
921: hz_relationship_v2pub.get_relationship_rec ('T', x_relationship_id, x_directional_flag, x_relationship_rec,
922: x_return_status, x_msg_count, x_msg_data );
923: -- UPDATE THE CORRESPONDING RELATIONSHIP RECORD, BY END DATING IT AND CALLING THE UPDATE RELATIONSHIP API
924: x_relationship_rec.end_date := sysdate;
925: hz_relationship_v2pub.update_relationship ('T', x_relationship_rec,

Line 925: hz_relationship_v2pub.update_relationship ('T', x_relationship_rec,

921: hz_relationship_v2pub.get_relationship_rec ('T', x_relationship_id, x_directional_flag, x_relationship_rec,
922: x_return_status, x_msg_count, x_msg_data );
923: -- UPDATE THE CORRESPONDING RELATIONSHIP RECORD, BY END DATING IT AND CALLING THE UPDATE RELATIONSHIP API
924: x_relationship_rec.end_date := sysdate;
925: hz_relationship_v2pub.update_relationship ('T', x_relationship_rec,
926: x_object_version_number, x_party_object_version_number,x_return_status, x_msg_count, x_msg_data );
927: return 0;
928:
929: END end_date_rel ;