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_AUCTION_HEADERS_ALL

Line 665: -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.

661: -- Pre-reqs : Negotiation with the given trading_partner_contact_id
662: -- (p_From_FK_id) must exists in the database
663: --
664: -- Function : This procedure will be attached to the TRADING_PARTNER_CONTACT_ID
665: -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.
666: --
667: -- It will veto Party Merge if -
668: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
669: --

Line 670: -- This will merge the all the PON_AUCTION_HEADERS_ALL records

666: --
667: -- It will veto Party Merge if -
668: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
669: --
670: -- This will merge the all the PON_AUCTION_HEADERS_ALL records
671: -- having TRADING_PARTNER_CONTACT_ID equals to p_From_FK_id
672: -- to party id having value (p_To_FK_id)
673: --
674: -- Parameters:

Line 758: -- PON_AUCTION_HEADERS_ALL.TRADING_PARTNER_CONTACT_ID

754:
755: fnd_file.put_line (fnd_file.log, '20 : Seller Merge - Error');
756: --
757: -- This can not happen in any normal scenario as
758: -- PON_AUCTION_HEADERS_ALL.TRADING_PARTNER_CONTACT_ID
759: -- can never contain a seller user id. Thus, raising a veto though
760: -- it will possibly never be called
761: --
762: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 783: UPDATE PON_AUCTION_HEADERS_ALL

779: -- following SQLs will not be executed. Moreover,
780: -- there is no chance of unique key constraint violation
781: -- due to the following updates
782: --
783: UPDATE PON_AUCTION_HEADERS_ALL
784: SET TRADING_PARTNER_CONTACT_ID = p_To_FK_id,
785: LAST_UPDATE_DATE = SYSDATE,
786: LAST_UPDATED_BY = -1,
787: TRADING_PARTNER_CONTACT_NAME = l_user_name

Line 790: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated TPC IDs in PON_AUCTION_HEADERS_ALL: '||sql%rowcount||' rows');

786: LAST_UPDATED_BY = -1,
787: TRADING_PARTNER_CONTACT_NAME = l_user_name
788: WHERE TRADING_PARTNER_CONTACT_ID = p_From_FK_id;
789:
790: fnd_file.put_line (fnd_file.log, '50 : Buyer Merge - Updated TPC IDs in PON_AUCTION_HEADERS_ALL: '||sql%rowcount||' rows');
791:
792: UPDATE PON_DISCUSSIONS
793: SET OWNER_PARTY_ID = p_To_FK_id,
794: LAST_UPDATE_DATE = SYSDATE

Line 842: -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.

838: -- Pre-reqs : Negotiation with the given draft_locked_by_contact_id
839: -- (p_From_FK_id) must exists in the database
840: --
841: -- Function : This procedure will be attached to the DRAFT_LOCKED_BY_CONTACT_ID
842: -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.
843: --
844: -- It will veto Party Merge if -
845: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
846: --

Line 847: -- This will merge the all the PON_AUCTION_HEADERS_ALL records

843: --
844: -- It will veto Party Merge if -
845: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
846: --
847: -- This will merge the all the PON_AUCTION_HEADERS_ALL records
848: -- having DRAFT_LOCKED_BY_CONTACT_ID equals to p_From_FK_id
849: -- to party id having value (p_To_FK_id)
850: --
851: -- Parameters:

Line 932: -- PON_AUCTION_HEADERS_ALL.DRAFT_LOCKED_BY_CONTACT_ID

928:
929: fnd_file.put_line (fnd_file.log, '20 : Seller or Incompatible Merge - Error');
930: --
931: -- This can not happen in any normal scenario as
932: -- PON_AUCTION_HEADERS_ALL.DRAFT_LOCKED_BY_CONTACT_ID
933: -- can never contain a seller user id. Thus, raising a veto though
934: -- it will possibly never be called
935: --
936: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 950: UPDATE PON_AUCTION_HEADERS_ALL

946: --
947: -- there is no chance of unique key constraint violation
948: -- due to the following updates
949: --
950: UPDATE PON_AUCTION_HEADERS_ALL
951: SET LAST_UPDATE_DATE = SYSDATE,
952: LAST_UPDATED_BY = -1,
953: DRAFT_LOCKED_BY_CONTACT_ID = p_To_FK_id
954: WHERE DRAFT_LOCKED_BY_CONTACT_ID = p_From_FK_id;

Line 956: fnd_file.put_line (fnd_file.log, '40 : Buyer Merge - Updated DRAFT_LOCKED_BY_CONTACT_IDs in PON_AUCTION_HEADERS_ALL: '||sql%rowcount||' rows');

952: LAST_UPDATED_BY = -1,
953: DRAFT_LOCKED_BY_CONTACT_ID = p_To_FK_id
954: WHERE DRAFT_LOCKED_BY_CONTACT_ID = p_From_FK_id;
955:
956: fnd_file.put_line (fnd_file.log, '40 : Buyer Merge - Updated DRAFT_LOCKED_BY_CONTACT_IDs in PON_AUCTION_HEADERS_ALL: '||sql%rowcount||' rows');
957:
958: --
959: -- We will be updating the user_id column of pon_neg_team_members table
960: -- if there are only one FND_USER associated with the merge from ot merge to party id.

Line 1001: -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.

997: -- Pre-reqs : Negotiation with the given draft_unlocked_by_contact_id
998: -- (p_From_FK_id) must exists in the database
999: --
1000: -- Function : This procedure will be attached to the DRAFT_UNLOCKED_BY_CONTACT_ID
1001: -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.
1002: --
1003: -- It will veto Party Merge if -
1004: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1005: --

Line 1006: -- This will merge the all the PON_AUCTION_HEADERS_ALL records

1002: --
1003: -- It will veto Party Merge if -
1004: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1005: --
1006: -- This will merge the all the PON_AUCTION_HEADERS_ALL records
1007: -- having DRAFT_UNLOCKED_BY_CONTACT_ID equals to p_From_FK_id
1008: -- to party id having value (p_To_FK_id)
1009: --
1010: -- Parameters:

Line 1092: -- PON_AUCTION_HEADERS_ALL.DRAFT_UNLOCKED_BY_CONTACT_ID

1088: fnd_file.put_line (fnd_file.log, '20 : Seller or Incompatible Merge - Error');
1089:
1090: --
1091: -- This can not happen in any normal scenario as
1092: -- PON_AUCTION_HEADERS_ALL.DRAFT_UNLOCKED_BY_CONTACT_ID
1093: -- can never contain a seller user id. Thus, raising a veto though
1094: -- it will possibly never be called
1095: --
1096: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 1112: UPDATE PON_AUCTION_HEADERS_ALL

1108: --
1109: -- there is no chance of unique key constraint violation
1110: -- due to the following updates
1111: --
1112: UPDATE PON_AUCTION_HEADERS_ALL
1113: SET LAST_UPDATE_DATE = SYSDATE,
1114: LAST_UPDATED_BY = -1,
1115: DRAFT_UNLOCKED_BY_CONTACT_ID = p_To_FK_id
1116: WHERE DRAFT_UNLOCKED_BY_CONTACT_ID = p_From_FK_id;

Line 1118: fnd_file.put_line (fnd_file.log, '40 : Buyer Merge - Updated DRAFT_UNLOCKED_BY_CONTACT_IDs in PON_AUCTION_HEADERS_ALL: '||sql%rowcount||' rows');

1114: LAST_UPDATED_BY = -1,
1115: DRAFT_UNLOCKED_BY_CONTACT_ID = p_To_FK_id
1116: WHERE DRAFT_UNLOCKED_BY_CONTACT_ID = p_From_FK_id;
1117:
1118: fnd_file.put_line (fnd_file.log, '40 : Buyer Merge - Updated DRAFT_UNLOCKED_BY_CONTACT_IDs in PON_AUCTION_HEADERS_ALL: '||sql%rowcount||' rows');
1119:
1120: --
1121: -- We will be updating the user_id column of pon_neg_team_members table
1122: -- if there are only one FND_USER associated with the merge from ot merge to party id.

Line 1165: -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.

1161: -- Pre-reqs : Negotiation with the given scoring_lock_tp_contact_id
1162: -- (p_From_FK_id) must exists in the database
1163: --
1164: -- Function : This procedure will be attached to the SCORING_LOCK_TP_CONTACT_ID
1165: -- merge for Sourcing PON_AUCTION_HEADERS_ALL entity.
1166: --
1167: -- It will veto Party Merge if -
1168: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1169: --

Line 1170: -- This will merge the all the PON_AUCTION_HEADERS_ALL records

1166: --
1167: -- It will veto Party Merge if -
1168: -- p_From_FK_id and p_To_FK_id both are not Buyer user party
1169: --
1170: -- This will merge the all the PON_AUCTION_HEADERS_ALL records
1171: -- having SCORING_LOCK_TP_CONTACT_ID equals to p_From_FK_id
1172: -- to party id having value (p_To_FK_id)
1173: --
1174: -- Parameters:

Line 1256: -- PON_AUCTION_HEADERS_ALL.SCORING_LOCK_TP_CONTACT_ID

1252: fnd_file.put_line (fnd_file.log, '20 : Seller Merge - Error');
1253:
1254: --
1255: -- This can not happen in any normal scenario as
1256: -- PON_AUCTION_HEADERS_ALL.SCORING_LOCK_TP_CONTACT_ID
1257: -- can never contain a seller user id. Thus, raising a veto though
1258: -- it will possibly never be called
1259: --
1260: FND_MESSAGE.SET_NAME('AR', 'PON_TCA_MRG_ERR'); -- Need to put some Sourcing Specific Error Message

Line 1274: UPDATE PON_AUCTION_HEADERS_ALL

1270: --
1271: -- there is no chance of unique key constraint violation
1272: -- due to the following updates
1273: --
1274: UPDATE PON_AUCTION_HEADERS_ALL
1275: SET LAST_UPDATE_DATE = SYSDATE,
1276: LAST_UPDATED_BY = -1,
1277: SCORING_LOCK_TP_CONTACT_ID = p_To_FK_id
1278: WHERE SCORING_LOCK_TP_CONTACT_ID = p_From_FK_id;

Line 1280: fnd_file.put_line (fnd_file.log, '40 : Buyer Merge - Updated SCORING_LOCK_TP_CONTACT_IDs in PON_AUCTION_HEADERS_ALL: '||sql%rowcount||' rows');

1276: LAST_UPDATED_BY = -1,
1277: SCORING_LOCK_TP_CONTACT_ID = p_To_FK_id
1278: WHERE SCORING_LOCK_TP_CONTACT_ID = p_From_FK_id;
1279:
1280: fnd_file.put_line (fnd_file.log, '40 : Buyer Merge - Updated SCORING_LOCK_TP_CONTACT_IDs in PON_AUCTION_HEADERS_ALL: '||sql%rowcount||' rows');
1281:
1282: --
1283: -- We will be updating the user_id column of pon_neg_team_members table
1284: -- if there are only one FND_USER associated with the merge from ot merge to party id.