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.PON_TCA_MERGE_PVT dependencies on PON_ACKNOWLEDGEMENTS

Line 3076: -- merge for Sourcing PON_ACKNOWLEDGEMENTS entity.

3072: -- Pre-reqs : Responses with the given surrog_bid_ack_contact_id
3073: -- (p_From_FK_id) must exists in the database
3074: --
3075: -- Function : This procedure will be attached to the SURROG_BID_ACK_CONTACT_ID
3076: -- merge for Sourcing PON_ACKNOWLEDGEMENTS entity.
3077: --
3078: -- It will veto Party Merge if -
3079: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
3080: --

Line 3081: -- This will merge the all the PON_ACKNOWLEDGEMENTS records

3077: --
3078: -- It will veto Party Merge if -
3079: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
3080: --
3081: -- This will merge the all the PON_ACKNOWLEDGEMENTS records
3082: -- having SURROG_BID_ACK_CONTACT_ID equals to p_From_FK_id
3083: -- to party id having value (p_To_FK_id)
3084: --
3085: -- Parameters:

Line 3167: -- PON_ACKNOWLEDGEMENTS.SURROG_BID_ACK_CONTACT_ID

3163: fnd_file.put_line (fnd_file.log, '20 : Incompatible or Seller Merge - Error');
3164:
3165: --
3166: -- This can not happen in any normal scenario as
3167: -- PON_ACKNOWLEDGEMENTS.SURROG_BID_ACK_CONTACT_ID
3168: -- can never contain a seller user id. Thus, raising a veto though
3169: -- it will possibly never be called
3170: --
3171: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 3186: UPDATE PON_ACKNOWLEDGEMENTS

3182: --
3183: -- there is no chance of unique key constraint violation
3184: -- due to the following updates
3185: --
3186: UPDATE PON_ACKNOWLEDGEMENTS
3187: SET LAST_UPDATE_DATE = SYSDATE,
3188: LAST_UPDATED_BY = -1,
3189: SURROG_BID_ACK_CONTACT_ID = p_To_FK_id
3190: WHERE SURROG_BID_ACK_CONTACT_ID = p_From_FK_id;

Line 3192: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated SURROG_BID_ACK_CONTACT_IDs in PON_ACKNOWLEDGEMENTS: '||sql%rowcount||' rows');

3188: LAST_UPDATED_BY = -1,
3189: SURROG_BID_ACK_CONTACT_ID = p_To_FK_id
3190: WHERE SURROG_BID_ACK_CONTACT_ID = p_From_FK_id;
3191:
3192: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated SURROG_BID_ACK_CONTACT_IDs in PON_ACKNOWLEDGEMENTS: '||sql%rowcount||' rows');
3193:
3194: --
3195: -- We will be updating the user_id column of pon_neg_team_members table
3196: -- if there are only one FND_USER associated with the merge from ot merge to party id.

Line 4328: -- merge for Sourcing PON_ACKNOWLEDGEMENTS entity.

4324: -- Pre-reqs : Invitation Response with the given trading_partner_contact_id
4325: -- (p_From_FK_id) must exists in the database
4326: --
4327: -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
4328: -- merge for Sourcing PON_ACKNOWLEDGEMENTS entity.
4329: --
4330: -- It will veto Party Merge if -
4331: -- p_From_FK_id and p_To_FK_id both are not Seller user party
4332: --

Line 4333: -- This will merge the all the PON_ACKNOWLEDGEMENTS records

4329: --
4330: -- It will veto Party Merge if -
4331: -- p_From_FK_id and p_To_FK_id both are not Seller user party
4332: --
4333: -- This will merge the all the PON_ACKNOWLEDGEMENTS records
4334: -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
4335: -- to party id having value (p_To_FK_id)
4336: --
4337: -- Parameters:

Line 4418: -- PON_ACKNOWLEDGEMENTS.TRADING_PARTNER_CONTACT_ID

4414:
4415: fnd_file.put_line (fnd_file.log, '20 : Buyer or Incompatible Merge - Error');
4416: --
4417: -- This can not happen in any normal scenario as
4418: -- PON_ACKNOWLEDGEMENTS.TRADING_PARTNER_CONTACT_ID
4419: -- can never contain a buyer user id. Thus, raising a veto though
4420: -- it will possibly never be called
4421: --
4422: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 4432: -- clash in an auction_header_id (PON_ACKNOWLEDGEMENTS_U1 violation)

4428: fnd_file.put_line (fnd_file.log, '30 : Seller Merge ');
4429: --
4430: -- there is no chance of unique key constraint violation
4431: -- due to the following logic - trading_partner_contact_id should not
4432: -- clash in an auction_header_id (PON_ACKNOWLEDGEMENTS_U1 violation)
4433: --
4434: UPDATE PON_ACKNOWLEDGEMENTS pa
4435: SET pa.LAST_UPDATE_DATE = SYSDATE,
4436: pa.LAST_UPDATED_BY = -1,

Line 4434: UPDATE PON_ACKNOWLEDGEMENTS pa

4430: -- there is no chance of unique key constraint violation
4431: -- due to the following logic - trading_partner_contact_id should not
4432: -- clash in an auction_header_id (PON_ACKNOWLEDGEMENTS_U1 violation)
4433: --
4434: UPDATE PON_ACKNOWLEDGEMENTS pa
4435: SET pa.LAST_UPDATE_DATE = SYSDATE,
4436: pa.LAST_UPDATED_BY = -1,
4437: pa.TRADING_PARTNER_CONTACT_ID = p_To_FK_id
4438: WHERE pa.TRADING_PARTNER_CONTACT_ID = p_From_FK_id

Line 4440: FROM PON_ACKNOWLEDGEMENTS pa1

4436: pa.LAST_UPDATED_BY = -1,
4437: pa.TRADING_PARTNER_CONTACT_ID = p_To_FK_id
4438: WHERE pa.TRADING_PARTNER_CONTACT_ID = p_From_FK_id
4439: AND NOT EXISTS ( SELECT 'DUPLICATE'
4440: FROM PON_ACKNOWLEDGEMENTS pa1
4441: WHERE pa1.AUCTION_HEADER_ID = pa.AUCTION_HEADER_ID
4442: AND pa1.TRADING_PARTNER_CONTACT_ID = p_To_FK_id );
4443:
4444:

Line 4445: fnd_file.put_line (fnd_file.log, '50 : Seller Merge - Updated TRADING_PARTNER_CONTACT_IDs in PON_ACKNOWLEDGEMENTS: '||sql%rowcount||' rows');

4441: WHERE pa1.AUCTION_HEADER_ID = pa.AUCTION_HEADER_ID
4442: AND pa1.TRADING_PARTNER_CONTACT_ID = p_To_FK_id );
4443:
4444:
4445: fnd_file.put_line (fnd_file.log, '50 : Seller Merge - Updated TRADING_PARTNER_CONTACT_IDs in PON_ACKNOWLEDGEMENTS: '||sql%rowcount||' rows');
4446:
4447: ELSIF (l_merge_scenario = G_IRRELEVANT) THEN
4448: --
4449: -- Nothing to do