APPS.JTF_FM_PARTY_MERGE_PKG dependencies on JTF_FM_CONTENT_HISTORY

Line 75: -- In the case of JTF_FM_CONTENT_HISTORY table, if party id 1000 got merged to party id 2000

71: -- dependent record exists on the new parent. If a duplicate exists then do
72: -- not transfer and return the id of the duplicate record as the Merged To Id
73:
74:
75: -- In the case of JTF_FM_CONTENT_HISTORY table, if party id 1000 got merged to party id 2000
76: -- then, we have to update all records with customer_id = 1000 to 2000
77:
78: if p_from_fk_id <> p_to_fk_id then
79: begin

Line 108: update JTF_FM_CONTENT_HISTORY

104: last_updated_by = hz_utility_pub.user_id,
105: last_update_login = hz_utility_pub.last_update_login
106: where party_id = p_from_fk_id;
107: ELSE
108: update JTF_FM_CONTENT_HISTORY
109: set party_id = p_to_fk_id,
110: party_name = l_party_name,
111: last_update_date = hz_utility_pub.last_update_date,
112: last_updated_by = hz_utility_pub.user_id,