APPS.PON_TCA_MERGE_PVT dependencies on PON_CONTRACTS

Line 2274: -- merge for Sourcing PON_CONTRACTS entity.

2270: -- Pre-reqs : Negotitions with the given authoring_party_contact_id
2271: -- (p_From_FK_id) must exists in the database
2272: --
2273: -- Function : This procedure will be attached to the AUTHORING_PARTY_CONTACT_ID
2274: -- merge for Sourcing PON_CONTRACTS entity.
2275: --
2276: -- It will veto Party Merge if -
2277: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
2278: --

Line 2279: -- This will merge the all the PON_CONTRACTS records

2275: --
2276: -- It will veto Party Merge if -
2277: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
2278: --
2279: -- This will merge the all the PON_CONTRACTS records
2280: -- having AUTHORING_PARTY_CONTACT_ID equals to p_From_FK_id
2281: -- to party id having value (p_To_FK_id)
2282: --
2283: -- Parameters:

Line 2364: -- PON_CONTRACTS.AUTHORING_PARTY_CONTACT_ID

2360:
2361: fnd_file.put_line (fnd_file.log, '20 : Seller Merge - Error');
2362: --
2363: -- This can not happen in any normal scenario as
2364: -- PON_CONTRACTS.AUTHORING_PARTY_CONTACT_ID
2365: -- can never contain a seller user id. Thus, raising a veto though
2366: -- it will possibly never be called
2367: --
2368: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 2383: UPDATE PON_CONTRACTS

2379: --
2380: -- there is no chance of unique key constraint violation
2381: -- due to the following updates
2382: --
2383: UPDATE PON_CONTRACTS
2384: SET LAST_UPDATE_DATE = SYSDATE,
2385: LAST_UPDATED_BY = -1,
2386: AUTHORING_PARTY_CONTACT_ID = p_To_FK_id
2387: WHERE AUTHORING_PARTY_CONTACT_ID = p_From_FK_id;

Line 2389: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated AUTHORING_PARTY_CONTACT_IDs in PON_CONTRACTS: '||sql%rowcount||' rows');

2385: LAST_UPDATED_BY = -1,
2386: AUTHORING_PARTY_CONTACT_ID = p_To_FK_id
2387: WHERE AUTHORING_PARTY_CONTACT_ID = p_From_FK_id;
2388:
2389: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated AUTHORING_PARTY_CONTACT_IDs in PON_CONTRACTS: '||sql%rowcount||' rows');
2390:
2391: --
2392: -- We will be updating the user_id column of pon_neg_team_members table
2393: -- if there are only one FND_USER associated with the merge from ot merge to party id.